@Michal Koziorowski, from the log files you attached I see you get a flood of "iwlagn: Can not allocate SKB buffers" (see bug 250139) and then you seem to be hit with this bug. I'm guessing from examining from some of the other logs posted here this is related to wifi and specifically the iwlagn driver you all seem to be using. If you can all try the following report back your results that would be great:
1) Try installing the linux-backports-modules package. It recently pulled in an updated version of the compat-wireless stack:
* Added iwlwifi firmware
* Added the upstream compat-wireless-2.6 tree.
* Updated compat-wireless to wireless-testing tag master-2008-10-14
* Set CONFIG_WIRELESS_OLD_REGULATORY=y by default.
Ideally, the updated version of the driver provided in linux-backports-modules will resolve this issue. If it doesni't help then try the following:
2) Disable wireless by unloading the iwlagn driver - 'sudo rmmod iwlagn'. From the timestamps on the logs it doesn't seem that this issue happens immediately so I don't think it would require require blacklisting the driver from ever loading. Does unloading the driver at least prevent this issue from happening? This will at least confirm my assumption this is related to the iwlagn driver.
Hi Everyone,
@Michal Koziorowski, from the log files you attached I see you get a flood of "iwlagn: Can not allocate SKB buffers" (see bug 250139) and then you seem to be hit with this bug. I'm guessing from examining from some of the other logs posted here this is related to wifi and specifically the iwlagn driver you all seem to be using. If you can all try the following report back your results that would be great:
1) Try installing the linux-backports -modules package. It recently pulled in an updated version of the compat-wireless stack:
https:/ /edge.launchpad .net/ubuntu/ +source/ linux-backports -modules- 2.6.27
linux-backports -modules- 2.6.27 (2.6.27-7.3) intrepid; urgency=low
[Tim Gardner]
* Added iwlwifi firmware WIRELESS_ OLD_REGULATORY= y by default.
* Added the upstream compat-wireless-2.6 tree.
* Updated compat-wireless to wireless-testing tag master-2008-10-14
* Set CONFIG_
Ideally, the updated version of the driver provided in linux-backports -modules will resolve this issue. If it doesni't help then try the following:
2) Disable wireless by unloading the iwlagn driver - 'sudo rmmod iwlagn'. From the timestamps on the logs it doesn't seem that this issue happens immediately so I don't think it would require require blacklisting the driver from ever loading. Does unloading the driver at least prevent this issue from happening? This will at least confirm my assumption this is related to the iwlagn driver.
Please let us know your results. Thanks.