Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-12-21 Thread Julien Cristau
On Wed, Oct 6, 2010 at 22:54:03 +0100, Ben Hutchings wrote: On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote: Package: linux-2.6 Version: 2.6.32-23 Severity: normal iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot, because it was unhappy after resume.

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-12-21 Thread Ben Hutchings
On Wed, 2010-10-13 at 17:30 +0200, Johannes Berg wrote: On Wed, 2010-10-13 at 17:17 +0200, Julien Cristau wrote: Getting lots of those in dmesg: iwlagn :0c:00.0: Too many chunks: 2 Doesn't seem to prevent the network from working though. It'll at least leak lots of memory

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-10-13 Thread Julien Cristau
On Sun, Oct 10, 2010 at 20:03:13 +0100, Ben Hutchings wrote: On Thu, 2010-10-07 at 09:51 +0200, Johannes Berg wrote: On Wed, 2010-10-06 at 22:54 +0100, Ben Hutchings wrote: On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote: Package: linux-2.6 Version: 2.6.32-23 Oct 6

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-10-13 Thread Johannes Berg
On Wed, 2010-10-13 at 17:17 +0200, Julien Cristau wrote: Getting lots of those in dmesg: iwlagn :0c:00.0: Too many chunks: 2 Doesn't seem to prevent the network from working though. It'll at least leak lots of memory though. But I think the check there is just wrong -- there are TFDs,

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-10-10 Thread Ben Hutchings
On Thu, 2010-10-07 at 09:51 +0200, Johannes Berg wrote: On Wed, 2010-10-06 at 22:54 +0100, Ben Hutchings wrote: On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote: Package: linux-2.6 Version: 2.6.32-23 Oct 6 21:05:02 radis kernel: [378665.326381] NetworkManager: page

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-10-10 Thread Johannes Berg
On Sun, 2010-10-10 at 20:03 +0100, Ben Hutchings wrote: I have, however much more recently than that kernel, cleaned this up in commit ff0d91c3eea6e25b47258349b455671f98f1b0cd -- this particular allocation is now 2048 or 4096 bytes depending on the architecture (32 vs 64 bit pointers). If

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-10-07 Thread Johannes Berg
On Wed, 2010-10-06 at 22:54 +0100, Ben Hutchings wrote: On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote: Package: linux-2.6 Version: 2.6.32-23 Oct 6 21:05:02 radis kernel: [378665.326381] NetworkManager: page allocation failure. order:4, mode:0x40d0 Oct 6 21:05:02 radis

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-10-06 Thread Julien Cristau
Package: linux-2.6 Version: 2.6.32-23 Severity: normal iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot, because it was unhappy after resume. Bit of kern.log: Oct 6 21:05:02 radis kernel: [378665.326381] NetworkManager: page allocation failure. order:4, mode:0x40d0 Oct

Bug#599345: linux-image-2.6.32-5-amd64: iwlagn allocation failure

2010-10-06 Thread Ben Hutchings
On Wed, 2010-10-06 at 21:19 +0200, Julien Cristau wrote: Package: linux-2.6 Version: 2.6.32-23 Severity: normal iwlagn decided 2 weeks of uptime was enough and it wanted me to reboot, because it was unhappy after resume. You also told me that this machine had no swap enabled, which is an