kernel oops on shutdown in 2.6.28

Bug #354216 reported by Rocko
This bug report is a duplicate of:  Bug #318360: null pointer reference in iwl3945. Edit Remove
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Most times that I shutdown kernel 2.6.28-11 on my Dell XPS M1530, I get a kernel oops: the screen goes blank (completely blank - there's no output on any console eg ctrl-alt-1, ctlrl-alt-2) and I have to press ctrl-alt-del to get it to continue. When it continues, it displays the last few lines of a kernel oops on the screen.

I've captured the full oops log using netconsole (see attached log).

This happens in Jaunty and also in Intrepid, where I've installed the Jaunty kernel. It has been happening with all previous versions of kernel 2.6.28 as well. It doesn't happen with 2.6.27 (ie the normal Intrepid kernel).

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
MachineType: Dell Inc. XPS M1530
NonfreeKernelModules: nvidia
Package: linux-image-2.6.28-11-generic 2.6.28-11.39
ProcCmdLine: root=UUID=709f7178-44db-418f-be0e-489169db001a ro quiet splash
ProcEnviron:
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.39-generic
SourcePackage: linux

Revision history for this message
Rocko (rockorequin) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Rocko,

Can you try unloading the iwlagn driver prior to shutting down to see if this prevents the oops from happening? Also, you may want to try installing linux-backports-modules-jaunty to see if it helps as it contains an updated compat-wireless stack. Thanks.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Rocko (rockorequin) wrote :

I tried removing iwlagn and doing a restart, and it restarted correctly without stopping on the kernel oops this time (although that isn't yet conclusive since it didn't do it every time before).

Is there a way to automate removing iwlagn on shutdown?

I enabled backports and reloaded the repositories (from Ubuntu main), but afterwards Synaptic didn't offer any new updates. (I normally have proposed enabled - perhaps it was already in there?) What's the updated package name and version?

Revision history for this message
Rocko (rockorequin) wrote :

Oops, I finally realised what you mean by linux-backports-modules :) and installed it.

I've tried a single reboot cycle and so far so good. I'll continue monitoring it.

Revision history for this message
kkhan (kublakhan) wrote :

I had the same issue (see #325426) and after installing linux-backports-modules the oops is gone; yet I still see:

error response NULL in 'REPLY_ADD_STA'

flashing by when shutting down/rebooting.

Revision history for this message
Rocko (rockorequin) wrote :

I've rebooted a second time without the oops/hang now.

I didn't notice any "error response NULL" messages though, and grep doesn't find any in /var/log.

Also note: handily, the backports module fixes an 11N bug for me (bug #305338 - can't get a DHCP address) but introduces a CRDA bug (bug #349001 - it always chooses the US regulatory domain).

Revision history for this message
Rocko (rockorequin) wrote :

I've done over ten reboots now without the oops, including in Intrepid with the 2.6.28-11.40 kernel (and backports). Intrepid used to oops every time, and it couldn't connect to my work 11N network at all with the 2.6.28-11 kernel, but it does now with the backports.

So the backports module does seem to fix the oops as well as some other bugs, although the new CRDA bug is a concern.

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.