* Problem: irq 217: nobody cared + backtrace
@ 2006-08-03 14:17 Jesper Juhl
2006-08-03 16:08 ` Alan Stern
0 siblings, 1 reply; 11+ messages in thread
From: Jesper Juhl @ 2006-08-03 14:17 UTC (permalink / raw)
To: Linux Kernel Mailing List; +Cc: linux-usb-devel, Alan Stern, Greg Kroah-Hartman
[-- Attachment #1: Type: text/plain, Size: 4476 bytes --]
Hi,
A server of mine just dumped a backtrace (below).
The machine seems to be running fine, but it would be nice to know
what the cause of this dump is.
The box is running 2.6.18-rc3-git3
Full dmesg output is attached.
If more info than what is below is needed, then just ask and I'll
provide it if I can.
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
eth0.20: add 01:00:5e:00:00:01 mcast address to master interface
IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
irq 217: nobody cared (try booting with the "irqpoll" option)
[<c0103a3c>] show_trace_log_lvl+0x152/0x165
[<c0103a5e>] show_trace+0xf/0x13
[<c0103b59>] dump_stack+0x15/0x19
[<c013846e>] __report_bad_irq+0x24/0x7f
[<c0138552>] note_interrupt+0x6b/0xd5
[<c0137ca8>] __do_IRQ+0xf4/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c02d61b7>] uhci_irq+0x27/0x153
[<c02c45e8>] usb_hcd_irq+0x24/0x53
[<c0137b84>] handle_IRQ_event+0x26/0x56
[<c0137c4c>] __do_IRQ+0x98/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c0100e64>] mwait_idle+0x30/0x35
[<c0100d45>] cpu_idle+0x78/0x81
[<c04bf7fb>] start_kernel+0x173/0x19d
[<c0100210>] 0xc0100210
DWARF2 unwinder stuck at 0xc0100210
Leftover inexact backtrace:
=======================
handlers:
[<c02c45c4>] (usb_hcd_irq+0x0/0x53)
Disabling IRQ #217
# scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux server 2.6.18-rc3-git3 #1 SMP Thu Aug 3 13:28:08 CEST 2006 i686 GNU/Linux
Gnu C 3.3.5
Gnu make 3.80
binutils 2.15
util-linux 2.12p
mount 2.12p
module-init-tools 3.2-pre1
e2fsprogs 1.37
xfsprogs 2.6.20
nfs-utils 1.0.6
Linux C Library 2.3.2
Dynamic linker (ldd) 2.3.2
Procps 3.2.1
Net-tools 1.60
Console-tools 0.2.3
Sh-utils 5.2.1
udev 056
Modules Loaded sky2 piix ide_core eeprom
# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Xeon(TM) CPU 3.20GHz
stepping : 3
cpu MHz : 3192.358
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx
lm constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips : 6388.63
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Xeon(TM) CPU 3.20GHz
stepping : 3
cpu MHz : 3192.358
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx
lm constant_tsc pni monitor ds_cpl cid cx16 xtpr
bogomips : 6384.44
# cat /proc/interrupts
CPU0 CPU1
0: 175546 3503 IO-APIC-edge timer
1: 3 5 IO-APIC-edge i8042
8: 3 1 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
50: 1 0 PCI-MSI sky2
169: 5177874 1 IO-APIC-level uhci_hcd:usb2, eth0
177: 26052 26 IO-APIC-level 3w-9xxx
185: 32334 35 IO-APIC-level 3w-9xxx
193: 17290 14 IO-APIC-level 3w-9xxx
201: 23050 16 IO-APIC-level 3w-9xxx, libata, uhci_hcd:usb4
209: 0 0 IO-APIC-level ehci_hcd:usb1
217: 99932 68 IO-APIC-level uhci_hcd:usb3
NMI: 178992 178964
LOC: 178936 178936
ERR: 0
MIS: 0
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
[-- Attachment #2: boot.log --]
[-- Type: text/x-log, Size: 29949 bytes --]
Linux version 2.6.18-rc3-git3 (root@server) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Thu Aug 3 13:28:08 CEST 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e2000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000007ffe0000 (usable)
BIOS-e820: 000000007ffe0000 - 000000007ffef000 (ACPI data)
BIOS-e820: 000000007ffef000 - 000000007fffdc00 (ACPI NVS)
BIOS-e820: 000000007fffdc00 - 0000000080000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fec86000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffc00000 - 0000000100000000 (reserved)
1151MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000ff780
On node 0 totalpages: 524256
DMA zone: 4096 pages, LIFO batch:0
Normal zone: 225280 pages, LIFO batch:31
HighMem zone: 294880 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 ACPIAM ) @ 0x000f8370
ACPI: RSDT (v001 A M I OEMRSDT 0x09000520 MSFT 0x00000097) @ 0x7ffe0000
ACPI: FADT (v002 A M I OEMFACP 0x09000520 MSFT 0x00000097) @ 0x7ffe0200
ACPI: MADT (v001 A M I OEMAPIC 0x09000520 MSFT 0x00000097) @ 0x7ffe0390
ACPI: SPCR (v001 A M I OEMSPCR 0x09000520 MSFT 0x00000097) @ 0x7ffe0420
ACPI: MCFG (v001 A M I OEMMCFG 0x09000520 MSFT 0x00000097) @ 0x7ffe0470
ACPI: OEMB (v001 A M I AMI_OEM 0x09000520 MSFT 0x00000097) @ 0x7ffef040
ACPI: DSDT (v001 SBD2B SBD2B016 0x00000016 INTL 0x02002026) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:4 APIC version 20
ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: IOAPIC (id[0x03] address[0xfec80000] gsi_base[24])
IOAPIC[1]: apic_id 3, version 32, address 0xfec80000, GSI 24-47
ACPI: IOAPIC (id[0x04] address[0xfec80400] gsi_base[48])
IOAPIC[2]: apic_id 4, version 32, address 0xfec80400, GSI 48-71
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Enabling APIC mode: Flat. Using 3 I/O APICs
Using ACPI (MADT) for SMP configuration information
Allocating PCI resources starting at 88000000 (gap: 80000000:7ec00000)
Detected 3192.358 MHz processor.
Built 1 zonelists. Total pages: 524256
Kernel command line: root=/dev/md1 ro nmi_watchdog=1
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
mapped IOAPIC to ffffb000 (fec80000)
mapped IOAPIC to ffffa000 (fec80400)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c04fb000 soft=c04f3000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 2070156k/2097024k available (2512k kernel code, 25736k reserved, 887k data, 188k init, 1179520k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6388.63 BogoMIPS (lpj=12777275)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
monitor/mwait feature present.
using mwait in idle threads.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000641d 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU0: Intel P4/Xeon Extended MCE MSRs (24) available
CPU0: Thermal monitoring enabled
Compat vDSO mapped to ffffe000.
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 16k freed
ACPI: Core revision 20060707
CPU0: Intel(R) Xeon(TM) CPU 3.20GHz stepping 03
Booting processor 1/1 eip 2000
CPU 1 irqstacks, hard=c04fc000 soft=c04f4000
Initializing CPU#1
Calibrating delay using timer specific routine.. 6384.44 BogoMIPS (lpj=12768892)
CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 20100000 00000000 00000000 0000641d 00000000 00000000
monitor/mwait feature present.
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 20100000 00000000 00000180 0000641d 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU1: Intel P4/Xeon Extended MCE MSRs (24) available
CPU1: Thermal monitoring enabled
CPU1: Intel(R) Xeon(TM) CPU 3.20GHz stepping 03
Total of 2 processors activated (12773.08 BogoMIPS).
ENABLING IO-APIC IRQs
..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
checking TSC synchronization across 2 CPUs: passed.
Brought up 2 CPUs
migration_cost=1440
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=7
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 0400-047f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 0500-053f claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: PXH quirk detected, disabling MSI for SHPC device
PCI: PXH quirk detected, disabling MSI for SHPC device
Boot video device is 0000:07:0c.0
PCI: Transparent bridge - 0000:00:1e.0
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P7._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EPA0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EPA0.PXHA._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EPA0.PXHB._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EPB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EPC0._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 6 7 10 11 12 14 *15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 6 *7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKH] (IRQs *5)
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Bridge: 0000:01:00.0
IO window: b000-bfff
MEM window: fcd00000-fcdfffff
PREFETCH window: fa000000-faffffff
PCI: Bridge: 0000:01:00.2
IO window: c000-cfff
MEM window: fce00000-fcefffff
PREFETCH window: fb000000-fb7fffff
PCI: Bridge: 0000:00:02.0
IO window: b000-cfff
MEM window: fcc00000-fcefffff
PREFETCH window: fa000000-fb7fffff
PCI: Bridge: 0000:00:04.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:05.0
IO window: d000-dfff
MEM window: fcf00000-fcffffff
PREFETCH window: disabled.
PCI: Bridge: 0000:00:06.0
IO window: disabled.
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: e000-efff
MEM window: fd000000-febfffff
PREFETCH window: fb800000-fbffffff
ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:02.0 to 64
PCI: Setting latency timer of device 0000:01:00.0 to 64
PCI: Setting latency timer of device 0000:01:00.2 to 64
ACPI: PCI Interrupt 0000:00:04.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:04.0 to 64
ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:05.0 to 64
ACPI: PCI Interrupt 0000:00:06.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:06.0 to 64
PCI: Setting latency timer of device 0000:00:1e.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2621440 bytes)
TCP bind hash table entries: 65536 (order: 8, 1310720 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
highmem bounce pool size: 64 pages
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
SGI XFS with large block numbers, no debug enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered (default)
io scheduler cfq registered
PCI: Setting latency timer of device 0000:00:02.0 to 64
Allocate Port Service[0000:00:02.0:pcie00]
PCI: Setting latency timer of device 0000:00:04.0 to 64
Allocate Port Service[0000:00:04.0:pcie00]
PCI: Setting latency timer of device 0000:00:05.0 to 64
Allocate Port Service[0000:00:05.0:pcie00]
PCI: Setting latency timer of device 0000:00:06.0 to 64
Allocate Port Service[0000:00:06.0:pcie00]
Real Time Clock Driver v1.12ac
i8xx TCO timer: initialized (0x0460). heartbeat=30 sec (nowayout=0)
ipmi message handler version 39.0
ipmi device interface
IPMI System Interface driver.
ipmi_si: Unable to find any System Interface(s)
IPMI Watchdog: driver initialized
Intel(R) PRO/1000 Network Driver - version 7.1.9-k4-NAPI
Copyright (c) 1999-2006 Intel Corporation.
ACPI: PCI Interrupt 0000:07:04.0[A] -> GSI 16 (level, low) -> IRQ 169
e1000: 0000:07:04.0: e1000_probe: (PCI:33MHz:32-bit) 00:04:23:bf:d9:62
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
3ware 9000 Storage Controller device driver for Linux v2.26.02.007.
ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 28 (level, low) -> IRQ 177
3w-9xxx: scsi0: AEN: INFO (0x04:0x0053): Battery capacity test is overdue:.
3w-9xxx: scsi0: AEN: WARNING (0x04:0x0042): Primary DCB read error occurred:port=5, error=0x208.
scsi0 : 3ware 9000 Storage Controller
3w-9xxx: scsi0: Found a 3ware 9000 Storage Controller at 0xfcdffc00, IRQ: 177.
3w-9xxx: scsi0: Firmware FE9X 2.06.00.009, BIOS BE9X 2.03.01.051, Ports: 12.
Vendor: AMCC Model: 9500S-12MI DISK Rev: 2.06
Type: Direct-Access ANSI SCSI revision: 03
Vendor: AMCC Model: 9500S-12MI DISK Rev: 2.06
Type: Direct-Access ANSI SCSI revision: 03
Vendor: AMCC Model: 9500S-12MI DISK Rev: 2.06
Type: Direct-Access ANSI SCSI revision: 03
ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 24 (level, low) -> IRQ 185
scsi1 : 3ware 9000 Storage Controller
3w-9xxx: scsi1: Found a 3ware 9000 Storage Controller at 0xfcdff800, IRQ: 185.
3w-9xxx: scsi1: Firmware FE9X 2.02.00.008, BIOS BE9X 2.02.01.037, Ports: 12.
Vendor: 3ware Model: Logical Disk 00 Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: 3ware Model: Logical Disk 01 Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: 3ware Model: Logical Disk 02 Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: 3ware Model: Logical Disk 03 Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: 3ware Model: Logical Disk 04 Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
ACPI: PCI Interrupt 0000:03:01.0[A] -> GSI 48 (level, low) -> IRQ 193
3w-9xxx: scsi2: AEN: INFO (0x04:0x0053): Battery capacity test is overdue:.
scsi2 : 3ware 9000 Storage Controller
3w-9xxx: scsi2: Found a 3ware 9000 Storage Controller at 0xfceffc00, IRQ: 193.
3w-9xxx: scsi2: Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047, Ports: 8.
Vendor: 3ware Model: Logical Disk 00 Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
ACPI: PCI Interrupt 0000:07:06.0[A] -> GSI 18 (level, low) -> IRQ 201
3w-9xxx: scsi3: AEN: INFO (0x04:0x0053): Battery capacity test is overdue:.
scsi3 : 3ware 9000 Storage Controller
3w-9xxx: scsi3: Found a 3ware 9000 Storage Controller at 0xfebdbc00, IRQ: 201.
3w-9xxx: scsi3: Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047, Ports: 8.
Vendor: 3ware Model: Logical Disk 00 Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
libata version 2.00 loaded.
ata_piix 0000:00:1f.2: version 2.00
ata_piix 0000:00:1f.2: MAP [ P0 -- P1 -- ]
ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0xA800 ctl 0xA482 bmdma 0xA000 irq 201
ata2: SATA max UDMA/133 cmd 0xA400 ctl 0xA082 bmdma 0xA008 irq 201
scsi4 : ata_piix
ata1.00: ATA-6, max UDMA/133, 390721968 sectors: LBA48
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi5 : ata_piix
ata2.00: ATA-6, max UDMA/133, 390721968 sectors: LBA48
ata2.00: ata2: dev 0 multi count 16
ata2.00: configured for UDMA/133
Vendor: ATA Model: ST3200822AS Rev: 3.01
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3200822AS Rev: 3.01
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 976541696 512-byte hdwr sectors (499989 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
SCSI device sda: drive cache: write back, no read (daft)
SCSI device sda: 976541696 512-byte hdwr sectors (499989 MB)
sda: Write Protect is off
sda: Mode Sense: 23 00 00 00
SCSI device sda: drive cache: write back, no read (daft)
sda: unknown partition table
sd 0:0:0:0: Attached scsi disk sda
SCSI device sdb: 976541696 512-byte hdwr sectors (499989 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
SCSI device sdb: drive cache: write back, no read (daft)
SCSI device sdb: 976541696 512-byte hdwr sectors (499989 MB)
sdb: Write Protect is off
sdb: Mode Sense: 23 00 00 00
SCSI device sdb: drive cache: write back, no read (daft)
sdb: unknown partition table
sd 0:0:1:0: Attached scsi disk sdb
SCSI device sdc: 976541696 512-byte hdwr sectors (499989 MB)
sdc: Write Protect is off
sdc: Mode Sense: 23 00 00 00
SCSI device sdc: drive cache: write back, no read (daft)
SCSI device sdc: 976541696 512-byte hdwr sectors (499989 MB)
sdc: Write Protect is off
sdc: Mode Sense: 23 00 00 00
SCSI device sdc: drive cache: write back, no read (daft)
sdc: unknown partition table
sd 0:0:2:0: Attached scsi disk sdc
SCSI device sdd: 781228032 512-byte hdwr sectors (399989 MB)
sdd: Write Protect is off
sdd: Mode Sense: 23 00 00 00
SCSI device sdd: drive cache: none
SCSI device sdd: 781228032 512-byte hdwr sectors (399989 MB)
sdd: Write Protect is off
sdd: Mode Sense: 23 00 00 00
SCSI device sdd: drive cache: none
sdd: unknown partition table
sd 1:0:0:0: Attached scsi disk sdd
SCSI device sde: 976541696 512-byte hdwr sectors (499989 MB)
sde: Write Protect is off
sde: Mode Sense: 23 00 00 00
SCSI device sde: drive cache: none
SCSI device sde: 976541696 512-byte hdwr sectors (499989 MB)
sde: Write Protect is off
sde: Mode Sense: 23 00 00 00
SCSI device sde: drive cache: none
sde: unknown partition table
sd 1:0:1:0: Attached scsi disk sde
SCSI device sdf: 976541696 512-byte hdwr sectors (499989 MB)
sdf: Write Protect is off
sdf: Mode Sense: 23 00 00 00
SCSI device sdf: drive cache: none
SCSI device sdf: 976541696 512-byte hdwr sectors (499989 MB)
sdf: Write Protect is off
sdf: Mode Sense: 23 00 00 00
SCSI device sdf: drive cache: none
sdf: unknown partition table
sd 1:0:2:0: Attached scsi disk sdf
SCSI device sdg: 976541696 512-byte hdwr sectors (499989 MB)
sdg: Write Protect is off
sdg: Mode Sense: 23 00 00 00
SCSI device sdg: drive cache: none
SCSI device sdg: 976541696 512-byte hdwr sectors (499989 MB)
sdg: Write Protect is off
sdg: Mode Sense: 23 00 00 00
SCSI device sdg: drive cache: none
sdg: unknown partition table
sd 1:0:3:0: Attached scsi disk sdg
SCSI device sdh: 976541696 512-byte hdwr sectors (499989 MB)
sdh: Write Protect is off
sdh: Mode Sense: 23 00 00 00
SCSI device sdh: drive cache: none
SCSI device sdh: 976541696 512-byte hdwr sectors (499989 MB)
sdh: Write Protect is off
sdh: Mode Sense: 23 00 00 00
SCSI device sdh: drive cache: none
sdh: unknown partition table
sd 1:0:4:0: Attached scsi disk sdh
sdi : very big device. try to use READ CAPACITY(16).
SCSI device sdi: 5468596224 512-byte hdwr sectors (2799921 MB)
sdi: Write Protect is off
sdi: Mode Sense: 23 00 00 00
SCSI device sdi: drive cache: write back, no read (daft)
sdi : very big device. try to use READ CAPACITY(16).
SCSI device sdi: 5468596224 512-byte hdwr sectors (2799921 MB)
sdi: Write Protect is off
sdi: Mode Sense: 23 00 00 00
SCSI device sdi: drive cache: write back, no read (daft)
sdi: unknown partition table
sd 2:0:0:0: Attached scsi disk sdi
SCSI device sdj: 1953083392 512-byte hdwr sectors (999979 MB)
sdj: Write Protect is off
sdj: Mode Sense: 23 00 00 00
SCSI device sdj: drive cache: write back, no read (daft)
SCSI device sdj: 1953083392 512-byte hdwr sectors (999979 MB)
sdj: Write Protect is off
sdj: Mode Sense: 23 00 00 00
SCSI device sdj: drive cache: write back, no read (daft)
sdj: unknown partition table
sd 3:0:0:0: Attached scsi disk sdj
SCSI device sdk: 390721968 512-byte hdwr sectors (200050 MB)
sdk: Write Protect is off
sdk: Mode Sense: 00 3a 00 00
SCSI device sdk: drive cache: write back
SCSI device sdk: 390721968 512-byte hdwr sectors (200050 MB)
sdk: Write Protect is off
sdk: Mode Sense: 00 3a 00 00
SCSI device sdk: drive cache: write back
sdk: sdk1 sdk2 sdk3
sd 4:0:0:0: Attached scsi disk sdk
SCSI device sdl: 390721968 512-byte hdwr sectors (200050 MB)
sdl: Write Protect is off
sdl: Mode Sense: 00 3a 00 00
SCSI device sdl: drive cache: write back
SCSI device sdl: 390721968 512-byte hdwr sectors (200050 MB)
sdl: Write Protect is off
sdl: Mode Sense: 00 3a 00 00
SCSI device sdl: drive cache: write back
sdl: sdl1 sdl2 sdl3
sd 5:0:0:0: Attached scsi disk sdl
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 0:0:1:0: Attached scsi generic sg1 type 0
sd 0:0:2:0: Attached scsi generic sg2 type 0
sd 1:0:0:0: Attached scsi generic sg3 type 0
sd 1:0:1:0: Attached scsi generic sg4 type 0
sd 1:0:2:0: Attached scsi generic sg5 type 0
sd 1:0:3:0: Attached scsi generic sg6 type 0
sd 1:0:4:0: Attached scsi generic sg7 type 0
sd 2:0:0:0: Attached scsi generic sg8 type 0
sd 3:0:0:0: Attached scsi generic sg9 type 0
sd 4:0:0:0: Attached scsi generic sg10 type 0
sd 5:0:0:0: Attached scsi generic sg11 type 0
usbmon: debugfs is not available
ACPI: PCI Interrupt 0000:00:1d.7[D] -> GSI 23 (level, low) -> IRQ 209
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 209, io mem 0xfcbfec00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.0: irq 169, io base 0x0000a880
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 217
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.1: irq 217, io base 0x0000ac00
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 201
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
uhci_hcd 0000:00:1d.2: irq 201, io base 0x0000ac80
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 17 (level, low) -> IRQ 225
md: raid1 personality registered for level 1
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com
EDAC MC: Ver: 2.0.1 Aug 3 2006
EDAC e752x: tolm = 80000, remapbase = ffc000, remaplimit = 0
EDAC MC0: Giving out device to e752x_edac E7520: DEV 0000:00:00.0
ip_conntrack version 2.4 (8192 buckets, 65536 max) - 172 bytes per conntrack
input: AT Translated Set 2 keyboard as /class/input/input0
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
Testing NMI watchdog ... OK.
Starting balanced_irq
Using IPI Shortcut mode
md: Autodetecting RAID arrays.
Time: tsc clocksource has been installed.
md: autorun ...
md: considering sdl3 ...
md: adding sdl3 ...
md: sdl2 has different UUID to sdl3
md: sdl1 has different UUID to sdl3
md: adding sdk3 ...
md: sdk2 has different UUID to sdl3
md: sdk1 has different UUID to sdl3
md: created md3
md: bind<sdk3>
md: bind<sdl3>
md: running: <sdl3><sdk3>
raid1: raid set md3 active with 2 out of 2 mirrors
md: considering sdl2 ...
md: adding sdl2 ...
md: sdl1 has different UUID to sdl2
md: adding sdk2 ...
md: sdk1 has different UUID to sdl2
md: created md1
md: bind<sdk2>
md: bind<sdl2>
md: running: <sdl2><sdk2>
raid1: raid set md1 active with 2 out of 2 mirrors
md: considering sdl1 ...
md: adding sdl1 ...
md: adding sdk1 ...
md: created md0
md: bind<sdk1>
md: bind<sdl1>
md: running: <sdl1><sdk1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: ... autorun DONE.
Filesystem "md1": Disabling barriers, not supported by the underlying device
XFS mounting filesystem md1
Ending clean XFS mount for filesystem: md1
VFS: Mounted root (xfs filesystem) readonly.
Freeing unused kernel memory: 188k freed
Filesystem "md1": Disabling barriers, not supported by the underlying device
kjournald starting. Commit interval 5 seconds
EXT3 FS on md0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Filesystem "dm-0": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-0
Ending clean XFS mount for filesystem: dm-0
Filesystem "dm-31": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-31
Ending clean XFS mount for filesystem: dm-31
Filesystem "dm-32": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-32
Ending clean XFS mount for filesystem: dm-32
Filesystem "dm-33": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-33
Ending clean XFS mount for filesystem: dm-33
Filesystem "dm-34": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-34
Ending clean XFS mount for filesystem: dm-34
Filesystem "dm-35": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-35
Ending clean XFS mount for filesystem: dm-35
Filesystem "dm-38": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-38
Ending clean XFS mount for filesystem: dm-38
Filesystem "dm-39": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-39
Ending clean XFS mount for filesystem: dm-39
Filesystem "dm-40": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-40
Ending clean XFS mount for filesystem: dm-40
Filesystem "dm-41": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-41
Ending clean XFS mount for filesystem: dm-41
Filesystem "dm-42": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-42
Ending clean XFS mount for filesystem: dm-42
Filesystem "dm-43": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-43
Ending clean XFS mount for filesystem: dm-43
Filesystem "dm-44": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-44
Ending clean XFS mount for filesystem: dm-44
Filesystem "dm-45": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-45
Ending clean XFS mount for filesystem: dm-45
Filesystem "dm-46": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-46
Ending clean XFS mount for filesystem: dm-46
Filesystem "dm-48": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-48
Ending clean XFS mount for filesystem: dm-48
Filesystem "dm-49": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-49
Ending clean XFS mount for filesystem: dm-49
Filesystem "dm-51": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-51
Ending clean XFS mount for filesystem: dm-51
Filesystem "dm-53": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-53
Ending clean XFS mount for filesystem: dm-53
Filesystem "dm-57": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-57
Ending clean XFS mount for filesystem: dm-57
Filesystem "dm-58": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-58
Ending clean XFS mount for filesystem: dm-58
Filesystem "dm-59": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-59
Ending clean XFS mount for filesystem: dm-59
Filesystem "dm-47": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-47
Ending clean XFS mount for filesystem: dm-47
Filesystem "dm-52": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-52
Ending clean XFS mount for filesystem: dm-52
Filesystem "dm-54": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-54
Ending clean XFS mount for filesystem: dm-54
Filesystem "dm-56": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-56
Ending clean XFS mount for filesystem: dm-56
Filesystem "dm-36": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-36
Ending clean XFS mount for filesystem: dm-36
Filesystem "dm-37": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-37
Ending clean XFS mount for filesystem: dm-37
Filesystem "dm-50": Disabling barriers, not supported with external log device
XFS mounting filesystem dm-50
Ending clean XFS mount for filesystem: dm-50
Filesystem "dm-55": Disabling barriers, not supported by the underlying device
XFS mounting filesystem dm-55
Ending clean XFS mount for filesystem: dm-55
Adding 2097144k swap on /dev/Log/Swap. Priority:-1 extents:1 across:2097144k
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 201
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xfc00-0xfc07, BIOS settings: hda:pio, hdb:pio
Probing IDE interface ide0...
ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:05:00.0 to 64
sky2 v1.5 addr 0xfcffc000 irq 169 Yukon-EC (0xb6) rev 2
sky2 eth1: addr 00:04:23:bf:d9:63
e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
eth0.20: add 01:00:5e:00:00:01 mcast address to master interface
IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
irq 217: nobody cared (try booting with the "irqpoll" option)
[<c0103a3c>] show_trace_log_lvl+0x152/0x165
[<c0103a5e>] show_trace+0xf/0x13
[<c0103b59>] dump_stack+0x15/0x19
[<c013846e>] __report_bad_irq+0x24/0x7f
[<c0138552>] note_interrupt+0x6b/0xd5
[<c0137ca8>] __do_IRQ+0xf4/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c02d61b7>] uhci_irq+0x27/0x153
[<c02c45e8>] usb_hcd_irq+0x24/0x53
[<c0137b84>] handle_IRQ_event+0x26/0x56
[<c0137c4c>] __do_IRQ+0x98/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c0100e64>] mwait_idle+0x30/0x35
[<c0100d45>] cpu_idle+0x78/0x81
[<c04bf7fb>] start_kernel+0x173/0x19d
[<c0100210>] 0xc0100210
DWARF2 unwinder stuck at 0xc0100210
Leftover inexact backtrace:
=======================
handlers:
[<c02c45c4>] (usb_hcd_irq+0x0/0x53)
Disabling IRQ #217
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Problem: irq 217: nobody cared + backtrace
2006-08-03 14:17 Problem: irq 217: nobody cared + backtrace Jesper Juhl
@ 2006-08-03 16:08 ` Alan Stern
2006-08-04 14:36 ` Jesper Juhl
2006-08-04 15:33 ` Sergio Monteiro Basto
0 siblings, 2 replies; 11+ messages in thread
From: Alan Stern @ 2006-08-03 16:08 UTC (permalink / raw)
To: Jesper Juhl
Cc: Linux Kernel Mailing List, linux-usb-devel, Greg Kroah-Hartman
On Thu, 3 Aug 2006, Jesper Juhl wrote:
> Hi,
>
> A server of mine just dumped a backtrace (below).
> The machine seems to be running fine, but it would be nice to know
> what the cause of this dump is.
> The box is running 2.6.18-rc3-git3
> Full dmesg output is attached.
> If more info than what is below is needed, then just ask and I'll
> provide it if I can.
>
>
> e1000: eth0: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex
> eth0.20: add 01:00:5e:00:00:01 mcast address to master interface
> IA-32 Microcode Update Driver: v1.14a <tigran@veritas.com>
> irq 217: nobody cared (try booting with the "irqpoll" option)
> [<c0103a3c>] show_trace_log_lvl+0x152/0x165
> [<c0103a5e>] show_trace+0xf/0x13
> [<c0103b59>] dump_stack+0x15/0x19
> [<c013846e>] __report_bad_irq+0x24/0x7f
> [<c0138552>] note_interrupt+0x6b/0xd5
> [<c0137ca8>] __do_IRQ+0xf4/0x100
> [<c01050a1>] do_IRQ+0x95/0xbc
> [<c0103502>] common_interrupt+0x1a/0x20
> [<c02d61b7>] uhci_irq+0x27/0x153
> [<c02c45e8>] usb_hcd_irq+0x24/0x53
> [<c0137b84>] handle_IRQ_event+0x26/0x56
> [<c0137c4c>] __do_IRQ+0x98/0x100
> [<c01050a1>] do_IRQ+0x95/0xbc
> [<c0103502>] common_interrupt+0x1a/0x20
> [<c0100e64>] mwait_idle+0x30/0x35
> [<c0100d45>] cpu_idle+0x78/0x81
> [<c04bf7fb>] start_kernel+0x173/0x19d
> [<c0100210>] 0xc0100210
> DWARF2 unwinder stuck at 0xc0100210
> Leftover inexact backtrace:
> =======================
> handlers:
> [<c02c45c4>] (usb_hcd_irq+0x0/0x53)
> Disabling IRQ #217
This beats me. You didn't have any USB devices attached, did you? There
was nothing in the dmesg log about them.
Since no device was using IRQ 217 except for the UHCI controller, there
seem to be only two possibilities. Either the controller is broken and
generating IRQs for no reason at all, or else some other device is using
IRQ 217 when the system thinks it should be using a different line.
Has this happened more than once? In case it happens again, here's how
you can get more information. Turn on CONFIG_USB_DEBUG and
CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
/sys/kernel/debug). Then after the problem occurs, save a copy of
/sys/kernel/debug/uhci/0000:00:1d.1
That will indicate whether the UHCI controller thinks it is sending an
interrupt request.
Alan Stern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Problem: irq 217: nobody cared + backtrace
2006-08-03 16:08 ` Alan Stern
@ 2006-08-04 14:36 ` Jesper Juhl
2006-08-04 15:54 ` Alan Stern
` (2 more replies)
2006-08-04 15:33 ` Sergio Monteiro Basto
1 sibling, 3 replies; 11+ messages in thread
From: Jesper Juhl @ 2006-08-04 14:36 UTC (permalink / raw)
To: Alan Stern; +Cc: Linux Kernel Mailing List, linux-usb-devel, Greg Kroah-Hartman
On 03/08/06, Alan Stern <stern@rowland.harvard.edu> wrote:
>
> Has this happened more than once?
Seems to happen consistently after ~100000 interrupts.
> In case it happens again, here's how
> you can get more information. Turn on CONFIG_USB_DEBUG and
> CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> /sys/kernel/debug). Then after the problem occurs, save a copy of
>
> /sys/kernel/debug/uhci/0000:00:1d.1
>
# cat /sys/kernel/debug/uhci/0000:00:1d.1
Root-hub state: auto-stopped FSBR: 0
HC status
usbcmd = 0048 Maxp32 CF EGSM
usbstat = 0020 HCHalted
usbint = 0002
usbfrnum = (1)160
flbaseadd = 37428160
sof = 40
stat1 = 0080
stat2 = 0080
Most recent frame: 458 (88) Last ISO frame: 458 (88)
> That will indicate whether the UHCI controller thinks it is sending an
> interrupt request.
>
And just for completenes, here's the backtrace I got just before
saving the above info :
irq 217: nobody cared (try booting with the "irqpoll" option)
[<c0103a3c>] show_trace_log_lvl+0x152/0x165
[<c0103a5e>] show_trace+0xf/0x13
[<c0103b59>] dump_stack+0x15/0x19
[<c013846e>] __report_bad_irq+0x24/0x7f
[<c0138552>] note_interrupt+0x6b/0xd5
[<c0137ca8>] __do_IRQ+0xf4/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c0137b7e>] handle_IRQ_event+0x20/0x56
[<c0137c4c>] __do_IRQ+0x98/0x100
[<c01050a1>] do_IRQ+0x95/0xbc
[<c0103502>] common_interrupt+0x1a/0x20
[<c0100e64>] mwait_idle+0x30/0x35
[<c0100d45>] cpu_idle+0x78/0x81
[<c04cc7fb>] start_kernel+0x173/0x19d
[<c0100210>] 0xc0100210
DWARF2 unwinder stuck at 0xc0100210
Leftover inexact backtrace:
=======================
handlers:
[<c02c5c22>] (usb_hcd_irq+0x0/0x53)
Disabling IRQ #217
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Problem: irq 217: nobody cared + backtrace
2006-08-04 14:36 ` Jesper Juhl
@ 2006-08-04 15:54 ` Alan Stern
2006-08-04 22:40 ` Jesper Juhl
2006-08-04 16:23 ` Sergio Monteiro Basto
2006-08-07 20:52 ` Sergio Monteiro Basto
2 siblings, 1 reply; 11+ messages in thread
From: Alan Stern @ 2006-08-04 15:54 UTC (permalink / raw)
To: Jesper Juhl
Cc: Linux Kernel Mailing List, linux-usb-devel, Greg Kroah-Hartman
On Fri, 4 Aug 2006, Jesper Juhl wrote:
> On 03/08/06, Alan Stern <stern@rowland.harvard.edu> wrote:
> >
> > Has this happened more than once?
>
> Seems to happen consistently after ~100000 interrupts.
>
> > In case it happens again, here's how
> > you can get more information. Turn on CONFIG_USB_DEBUG and
> > CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> > /sys/kernel/debug). Then after the problem occurs, save a copy of
> >
> > /sys/kernel/debug/uhci/0000:00:1d.1
> >
>
> # cat /sys/kernel/debug/uhci/0000:00:1d.1
> Root-hub state: auto-stopped FSBR: 0
> HC status
> usbcmd = 0048 Maxp32 CF EGSM
> usbstat = 0020 HCHalted
> usbint = 0002
> usbfrnum = (1)160
> flbaseadd = 37428160
> sof = 40
> stat1 = 0080
> stat2 = 0080
> Most recent frame: 458 (88) Last ISO frame: 458 (88)
>
>
> > That will indicate whether the UHCI controller thinks it is sending an
> > interrupt request.
And it shows that the controller is idle. No IRQ should be pending.
> And just for completenes, here's the backtrace I got just before
> saving the above info :
>
> irq 217: nobody cared (try booting with the "irqpoll" option)
> [<c0103a3c>] show_trace_log_lvl+0x152/0x165
> [<c0103a5e>] show_trace+0xf/0x13
> [<c0103b59>] dump_stack+0x15/0x19
> [<c013846e>] __report_bad_irq+0x24/0x7f
> [<c0138552>] note_interrupt+0x6b/0xd5
> [<c0137ca8>] __do_IRQ+0xf4/0x100
> [<c01050a1>] do_IRQ+0x95/0xbc
> [<c0103502>] common_interrupt+0x1a/0x20
> [<c0137b7e>] handle_IRQ_event+0x20/0x56
> [<c0137c4c>] __do_IRQ+0x98/0x100
> [<c01050a1>] do_IRQ+0x95/0xbc
> [<c0103502>] common_interrupt+0x1a/0x20
> [<c0100e64>] mwait_idle+0x30/0x35
> [<c0100d45>] cpu_idle+0x78/0x81
> [<c04cc7fb>] start_kernel+0x173/0x19d
> [<c0100210>] 0xc0100210
> DWARF2 unwinder stuck at 0xc0100210
> Leftover inexact backtrace:
> =======================
> handlers:
> [<c02c5c22>] (usb_hcd_irq+0x0/0x53)
> Disabling IRQ #217
Just as before.
I can't tell you what's causing this to happen, except that it appears to
be some sort of hardware problem. Since it doesn't seem to cause any harm
you could just live with it.
Or, if you're not using any full-speed or low-speed USB devices, you could
simply prevent uhci-hcd from loading at all. Then IRQ 217 wouldn't get
enabled in the first place.
Alan Stern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Problem: irq 217: nobody cared + backtrace
2006-08-04 15:54 ` Alan Stern
@ 2006-08-04 22:40 ` Jesper Juhl
2006-08-05 14:48 ` Alan Stern
0 siblings, 1 reply; 11+ messages in thread
From: Jesper Juhl @ 2006-08-04 22:40 UTC (permalink / raw)
To: Alan Stern; +Cc: Linux Kernel Mailing List, linux-usb-devel, Greg Kroah-Hartman
On 04/08/06, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Fri, 4 Aug 2006, Jesper Juhl wrote:
>
> > On 03/08/06, Alan Stern <stern@rowland.harvard.edu> wrote:
> > >
> > > Has this happened more than once?
> >
> > Seems to happen consistently after ~100000 interrupts.
> >
> > > In case it happens again, here's how
> > > you can get more information. Turn on CONFIG_USB_DEBUG and
> > > CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> > > /sys/kernel/debug). Then after the problem occurs, save a copy of
> > >
> > > /sys/kernel/debug/uhci/0000:00:1d.1
> > >
> >
> > # cat /sys/kernel/debug/uhci/0000:00:1d.1
> > Root-hub state: auto-stopped FSBR: 0
> > HC status
> > usbcmd = 0048 Maxp32 CF EGSM
> > usbstat = 0020 HCHalted
> > usbint = 0002
> > usbfrnum = (1)160
> > flbaseadd = 37428160
> > sof = 40
> > stat1 = 0080
> > stat2 = 0080
> > Most recent frame: 458 (88) Last ISO frame: 458 (88)
> >
> >
> > > That will indicate whether the UHCI controller thinks it is sending an
> > > interrupt request.
>
> And it shows that the controller is idle. No IRQ should be pending.
>
> > And just for completenes, here's the backtrace I got just before
> > saving the above info :
> >
> > irq 217: nobody cared (try booting with the "irqpoll" option)
> > [<c0103a3c>] show_trace_log_lvl+0x152/0x165
> > [<c0103a5e>] show_trace+0xf/0x13
> > [<c0103b59>] dump_stack+0x15/0x19
> > [<c013846e>] __report_bad_irq+0x24/0x7f
> > [<c0138552>] note_interrupt+0x6b/0xd5
> > [<c0137ca8>] __do_IRQ+0xf4/0x100
> > [<c01050a1>] do_IRQ+0x95/0xbc
> > [<c0103502>] common_interrupt+0x1a/0x20
> > [<c0137b7e>] handle_IRQ_event+0x20/0x56
> > [<c0137c4c>] __do_IRQ+0x98/0x100
> > [<c01050a1>] do_IRQ+0x95/0xbc
> > [<c0103502>] common_interrupt+0x1a/0x20
> > [<c0100e64>] mwait_idle+0x30/0x35
> > [<c0100d45>] cpu_idle+0x78/0x81
> > [<c04cc7fb>] start_kernel+0x173/0x19d
> > [<c0100210>] 0xc0100210
> > DWARF2 unwinder stuck at 0xc0100210
> > Leftover inexact backtrace:
> > =======================
> > handlers:
> > [<c02c5c22>] (usb_hcd_irq+0x0/0x53)
> > Disabling IRQ #217
>
> Just as before.
>
> I can't tell you what's causing this to happen, except that it appears to
> be some sort of hardware problem.
Hmm, the odd thing is that there are no USB devices connected at all.
> Since it doesn't seem to cause any harm
> you could just live with it.
>
> Or, if you're not using any full-speed or low-speed USB devices, you could
> simply prevent uhci-hcd from loading at all. Then IRQ 217 wouldn't get
> enabled in the first place.
>
True, that just seems like a hack...
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Problem: irq 217: nobody cared + backtrace
2006-08-04 22:40 ` Jesper Juhl
@ 2006-08-05 14:48 ` Alan Stern
0 siblings, 0 replies; 11+ messages in thread
From: Alan Stern @ 2006-08-05 14:48 UTC (permalink / raw)
To: Jesper Juhl
Cc: Linux Kernel Mailing List, linux-usb-devel, Greg Kroah-Hartman
On Sat, 5 Aug 2006, Jesper Juhl wrote:
> > Just as before.
> >
> > I can't tell you what's causing this to happen, except that it appears to
> > be some sort of hardware problem.
>
> Hmm, the odd thing is that there are no USB devices connected at all.
My guess is that this has nothing to do with the USB controller, other
than the fact that IRQ 217 is enabled because the controller uses it.
Probably the real problem, the unhandled interrupt requests, comes from
some other device entirely.
> > Since it doesn't seem to cause any harm
> > you could just live with it.
> >
> > Or, if you're not using any full-speed or low-speed USB devices, you could
> > simply prevent uhci-hcd from loading at all. Then IRQ 217 wouldn't get
> > enabled in the first place.
> >
> True, that just seems like a hack...
It is. Without knowing the underlying cause of the problem, it's the best
I can suggest.
If you compare /proc/interrupts with earlier versions of the kernel (where
the problem doesn't occur), does it look the same?
Alan Stern
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Problem: irq 217: nobody cared + backtrace
2006-08-04 14:36 ` Jesper Juhl
2006-08-04 15:54 ` Alan Stern
@ 2006-08-04 16:23 ` Sergio Monteiro Basto
2006-08-07 20:52 ` Sergio Monteiro Basto
2 siblings, 0 replies; 11+ messages in thread
From: Sergio Monteiro Basto @ 2006-08-04 16:23 UTC (permalink / raw)
To: Jesper Juhl
Cc: Alan Stern, Linux Kernel Mailing List, linux-usb-devel,
Greg Kroah-Hartman
On Fri, 2006-08-04 at 16:36 +0200, Jesper Juhl wrote:
> >
> > Has this happened more than once?
>
> Seems to happen consistently after ~100000 interrupts.
yap , I remember this same number when I cat /proc/interrupts
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Problem: irq 217: nobody cared + backtrace
2006-08-04 14:36 ` Jesper Juhl
2006-08-04 15:54 ` Alan Stern
2006-08-04 16:23 ` Sergio Monteiro Basto
@ 2006-08-07 20:52 ` Sergio Monteiro Basto
2 siblings, 0 replies; 11+ messages in thread
From: Sergio Monteiro Basto @ 2006-08-07 20:52 UTC (permalink / raw)
To: Jesper Juhl
Cc: Alan Stern, Linux Kernel Mailing List, linux-usb-devel,
Greg Kroah-Hartman
[-- Attachment #1: Type: text/plain, Size: 3803 bytes --]
my system is much different, but I got similar problems
http://bugme.osdl.org/show_bug.cgi?id=6419#c17
irq 201: nobody cared (try booting with the "irqpoll" option)
Call Trace:
[<ffffffff8026a20a>] dump_stack+0x12/0x17
[<ffffffff802b6c26>] __report_bad_irq+0x30/0x7d
[<ffffffff802b6e46>] note_interrupt+0x1d3/0x219
[<ffffffff802b6383>] __do_IRQ+0xc8/0x107
[<ffffffff8026b166>] do_IRQ+0xe7/0xf5
[<ffffffff8025d189>] ret_from_intr+0x0/0xa
DWARF2 unwinder stuck at ret_from_intr+0x0/0xa
Leftover inexact backtrace:
<IRQ> <EOI> [<ffffffff80230d50>] unix_poll+0x0/0x99
[<ffffffff802569ed>] mwait_idle+0x36/0x4a
[<ffffffff8024888d>] cpu_idle+0x95/0xb8
[<ffffffff806da842>] start_kernel+0x220/0x225
[<ffffffff806da28a>] _sinittext+0x28a/0x28e
handlers:
[<ffffffff880eaaf5>] (rhine_interrupt+0x0/0xae3 [via_rhine])
Disabling IRQ #201
root@monteirov:~#cat /proc/interrupts
CPU0 CPU1
0: 356842 312644 IO-APIC-edge timer
1: 586 711 IO-APIC-edge i8042
6: 5 0 IO-APIC-edge floppy
7: 2 0 IO-APIC-edge parport0
8: 0 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
12: 33214 32075 IO-APIC-edge i8042
15: 11161 11127 IO-APIC-edge ide1
193: 65857 9444 IO-APIC-level libata
201: 100000 0 IO-APIC-level eth0
^^^^^^
209: 91593 91062 IO-APIC-level uhci_hcd:usb1,
uhci_hcd:usb2, uhci_hcd:usb3, uhci_hcd:usb4, ehci_hcd:usb5
217: 1151 538 IO-APIC-level VIA8237
225: 49661 49438 IO-APIC-level nvidia
NMI: 438 403
LOC: 669481 669457
ERR: 0
MIS: 0
On Fri, 2006-08-04 at 16:36 +0200, Jesper Juhl wrote:
> On 03/08/06, Alan Stern <stern@rowland.harvard.edu> wrote:
> >
> > Has this happened more than once?
>
> Seems to happen consistently after ~100000 interrupts.
>
> > In case it happens again, here's how
> > you can get more information. Turn on CONFIG_USB_DEBUG and
> > CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> > /sys/kernel/debug). Then after the problem occurs, save a copy of
> >
> > /sys/kernel/debug/uhci/0000:00:1d.1
> >
>
> # cat /sys/kernel/debug/uhci/0000:00:1d.1
> Root-hub state: auto-stopped FSBR: 0
> HC status
> usbcmd = 0048 Maxp32 CF EGSM
> usbstat = 0020 HCHalted
> usbint = 0002
> usbfrnum = (1)160
> flbaseadd = 37428160
> sof = 40
> stat1 = 0080
> stat2 = 0080
> Most recent frame: 458 (88) Last ISO frame: 458 (88)
>
>
> > That will indicate whether the UHCI controller thinks it is sending an
> > interrupt request.
> >
>
> And just for completenes, here's the backtrace I got just before
> saving the above info :
>
> irq 217: nobody cared (try booting with the "irqpoll" option)
> [<c0103a3c>] show_trace_log_lvl+0x152/0x165
> [<c0103a5e>] show_trace+0xf/0x13
> [<c0103b59>] dump_stack+0x15/0x19
> [<c013846e>] __report_bad_irq+0x24/0x7f
> [<c0138552>] note_interrupt+0x6b/0xd5
> [<c0137ca8>] __do_IRQ+0xf4/0x100
> [<c01050a1>] do_IRQ+0x95/0xbc
> [<c0103502>] common_interrupt+0x1a/0x20
> [<c0137b7e>] handle_IRQ_event+0x20/0x56
> [<c0137c4c>] __do_IRQ+0x98/0x100
> [<c01050a1>] do_IRQ+0x95/0xbc
> [<c0103502>] common_interrupt+0x1a/0x20
> [<c0100e64>] mwait_idle+0x30/0x35
> [<c0100d45>] cpu_idle+0x78/0x81
> [<c04cc7fb>] start_kernel+0x173/0x19d
> [<c0100210>] 0xc0100210
> DWARF2 unwinder stuck at 0xc0100210
> Leftover inexact backtrace:
> =======================
> handlers:
> [<c02c5c22>] (usb_hcd_irq+0x0/0x53)
> Disabling IRQ #217
>
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Problem: irq 217: nobody cared + backtrace
2006-08-03 16:08 ` Alan Stern
2006-08-04 14:36 ` Jesper Juhl
@ 2006-08-04 15:33 ` Sergio Monteiro Basto
2006-08-04 17:33 ` Greg KH
1 sibling, 1 reply; 11+ messages in thread
From: Sergio Monteiro Basto @ 2006-08-04 15:33 UTC (permalink / raw)
To: Alan Stern
Cc: Jesper Juhl, Linux Kernel Mailing List, linux-usb-devel,
Greg Kroah-Hartman
On Thu, 2006-08-03 at 12:08 -0400, Alan Stern wrote:
> Has this happened more than once?
In my case (it very different), all the time.
I also got :
uhci_hcd 0000:00:10.1: host controller process error, something bad
happened!
uhci_hcd 0000:00:10.1: host controller halted, very bad!
uhci_hcd 0000:00:10.1: HC died; cleaning up
usb 3-2: USB disconnect, address 2
> In case it happens again, here's how
> you can get more information. Turn on CONFIG_USB_DEBUG and
> CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> /sys/kernel/debug). Then after the problem occurs, save a copy of
>
> /sys/kernel/debug/uhci/0000:00:1d.1
can you explain to me how I mount debugfs filesystem ? please
Thanks,
--
Sérgio M. B.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Problem: irq 217: nobody cared + backtrace
2006-08-04 15:33 ` Sergio Monteiro Basto
@ 2006-08-04 17:33 ` Greg KH
0 siblings, 0 replies; 11+ messages in thread
From: Greg KH @ 2006-08-04 17:33 UTC (permalink / raw)
To: Sergio Monteiro Basto
Cc: Alan Stern, Jesper Juhl, Linux Kernel Mailing List,
linux-usb-devel
On Fri, Aug 04, 2006 at 04:33:11PM +0100, Sergio Monteiro Basto wrote:
> On Thu, 2006-08-03 at 12:08 -0400, Alan Stern wrote:
> > In case it happens again, here's how
> > you can get more information. Turn on CONFIG_USB_DEBUG and
> > CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> > /sys/kernel/debug). Then after the problem occurs, save a copy of
> >
> > /sys/kernel/debug/uhci/0000:00:1d.1
>
> can you explain to me how I mount debugfs filesystem ? please
as root:
mount -t debugfs none /sys/kernel/debug
thanks,
greg k-h
^ permalink raw reply [flat|nested] 11+ messages in thread
[parent not found: <Pine.LNX.4.44L0.0608041309360.7905-100000@iolanthe.rowland.org>]
* Re: Problem: irq 217: nobody cared + backtrace
[not found] <Pine.LNX.4.44L0.0608041309360.7905-100000@iolanthe.rowland.org>
@ 2006-08-07 1:54 ` Sergio Monteiro Basto
0 siblings, 0 replies; 11+ messages in thread
From: Sergio Monteiro Basto @ 2006-08-07 1:54 UTC (permalink / raw)
To: Alan Stern; +Cc: Linux Kernel Mailing List, linux-usb-devel, Greg Kroah-Hartman
[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]
On Fri, 2006-08-04 at 13:11 -0400, Alan Stern wrote:
> On Fri, 4 Aug 2006, Sergio Monteiro Basto wrote:
>
> > > > I also got :
> > > > uhci_hcd 0000:00:10.1: host controller process error, something bad
> > > > happened!
> > > > uhci_hcd 0000:00:10.1: host controller halted, very bad!
> > > > uhci_hcd 0000:00:10.1: HC died; cleaning up
> > > > usb 3-2: USB disconnect, address 2
> > > >
> > > > > In case it happens again, here's how
> > > > > you can get more information. Turn on CONFIG_USB_DEBUG and
> > > > > CONFIG_DEBUG_FS, and mount a debugfs filesystem somewhere (say
> > > > > /sys/kernel/debug). Then after the problem occurs, save a copy of
> > > > >
> > > > > /sys/kernel/debug/uhci/0000:00:1d.1
> > > >
> > > > can you explain to me how I mount debugfs filesystem ? please
> > >
> > > You don't need debugfs to solve the problem shown above.
> > >
> > > What version of the kernel are you using?
> > >
> > > Alan Stern
> >
> > http://bugme.osdl.org/show_bug.cgi?id=6419#c16
> > http://bugme.osdl.org/show_bug.cgi?id=6419#c19
> > all the time, with 2.6.18-rc3
>
> Here is a patch which should fix the "host controller process error"
> problem:
>
> http://marc.theaimsgroup.com/?l=linux-usb-devel&m=115435540308759&w=2
>
yes! I am testing 2.6.18-rc3-git7.bz2 which have your patch, with
CONFIG_USB_DEBUG and CONFIG_DEBUG_FS on and I can googling :), it is
working. I have done a stress test with azureus and still working!
Tomorrow I will test the irq 201, 209 or 217 nobody care.
Many thanks Alan,
--
Sérgio M. B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2006-08-07 20:52 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-08-03 14:17 Problem: irq 217: nobody cared + backtrace Jesper Juhl
2006-08-03 16:08 ` Alan Stern
2006-08-04 14:36 ` Jesper Juhl
2006-08-04 15:54 ` Alan Stern
2006-08-04 22:40 ` Jesper Juhl
2006-08-05 14:48 ` Alan Stern
2006-08-04 16:23 ` Sergio Monteiro Basto
2006-08-07 20:52 ` Sergio Monteiro Basto
2006-08-04 15:33 ` Sergio Monteiro Basto
2006-08-04 17:33 ` Greg KH
[not found] <Pine.LNX.4.44L0.0608041309360.7905-100000@iolanthe.rowland.org>
2006-08-07 1:54 ` Sergio Monteiro Basto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox