Re: pcmcia oops on 2.6.17-rc[12]
From: Andreas Mohr
Date: Mon May 08 2006 - 10:55:53 EST
Hi,
On Sun, Apr 23, 2006 at 03:02:06PM -0700, Andrew Morton wrote:
> It's actually not an oops - it's a warning, telling us that i82365 is
> requesting an IRQ in non-sharing mode, but there's already a handler
> registered for that IRQ (which might or might not be shareable).
And the same thing on a Toshiba Satellite 4280, P3/450, 2.6.17-rc3-ck2:
setup_irq: irq handler mismatch
<c0103248> show_trace+0xd/0xf <c010325f> dump_stack+0x15/0x17
<c012aeca> setup_irq+0xd9/0xe8 <c012b002> request_irq+0x6e/0x8c
<c020cdfd> serial8250_startup+0x263/0x394 <c020a1aa> uart_startup+0x68/0xf1
<c020adba> uart_ioctl+0x554/0x847 <c01f31ed> tty_ioctl+0xbae/0xc36
<c0151eec> do_ioctl+0x3c/0x4f <c01520ed> vfs_ioctl+0x1ee/0x205
<c015212e> sys_ioctl+0x2a/0x44 <c01029bb> sysenter_past_esp+0x54/0x75
setup_irq: irq handler mismatch
<c0103248> show_trace+0xd/0xf <c010325f> dump_stack+0x15/0x17
<c012aeca> setup_irq+0xd9/0xe8 <c012b002> request_irq+0x6e/0x8c
<c020cdfd> serial8250_startup+0x263/0x394 <c020a1aa> uart_startup+0x68/0xf1
<c020a3aa> uart_open+0x177/0x345 <c01f399d> tty_open+0x174/0x29a
<c014b0b5> chrdev_open+0xf6/0x10d <c0143b37> __dentry_open+0xb7/0x185
<c0143c73> nameidata_to_filp+0x1c/0x2e <c0143cb3> do_filp_open+0x2e/0x35
<c0143d9e> do_sys_open+0x3f/0xb7 <c0143e42> sys_open+0x16/0x18
<c01029bb> sysenter_past_esp+0x54/0x75
setup_irq: irq handler mismatch
<c0103248> show_trace+0xd/0xf <c010325f> dump_stack+0x15/0x17
<c012aeca> setup_irq+0xd9/0xe8 <c012b002> request_irq+0x6e/0x8c
<c020cdfd> serial8250_startup+0x263/0x394 <c020a1aa> uart_startup+0x68/0xf1
<c020a3aa> uart_open+0x177/0x345 <c01f399d> tty_open+0x174/0x29a
<c014b0b5> chrdev_open+0xf6/0x10d <c0143b37> __dentry_open+0xb7/0x185
<c0143c73> nameidata_to_filp+0x1c/0x2e <c0143cb3> do_filp_open+0x2e/0x35
<c0143d9e> do_sys_open+0x3f/0xb7 <c0143e42> sys_open+0x16/0x18
<c01029bb> sysenter_past_esp+0x54/0x75
# cat /proc/interrupts
CPU0
0: 31607214 XT-PIC timer
1: 11092 XT-PIC i8042
2: 0 XT-PIC cascade
3: 36368 XT-PIC pcnet_cs
8: 3 XT-PIC rtc
9: 84 XT-PIC acpi
11: 73639 XT-PIC yenta, yenta, uhci_hcd:usb1, YMFPCI, irda0
12: 9996 XT-PIC i8042
14: 63830 XT-PIC ide0
15: 536942 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
# lspci
0000:00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
0000:00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
0000:00:05.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
0000:00:05.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
0000:00:05.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
0000:00:05.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
0000:00:07.0 Communication controller: Agere Systems 56k WinModem (rev 01)
0000:00:09.0 IRDA controller: Toshiba America Info Systems FIR Port Type-DO
0000:00:0b.0 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 20)
0000:00:0b.1 CardBus bridge: Toshiba America Info Systems ToPIC100 PCI to Cardbus Bridge with ZV Support (rev 20)
0000:00:0c.0 Multimedia audio controller: Yamaha Corporation YMF-744B [DS-1S Audio Controller] (rev 02)
0000:01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/IX-MV (rev 11)
> Your machine should otherwise continue to work OK. Is that the case?
It seems so, yes.
> i82365 appears to be poking around in interrupt space trying to find an IRQ
> which isn't shared with anyone else (I'm not sure why, but these sorts of
> things tend to be derived from hard experience).
>
> Anyway. We need to either a) make i82365 better-behaved or b) remove the
> warning or c) allow callers to suppress the warning (SA_PROBEIRQ?).
Add SA_PROBEIRQ to 8250.c, then, I guess?
Thanks!
Andreas Mohr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/