Re: 2.6.10: irq 12 nobody cared!

2005-02-19 Thread Rogério Brito
On Feb 17 2005, Linus Torvalds wrote: > Does the box still work? It may well be that once all drivers have had a > chance to initialize their hardware properly, the problem is just gone, > and that the interim reports about not being able to handle the irq are > just temporary noise. I started

Re: 2.6.10: irq 12 nobody cared!

2005-02-17 Thread Linus Torvalds
On Thu, 17 Feb 2005, Joshua Kwan wrote: > > What was the previous kernel you ran on that machine, just out of > > interest? If it hasn't happened before, it would be interesting to know > > when it started happening... > > It used to be running 2.4.27, where there was no evidence of such a bug

Re: 2.6.10: irq 12 nobody cared!

2005-02-17 Thread Joshua Kwan
Linus Torvalds wrote: Does the box still work? It may well be that once all drivers have had a chance to initialize their hardware properly, the problem is just gone, and that the interim reports about not being able to handle the irq are just temporary noise. The box seems to work fine; on the oth

Re: 2.6.10: irq 12 nobody cared!

2005-02-17 Thread Linus Torvalds
On Wed, 16 Feb 2005, Joshua Kwan wrote: > > Just migrated to 2.6.10 on an old VIA MVP3 box and I'm getting this: > > irq 12: nobody cared! IRQ 12 should be your PS/2 mouse irq too. It seems your wireless card shares that interrupt, which is unusual, but not necessarily wrong. My guess is tha

Re: 2.6.10: irq 12 nobody cared!

2005-02-17 Thread Ondrej Zary
Joshua Kwan wrote: irq 12: nobody cared! [...] Disabling IRQ #12 serio: i8042 AUX port at 0x60,0x64 irq 12 ^^ mice: PS/2 mouse device common for all mice irq 12: nobody cared! I'd say that there is a conflict between the card and PS/2 mouse port. -- Ondrej Z

Re: 2.6.10: irq 12 nobody cared!

2005-02-17 Thread Zwane Mwaikambo
On Thu, 17 Feb 2005, Joshua Kwan wrote: > Zwane Mwaikambo wrote: > > Check that the hostap interrupt handler is 2.6 aware (IRQ_HANDLED etc) > > It shows up even before the hostap module is loaded (and in fact appears > to stop showing up when that happens.) Here's the full output of dmesg. > []

Re: 2.6.10: irq 12 nobody cared!

2005-02-17 Thread Joshua Kwan
Zwane Mwaikambo wrote: Check that the hostap interrupt handler is 2.6 aware (IRQ_HANDLED etc) It shows up even before the hostap module is loaded (and in fact appears to stop showing up when that happens.) Here's the full output of dmesg. Linux version 2.6.10-influx ([EMAIL PROTECTED]) (gcc version

Re: 2.6.10: irq 12 nobody cared!

2005-02-17 Thread Zwane Mwaikambo
On Wed, 16 Feb 2005, Joshua Kwan wrote: >CPU0 > 0:1073809 XT-PIC timer > 1: 1291 XT-PIC i8042 > 2: 0 XT-PIC cascade > 4: 7 XT-PIC serial > 5: 4366 XT-PIC eth0 > 7: 12 XT-PIC

2.6.10: irq 12 nobody cared!

2005-02-16 Thread Joshua Kwan
Hi, Just migrated to 2.6.10 on an old VIA MVP3 box and I'm getting this: irq 12: nobody cared! [] __report_bad_irq+0x22/0x80 [] note_interrupt+0x4c/0x80 [] __do_IRQ+0x118/0x140 [] do_IRQ+0x36/0x60 === [] common_interrupt+0x1a/0x20 [] __do_softirq+0x30/0xa0 [] do_softirq+