Re: FC4 Slow System

[Bob Chiodini <rchiodin@xxxxxxxxxxxxx>]

On Thu, 2005-12-29 at 19:11 +0100, Jeremy Thompson wrote:
> 
> 
> On 12/29/05, Jeremy Thompson <jeremy.a.thompson+fedoralist@xxxxxxxxx>
> wrote:
>         
>         
>         On 12/29/05, Jeremy Thompson <jeremy.a.thompson
>         +fedoralist@xxxxxxxxx> wrote:
>                 
>                 
>                 On 12/29/05, Bob Chiodini <rchiodin@xxxxxxxxxxxxx>
>                 wrote:
>                         On Thu, 2005-12-29 at 17:43 +0100, Jeremy
>                         Thompson wrote:
>                         > All,
>                         >   Just built a Fedora System to act as a
>                         PVR.  But it is running so
>                         > slow.  Takes almost a minute to open a
>                         terminal window.  It's a P4 
>                         > 2.4Ghz with a Gig of mem, so it should be a
>                         problem.  Currently it's
>                         > showing syslogd, and klogd each taking
>                         20~24% of the CPU cycle.  I
>                         > haven't had this problem before so I can't
>                         tell if this is a problem 
>                         > or not.
>                         >
>                         >   I tried searching google and the archives,
>                         but it didn't help much.
>                         > Most replies were to FC1&2 from years ago.
>                         >
>                         >   If someone could point me in the right
>                         direction I would appreciate 
>                         > it.
>                         >
>                         >   Thank you,
>                         >
>                         > JT
>                         
>                         
>                         JT,
>                         
>                         Is anything getting logged?  Presumably
>                         syslogd and klogd are doing
>                         something.
>                         
>                         Bob...
>                 
>                 
>                 Yeah,
>                   That would be something to check.. I'm such a
>                 newb...
>                 
>                 checking on klogd, did the following - 
>                 from 
>                 /proc
>                 [root@mythtv proc]# cat kmsg   
>                 <7>cx88[0]: irq pci [0x8000] ipb_dma_err*
>                 
>                 and checking
>                 /var/log
>                 [root@mythtv log]# cat messages 
>                 Dec 29 18:28:50 mythtv kernel: : irq pci [0x8000]
>                 ipb_dma_err*
>                 
>                   Of course these messages were spammed like crazy.
>                 
>                   I am going to google these errors and search
>                 archives.  If you find anything of interest let me
>                 know, as I will reply to this if I find anything.
>                 
>                   On a side note, thanks.  I have already learned a
>                 lot, I have never checked logs before... so I had to
>                 find them first!
>                 
>                 JT
>                 
>                 
>                 
>         Ok,
>           I haven't been able to find anything.  Searched the
>         following - 
>         
>         Google
>         "ipb_dma_err* site:http://mythtv.org/pipermail/mythtv-users/";
>         
>         Since it's a mythtv system I am trying to build.
>         
>         "irq pci [0x8000] ipb_dma_err*
>         site:https://www.redhat.com/archives/fedora-list/";
>         
>         On Google Linux Search
>         "irq pci [0x8000] ipb_dma_err" and various iterations.
>         However all I get are kernel mailing list patch notices, or
>         nothing. 
>         
>         Seems it's a PCI DMA error?  
>         
>         I am starting to lean towards a problem with one of the cards
>         I have installed, just cause I can't think of anything else.
>         Currently I have the following - 
>         
>         [root@mythtv proc]# cat pci
>         PCI devices found:
>           Bus  0, device   0, function  0:
>             Class 0600: PCI device 8086:2560 (rev 3).
>               Prefetchable 32 bit memory at 0xf0000000 [0xf7ffffff].
>           Bus  0, device   1, function  0:
>             Class 0604: PCI device 8086:2561 (rev 3).
>               Master Capable.  Latency=64.  Min Gnt=8.
>           Bus  0, device  29, function  0:
>             Class 0c03: PCI device 8086:24c2 (rev 2).
>               IRQ 11.
>               I/O at 0xd800 [0xd81f].
>           Bus  0, device  29, function  1:
>             Class 0c03: PCI device 8086:24c4 (rev 2).
>               IRQ 4.
>               I/O at 0xd400 [0xd41f].
>           Bus  0, device  29, function  2:
>             Class 0c03: PCI device 8086:24c7 (rev 2).
>               IRQ 10.
>               I/O at 0xd000 [0xd01f].
>           Bus  0, device  29, function  7:
>             Class 0c03: PCI device 8086:24cd (rev 2).
>               IRQ 10.
>               Non-prefetchable 32 bit memory at 0xe5800000
>         [0xe58003ff].
>           Bus  0, device  30, function  0:
>             Class 0604: PCI device 8086:244e (rev 130).
>               Master Capable.  No bursts.  Min Gnt=6.
>           Bus  0, device  31, function  0:
>             Class 0601: PCI device 8086:24c0 (rev 2).
>           Bus  0, device  31, function  1:
>             Class 0101: PCI device 8086:24cb (rev 2).
>               IRQ 10.
>               I/O at 0xf000 [0xf00f].
>               Non-prefetchable 32 bit memory at 0x30000000
>         [0x300003ff].
>           Bus  0, device  31, function  3:
>             Class 0c05: PCI device 8086:24c3 (rev 2).
>               I/O at 0xe800 [0xe81f].
>           Bus  1, device   0, function  0:
>             Class 0300: PCI device 10de:0171 (rev 163).
>               IRQ 11.
>               Master Capable.  Latency=248.  Min Gnt=5.Max Lat=1.
>               Non-prefetchable 32 bit memory at 0xe6000000
>         [0xe6ffffff].
>               Prefetchable 32 bit memory at 0xe8000000 [0xefffffff].
>               Prefetchable 32 bit memory at 0xe7800000 [0xe787ffff].
>           Bus  2, device   8, function  0:
>             Class 0200: PCI device 8086:103a (rev 130).
>               IRQ 11.
>               Master Capable.  Latency=32.  Min Gnt=8.Max Lat=56.
>               Non-prefetchable 32 bit memory at 0xe5000000
>         [0xe5000fff].
>               I/O at 0xb800 [0xb83f].
>           Bus  2, device  10, function  0:
>             Class 0401: PCI device 1102:0004 (rev 4).
>               IRQ 11.
>               Master Capable.  Latency=32.  Min Gnt=2.Max Lat=20.
>               I/O at 0xb400 [0xb43f].
>           Bus  2, device  10, function  1:
>             Class 0980: PCI device 1102:7003 (rev 4).
>               Master Capable.  Latency=32.
>               I/O at 0xb000 [0xb007].
>           Bus  2, device  10, function  2:
>             Class 0c00: PCI device 1102:4001 (rev 4).
>               IRQ 10.
>               Master Capable.  Latency=32.  Min Gnt=2.Max Lat=4.
>               Non-prefetchable 32 bit memory at 0xe4800000
>         [0xe48007ff].
>               Non-prefetchable 32 bit memory at 0xe4000000
>         [0xe4003fff].
>           Bus  2, device  11, function  0:
>             Class 0400: PCI device 14f1:8800 (rev 5).
>               IRQ 10.
>               Master Capable.  Latency=32.  Min Gnt=20.Max Lat=55.
>               Non-prefetchable 32 bit memory at 0xe3000000
>         [0xe3ffffff].
>           Bus  2, device  11, function  2:
>             Class 0480: PCI device 14f1:8802 (rev 5).
>               IRQ 10.
>               Master Capable.  Latency=32.  Min Gnt=6.Max Lat=88.
>               Non-prefetchable 32 bit memory at 0xe2000000
>         [0xe2ffffff].
>         
>         did a cat pci | grep 0x8000, but got nothing.
>         
>         I don't know how to get the output of the KinfoCenter,
>         otherwise I would paste that as well.  Checking the interrupts
>         I get - 
>         
>         [root@mythtv proc]# cat interrupts
>                    CPU0
>           0:     799753          XT-PIC  timer
>           1:       4063          XT-PIC  i8042
>           2:          0          XT-PIC  cascade
>           4:      81187          XT-PIC  uhci_hcd:usb3
>           8:          1          XT-PIC  rtc
>           9:          1          XT-PIC  acpi
>          10:   90662208          XT-PIC  cx88[0], cx88[0],
>         ehci_hcd:usb1, uhci_hcd:usb4, ohci1394
>          11:     198655          XT-PIC  EMU10K1, uhci_hcd:usb2, eth0,
>         nvidia
>          12:        104          XT-PIC  i8042
>          14:     270969          XT-PIC  ide0
>          15:     227687          XT-PIC  ide1
>         NMI:          0
>         ERR:          1
>          
>         also, 
>         
>         root@mythtv proc]# cat dma
>          4: cascade
>         
>         not sure what to do past this.  Thanks.
>         
>         JT
> 
> Bob,
>   I haven't started config on mythtv  yet.  It takes forever for
> Firefox to start, I couldn't imagine mythtv doing much better.
> 
>   I assume by buffer card you mean the capture card I have?  It's a
> PCHDTV HD3000 card.  The guidance I have found states the drivers are
> in the kernel.
> 
>   If you think moving it'll help let me know.
> 
> JT
> 
> 
> 
JT,

I've heard that too, about the drivers.  lspci -vv will give you a
little more detail about the devices.  How many capture cards do you
have?

It looks like the interrupt from the capture card is shared with your
USB and Firewire interfaces.  Is there any thing on those interfaces
that might be very active, like a disk?

Have you searched pchdtv.com?  There is a forum, but I did not see
anything in particular, but it was just a quick look.  I did notice that
their is apparently downloadable firmware for the 3000.

Are you specifying any special boot parameters to the kernel like
noacpi?

Bob...