Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

2010-06-23 Thread Arne Nordmark
Ben Hutchings wrote: On Fri, 2010-06-18 at 16:40 +0200, Arne Nordmark wrote: My problem seems related to those in Ubuntu report #55 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/55. If I unload the 3c59x module, I can no longer reproduce this problem, and wireless is stable.

Bug#586967: Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

2010-06-23 Thread Ben Hutchings
On Wed, 2010-06-23 at 21:12 +0200, Arne Nordmark wrote: Ben Hutchings wrote: On Fri, 2010-06-18 at 16:40 +0200, Arne Nordmark wrote: My problem seems related to those in Ubuntu report #55 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/55. If I unload the 3c59x module, I

Bug#586967: Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

2010-06-23 Thread Ben Hutchings
Forwarded Message From: Arne Nordmark nordm...@mech.kth.se To: Ben Hutchings b...@decadent.org.uk Cc: 574...@bugs.debian.org Subject: Re: Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x0101 Date: Wed, 23 Jun 2010 21:12:08 +0200 Ben Hutchings wrote: On Fri

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

2010-06-20 Thread Ben Hutchings
On Fri, 2010-06-18 at 16:40 +0200, Arne Nordmark wrote: My problem seems related to those in Ubuntu report #55 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/55. If I unload the 3c59x module, I can no longer reproduce this problem, and wireless is stable. With the 3c59x module

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

2010-06-18 Thread Arne Nordmark
My problem seems related to those in Ubuntu report #55 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/55. If I unload the 3c59x module, I can no longer reproduce this problem, and wireless is stable. With the 3c59x module loaded, b43 wireless is essentially unusable, since the

Bug#574555: BUG: scheduling while atomic: irq/11-b43/2018/0x00000101

2010-05-09 Thread Arne Nordmark
I find a similar oops very reliably whenever there is moderate network traffic, like updating squeeze. This happens on 2.6.32-3-686, 2.6.32-5-686, and 2.6.33-2-686 from experimental, but not at all on the earlier squeeze kernel 2.6.30-2-686. Soon after this the system locks up completely.