Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Kubo Hiroshi h-k...@geisya.or.jp writes: Hi. Do the functions 'i8xx_irq_handler' and 'queue_work_on' always appear in the call trace? I can't remember. If I encounter the problem again, I will check it. After the last reply, I encountered the same problems twice. In the both problems, the functions 'i8xx_irq_handler' and 'queue_work_on' appeared in the call trace. This is most likely a duplicate of http://bugs.debian.org/692607 I am sorry I haven't had any time following up on that. It seems that the necessarry debugging output has been collected by Сергей, confirming the suspicions. But I still don't see how this corruption can happen, and the fact that the machine crashes even if we ignore it shows that it is not limited to this particular struct. It's just one of the points where we will crash after such corruptions because of the BUG_ON in kernel/workqueue.c Bjørn -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871uc18zk3@nemi.mork.no
Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Hi. Do the functions 'i8xx_irq_handler' and 'queue_work_on' always appear in the call trace? I can't remember. If I encounter the problem again, I will check it. After the last reply, I encountered the same problems twice. In the both problems, the functions 'i8xx_irq_handler' and 'queue_work_on' appeared in the call trace. --- Kubo Hiroshi h-k...@geisya.or.jp -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130226.014217.274437003.h-k...@geisya.or.jp
Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Hi. Control: severity -1 grave Sorry, no. This package works for most people, so it doesn't 'break the whole system'. I see. I haven't experience the same crash before the last update of the linux-image package. Do the functions 'i8xx_irq_handler' and 'queue_work_on' always appear in the call trace? I can't remember. If I encounter the problem again, I will check it. The attached file is another information about the machine. I didn't receive any attachment with this mail. Oops. I forgot to attach it. Here it is. --- Kubo Hiroshi h-k...@geisya.or.jp $ cat /proc/interrupts CPU0 CPU1 0: 42 0 IO-APIC-edge timer 1:336 0 IO-APIC-edge i8042 6: 3 0 IO-APIC-edge floppy 7: 0 0 IO-APIC-edge parport0 8: 1 0 IO-APIC-edge rtc0 9: 0 0 IO-APIC-fasteoi acpi 12: 5444 0 IO-APIC-edge i8042 14: 0 0 IO-APIC-edge ata_piix 15:589 0 IO-APIC-edge ata_piix 16: 1413 0 IO-APIC-fasteoi uhci_hcd:usb2, uhci_hcd:usb5, i915 17:192 0 IO-APIC-fasteoi snd_intel8x0 18: 30562 0 IO-APIC-fasteoi uhci_hcd:usb4, ata_piix 19: 0 0 IO-APIC-fasteoi uhci_hcd:usb3 23: 1203 0 IO-APIC-fasteoi ehci_hcd:usb1, eth0 NMI: 6 4 Non-maskable interrupts LOC: 33111 27203 Local timer interrupts SPU: 0 0 Spurious interrupts PMI: 6 4 Performance monitoring interrupts IWI: 0 0 IRQ work interrupts RES: 14142 20913 Rescheduling interrupts CAL:412787 Function call interrupts TLB: 1903 1773 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP: 2 2 Machine check polls ERR: 0 MIS: 0 $ cat /proc/ioports -001f : dma1 0020-0021 : pic1 0040-0043 : timer0 0050-0053 : timer1 0060-0060 : keyboard 0064-0064 : keyboard 0070-0073 : rtc0 0080-008f : dma page reg 00a0-00a1 : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : :00:1f.1 0170-0177 : ata_piix 01f0-01f7 : :00:1f.1 01f0-01f7 : ata_piix 0201-0207 : ns558-pnp 0294-0297 : pnp 00:01 02f8-02ff : serial 0376-0376 : :00:1f.1 0376-0376 : ata_piix 0378-037a : parport0 03c0-03df : vga+ 03f2-03f2 : floppy 03f4-03f5 : floppy 03f6-03f6 : :00:1f.1 03f6-03f6 : ata_piix 03f7-03f7 : floppy 03f8-03ff : serial 0400-04bf : pnp 00:0d 0400-0403 : ACPI PM1a_EVT_BLK 0404-0405 : ACPI PM1a_CNT_BLK 0408-040b : ACPI PM_TMR 0428-042f : ACPI GPE0_BLK 0430-0433 : iTCO_wdt 0460-047f : iTCO_wdt 04d0-04d1 : pnp 00:01 0500-051f : :00:1f.3 0500-051f : i801_smbus 0a78-0a7b : pnp 00:01 0b78-0b7b : pnp 00:01 0bbc-0bbf : pnp 00:01 0cf8-0cff : PCI conf1 0e78-0e7b : pnp 00:01 0f78-0f7b : pnp 00:01 0fbc-0fbf : pnp 00:01 a000-afff : PCI Bus :01 a000-a0ff : :01:0d.0 a000-a0ff : 8139too b000-b01f : :00:1d.0 b000-b01f : uhci_hcd b400-b41f : :00:1d.1 b400-b41f : uhci_hcd b800-b81f : :00:1d.2 b800-b81f : uhci_hcd bc00-bc1f : :00:1d.3 bc00-bc1f : uhci_hcd c000-c007 : :00:02.0 c400-c407 : :00:1f.2 c400-c407 : ata_piix c800-c803 : :00:1f.2 c800-c803 : ata_piix cc00-cc07 : :00:1f.2 cc00-cc07 : ata_piix d000-d003 : :00:1f.2 d000-d003 : ata_piix d400-d40f : :00:1f.2 d400-d40f : ata_piix dc00-dcff : :00:1f.5 dc00-dcff : Intel ICH5 e000-e03f : :00:1f.5 e000-e03f : Intel ICH5 f000-f00f : :00:1f.1 f000-f00f : ata_piix $ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 3 model name : Intel(R) Pentium(R) 4 CPU 3.00GHz stepping: 4 microcode : 0xe cpu MHz : 2000.047 cache size : 1024 KB physical id : 0 siblings: 2 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 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 constant_tsc pebs bts pni dtes64 monitor ds_cpl cid xtpr bogomips: 4000.09 clflush size: 64 cache_alignment : 128 address sizes : 36 bits physical, 32 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 3 model name : Intel(R) Pentium(R) 4 CPU 3.00GHz stepping: 4 microcode : 0xe cpu MHz : 2000.047 cache size : 1024 KB physical id : 0 siblings: 2 core id
Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Control: severity -1 grave Hi dear, After I repoted the crash, I experienced the same crashes for serveral times on the same machine. Most common situation is shutting down process, but not limited to it. I haven't experience the same crash before the last update of the linux-image package. The attached file is another information about the machine. Thank you in advance. --- Kubo Hiroshi h-k...@geisya.or.jp -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130222.233714.492728149.h-k...@geisya.or.jp
Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Control: severity -1 important On Fri, 2013-02-22 at 23:37 +0900, Kubo Hiroshi wrote: Control: severity -1 grave Sorry, no. This package works for most people, so it doesn't 'break the whole system'. Hi dear, After I repoted the crash, I experienced the same crashes for serveral times on the same machine. Most common situation is shutting down process, but not limited to it. I haven't experience the same crash before the last update of the linux-image package. Do the functions 'i8xx_irq_handler' and 'queue_work_on' always appear in the call trace? The attached file is another information about the machine. I didn't receive any attachment with this mail. Ben. -- Ben Hutchings Sturgeon's Law: Ninety percent of everything is crap. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#700739: Kernel panic - not syncing: Fatal exception in interrupt
Processing control commands: severity -1 important Bug #700739 [src:linux] Kernel panic - not syncing: Fatal exception in interrupt Severity set to 'important' from 'grave' -- 700739: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b700739.136157158329539.transcr...@bugs.debian.org
