Ubuntu 13.04 full system crash/kernel panic

[Elco]

Ubuntu 13.04 (with latest updates) crashes after a while every time I start it, the screen freezes, keyboard and mouse/touchpad do not generate any reponse. Ive tried to follow https://help.ubuntu.com/community/DebuggingSystemCrash to provide as much information as possible.

I'm using:
- Dell Studio 1558 (Intel core i3, ATI Mobility Radeon HD 5430/5450/5470)

I've tried:
- switching to command line using Ctrl-F1, no response;
- Prt Scr + R E I S U B, no response;
- monitoring /var/log/syslog and dmesg, I can't find anything that happened at the moment of the crash that might have caused it;
- running a memory check (for 45 minutes), it passed one time and then I let it continue for a while longer, but no errors showed up;
- disconnecting everyting attached to the laptop (power chord, wireless mouse), but the laptop still crashes;
- using different videocard drivers: fglrx, fglrx-updates and fglrx-12 (from the xorg-edgers ppa); does not appear to make any difference, although the fglrx drivers seem to increase time before the system crashes (but they ironically show a 'AMD unsupported hardware' watermark in the corner of the screen);
- remotely monitoring dmesg and /var/log/syslog over ssh, but ssh also goes crashes, the last reports are the same as on the laptop;
- installing the 32-bit version of Ubuntu 13.04, same problem as on 64-bit.
- updating Dell BIOS to A12

I'm not sure what else I can do to get more information on the crash, I'm sorry this is all rather vague. I've tried to gather as much information as possible. If there is anyting else I can do, please ask.

UPDATE: I'm now using the open source videocard drivers, and now when the system crashes I get a kernel panic (unfortunatelly I seem to be unable to find the full message in a log, if there are any at all). I'm not sure if the kernel panic is the same crash as under the other videocard drivers, but the effect appears to be the same, with the exception that the screen does not freeze, but switches to text-mode (still accepts no keyboard input).
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: elco 1953 F.... pulseaudio
CRDA:
 country NL:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5330 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=d4e85ebe-079f-44d5-af90-efd4595f5095
InstallationDate: Installed on 2013-04-26 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
MachineType: Dell Inc. Studio 1558
MarkForUpload: True
NonfreeKernelModules: wl
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=9a065c8b-ac87-49f1-b417-d221a205181f ro quiet splash pcie_aspm=force acpi_backlight=vendor vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-19-generic i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A12
dmi.board.name: 0874P6
dmi.board.vendor: Dell Inc.
dmi.board.version: A12
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A12
dmi.modalias: dmi:bvnDellInc.:bvrA12:bd03/30/2011:svnDellInc.:pnStudio1558:pvrA12:rvnDellInc.:rn0874P6:rvrA12:cvnDellInc.:ct8:cvrA12:
dmi.product.name: Studio 1558
dmi.product.version: A12
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1173581

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

apport information

[Elco (eajnab)]

Appologies for the missing logs, if anything else is required, please say so.

While running apport the system crashed again (twice), allowing me to take a picture of the kernel panic screen.

[soft (pourjour)]

I have the same when I tried to boot using a fresh copy in USB drive.

[Elco (eajnab)]

The problem is still occuring. I've been trying to narrow down the problem.

I switched to the command line (Ctrl-F1) immediately after reaching the login screen, killed X, lightdm and unity-greeter and the system still crashes after a while.

I can't determine whether the error showing up is the same is in the screenshot in comment #16, since I can only see the top part and then the screen has already frozen. The part I can see reads: BUG: Unable to handle kernel null pointer dereference at (null)

[dekeyserkarel (dekeyserkarel)]

Same problem over here on a Dell studio 1749.

I thought it was related to the video driver, but this isn't the case as my system crashes with the open source driver, fglrx, fglrx-updates and the latest version (13.4) available on the ATI website.

[Elco (eajnab)]

I tried a few different kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/. I tried kernel 3.8.9 and kernel 3.9-rc8, both still crash after a while, so a fix for this bug is still needed for future kernels. I haven't tried 3.7.x.

I then installed kernel 3.6.11 (for raring), which seems to work (fingers crossed). I have not had a crash for the last 4 hours (which is either a new record or the kernel fixed the problem). For everybody looking for a step-by-step solution:

I downloaded (from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6.11-raring/):
linux-headers-3.6.11-030611-generic_3.6.11-030611.201212171335_i386.deb
linux-headers-3.6.11-030611_3.6.11-030611.201212171335_all.deb
linux-image-3.6.11-030611-generic_3.6.11-030611.201212171335_i386.deb
linux-image-extra-3.6.11-030611-generic_3.6.11-030611.201212171335_i386.deb

I'm not sure if the last one is necessary, but it doesn't seem to hurt.

Install with:
cd Downloads (or whatever folder you downloaded the files to)
sudo dpkg -i linux*

Reboot and select the 3.6.11 kernel in grub under advanced options for Ubuntu (you might have to hold Shift if Grub doesn't normally show at boot).

You may have to reset unity after rebooting and logging in (it crashed in my case and refused to restart, but after resetting it works fine). You can get acces to a terminal if unity is crashed by either pressing Ctrl-Alt-T or Ctrl-Alt-F1. Then do:
dconf reset -f /org/compiz/

After resetting unity, you have to either reboot or do:
setsid unity

[Elco (eajnab)]

And just for the record, I had some problems setting grub to automatically boot to this kernel. Since the older kernel is hidden under a submenu you have to first find the entry which the 'advanced options' section is, and which entry the 3.6 kernel is within the 'advanced options'. Then you have to remember that Grub starts counting from 0, so substract 1 from both and change the default in:

sudo gedit /etc/default/grub

In my case, advanced options for Ubuntu was the 3d option (so 2), and the 3.6 kernel was the 2nd option in the submenu (so 1).

GRUB_DEFAULT="2>1"

(Note the " around 2>1, it won't work without them).

sudo update-grub

Reboot to check your settings.

[Elco (eajnab)]

Also, I noted that on shutdown, my screen turns competely yellow, not sure why.

I'm using the fglrx-updates videocard drivers now, because the fglrx drivers show the "unsupported hardware" watermark in the corner of my display.

[dekeyserkarel (dekeyserkarel)]

I think my crashes are related to this bug https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1134389 as I have a Broadcom 4312 in my Dell Studio 17

[Martin Wirth (martin-wirth-d)]

I can't offer any more technical information, but I have the same problem. It occurs a couple of times a day just as the other described.
I, too, have a Dell Studio 17 with the Broadcom adapter. However, I've seen messages in the kernel panic text indicating that the problem is chrome related. Might be the new open source drivers for the ATI graphics card (mobile 4xxx series which isn't supported by the proprietary ATI drivers anymore).

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/

[Joseph Salisbury (jsalisbury)]

I'd like to perform a bisect to figure out what commit caused this regression. It would be very helpful to know the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue. If it's confirmed this bug still exists in the mainline kernel after testing per comment #25, then it would be good to test some of the 3.7 kernels to see where the bug was introduced..

Can you test the following kernels and report back? We are looking for the earliest kernel version that exhibits this bug:

v3.7-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc4-raring/

If v3.7-rc4 does not exhibit the bug then test v3.7-rc6:
v3.7-rc6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc6-raring/

If v3.7-rc4 does exhibit the bug then test v3.7-rc2:
v3.7-rc2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.7-rc2-raring/

You don't have to test every kernel, just up until the kernel that first has this bug.

One thing to note, you will need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance!

[Elco (eajnab)]

I've been running the 3.9.0 kernel (from comment #25) for about an hour now, and it hasn't crashed yet. However, I should note that virtually nothing worked during that test. There was a problem with the graphics drivers during the installation of the kernel, although I do get to a graphical interface. Unity does not work, and resetting it does not appear to help. Wireless Internet will not activate (and I don't have a GUI to see why, but I expect driver problems).

Another problem is that I have to wait for the bug to happen, which can sometimes take a long time. I haven't figured out how to trigger it (if that is possible at all).

Also, I already tested the 3.9-rc8 kernel, and that kernel still had this bug.

Because of all that, I'm not sure if this can be considered a realistic test, especially since someone already pointed out that they suspect a problem with the wireless drivers and the wireless did not function at all.

I will move on to the instructions in comment #26 and test the 3.7 kernel. Perhaps someone else can test 3.9 more thoroughly.

[Elco (eajnab)]

Full list of results from my testing:
- v3.6.11 --> works
- v3.7-rc1 --> crash
- v3.7-rc2 --> crash
- v3.7-rc4 --> crash
- v3.8.9 --> crash
- v3.9-rc8 --> crash
- v3.9.0 --> ? (unable to fully test)

[Joseph Salisbury (jsalisbury)]

So it sounds like this bug was introduced in v3.7-rc1 and could still exist in mainline. I'll start a bisect between v3.6 final and v3.7-rc1.

[Martin Wirth (martin-wirth-d)]

I just witnessed this kernel panic (at least the one happening on my machine..) and I noticed that i was caused by the broadcom driver. I am sure the driver received a faulty packet (it crashed just when the entire building LAN here had a malfunction) and panicked. I think there is another thread dealing with the Broadcom driver causing a panic. I'll switch to that.

[Joseph Salisbury (jsalisbury)]

Unfortunately, There isn't much more we can do on the kernel side because of the proprietary nature of this package. Since we can't look at the code and figure out what's wrong and fix it.

However, this does seem to be a known issue. Similar reports:
https://bugzilla.redhat.com/show_bug.cgi?id=896587
https://bbs.archlinux.org/viewtopic.php?pid=1223933
https://retrace.fedoraproject.org/faf/reports/53531/

[jason strait (jasonstrait)]

i get this screen

http://img.photobucket.com/albums/v651/spacin/CRfh-EYPN06fqTUAaFj7K-UWIE_1MtmthsAvJJ6wmhM_zpse58dc168.jpg

[Joseph Salisbury (jsalisbury)]

@Jason strait,

That screen shot seems to be a different issue, maybe associated with the scheduler. I'd suggest opening a new bug for that.

[Deepak (deepakiitr2015)]

I never faced this problem while using LAN, but when I started using wi-fi it hardly runs for 10 mins, freezes and then reboots.
When it freezes, disk activity LED is continuously on (high disk usage). I do not have any problem on windows while using wi-fi.

[Alfons Kemming (alfons-kemming)]

I'm using a Dell Inspiron 1564. A broadcom BCM 4313. After installing 13.04 every 5 - 10 minutes the whole PC froze. Nothing worked. I uninstalled the proprietary driver through Systemsettings->software and updates->Additional drivers. And used a
Wireless N USB Adapter (D-Link DWA-140) and no more freezes. Today i forgot this D-Link for a trip and reinstalled the proprietary Broadcom driver throug Additional drivers and after several hours no freeze!

[vinlos (vincenzo-losito)]

why an Importan bug who compromises the access to the operating system won't be fixed? Wouldn't it be possible to patch the kernel 3.8 to solve the problem?

I'm going to uninstall Ubuntu for this bug, switching to another (hopefully) working distro.

[Michele Giacomoli (michele-giacomoli)]

@vinlos
According to this comment in bug #1098225 (https://bugs.launchpad.net/broadcom/+bug/1098225/comments/26) it's available a version of Broadcom drivers from Ubuntu 13.10 which seems to fix the bug. You can find it here:
https://launchpad.net/ubuntu/saucy/amd64/bcmwl-kernel-source/6.30.223.30+bdcom-0ubuntu1

Note that even if you switch to another distro with a linux kernel version between 3.7 and 3.8 the problem will persist ;)

[Firedragon (shagrath)]

Although i,m using linux mint 15 32bit i have the same problem multiple system freezes a day no respons ad all from the system only thing that works is a hard reset.

I don,t have any broadcom devices in this system.
When i,m in Arch linux with kernel 3.9.4-1 i have no freezes ad all.

[Julian Muzyczka (julmuzy)]

I have exactly the same issues with 13.04; freezes completely after 5/ 10 mins no matter what I'm doing. Running on Acer travelmate 8471 which uses Intel wifi. No recording of anything in the logs, no way of reproducing the fault, it just happens. When I revert to booting with 3.5 kernel (the only one I have prior to 3.8) everything works flawlessly as it has done for over 5 years. Really frustrating and I can't narrow down anything.

Sorry to add to the confusion.

[Hugh Bond II (uburtu)]

Similar problem here: 3.5 could boot just fine, but 3.6 and 3.8 would freeze during boot. Automatic login was enabled; oddly enough, disabling it allowed me to boot 3.8. In the hope it sparks something.

[Julian Muzyczka (julmuzy)]

Update to the freezing problem........I remembered that since I updated to 13.04 I wasn't getting the "Sorry, ubuntu 13.04 has experienced an internal error" which I always got with 12.10, so I disabled apport. ie sudo gedit /etc/default/apport and then set enabled=0. Rebooted. Hey presto machine running for 24 hours and no problems. Hope that helps with diagnosing the bug.

[Julian Muzyczka (julmuzy)]

1 week later, the bug has returned, no system error messages, just a slow grind to a complete stop, sometimes after 5/10/ 15 mins of usage, no matter which application is being used. No idea as to the cause because nothing is recorded in any log that provides a clue.

[Arie Skliarouk (skliarie)]

I had the same problem, the laptop Dell Studio 1569 have been freezing after 3-4 hours of work (ubuntu 13.04 amd64).

I tried to install bcmwl-kernel 6.30.223, disabled apport, disabled Intel SpeedStep, used "acpi=off noapic" kernel args, to no avail.

Upgraded kernel to version 3.10.0.6 (taken from ubuntu saucy) and worked for 15 hours already. Suspend is still broken though...

[daniel.fanica (dfanica)]

I have experienced 2 different problems, both freezes that need me to pull the plug on my machine.
1. kernel panic... solution: I have installed version 3.8.8 and I haven't seen it since. I have almost a full day of use.
2. graphic freeze... I am on the opne source drivers at the moment tho I have tried the other ones as well with pretty much the same result. I have a Dell Inspiron 1764

[TG12 (cyclonetimmy)]

I have a similar report to the above.
I have a 2006 iMac that was running Debian (Kernel Panics), and now onto an Ubuntu distro (Less Kernel Panics).
The iMac has a Broadcom chip in it (b43), the Kernel Panics I now get are related to when I use the Chrome browser.

There doesnt seem to be any particular trigger for it.
I am running the AMD open source driver on a Radeon x1600.

The kernel Panics I have are not recoverable unless you hold down the power button for 6 or so seconds. After the power button is pressed a garbeled desktop comes with lines everywhere(nothing is recognisable).

I am not sure what issue this is exactly to with? Broadcomb43 or AMD or the Kernel itself.

If anyone has a clue please reply!

[aury88 (spacedriver88)]

I've a similar problem.
no Error message in Log Report, or error message on screen, simply everything freeze.
Mouse e keyboard do not work (caplock or numlock doesn't activate the corresponding LED) and I can't use the terminale during these freeze
I need to force the shutdown using the power key.
this problem always occur immediately after the user login and some time when I launch Firefox
I have an Acer Extensa 5635z:
Pentium(R) Dual-Core CPU T4300 @ 2.10GHz × 2
Mobile Intel® GM45 Express Chipset
Ubuntu 13.04 64

[Chuck_S. (pretmetmij)]

Not really a solution but upgrading to Ubuntu 13.10 (kernel 3.11) fixed the problem for me.