All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
To: bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours
Date: Tue, 15 Apr 2008 01:32:51 -0700	[thread overview]
Message-ID: <20080415013251.e90e5abd.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10455-10286-V0hAGp6uBxO456/isadD/XN4h3HLQggn@public.gmane.org/>


(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

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: bart.vanassche@gmail.com
Cc: bugme-daemon@bugzilla.kernel.org, linux-wireless@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 10455] New: Kernel lockup when iwl3945 modules is loaded after a few hours
Date: Tue, 15 Apr 2008 01:32:51 -0700	[thread overview]
Message-ID: <20080415013251.e90e5abd.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10455-10286@http.bugzilla.kernel.org/>


(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@bugzilla.kernel.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@kernel-bugs.osdl.org
>         ReportedBy: bart.vanassche@gmail.com
> 
> 
> 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?


       reply	other threads:[~2008-04-15  8:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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   ` Andrew Morton [this message]
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
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 15:15               ` Bjorn Helgaas
2008-04-15 17:22               ` Chatre, Reinette
2008-04-15 17:22                 ` Chatre, Reinette

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080415013251.e90e5abd.akpm@linux-foundation.org \
    --to=akpm-de/tnxtf+jlsfhdxvbkv3wd2fqjk+8+b@public.gmane.org \
    --cc=bart.vanassche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=bugme-daemon-590EEB7GvNiWaY/ihj7yzEB+6BGkLq7r@public.gmane.org \
    --cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.