SMP HT + USB2.0 crash

SMP HT + USB2.0 crash

[davor emard]

HI

I have an asus MB with intel 925XE chipset and hyperthreading capable CPU.
Certain lockups with random oops occur all through kernel 2.6.16.19. Some of
lockups are SMP only oopses (sorry but I didn't catch them exactly to a file),
other are usually like this attached file

As a general rule, if both
1) SMP
2) EHCI (usb 2.0)

Are enabled and USB2.0 devices are used frequently, then
kernel lockup appear between few minutes and 1 day. It is very annoying

Disabling either SMP or the EHCI fixes the lockups. Probably some
missing spin_lock or whatever in EHCI...

Emard

SMP HT + USB2.0 crash

[davor emard]

[-- Attachment #1: Type: text/plain, Size: 37 bytes --]

Usually SMP + EHCI crashes like this

[-- Attachment #2: crash2.syslog --]
[-- Type: text/plain, Size: 3343 bytes --]

Apr 13 00:49:00 localhost kernel: Unable to handle kernel paging request at virtual address 1359024b
Apr 13 00:49:00 localhost kernel:  printing eip:
Apr 13 00:49:00 localhost kernel: c013c633
Apr 13 00:49:00 localhost kernel: *pde = 00000000
Apr 13 00:49:00 localhost kernel: Oops: 0002 [#1]
Apr 13 00:49:00 localhost kernel: PREEMPT SMP 
Apr 13 00:49:00 localhost kernel: Modules linked in: police sch_ingress cls_u32 sch_sfq sch_cbq pppoe pppox rfcomm l2cap lp thermal fan button processor ac battery ppp_generic slhc dv1394 raw1394 w83627ehf hwmon i2c_isa uinput nvram ircomm_tty ircomm stir4200 irda vfat fat db9 saa7134_alsa eeprom nvidia pl2303 usbserial usbhid usblp eth1394 dvb_usb_a800 dvb_usb_dibusb_common dib3000mc dib3000_common dvb_usb dvb_pll hci_usb bluetooth tuner snd_mpu401 8250_pnp snd_mpu401_uart 8250 serial_core snd_rawmidi snd_hda_intel saa7134 ir_kbd_i2c ir_common serio_raw snd_seq_device pcspkr dvb_ttpci l64781 saa7146_vv video_buf saa7146 v4l1_compat v4l2_common videodev ves1820 stv0299 dvb_core tda8083 stv0297 sp8870 ves1x93 snd_hda_codec parport_pc parport rtc ohci1394 ieee1394 ttpci_eeprom i2c_i801 snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd ehci_hcd snd_page_alloc uhci_hcd ide_cd cdrom
Apr 13 00:49:00 localhost kernel: CPU:    1
Apr 13 00:49:00 localhost kernel: EIP:    0060:[free_block+57/183]    Tainted: P      VLI
Apr 13 00:49:00 localhost kernel: EFLAGS: 00210002   (2.6.15.7) 
Apr 13 00:49:00 localhost kernel: EIP is at free_block+0x39/0xb7
Apr 13 00:49:00 localhost kernel: eax: 87be9624   ebx: dc6b7000   ecx: dc6b76f8   edx: 13590247
Apr 13 00:49:00 localhost kernel: esi: f792bfc0   edi: f7f20840   ebp: 00000008   esp: f7c8ff14
Apr 13 00:49:00 localhost kernel: ds: 007b   es: 007b   ss: 0068
Apr 13 00:49:00 localhost kernel: Process events/1 (pid: 9, threadinfo=f7c8c000 task=f7c64a30)
Apr 13 00:49:00 localhost kernel: Stack: f7fbe618 00000018 f7fbe600 00000000 c013ce68 f7f20840 f7fbe618 00000018 
Apr 13 00:49:00 localhost kernel:        00000000 f7f20840 f792bf50 f792bfc0 f7f20840 00000001 c013cefb f7f20840 
Apr 13 00:49:00 localhost kernel:        f7fbe600 00000000 00000000 f792bfe8 f7f20898 c1712120 f7c081c0 c1712124 
Apr 13 00:49:00 localhost kernel: Call Trace:
Apr 13 00:49:00 localhost kernel:  [drain_array_locked+98/140] drain_array_locked+0x62/0x8c
Apr 13 00:49:00 localhost kernel:  [cache_reap+105/372] cache_reap+0x69/0x174
Apr 13 00:49:00 localhost kernel:  [worker_thread+342/452] worker_thread+0x156/0x1c4
Apr 13 00:49:00 localhost kernel:  [cache_reap+0/372] cache_reap+0x0/0x174
Apr 13 00:49:00 localhost kernel:  [default_wake_function+0/18] default_wake_function+0x0/0x12
Apr 13 00:49:00 localhost kernel:  [worker_thread+0/452] worker_thread+0x0/0x1c4
Apr 13 00:49:00 localhost kernel:  [kthread+114/159] kthread+0x72/0x9f
Apr 13 00:49:00 localhost kernel:  [kthread+0/159] kthread+0x0/0x9f
Apr 13 00:49:00 localhost kernel:  [kernel_thread_helper+5/11] kernel_thread_helper+0x5/0xb
Apr 13 00:49:00 localhost kernel: Code: 00 8b 44 24 18 8b 0c a8 8d 81 00 00 00 40 c1 e8 0c c1 e0 05 8b 15 10 e2 4f c0 8b 5c 10 1c 8b 44 24 20 8b 74 87 18 8b 13 8b 43 04 <89> 42 04 89 10 c7 03 00 01 10 00 c7 43 04 00 02 20 00 2b 4b 0c 
Apr 13 00:49:00 localhost kernel:  <6>note: events/1[9] exited with preempt_count 1
Apr 13 00:52:11 localhost syslogd 1.4.1#17: restart.

Re: SMP HT + USB2.0 crash

[Con Kolivas]

On Sunday 04 June 2006 20:22, davor emard wrote:
> Usually SMP + EHCI crashes like this

Unless you can reproduce your crash without binary only drivers such as the 
nvidia one your bug report cannot be acted upon.

-- 
-ck

Re: SMP HT + USB2.0 crash

[davor emard]

I tested this _A_LOT_ and it doesn't matter if I
use "nvidia" binary drivers or x.org's free "nv" or
have just a text console with no X at all.
It happens on a production machine :(

Most easily to trigger this bug is to use USB2.0 epson
scanner over and have scanbuttond running - it will poll
scan buttons via usb2.0 and crash

On 6/4/06, Con Kolivas <kernel@kolivas.org> wrote:
> On Sunday 04 June 2006 20:22, davor emard wrote:
> > Usually SMP + EHCI crashes like this
>
> Unless you can reproduce your crash without binary only drivers such as the
> nvidia one your bug report cannot be acted upon.
>
> --
> -ck
>

Re: SMP HT + USB2.0 crash

[Olaf Hering]

 On Sun, Jun 04, davor emard wrote:

> It happens on a production machine :(

Either hire a professional sysadmin, or disable CONFIG_PREEMPT

Re: SMP HT + USB2.0 crash

[davor emard]

I tested it with kernel 2.6.15.7 with nvidia
7174 drivers from which syslog's this oops capture
probably came from but the same thing but less frequently
happens with kernel 2.6.16.19 without nvidia drivers
(nvidia 7174 can't be compiled for 2.6.16.19).

For 2.6.15.7 it takes 2-10 minutes to crash, while for 2.6.16.19
it takes 1-2 days to crash. Yes it is more stable.
Usually it reports the similar oops like I supplied, but sometimes
also 2.6.16.19 reports SMP type crash - sorry I didn't have serial
console connected and didn't write it down - it looks different than
usual oops, contains less registers and no call traces showing
where in the source it crashed (I have never seen such oops before).

2.6.16.19 was running in console only mode and only with
drivers shipped in kernel. No external binary for nvidia, no
external source for ethernet. As the crash location report was
not indicatve to which module caused it, I was removing
one by one suspect module (dvb, firewire ethernet etc) and
reinserting them again until I narrowed it down to the
combination of SMP and EHCI that caused the crash.
Removing either of them makes the machine stable


On 6/4/06, davor emard <davoremard@gmail.com> wrote:
> I tested this _A_LOT_ and it doesn't matter if I
> use "nvidia" binary drivers or x.org's free "nv" or
> have just a text console with no X at all.
> It happens on a production machine :(
>
> Most easily to trigger this bug is to use USB2.0 epson
> scanner over and have scanbuttond running - it will poll
> scan buttons via usb2.0 and crash
>
> On 6/4/06, Con Kolivas <kernel@kolivas.org> wrote:
> > On Sunday 04 June 2006 20:22, davor emard wrote:
> > > Usually SMP + EHCI crashes like this
> >
> > Unless you can reproduce your crash without binary only drivers such as
> the
> > nvidia one your bug report cannot be acted upon.
> >
> > --
> > -ck
> >
>

Re: SMP HT + USB2.0 crash

[davor emard]

> Either hire a professional sysadmin, or disable CONFIG_PREEMPT
>

I tried it also with SMP enabled and disabled PREEMPT and
big kernel lock preempt - it also crashes.

So there's no need for a yet more professional sysadmin I guess.

Try it yourself on your machine if you have handy some intel 925X series
to crash.
I did it on 2 asus p5ad2-e premium boards, they both crash the same way.

Re: SMP HT + USB2.0 crash

[Alistair John Strachan]

On Sunday 04 June 2006 11:22, davor emard wrote:
> Usually SMP + EHCI crashes like this

Please attach another log without NVIDIA ever having being loaded. This is a 
technical forum, we need precise facts "nvidia has not been loaded", not 
vague recollections "nvidia probably wasn't loaded some time before".

Secondly, I highly recommend running memtest86 on your system for at least a 
couple of passes. You can download an ISO from the homepage and boot it from 
a CD. If this fails, you have faulty memory.

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

Re: SMP HT + USB2.0 crash

[davor emard]

On 6/4/06, Alistair John Strachan <s0348365@sms.ed.ac.uk> wrote:
> On Sunday 04 June 2006 11:22, davor emard wrote:
> > Usually SMP + EHCI crashes like this
>
> Please attach another log without NVIDIA ever having being loaded. This is a
> technical forum, we need precise facts "nvidia has not been loaded", not
> vague recollections "nvidia probably wasn't loaded some time before".
>
> Secondly, I highly recommend running memtest86 on your system for at least a
> couple of passes. You can download an ISO from the homepage and boot it from
> a CD. If this fails, you have faulty memory.
>
> --
> Cheers,
> Alistair.
>
> Third year Computer Science undergraduate.
> 1F2 55 South Clerk Street, Edinburgh, UK.
>

Re: SMP HT + USB2.0 crash

[davor emard]

> Please attach another log without NVIDIA ever having being loaded. This is a
> technical forum, we need precise facts "nvidia has not been loaded", not
> vague recollections "nvidia probably wasn't loaded some time before".

that's not just a vague recollection: nvidia 7174 from debian's nvidia
legacy source
could not be even compiled and therefore also was certainly
not loaded for 2.6.16.19. But for this special occasion I am going to
reproduce this sucker on 2.6.16.19 once again with quite minimal
stuff compiled in. I can even connect serial cable and get a laptop
capture the bloody oops just to find out which kernel boot option is
for serial console :(

> Secondly, I highly recommend running memtest86 on your system for at least a
> couple of passes. You can download an ISO from the homepage and boot it from
> a CD. If this fails, you have faulty memory.

hmm I don't know why I didn't use memtest86. but I usually test memory on
new machine linux, by continuously gzip-ing and ungzip-ing
4GB file for 2 days and verify if the beginning
and the end file  are the same memory, CPU and a bit of
hardware handling them together should be good...

Re: SMP HT + USB2.0 crash

[Alistair John Strachan]

On Sunday 04 June 2006 17:23, davor emard wrote:
[snip]
> > Secondly, I highly recommend running memtest86 on your system for at
> > least a couple of passes. You can download an ISO from the homepage and
> > boot it from a CD. If this fails, you have faulty memory.
>
> hmm I don't know why I didn't use memtest86. but I usually test memory on
> new machine linux, by continuously gzip-ing and ungzip-ing
> 4GB file for 2 days and verify if the beginning
> and the end file  are the same memory, CPU and a bit of
> hardware handling them together should be good...

The reason I'm suggesting memtest86, is that it can detect very subtle errors 
(gzip will not do this). The crash you're experiencing is in core kernel 
code, and it is very unlikely to be a real bug.

This is why Con and myself have suggested to reproduce without the binary 
junk, and why bad memory could be a very probable cause.

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

Re: SMP HT + USB2.0 crash

[Lee Revell]

On Sun, 2006-06-04 at 16:54 +0200, Olaf Hering wrote:
>  On Sun, Jun 04, davor emard wrote:
> 
> > It happens on a production machine :(
> 
> Either hire a professional sysadmin, or disable CONFIG_PREEMPT

Um, he said "production machine" not "web server".  There are lots of
applications that require preemption.

Lee

Re: SMP HT + USB2.0 crash

[davor emard]

[-- Attachment #1: Type: text/plain, Size: 697 bytes --]

HI

Due to popular demand I'm mailing the recent crash
captured with serial cable on 2.6.16.19 on intel 925X
triggered with SMP + USB2.0 combination.

Here we got it, it's pretty random and useless for
tracking the real problem so please don't blame
software demux in DVB core just becaise it randomly
crashed there - only thing that matters is that a800
terrestroal receiver was running in USB 2.0 mode in
order to generate enough usb2.0 traffic
to trigger SMP+EHCI bug.

I contributed myself to the dvb software demux code
and it runs stable with it's demux core part almost
unchanged for 2 years.

If I remove EHCI and run a800 in USB 1.1 mode everything
can run stable for any amount of time.

[-- Attachment #2: crashreport.usb20 --]
[-- Type: text/plain, Size: 27240 bytes --]

Linux version 2.6.16.19-crash (root@emard) (gcc version 4.0.4 20060507 (prerelease) (Debian 4.0.3-3)) #1 SMP Sun Jun 4 23:45:30 CEST 2006
\rBIOS-provided physical RAM map:
\r BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
\r BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
\r BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
\r BIOS-e820: 0000000000100000 - 000000003ffb0000 (usable)
\r BIOS-e820: 000000003ffb0000 - 000000003ffbe000 (ACPI data)
\r BIOS-e820: 000000003ffbe000 - 000000003fff0000 (ACPI NVS)
\r BIOS-e820: 000000003fff0000 - 0000000040000000 (reserved)
\r BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
\r1023MB LOWMEM available.
\rfound SMP MP-table at 000ff780
\rDMI 2.3 present.
\rACPI: PM-Timer IO Port: 0x808
\rACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
\rProcessor #0 15:3 APIC version 20
\rACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
\rProcessor #1 15:3 APIC version 20
\rACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
\rIOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
\rACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
\rACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
\rACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
\rACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
\rEnabling APIC mode:  Flat.  Using 1 I/O APICs
\rUsing ACPI (MADT) for SMP configuration information
\rAllocating PCI resources starting at 50000000 (gap: 40000000:bfb00000)
\rBuilt 1 zonelists
\rKernel command line: root=/dev/hde5 ro acpi=strict console=ttyS0,115200 console=tty0
\rEnabling fast FPU save and restore... done.
\rEnabling unmasked SIMD FPU exception support... done.
\rInitializing CPU#0
\rPID hash table entries: 4096 (order: 12, 65536 bytes)
\rDetected 3212.965 MHz processor.
\rUsing pmtmr for high-res timesource
\rConsole: colour VGA+ 80x25
\rDentry cache hash table entries: 262144 (order: 8, 1048576 bytes)
\rInode-cache hash table entries: 131072 (order: 7, 524288 bytes)
\rMemory: 1033848k/1048256k available (2615k kernel code, 13852k reserved, 888k data, 208k init, 0k highmem)
\rChecking if this processor honours the WP bit even in supervisor mode... Ok.
\rCalibrating delay using timer specific routine.. 6431.93 BogoMIPS (lpj=3215968)
\rMount-cache hash table entries: 512
\rmonitor/mwait feature present.
\rusing mwait in idle threads.
\rCPU: Trace cache: 12K uops, L1 D cache: 16K
\rCPU: L2 cache: 1024K
\rCPU: Physical Processor ID: 0
\rIntel machine check architecture supported.
\rIntel machine check reporting enabled on CPU#0.
\rCPU0: Intel P4/Xeon Extended MCE MSRs (12) available
\rCPU0: Thermal monitoring enabled
\rChecking 'hlt' instruction... OK.
\rCPU0: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 04
\rBooting processor 1/1 eip 2000
\rInitializing CPU#1
\rCalibrating delay using timer specific routine.. 6421.83 BogoMIPS (lpj=3210918)
\rmonitor/mwait feature present.
\rCPU: Trace cache: 12K uops, L1 D cache: 16K
\rCPU: L2 cache: 1024K
\rCPU: Physical Processor ID: 0
\rIntel machine check architecture supported.
\rIntel machine check reporting enabled on CPU#1.
\rCPU1: Intel P4/Xeon Extended MCE MSRs (12) available
\rCPU1: Thermal monitoring enabled
\rCPU1: Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 04
\rTotal of 2 processors activated (12853.77 BogoMIPS).
\rENABLING IO-APIC IRQs
\r..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
\rchecking TSC synchronization across 2 CPUs: passed.
\rBrought up 2 CPUs
\rmigration_cost=1000
\rNET: Registered protocol family 16
\rACPI: bus type pci registered
\rPCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=5
\rPCI: Using MMCONFIG
\rACPI: Subsystem revision 20060127
\rACPI: Interpreter enabled
\rACPI: Using IOAPIC for interrupt routing
\rACPI: PCI Root Bridge [PCI0] (0000:00)
\rPCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
\rPCI: Transparent bridge - 0000:00:1e.0
\rACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
\rACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
\rACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
\rACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
\rACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 *11 12 14 15)
\rACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 *5 6 7 10 11 12 14 15)
\rACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
\rACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15)
\rLinux Plug and Play Support v0.97 (c) Adam Belay
\rpnp: PnP ACPI init
\rpnp: PnP ACPI: found 18 devices
\rSCSI subsystem initialized
\rusbcore: registered new driver usbfs
\rusbcore: registered new driver hub
\rPCI: Using ACPI for IRQ routing
\rPCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
\rTC classifier action (bugs to netdev@vger.kernel.org cc hadi@cyberus.ca)
\rpnp: 00:08: ioport range 0x290-0x297 has been reserved
\rPCI: Bridge: 0000:00:01.0
\r  IO window: e000-efff
\r  MEM window: cdf00000-cfffffff
\r  PREFETCH window: d0000000-dfffffff
\rPCI: Bridge: 0000:00:1c.0
\r  IO window: d000-dfff
\r  MEM window: disabled.
\r  PREFETCH window: disabled.
\rPCI: Bridge: 0000:00:1c.1
\r  IO window: c000-cfff
\r  MEM window: cde00000-cdefffff
\r  PREFETCH window: disabled.
\rPCI: Bridge: 0000:00:1c.2
\r  IO window: b000-bfff
\r  MEM window: cdd00000-cddfffff
\r  PREFETCH window: disabled.
\rPCI: Bridge: 0000:00:1e.0
\r  IO window: 9000-afff
\r  MEM window: cdc00000-cdcfffff
\r  PREFETCH window: 50000000-500fffff
\rACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
\rACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
\rACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
\rACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
\rMachine check exception polling timer started.
\rIA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
\rInstalling knfsd (copyright (C) 1996 okir@monad.swb.de).
\rSGI XFS with ACLs, security attributes, no debug enabled
\rSGI XFS Quota Management subsystem
\rInitializing Cryptographic API
\rio scheduler noop registered
\rio scheduler anticipatory registered (default)
\rio scheduler deadline registered
\rio scheduler cfq registered
\rACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 16
\rassign_interrupt_mode Found MSI capability
\rACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
\rassign_interrupt_mode Found MSI capability
\rACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 17 (level, low) -> IRQ 17
\rassign_interrupt_mode Found MSI capability
\rACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 18
\rassign_interrupt_mode Found MSI capability
\rpci_hotplug: PCI Hot Plug PCI Core version: 0.5
\risapnp: Scanning for PnP cards...
\risapnp: No Plug & Play device found
\rPNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
\rPNP: PS/2 controller doesn't have AUX irq; using default 12
\rserio: i8042 AUX port at 0x60,0x64 irq 12
\rserio: i8042 KBD port at 0x60,0x64 irq 1
\rSerial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
\rserial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
\r00:0e: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
\rFloppy drive(s): fd0 is 1.44M
\rFDC 0 is a post-1991 82077
\rRAMDISK driver initialized: 16 RAM disks of 32768K size 1024 blocksize
\rloop: loaded (max 8 devices)
\rUniform Multi-Platform E-IDE driver Revision: 7.00alpha2
\ride: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
\rICH6: IDE controller at PCI slot 0000:00:1f.1
\rACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
\rICH6: chipset revision 4
\rICH6: not 100% native mode: will probe irqs later
\r    ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
\r    ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
\rhda: HL-DT-ST DVDRAM GSA-4167B, ATAPI CD/DVD-ROM drive
\rhdb: PIONEER DVD-RW DVR-108, ATAPI CD/DVD-ROM drive
\ride0 at 0x1f0-0x1f7,0x3f6 on irq 14
\rIT8212: IDE controller at PCI slot 0000:01:04.0
\rACPI: PCI Interrupt 0000:01:04.0[A] -> GSI 23 (level, low) -> IRQ 19
\rIT8212: chipset revision 19
\rit821x: controller in smart mode.
\rIT8212: 100% native mode on irq 19
\r    ide2: BM-DMA at 0x9400-0x9407, BIOS settings: hde:DMA, hdf:pio
\r    ide3: BM-DMA at 0x9408-0x940f, BIOS settings: hdg:pio, hdh:pio
\rhde: Integrated Technology Express Inc, ATA DISK drive
\rhde: IT8212 RAID 1 volume.
\ride2 at 0xa800-0xa807,0xa402 on irq 19
\rhde: max request size: 128KiB
\rhde: 160836478 sectors (82348 MB), CHS=10011/255/63
\rhde: cache flushes not supported
\r hde: hde1 hde2 hde3 < hde5 hde6 >
\rACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 20
\rahci 0000:00:1f.2: AHCI 0001.0000 32 slots 4 ports 1.5 Gbps 0xf impl IDE mode
\rahci 0000:00:1f.2: flags: 64bit ncq pm led slum part 
\rata1: SATA max UDMA/133 cmd 0xF0806D00 ctl 0x0 bmdma 0x0 irq 20
\rata2: SATA max UDMA/133 cmd 0xF0806D80 ctl 0x0 bmdma 0x0 irq 20
\rata3: SATA max UDMA/133 cmd 0xF0806E00 ctl 0x0 bmdma 0x0 irq 20
\rata4: SATA max UDMA/133 cmd 0xF0806E80 ctl 0x0 bmdma 0x0 irq 20
\rata1: SATA link down (SStatus 0)
\rscsi0 : ahci
\rata2: SATA link up 1.5 Gbps (SStatus 113)
\rata2: dev 0 ATA-6, max UDMA/100, 241254720 sectors: LBA48
\rata2: dev 0 configured for UDMA/100
\rscsi1 : ahci
\rata3: SATA link down (SStatus 0)
\rscsi2 : ahci
\rata4: SATA link down (SStatus 0)
\rscsi3 : ahci
\r  Vendor: ATA       Model: HDS722512VLSA80   Rev: V33O
\r  Type:   Direct-Access                      ANSI SCSI revision: 05
\rSCSI device sda: 241254720 512-byte hdwr sectors (123522 MB)
\rsda: Write Protect is off
\rSCSI device sda: drive cache: write back
\rSCSI device sda: 241254720 512-byte hdwr sectors (123522 MB)
\rsda: Write Protect is off
\rSCSI device sda: drive cache: write back
\r sda: sda1 sda2
\rsd 1:0:0:0: Attached scsi disk sda
\rusbmon: debugfs is not available
\rInitializing USB Mass Storage driver...
\rusbcore: registered new driver usb-storage
\rUSB Mass Storage support registered.
\rmice: PS/2 mouse device common for all mice
\rmd: raid1 personality registered for level 1
\rmd: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
\rmd: bitmap version 4.39
\rdevice-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
\rNET: Registered protocol family 2
\rIP route cache hash table entries: 65536 (order: 6, 262144 bytes)
\rTCP established hash table entries: 262144 (order: 9, 2097152 bytes)
\rTCP bind hash table entries: 65536 (order: 7, 524288 bytes)
\rinput: AT Translated Set 2 keyboard as /class/input/input0
\rTCP: Hash tables configured (established 262144 bind 65536)
\rTCP reno registered
\rip_conntrack version 2.4 (8189 buckets, 65512 max) - 228 bytes per conntrack
\rNET: Registered protocol family 1
\rNET: Registered protocol family 17
\rNET: Registered protocol family 15
\rStarting balanced_irq
\rUsing IPI Shortcut mode
\rmd: Autodetecting RAID arrays.
\rmd: autorun ...
\rmd: ... autorun DONE.
\rReiserFS: hde5: found reiserfs format "3.6" with standard journal
\rReiserFS: hde5: using ordered data mode
\rReiserFS: hde5: journal params: device hde5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
\rReiserFS: hde5: checking transaction log (hde5)
\rReiserFS: hde5: Using r5 hash to sort names
\rVFS: Mounted root (reiserfs filesystem) readonly.
\rFreeing unused kernel memory: 208k freed
\rhda: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache, UDMA(33)
\rUniform CD-ROM driver Revision: 3.20
\rhdb: ATAPI 40X DVD-ROM DVD-R CD-R/RW drive, 2000kB Cache, UDMA(66)
\rUSB Universal Host Controller Interface driver v2.3
\rACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 19
\ruhci_hcd 0000:00:1d.0: UHCI Host Controller
\ruhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
\ruhci_hcd 0000:00:1d.0: irq 19, io base 0x00006000
\rusb usb1: configuration #1 chosen from 1 choice
\rhub 1-0:1.0: USB hub found
\rhub 1-0:1.0: 2 ports detected
\rACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 20
\ruhci_hcd 0000:00:1d.1: UHCI Host Controller
\ruhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
\ruhci_hcd 0000:00:1d.1: irq 20, io base 0x00006400
\rusb usb2: configuration #1 chosen from 1 choice
\rhub 2-0:1.0: USB hub found
\rhub 2-0:1.0: 2 ports detected
\rACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
\ruhci_hcd 0000:00:1d.2: UHCI Host Controller
\ruhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
\ruhci_hcd 0000:00:1d.2: irq 18, io base 0x00006800
\rusb usb3: configuration #1 chosen from 1 choice
\rhub 3-0:1.0: USB hub found
\rhub 3-0:1.0: 2 ports detected
\rusb 1-1: new full speed USB device using uhci_hcd and address 2
\rACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
\ruhci_hcd 0000:00:1d.3: UHCI Host Controller
\ruhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
\ruhci_hcd 0000:00:1d.3: irq 16, io base 0x00007000
\rusb usb4: configuration #1 chosen from 1 choice
\rhub 4-0:1.0: USB hub found
\rhub 4-0:1.0: 2 ports detected
\rACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 19
\rehci_hcd 0000:00:1d.7: EHCI Host Controller
\rehci_hcd 0000:00:1d.7: debug port 1
\rehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
\rusb 1-1: configuration #1 chosen from 1 choice
\rehci_hcd 0000:00:1d.7: irq 19, io mem 0xcdbff800
\rehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
\rusb usb5: configuration #1 chosen from 1 choice
\rhub 5-0:1.0: USB hub found
\rhub 5-0:1.0: 8 ports detected
\rparport: PnPBIOS parport detected.
\rparport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
\rACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 17
\rsky2 v0.15 addr 0xcdefc000 irq 17 Yukon-EC (0xb6) rev 1
\rsky2 eth0: addr 00:11:d8:13:c8:04
\rACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 18
\rsky2 v0.15 addr 0xcddfc000 irq 18 Yukon-EC (0xb6) rev 1
\rsky2 eth1: addr 00:11:d8:13:c5:48
\rACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
\rReal Time Clock Driver v1.12ac
\rinput: PC Speaker as /class/input/input1
\rusb 1-1: USB disconnect, address 2
\rLinux video capture interface: v1.00
\rsaa7146: register extension 'dvb'.
\rACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 21
\rsaa7146: found saa7146 @ mem f09b6c00 (revision 1, irq 21) (0x13c2,0x0000).
\rsaa7130/34: v4l2 driver version 0.2.14 loaded
\rusb 5-2: new high speed USB device using ehci_hcd and address 3
\rusb 5-2: configuration #1 chosen from 1 choice
\rusb 5-3: new high speed USB device using ehci_hcd and address 4
\rusb 5-3: configuration #1 chosen from 1 choice
\rusb 5-4: new high speed USB device using ehci_hcd and address 5
\rusb 5-4: configuration #1 chosen from 1 choice
\rhub 5-4:1.0: USB hub found
\rhub 5-4:1.0: 3 ports detected
\rusb 1-1: new full speed USB device using uhci_hcd and address 3
\rusb 1-1: configuration #1 chosen from 1 choice
\rusb 5-4.3: new full speed USB device using ehci_hcd and address 8
\rusb 5-4.3: configuration #1 chosen from 1 choice
\rusb 4-1: new full speed USB device using uhci_hcd and address 2
\rDVB: registering new adapter (Technotrend/Hauppauge WinTV DVB-S rev1.X or Fujitsu Siemens DVB-C).
\radapter has MAC addr = 00:d0:5c:00:9d:9a
\rBluetooth: Core ver 2.8
\rNET: Registered protocol family 31
\rBluetooth: HCI device and connection manager initialized
\rBluetooth: HCI socket layer initialized
\rhci_usb: Unknown symbol hci_free_dev
\rhci_usb: Unknown symbol hci_alloc_dev
\rhci_usb: Unknown symbol hci_unregister_dev
\rhci_usb: Unknown symbol hci_register_dev
\rBluetooth: HCI USB driver ver 2.9
\rdvb-ttpci: gpioirq unknown type=0 len=0
\rdvb-ttpci: info @ card 0: firm f0240009, rtsl b0250018, vid 71010068, app 80002622
\rdvb-ttpci: firmware @ card 0 supports CI link layer interface
\rusb 4-1: configuration #1 chosen from 1 choice
\rusb 4-2: new full speed USB device using uhci_hcd and address 3
\rdvb-ttpci: adac type set to 0 @ card 0
\rsaa7146_vv: saa7146 (0): registered device video0 [v4l2]
\rsaa7146_vv: saa7146 (0): registered device vbi0 [v4l2]
\rves1x93: Detected ves1893a rev2
\rDVB: registering frontend 0 (VLSI VES1x93 DVB-S)...
\rinput: DVB on-card IR receiver as /class/input/input2
\rdvb-ttpci: found av7110-0.
\rACPI: PCI Interrupt 0000:01:09.0[A] -> GSI 17 (level, low) -> IRQ 17
\rsaa7134[0]: found at 0000:01:09.0, rev: 1, irq: 17, latency: 64, mmio: 0xcdcff800
\rsaa7134[0]: subsystem: 5168:0138, board: LifeView FlyVIDEO3000 [card=2,autodetected]
\rsaa7134[0]: board init: gpio is 39000
\rsaa7134[0]: there are different flyvideo cards with different tuners
\rsaa7134[0]: out there, you might have to use the tuner=<nr> insmod
\rsaa7134[0]: option to override the default value.
\rinput: saa7134 IR (LifeView FlyVIDEO30 as /class/input/input3
\rusb 4-2: configuration #1 chosen from 1 choice
\rusbcore: registered new driver usbserial
\rdrivers/usb/serial/usb-serial.c: USB Serial Driver core
\rdvb-usb: found a 'AVerMedia AverTV DVB-T USB 2.0 (A800)' in warm state.
\rdvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
\rDVB: registering new adapter (AVerMedia AverTV DVB-T USB 2.0 (A800)).
\rdrivers/usb/serial/usb-serial.c: USB Serial support registered for pl2303
\rdib3000: Found a DiBcom 3000P.
\rDVB: registering frontend 1 (DiBcom 3000P/M-C DVB-T)...
\rinput: IR-receiver inside an USB DVB receiver as /class/input/input4
\rdvb-usb: schedule remote query interval to 150 msecs.
\rdvb-usb: AVerMedia AverTV DVB-T USB 2.0 (A800) successfully initialized and connected.
\rusbcore: registered new driver hci_usb
\rpl2303 1-1:1.0: pl2303 converter detected
\rusb 1-1: pl2303 converter now attached to ttyUSB0
\rusbcore: registered new driver pl2303
\rdrivers/usb/serial/pl2303.c: Prolific PL2303 USB to serial adaptor driver
\rusbcore: registered new driver dvb_usb_a800
\rsaa7134[0]: i2c eeprom 00: 68 51 38 01 10 28 ff ff ff ff ff ff ff ff ff ff
\rsaa7134[0]: i2c eeprom 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
\rsaa7134[0]: i2c eeprom 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
\rsaa7134[0]: i2c eeprom 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
\rsaa7134[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
\rsaa7134[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
\rsaa7134[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
\rsaa7134[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
\rdrivers/usb/class/usblp.c: usblp0: USB Bidirectional printer dev 3 if 0 alt 1 proto 2 vid 0x03F0 pid 0x1204
\rusbcore: registered new driver usblp
\rdrivers/usb/class/usblp.c: v0.13: USB Printer Device Class driver
\rtuner 3-0061: chip found @ 0xc2 (saa7134[0])
\rtuner 3-0061: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
\rsaa7134[0]: registered device video1 [v4l2]
\rsaa7134[0]: registered device vbi1
\rsaa7134[0]: registered device radio0
\rReiserFS: dm-7: found reiserfs format "3.6" with standard journal
\rReiserFS: dm-7: using ordered data mode
\rReiserFS: dm-7: journal params: device dm-7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
\rReiserFS: dm-7: checking transaction log (dm-7)
\rReiserFS: dm-7: Using r5 hash to sort names
\rReiserFS: dm-1: found reiserfs format "3.6" with standard journal
\rReiserFS: dm-1: using ordered data mode
\rReiserFS: dm-1: journal params: device dm-1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
\rReiserFS: dm-1: checking transaction log (dm-1)
\rReiserFS: dm-1: Using r5 hash to sort names
\rReiserFS: dm-2: found reiserfs format "3.6" with standard journal
\rReiserFS: dm-2: using ordered data mode
\rReiserFS: dm-2: journal params: device dm-2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
\rReiserFS: dm-2: checking transaction log (dm-2)
\rReiserFS: dm-2: Using r5 hash to sort names
\rReiserFS: dm-0: found reiserfs format "3.6" with standard journal
\rReiserFS: dm-0: using ordered data mode
\rReiserFS: dm-0: journal params: device dm-0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
\rReiserFS: dm-0: checking transaction log (dm-0)
\rReiserFS: dm-0: Using r5 hash to sort names
\rReiserFS: dm-7: found reiserfs format "3.6" with standard journal
\rReiserFS: dm-7: using ordered data mode
\rReiserFS: dm-7: journal params: device dm-7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
\rReiserFS: dm-7: checking transaction log (dm-7)
\rReiserFS: dm-7: Using r5 hash to sort names
\rXFS mounting filesystem sda1
\rXFS mounting filesystem sda2
\rAdding 1048568k swap on /dev/mapper/cswap.  Priority:-1 extents:1 across:1048568k
\ri2c_adapter i2c-2: SMBus Quick command not supported, can't probe for chips
\rsaa7134 ALSA driver for DMA sound loaded
\rsaa7134[0]/alsa: saa7134[0] at 0xcdcff800 irq 17 registered as card -1
\rinput: Multisystem joystick (2 fire) as /class/input/input5
\rNET: Registered protocol family 23
\rIrCOMM protocol (Dag Brattli)
\rNon-volatile memory driver v1.2
\rieee1394: raw1394: /dev/raw1394 device initialized
\rsky2 eth0: enabling interface
\rsky2 eth1: enabling interface
\rCSLIP: code copyright 1989 Regents of the University of California
\rPPP generic driver version 2.4.2
\rttyS1: LSR safety check engaged!
\rttyS1: LSR safety check engaged!
\rsky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
\rmicrocode: CPU1 updated from revision 0x14 to 0x17, date = 04212005 
\rmicrocode: CPU0 updated from revision 0x14 to 0x17, date = 04212005 
\rACPI: Processor [CPU1] (supports 8 throttling states)
\rACPI: Power Button (FF) [PWRF]
\rACPI: Power Button (CM) [PWRB]
\rsaa7146: unregister extension 'dvb'.
\rACPI: PCI interrupt for device 0000:01:0a.0 disabled
\rsaa7146: register extension 'budget_patch dvb'.
\rACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 21
\rsaa7146: found saa7146 @ mem f09eec00 (revision 1, irq 21) (0x13c2,0x0000).
\rBUDGET-PATCH DETECTED.
\rDVB: registering new adapter (TT-Budget/Patch DVB-S 1.x PCI).
\radapter has MAC addr = 00:d0:5c:00:9d:9a
\rves1x93: Detected ves1893a rev2
\rDVB: registering frontend 0 (VLSI VES1x93 DVB-S)...
\rlp: driver loaded but no devices found
\rttyS1: LSR safety check engaged!
\rhde: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
\rhde: drive_cmd: error=0x04 { DriveStatusError }
\ride: failed opcode was: 0xb0
\rhde: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
\rhde: drive_cmd: error=0x04 { DriveStatusError }
\ride: failed opcode was: 0xa1
\rdevice eth0 entered promiscuous mode
\rBluetooth: L2CAP ver 2.8
\rBluetooth: L2CAP socket layer initialized
\rBluetooth: RFCOMM socket layer initialized
\rBluetooth: RFCOMM TTY layer initialized
\rBluetooth: RFCOMM ver 1.7
\rhci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb eed82814 err -38
\rhci_cmd_task: hci0 command tx timeout
\rhci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb eed82814 err -38
\rinput: Caliper as /class/input/input6
\rip_tables: (C) 2000-2006 Netfilter Core Team
\rsaa7146: unregister extension 'budget_patch dvb'.
\rACPI: PCI interrupt for device 0000:01:0a.0 disabled
\rsaa7146: register extension 'budget_patch dvb'.
\rACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 21
\rsaa7146: found saa7146 @ mem f09f8c00 (revision 1, irq 21) (0x13c2,0x0000).
\rbudget-patch not detected or saa7146 in non-default state.
\rtry enabling ressetting of 7146 with MASK_31 in MC1 register
\rDVB: registering new adapter (TT-Budget/Patch DVB-S 1.x PCI).
\radapter has MAC addr = 00:d0:5c:00:9d:9a
\rves1x93: Detected ves1893a rev2
\rDVB: registering frontend 0 (VLSI VES1x93 DVB-S)...
\rsaa7146: unregister extension 'budget_patch dvb'.
\rACPI: PCI interrupt for device 0000:01:0a.0 disabled
\rsaa7146: register extension 'budget_patch dvb'.
\rACPI: PCI Interrupt 0000:01:0a.0[A] -> GSI 21 (level, low) -> IRQ 21
\rsaa7146: found saa7146 @ mem f09f8c00 (revision 1, irq 21) (0x13c2,0x0000).
\rbudget-patch not detected or saa7146 in non-default state.
\rtry enabling ressetting of 7146 with MASK_31 in MC1 register
\rDVB: registering new adapter (TT-Budget/Patch DVB-S 1.x PCI).
\radapter has MAC addr = 00:d0:5c:00:9d:9a
\rves1x93: Detected ves1893a rev2
\rDVB: registering frontend 0 (VLSI VES1x93 DVB-S)...
\rusb 5-4.3: USB disconnect, address 8
\rusb 5-4.3: new low speed USB device using ehci_hcd and address 9
\rusb 5-4.3: configuration #1 chosen from 1 choice
\rusbcore: registered new driver hiddev
\rdrivers/usb/input/hid-core.c: timeout initializing reports
\rinput: Logitech Inc. iFeel Mouse    as /class/input/input7
\rinput: USB HID v1.00 Mouse [Logitech Inc. iFeel Mouse   ] on usb-0000:00:1d.7-4.3
\rusbcore: registered new driver usbhid
\rdrivers/usb/input/hid-core.c: v2.6:USB HID core driver
\rehci_hcd 0000:00:1d.7: qh ee925400 (#81) state 4
\rUnable to handle kernel paging request at virtual address 748b00f4
\r printing eip:
\rf09cc61e
\r*pde = 00000000
\rOops: 0000 [#1]
\rSMP 
\rModules linked in: usbhid budget_patch budget_core stv0299 iptable_filter ipt_TOS xt_tcpudp iptable_mangle ipt_MASQUERADE iptable_nat ip_nat ip_tables x_tables rfcomm l2cap lp thermal fan button processor ac battery ppp_generic slhc raw1394 ieee1394 w83627ehf hwmon i2c_isa uinput nvram ircomm_tty ircomm irda vfat fat db9 saa7134_alsa eeprom tuner usblp pl2303 hci_usb bluetooth dvb_usb_a800 dvb_usb_dibusb_common dib3000mc dib3000_common dvb_usb dvb_pll usbserial serio_raw saa7134 compat_ioctl32 ir_kbd_i2c l64781 saa7146_vv video_buf saa7146 v4l1_compat v4l2_common ves1820 dvb_core tda8083 stv0297 sp8870  ir_com  videodev ves1x93 ttpci_eeprom pcspkr snd_mpu401 snd_mpu401_uart snd_rawmidi rtc snd_seq_device parport_pc parport i2c_i801 snd_hda_intel sky2 ehci_hcd snd_hda_codec snd_pcm_oss snd_mixer_oss snd_pcm uhci_hcd snd_timer snd snd_page_alloc ide_cd cdrom
\rCPU:    1
\rEIP:    0060:[<f09cc61e>]    Not tainted VLI
\rEFLAGS: 00010207   (2.6.16.19-crash #1) 
\rEIP is at dvb_demux_poll+0x24/0x56 [dvb_core]
\reax: c2747561   ebx: c2747541   ecx: 0000ffea   edx: 748b00f4
\resi: a6fe63d0   edi: eed4d88c   ebp: eed2fa44   esp: d5935f60
\rds: 007b   es: 007b   ss: 0068
\rProcess vdr-kbd (pid: 7276, threadinfo=d5934000 task=edb18a50)
\rStack: <0>b015c19e c9c318c0 00000000 a6fe63d0 dca55ec0 000015a6 00000000 dca55ec0 
\r       00003bc8 b015b5d7 dd90a000 00000000 a6fe6390 000003e8 a7dbbff4 d5934000 
\r       b015c57f a6fe6390 00000008 d5935fb0 0000039f 00000000 b0102739 a6fe6390 
\rCall Trace:
\r [<b015c19e>] do_sys_poll+0x167/0x304
\r [<00000000>] rest_init+0x4feffd68/0x23
\r [<000015a6>] 0x15a6
\r [<00000000>] rest_init+0x4feffd68/0x23
\r [<00003bc8>] 0x3bc8
\r [<b015b5d7>] __pollwait+0x0/0x9b
\r [<00000000>] rest_init+0x4feffd68/0x23
\r [<000003e8>] 0x3e8
\r [<b015c57f>] sys_poll+0x42/0x47
\r [<00000008>] 0x8
\r [<0000039f>] 0x39f
\r [<00000000>] rest_init+0x4feffd68/0x23
\r [<b0102739>] syscall_call+0x7/0xb
\r [<00000008>] 0x8
\r [<000003e8>] 0x3e8
\r [<000003e8>] 0x3e8
\r [<000000a8>] 0xa8
\r [<0000007b>] 0x7b
\r [<000000a8>] 0xa8
\r [<00000073>] 0x73
\r [<00000246>] 0x246
\r [<0000007b>] 0x7b
\r [<00000000>] rest_init+0x4feffd68/0x23
\r [<00000000>] rest_init+0x4feffd68/0x23
\rCode: 00 ff ff 83 c4 14 c3 fa 00 8b 74 24 0c 8b 54 20 00 8b 5e 78 b9 ea ff 00 00 85 db 74 3b 8d 43 20 00 d2 74 0c 85 c0 74 00 00 50 56 <ff> 12 83 c4 20 00 43 4c 83 e8 03 31 00 00 f8 02 77 1b 8b 43 20 
\r <1>Unable to handle kernel paging request

Re: SMP HT + USB2.0 crash

[davor emard]

HI

I downloaded memtest86 iso image and let it running. I passed
1st battery of tests and continues. I'm pretty sure it will keep
pass those test without anyerrors, after all memories there
are 2x512MB samsung and for this machine I was choosing
ram's recommended by the manufacturer this motherboard.

Regarding nvidia, I don't like their binary policy but I may
tell you that both intel 925XE machines can run indefinitely
(for days even months until I reinstall new kernel)
each with a lot of simultaneous openGL with nvidia on 2 monitors
in dual head, dvb receiving over usb (here I mean USB 1.1 only)
firewire traffic, SPDIF output, ethernet traffic on both interfaces
and all that
through enabled SMP, PREEMPT and PREEMPT BIG_KERNEL_LOCK
and it is not going to crash.

As soon as I enable EHCI there it comes.
Otherwise I have option to use EHCI and don't use SMP
but not them both.



On 6/5/06, davor emard <davoremard@gmail.com> wrote:
> HI
>
> Due to popular demand I'm mailing the recent crash
> captured with serial cable on 2.6.16.19 on intel 925X
> triggered with SMP + USB2.0 combination.
>
> Here we got it, it's pretty random and useless for
> tracking the real problem so please don't blame
> software demux in DVB core just becaise it randomly
> crashed there - only thing that matters is that a800
> terrestroal receiver was running in USB 2.0 mode in
> order to generate enough usb2.0 traffic
> to trigger SMP+EHCI bug.
>
> I contributed myself to the dvb software demux code
> and it runs stable with it's demux core part almost
> unchanged for 2 years.
>
> If I remove EHCI and run a800 in USB 1.1 mode everything
> can run stable for any amount of time.
>
>

Re: SMP HT + USB2.0 crash

[davor emard]

[-- Attachment #1: Type: text/plain, Size: 81 bytes --]

Memtest86 runned for few hours and completed 15 passes
0 errors (see attachment)

[-- Attachment #2: memtest2.jpg --]
[-- Type: image/jpeg, Size: 39666 bytes --]