[HARDY] Kernel panic (hard lockup) on Asus Z37E with iwl4965

Bug #278030 reported by Mackenzie Morgan
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

2.6.24-21-generic #1 SMP Mon Aug 25 16:57:51 UTC 2008 x86_64 GNU/Linux
Ubuntu 2.6.24-21.42-generic
Hardy 8.04.1

I bought this laptop from ZaReason. It is available with the Intel 4965 802.11n card or some other Intel card. I have the Intel 4965 802.11n card. ZaReason says that nobody else has reported kernel panics with this model laptop, but that few others have chosen the 802.11n option.

The panics also have lately occurred just after boot or just after resuming from suspend. I login, get to the desktop, start up some apps, and then as soon as NetworkManager shows that it has connected...kernel panic.

The panics used to occur about once a week. However, I've had 2 today, 3 on Saturday, 1 Friday, and 1 Thursday that I can remember. It seems since Intrepid was released, Hardy's stability with this chipset has plummeted.

Revision history for this message
Mackenzie Morgan (maco.m) wrote :
Revision history for this message
Mackenzie Morgan (maco.m) wrote :
description: updated
description: updated
description: updated
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Mackenzie,

Just curious if you've updated this machine to Intrepid Ibex 8.10 and if this issue remains? I'd also be curious to hear about the latest Jaunty 9.04 Alpha3 release - http://cdimage.ubuntu.com/releases/jaunty/ . You should be able to test via a LiveCD. Definitely let us know your results. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Mackenzie Morgan (maco.m) wrote : Re: [Bug 278030] Re: [HARDY] Kernel panic (hard lockup) on Asus Z37E with iwl4965

Hi Leann, I think it ended up being a problem with my motherboard.
Since I replaced it and installed Jaunty, it's been mostly fine. At
least, there've been no lockups while I'm in the middle of anything. I
had one kernel panic during hibernate today, but that's quite a
different situation than the one under which this bug was filed.

 status invalid

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.