This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested in
Hi Matt,
Now that Karmic contains a newer 2.6.31 based kernel as well as the
linux-crashdump utility, definitely let us know if you still experience
any sort of panics which you might be able to capture now. Thanks.
--
Panics while using iwlagn wifi on some networks
https://bugs.launchpad.net/b
On Mon, May 11, 2009 at 09:38:47PM -, Leann Ogasawara wrote:
> Hi Matt,
>
> Are you still able to trigger these panics with the more recent
> 2.6.28-11 Jaunty kernel? If so, just curious if you've also tested with
> linux-backports-modules-jaunty as it contains an updated compat-wireless
> st
Hi Leann,
I'm currently on jaunty. Have been for the last month or so. The ath5k
driver was completely unusable, it kept disconnecting every minute... It
also had the lockups but not as frequent as ath_pci (madwifi) if I
remember correctly. So, I'm currently using ath_pci with the constant
lockups
Hi Matt,
Are you still able to trigger these panics with the more recent
2.6.28-11 Jaunty kernel? If so, just curious if you've also tested with
linux-backports-modules-jaunty as it contains an updated compat-wireless
stack.
@Julius, you may be experiencing a slightly different bug as I notice
y
I can confirm this bug. I've been having kernel panics either after I
upgraded to intrepid or since I started using a wireless network with
WPA encryption.
I'm running a system that was installed as 7.04 but has been updated to
every new release. It is now at intrepid. It is a IBM Thinkpad T60. I
The fact that I saw this after the upgrade seems to have been
incidental. I've now reproduced the same problem on 2.6.27-9.19 if I
use the same wifi network.
I don't think this is the same as bug 276990 because 1) this isn't an
802.11n network, and 2) it clearly is not fixed in 2.6.27-10.20.
I'm
