* Re: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours [not found] ` <bug-10455-10286-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/> @ 2008-04-15 8:32 ` Andrew Morton 2008-04-15 8:39 ` Bart Van Assche 0 siblings, 1 reply; 5+ messages in thread From: Andrew Morton @ 2008-04-15 8:32 UTC (permalink / raw) To: bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w Cc: bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r, linux-wireless-u79uwXL29TY76Z2rM5mHXA, linux-acpi-u79uwXL29TY76Z2rM5mHXA (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Tue, 15 Apr 2008 01:16:39 -0700 (PDT) bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=10455 > > Summary: Kernel lockup when iwl3945 modules is loaded after a few > hours > Product: Drivers > Version: 2.5 > KernelVersion: 2.6.25-rc9 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: network-wireless > AssignedTo: drivers_network-wireless-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org > ReportedBy: bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org > > > Latest working kernel version: (not known) > Earliest failing kernel version: 2.6.25-rc9 hm, why? Has this machine never run earlier kernels? > Distribution: Ubuntu Linux 7.10 > Hardware Environment: Acer Aspire laptop model 5633WLMi > Software Environment: Ubuntu Linux 7.10, 32 bit mode. > Problem Description: When the iwl3945 module is loaded, the kernel locks up > after a few hours. This problem does not occur when the iwl3945 module is not > loaded. > > Steps to reproduce: Boot the system. > > The following kernel messages look suspicious: > > Apr 14 20:16:24 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:16:24 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:18:28 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:18:28 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:20:32 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:20:32 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:22:36 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:22:36 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:24:40 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:24:40 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:26:44 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:26:44 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:28:48 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:28:48 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:30:52 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:30:52 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:32:56 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:32:56 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:35:00 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:35:00 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:37:04 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:37:04 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:39:08 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:39:08 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:41:12 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:41:12 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:43:16 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:43:16 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:45:20 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:45:20 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:47:24 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:47:24 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:49:28 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:49:28 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:51:32 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:51:32 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:53:36 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:53:36 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:55:40 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:55:40 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:57:44 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:57:44 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 20:59:48 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 20:59:48 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 21:01:52 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 21:01:52 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 21:03:56 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 21:03:56 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled > Apr 14 21:06:00 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > (level, low) -> IRQ 19 > Apr 14 21:06:00 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > disabled Yes, that does look like an ACPI problem. But one would expect it to kill the interface immediately, not several hours later. Can you send the /proc/interrupts contents? -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours 2008-04-15 8:32 ` [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours Andrew Morton @ 2008-04-15 8:39 ` Bart Van Assche [not found] ` <e2e108260804150139kf816be5m91e6206853a0d755-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 0 siblings, 1 reply; 5+ messages in thread From: Bart Van Assche @ 2008-04-15 8:39 UTC (permalink / raw) To: Andrew Morton; +Cc: bugme-daemon, linux-wireless, linux-acpi On Tue, Apr 15, 2008 at 10:32 AM, Andrew Morton <akpm@linux-foundation.org> wrote: > > > Latest working kernel version: (not known) > > Earliest failing kernel version: 2.6.25-rc9 > > hm, why? Has this machine never run earlier kernels? 2.6.22-14 works fine on the same hardware. This is the kernel provided by Ubuntu. > > Apr 14 21:06:00 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > > (level, low) -> IRQ 19 > > Apr 14 21:06:00 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > > disabled > > Yes, that does look like an ACPI problem. But one would expect it to kill > the interface immediately, not several hours later. > > Can you send the /proc/interrupts contents? Here it is: CPU0 CPU1 0: 996478 0 IO-APIC-edge timer 1: 30 0 IO-APIC-edge i8042 8: 7 0 IO-APIC-edge rtc 9: 57710 0 IO-APIC-fasteoi acpi 12: 132 0 IO-APIC-edge i8042 14: 31294 11519 IO-APIC-edge ata_piix 15: 69158 0 IO-APIC-edge ata_piix 16: 85016 0 IO-APIC-fasteoi uhci_hcd:usb4, i915@pci:0000:00:02.0 18: 15921 0 IO-APIC-fasteoi uhci_hcd:usb3 19: 0 0 IO-APIC-fasteoi uhci_hcd:usb2 21: 79770 60509 IO-APIC-fasteoi eth0 22: 5811 0 IO-APIC-fasteoi HDA Intel 23: 3 0 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5 NMI: 0 0 Non-maskable interrupts LOC: 509 996926 Local timer interrupts RES: 29774 84400 Rescheduling interrupts CAL: 62 28154 function call interrupts TLB: 868 1262 TLB shootdowns TRM: 0 0 Thermal event interrupts SPU: 0 0 Spurious interrupts ERR: 0 MIS: 0 Bart. ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <e2e108260804150139kf816be5m91e6206853a0d755-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours [not found] ` <e2e108260804150139kf816be5m91e6206853a0d755-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> @ 2008-04-15 9:01 ` Andrew Morton [not found] ` <20080415020103.cd8e17f4.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> 0 siblings, 1 reply; 5+ messages in thread From: Andrew Morton @ 2008-04-15 9:01 UTC (permalink / raw) To: Bart Van Assche Cc: bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r, linux-wireless-u79uwXL29TY76Z2rM5mHXA, linux-acpi-u79uwXL29TY76Z2rM5mHXA On Tue, 15 Apr 2008 10:39:17 +0200 "Bart Van Assche" <bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > On Tue, Apr 15, 2008 at 10:32 AM, Andrew Morton > <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> wrote: > > > > > Latest working kernel version: (not known) > > > Earliest failing kernel version: 2.6.25-rc9 > > > > hm, why? Has this machine never run earlier kernels? > > 2.6.22-14 works fine on the same hardware. This is the kernel provided > by Ubuntu. OK, thanks, so it's a regression but we don't know if it's a post-2.6.25 regression. > > > Apr 14 21:06:00 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 > > > (level, low) -> IRQ 19 > > > Apr 14 21:06:00 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 > > > disabled > > > > Yes, that does look like an ACPI problem. But one would expect it to kill > > the interface immediately, not several hours later. > > > > Can you send the /proc/interrupts contents? > > Here it is: > > CPU0 CPU1 > 0: 996478 0 IO-APIC-edge timer > 1: 30 0 IO-APIC-edge i8042 > 8: 7 0 IO-APIC-edge rtc > 9: 57710 0 IO-APIC-fasteoi acpi > 12: 132 0 IO-APIC-edge i8042 > 14: 31294 11519 IO-APIC-edge ata_piix > 15: 69158 0 IO-APIC-edge ata_piix > 16: 85016 0 IO-APIC-fasteoi uhci_hcd:usb4, > i915@pci:0000:00:02.0 > 18: 15921 0 IO-APIC-fasteoi uhci_hcd:usb3 > 19: 0 0 IO-APIC-fasteoi uhci_hcd:usb2 > 21: 79770 60509 IO-APIC-fasteoi eth0 > 22: 5811 0 IO-APIC-fasteoi HDA Intel > 23: 3 0 IO-APIC-fasteoi uhci_hcd:usb1, ehci_hcd:usb5 > NMI: 0 0 Non-maskable interrupts > LOC: 509 996926 Local timer interrupts > RES: 29774 84400 Rescheduling interrupts > CAL: 62 28154 function call interrupts > TLB: 868 1262 TLB shootdowns > TRM: 0 0 Thermal event interrupts > SPU: 0 0 Spurious interrupts > ERR: 0 > MIS: 0 hm, OK. I'd suggest that you raise a separate report against acpi_config-interrupts-ztI5WcYan/vQLgFONoPN62D2FQJk+8+b@public.gmane.org for this one - it does appear to be unrelated, I think. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <20080415020103.cd8e17f4.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>]
* Re: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours [not found] ` <20080415020103.cd8e17f4.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org> @ 2008-04-15 15:15 ` Bjorn Helgaas 2008-04-15 17:22 ` Chatre, Reinette 0 siblings, 1 reply; 5+ messages in thread From: Bjorn Helgaas @ 2008-04-15 15:15 UTC (permalink / raw) To: Andrew Morton Cc: Bart Van Assche, bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r, linux-wireless-u79uwXL29TY76Z2rM5mHXA, linux-acpi-u79uwXL29TY76Z2rM5mHXA > > > > Apr 14 21:06:00 localhost kernel: ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 19 (level, low) -> IRQ 19 > > > > Apr 14 21:06:00 localhost kernel: ACPI: PCI interrupt for device 0000:05:00.0 disabled > > > > > > Yes, that does look like an ACPI problem. But one would expect it to kill > > > the interface immediately, not several hours later. I can't tell whether this is an ACPI problem. These messages are from pci_enable_device() and pci_disable_device(). So it looks like you're seeing an enable/disable pair every 124 seconds. This could be a problem somewhere in iwl3945_mac_start() that causes us to turn around and disable the device immediately. Most of the problems there have IWL_ERROR() messages associated with them, and you apparently aren't seeing those. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours 2008-04-15 15:15 ` Bjorn Helgaas @ 2008-04-15 17:22 ` Chatre, Reinette 0 siblings, 0 replies; 5+ messages in thread From: Chatre, Reinette @ 2008-04-15 17:22 UTC (permalink / raw) To: Bjorn Helgaas, Andrew Morton Cc: Bart Van Assche, bugme-daemon, linux-wireless, linux-acpi On , Bjorn Helgaas wrote: > iwl3945 modules is loaded after a few hours > >>>> > Apr 14 21:06:00 localhost kernel: ACPI: PCI Interrupt > 0000:05:00.0[A] -> GSI 19 (level, low) -> IRQ 19 >>>> > Apr 14 21:06:00 localhost kernel: ACPI: PCI interrupt > for device 0000:05:00.0 disabled >>>> >>>> Yes, that does look like an ACPI problem. But one would expect >>>> it to kill the interface immediately, not several hours later. > > I can't tell whether this is an ACPI problem. These messages are from > pci_enable_device() and pci_disable_device(). So it looks like you're > seeing an enable/disable pair every 124 seconds. > > This could be a problem somewhere in iwl3945_mac_start() that causes > us to turn around and disable the device immediately. Most of > the problems > there have IWL_ERROR() messages associated with them, and you > apparently aren't seeing those. (duplicate entry will be found in bugzilla) Are there any userspace apps managing this device? (eg. wpa_supplicant?) Could you please load the driver with debugging (modprobe iwl3945 debug=0x43ffb) - that will help us see if iwl3945_mac_start() is being called frequently. Thanks Reinette ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-04-15 17:23 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <bug-10455-10286@http.bugzilla.kernel.org/>
[not found] ` <bug-10455-10286-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>
2008-04-15 8:32 ` [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours Andrew Morton
2008-04-15 8:39 ` Bart Van Assche
[not found] ` <e2e108260804150139kf816be5m91e6206853a0d755-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-04-15 9:01 ` Andrew Morton
[not found] ` <20080415020103.cd8e17f4.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2008-04-15 15:15 ` Bjorn Helgaas
2008-04-15 17:22 ` Chatre, Reinette
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox