Linux kernel freeze (it seems in current/3.19.0-17) on Dell Inspiron 1525

Bug #1453302 reported by Páll Haraldsson
36
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

First READ about how I deceived ubuntu-bug!

I'm not sure it matters or what info ubuntu-bug collects, but I didn't do "ubuntu-bug linux" since it gave an error:

"Problem in linux-image-3.19.0-13-generic

The problem cannot be reported:

This is not an official Ubuntu package. Please remove any third party package and try again."

I did ubuntu-bug Xorg just to get some collection of info, NOT saying xorg is the fault.

Note that this bug report is NOT about that kernel but the most current (and maybe one or two others).

Yesterday I wasn't having this problem with kernels (at least not the newest one I had not installed.. I may have had different problems, do not believe hardware broken though).

$ ls -lrt /boot/initrd.img-3.1*
-rw-r--r-- 1 root root 19976179 apr 10 17:20 /boot/initrd.img-3.13.0-47-generic
-rw-r--r-- 1 root root 21779681 apr 11 14:54 /boot/initrd.img-3.19.0-13-generic
-rw-r--r-- 1 root root 21782845 apr 19 13:54 /boot/initrd.img-3.19.0-15-generic
-rw-r--r-- 1 root root 21733320 maí 8 20:26 /boot/initrd.img-3.19.0-15-lowlatency
-rw-r--r-- 1 root root 21780289 maí 8 21:04 /boot/initrd.img-3.19.0-17-generic

I believe I've been running 3.19.0-15-generic for the last few days. I just run the most recent one (usually - but not now because of the problems below).

Today (this evening) I upgraded some stuff including the kernel. 3.19.0-17 does not boot up. I've tried several times and get a blank screen. I may have gotten something else, a splash-screen (not as far as login-screen), on the first try. DO not count on that as I may misremember.

Then booting into 3.19.0-15-generic I could log in, so it seems the kernel above is the problem. Note I also upgraded more, say networking. AND now while I can log in, that kernel quickly froze (twice just after starting Chrome w/lots of tabs) - in a way I've never seen - the CAPS LOCK and the light to the RIGHT (NOT NUM LOCK to the left) where blinking in sync. I may have forgotten (or not?) to try a virtual terminal as this seemed a sure indication that something was wrong.

[I also booted into just-installed 3.19.0-15-lowlatency and got the blinking lights.]

Then I booted into 3.19.0-13 and am now for a much longer time in Chrome, so far no freeze..

[I was doing apt-get autoclean today, deleting kernels, so maybe I'm wrong about the exact version of the kernel I was running without problems, but at least all the info on kernels that do not work are right.]

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
Uname: Linux 3.19.0-13-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CompositorRunning: None
CurrentDesktop: Unity
Date: Fri May 8 21:50:41 2015
DistUpgraded: 2015-04-06 16:46:01,057 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Today
GraphicsCard:

InstallationDate: Installed on 2014-08-21 (260 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Inspiron 1525
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UnitySupportTest: Error: [Errno 12] Cannot allocate memory
UpgradeStatus: Upgraded to vivid on 2015-04-06 (32 days ago)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1
xserver.bootTime: Fri May 8 21:43:05 2015
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 12631
 vendor SEC
xserver.version: 2:1.17.1-0ubuntu3

Revision history for this message
Páll Haraldsson (pall-haraldsson) wrote :
summary: - Linux freeze on Dell Inspiron 1525
+ Linux kernel freeze (it seems in current/3.19.0-17) on Dell Inspiron
+ 1525
Revision history for this message
Páll Haraldsson (pall-haraldsson) wrote :

I was going to upload syslog with the correct info (what ubuntu-bug uploads seems only about since current boot).

It seems the freeze is that severe (nothing on 3.19.0-17) or early that nothing gets appended to syslog.

$ ls -lrt /var/log/syslog*
..
-rw-r----- 1 syslog adm 52942 maí 1 13:17 /var/log/syslog.2.gz
-rw-r----- 1 syslog adm 9474601 maí 8 20:01 /var/log/syslog.1
-rw-r----- 1 syslog adm 3226101 maí 8 22:34 /var/log/syslog

$ grep 'Linux version' /var/log/syslog
May 8 21:15:48 Ryksugan kernel: [ 0.000000] Linux version 3.19.0-15-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 (Ubuntu 3.19.0-15.15-generic 3.19.3)
May 8 21:25:42 Ryksugan kernel: [ 0.000000] Linux version 3.19.0-15-lowlatency (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP PREEMPT Fri Apr 17 00:03:20 UTC 2015 (Ubuntu 3.19.0-15.15-lowlatency 3.19.3)
May 8 21:39:24 Ryksugan kernel: [ 0.000000] Linux version 3.19.0-15-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 (Ubuntu 3.19.0-15.15-generic 3.19.3)
May 8 21:40:21 Ryksugan kernel: [ 0.000000] Linux version 3.19.0-15-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 (Ubuntu 3.19.0-15.15-generic 3.19.3)
May 8 21:43:04 Ryksugan kernel: [ 0.000000] Linux version 3.19.0-13-generic (buildd@lamiak) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #13-Ubuntu SMP Thu Apr 9 22:56:40 UTC 2015 (Ubuntu 3.19.0-13.13-generic 3.19.3)

$ grep 'Linux version' /var/log/syslog.1
May 8 19:48:01 Ryksugan kernel: [ 0.000000] Linux version 3.19.0-15-lowlatency (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP PREEMPT Fri Apr 17 00:03:20 UTC 2015 (Ubuntu 3.19.0-15.15-lowlatency 3.19.3)

$ zgrep 'Linux version' /var/log/syslog.2.gz

Uploading syslog in case it's helpful for the other kernels with blinking lights.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg (Ubuntu):
status: New → Confirmed
Revision history for this message
volker kempter (v-kempter) wrote :

kernel 3.19.0-17:
no boot that kernel on dell e6500; black screen at an early stage (way before login).

However, boots as follows: -> recovery mode -> resume normal boot (without taking any action prior to resuming!).

No boot problems with 3.19.0-16 nor with 4.0.0-1 (both boot normally).

Revision history for this message
volker kempter (v-kempter) wrote :

kernel 3.19.0-17:

forgot to mention that there are no boot problems when running the kernel 3.19.0-17 in a virtual machine in virtualbox (on the same hardware)

Revision history for this message
volker kempter (v-kempter) wrote :

kernel 3.19.0-17:

no boot on dell latitude d505 neither.
However, the kernel obviously boots with the grub option "nomodeset" because I can open a console (ctrl+alt+f1); could not open the display, though.

Revision history for this message
Piotr M (yabolus) wrote :

I have the same issue, pretty sure it's caused by the i915 driver since it looks like it hangs when switching video mode (screen goes blank) and the system boots up in recovery mode just fine (without the video driver).

Revision history for this message
richard jones (richard-jones-1952) wrote :

I think I have the same problem on an Acer Aspire 5920 laptop. The machine hangs very early in the boot process on Ubuntu 3.19.0-17-generic, but boots successfully using recovery mode, or booting 3.19.0-16-generic. Let me know if I can provide further info. I may need detailed instructions. Thanks.

Revision history for this message
Thomas (steffens12345) wrote :

Yes, on my Acer Aspire 5920 the same like richard-jones-1952 wrote. Question to ?. May be the same problem like this bug ?https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440724

Revision history for this message
richard jones (richard-jones-1952) wrote :

Additional info. Possibly irrelevant.

Using Firefox I have noticed a screen corruption that seems to occur after some time idle. The same problem occurred on Ubuntu 14.04. It suggests to me that somewhere deep in the graphics driver something is amiss.

To use the Google Chrome browser I have had to un-check 'Use hardware acceleration when available' to prevent the browser from crashing.

Attached is the dmesg output from a successful boot of 3.19.0-16-generic which may be helpful. Whether booting successfully or not just before the grub menu the following is reported: ACPI PCC Probe Failed. This is apparently benign.

Revision history for this message
unamico (grandesso-giovanni) wrote :

I have the same problem on an Acer Extensa 5620 laptop (further investigation on DELL precision M4500). The machine hangs very early in the boot process on Ubuntu 3.19.0-17-generic and don't start. Last kernel message [OK] Created slice system-ifup.slice

Revision history for this message
penalvch (penalvch) wrote :

Páll Haraldsson, thank you for reporting this and helping make Ubuntu better.

Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where XY and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-a17
affects: xorg (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
richard jones (richard-jones-1952) wrote :

I installed the upstream kernel packages on my Acer Aspire 5920 laptop:
linux-headers-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb
linux-image-4.1.0-040100rc2-generic_4.1.0-040100rc2.201505032335_amd64.deb
The machine booted successfully 3 times with warnings about installed packages having unmet dependencies.
uname -r command confirmed that the expected kernel was running: 4.1.0-040100rc2-generic

Hope that helps. Cheers Richard

Revision history for this message
richard jones (richard-jones-1952) wrote :

Very pleased to help immensely, though I need a little more hand holding...
What would you like the new report to say? Please excuse my dumb response! Thanks

Revision history for this message
volker kempter (v-kempter) wrote :

3.19.0-17, no boot - at #12:

15.04 on dell e6500 boots normally with the upstream kernel 4.1-rc2

Revision history for this message
volker kempter (v-kempter) wrote :

at #18:
could only repeat / duplicate the report of richard jones??

However, please let me know if you would eventually need the output of some specific commands concerning my system!

Revision history for this message
volker kempter (v-kempter) wrote :

ad #20:

okay!
used "ubuntu-bug linux" running with 3.19.0-16.
hope it helps!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.