Re: 2.6.20 "IRQ handler type mismatch for IRQ 4"

2007-02-12 Thread Alan
> > This is all scary and generally not needed spew but handy for debug. > > > > Looks like a PCMCIA layer bug. It should be respecting IRQ assignment > > (not just allocation) by other resource configuration layers. > > Ah thanks for taking a look. I was slowly getting the impression from older

Re: 2.6.20 "IRQ handler type mismatch for IRQ 4"

2007-02-12 Thread Florian Schmidt
On Monday 12 February 2007, Alan wrote: > > [ 23.783913] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ > > sharing enabled > > [ 23.787063] pnp: Device 00:0c activated. > > [ 23.787420] 00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A > > So the PnP layers put a device on IRQ 4,

Re: 2.6.20 "IRQ handler type mismatch for IRQ 4"

2007-02-12 Thread Alan
> [ 23.783913] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ > sharing enabled > [ 23.787063] pnp: Device 00:0c activated. > [ 23.787420] 00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A So the PnP layers put a device on IRQ 4, which is sensible > [ 37.516000] eth1: orinoco_cs

Re: 2.6.20 IRQ handler type mismatch for IRQ 4

2007-02-12 Thread Alan
[ 23.783913] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled [ 23.787063] pnp: Device 00:0c activated. [ 23.787420] 00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A So the PnP layers put a device on IRQ 4, which is sensible [ 37.516000] eth1: orinoco_cs at

Re: 2.6.20 IRQ handler type mismatch for IRQ 4

2007-02-12 Thread Florian Schmidt
On Monday 12 February 2007, Alan wrote: [ 23.783913] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled [ 23.787063] pnp: Device 00:0c activated. [ 23.787420] 00:0c: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A So the PnP layers put a device on IRQ 4, which is

Re: 2.6.20 IRQ handler type mismatch for IRQ 4

2007-02-12 Thread Alan
This is all scary and generally not needed spew but handy for debug. Looks like a PCMCIA layer bug. It should be respecting IRQ assignment (not just allocation) by other resource configuration layers. Ah thanks for taking a look. I was slowly getting the impression from older lkml

2.6.20 "IRQ handler type mismatch for IRQ 4"

2007-02-10 Thread Florian Schmidt
Hi, i upgraded my system from ubuntu edgy to feisty and a new kernel came with it (2.6.15 vs. 2.6.20). Sadly my wireless card (pcmcia) has stopped working under this system. Seeing a backttrace in the dmesg output made me believe it's a kernel problem. I built a vanilla kernel to see if maybe

2.6.20 IRQ handler type mismatch for IRQ 4

2007-02-10 Thread Florian Schmidt
Hi, i upgraded my system from ubuntu edgy to feisty and a new kernel came with it (2.6.15 vs. 2.6.20). Sadly my wireless card (pcmcia) has stopped working under this system. Seeing a backttrace in the dmesg output made me believe it's a kernel problem. I built a vanilla kernel to see if maybe