linux-image 3.19.0.12.11 will not boot - Intel mobile 965 chipset

[TK]

the recent Vivid linux meta package upgrade of 3.19.0.12.11 caused my Dell Latitude D630 to stop booting. The boot continues to "starting version 219" and then freezes.

Eliminating the "splash" option by editing GRUB allows the computer to boot until the login screen. After login, the computer again locks up, displaying a blue background and a immobile mouse pointer in the center of the screen.

The same behavior occurs when booting from the daily DVD image which contains 3.19.0.12.

I have reverted to 3.19.0.11.10 which is how I am reporting this bug. I'm not sure the usual commands for reporting bugs would be helpful while running the previous kernel. I am unable to run these commands with 3.19.0.12 as I cannot get to a point of interacting with the system.

I have attached the syslog from attempting to boot 3.19.0.12.
---
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0c: tom 1459 F...m pulseaudio
 /dev/snd/pcmC0D0p: tom 1459 F...m pulseaudio
 /dev/snd/controlC0: tom 1459 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=4588a704-477d-4b44-b827-bd13e745d90f
InstallationDate: Installed on 2012-08-01 (977 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120801)
MachineType: Dell Inc. Latitude D630
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-lowlatency root=UUID=91eb6d24-9c1b-47d8-ac9f-75db6a566e5c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-11.11-lowlatency 3.19.3
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-11-lowlatency N/A
 linux-backports-modules-3.19.0-11-lowlatency N/A
 linux-firmware 1.143
Tags: vivid
Uname: Linux 3.19.0-11-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dip lpadmin plugdev pulse sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0KU184
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D630
dmi.sys.vendor: Dell Inc.
---
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0c: tom 1459 F...m pulseaudio
 /dev/snd/pcmC0D0p: tom 1459 F...m pulseaudio
 /dev/snd/controlC0: tom 1459 F.... pulseaudio
 /dev/snd/seq: timidity 718 F.... timidity
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=4588a704-477d-4b44-b827-bd13e745d90f
InstallationDate: Installed on 2012-08-01 (977 days ago)
InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120801)
MachineType: Dell Inc. Latitude D630
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-11-lowlatency root=UUID=91eb6d24-9c1b-47d8-ac9f-75db6a566e5c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-11.11-lowlatency 3.19.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-11-lowlatency N/A
 linux-backports-modules-3.19.0-11-lowlatency N/A
 linux-firmware 1.143
Tags: vivid
Uname: Linux 3.19.0-11-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A19
dmi.board.name: 0KU184
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D630
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 1440724

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.

[Clay Weber (claydoh)]

Same here, on two laptops, one the same Dell D630 as the OP, as well as a basically identical D830. However, editing the boot parameters from the grub menu does not allow me to get to a login screen, and I am unable to even get to a vt to run any sort of commands.

[TK (tkrishan)]

Brad Figg (brad-figg) wrote 4 hours ago: 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'.

That information, "you are unable to run this command, please add a comment stating that fact", is in the original description. The sys log file is attached which is the best I could manage after rebooting using the previous kernel.

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

apport information

[TK (tkrishan)]

To avoid any arguments, I have run the command requested but please keep in mind that this was run from the previous kernel version, not the 3.19.0.12 version.

[penalvch (penalvch)]

TK, 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-3.XY-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-3.XY-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.

[Joseph Salisbury (jsalisbury)]

Can folks affected by this bug please test the v4.0-rc1 kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/

I also have a Vivid test kernel building with a cherry-pick of commit: 162b6a57a.

[Joseph Salisbury (jsalisbury)]

The Vivid test kernel that has a cherry pick of 162b6a57a can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440724/

In addition to testing upstream v4.0-rc1, can this kernel also be tested?

Note, with the Vivid kernel, you need to install both the linux-image and linux-image-extra packages.

[royden (ryts)]

BTW, this affects i386 Mobile 915GM as well.

[Jonas (joney)]

I can also confirm this problem for an older Fujitsu Siemens notebook (Intel Core Duo T2300, 1 GiB RAM, BIOS v. 1.20, Intel Mobile 945GM/GMS, 943/940GML945). Kernel 3.19.0-11 runs fine, 3.19.0-12 freezes during boot with exactly the same symptoms as described above.

Removing 'quiet splash' did not help to display any more output, but I also see the frozen login screen then (mouse pointer also does not move).

I installed the the i386 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc7-vivid/ (4.0.0-040000rc7-generic #201504061936 SMP Mon Apr 6 23:58:59 UTC 2015 i686 i686 i686 GNU/Linux) and the problem did not occur there (running it right now as I write these lines).

I could try the rc1 as well or provide further config files or other kind of tests if required, just let me know...

[royden (ryts)]

The v4.0-rc1 kernel fails for me as well.

HP Pavilion dv1000 Intel(R) Pentium(R) M processor 1.86GHz, 2 gigs RAM, Intel Mobile 915GM

[TK (tkrishan)]

Here are my testing results with a Dell Latitude D630, Intel Mobile 965 chipset.

V4.0-rc1 kernel fails to boot

lp1440724 kernel boots but with only 1024x768s fixed screen resolution. The Latitude D630 is a 1440x900 LCD display.

V4.0-rc7 kernel boots appears to work with a limited 10 minutes of testing; all hardware devices appear to be functioning correctly.

[Jonas (joney)]

Just did another test. Selecting recovery mode for kernel 3.19.0-12 and then resume seems to work and I could log in successfully, though resolution is then limited to max. 1024x768 and graphics is extremely slow (resolution should be max. 1280x800 for my nb).

[Joseph Salisbury (jsalisbury)]

@jonas, can you also try v4.0-rc1?

[royden (ryts)]

V4.0-rc7 kernel boots and works on 2 different i386 laptops with i915 graphics.

[Jonas (joney)]

Test with linux-headers-4.0.0-040000rc1-generic_4.0.0-040000rc1.201502222235_i386.deb:

- normal boot freezes as with 3.19.0-12
- booting with 'quiet splash' removed shows bootlog output, but too fast to read, ends in frozen login screen (switching to other consoles using Ctrl-Alt-F... does not work).
- boot in recovery mode and then resume seems to work, however again with low resolution of max. 1024x768 and slow graphics

BTW, I cannot test the lp1440724v1 Kernel as there are only 64 bit builds in the directory and the Intel Core Duo T2300 is only 32 bit.

[Timo Aaltonen (tjaalton)]

Try v4.0-rc2 too in the meantime. There is one suspicious commit that might help here..

[Jonas (joney)]

just booted the system using inux-image-4.0.0-040000rc2-generic_4.0.0-040000rc2.201503031836_i386.deb and it seems to work (writing from it now). Further tests will have to wait until tomorrow evening...

[Joseph Salisbury (jsalisbury)]

I built another Vivid test kernel with a cherry pick of commit 2caa80e72b57c62. It can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1440724/

When possible, can you also test this kernel?

Note, with this Vivid kernel, you need to install both the linux-image and linux-image-extra packages.

[Joseph Salisbury (jsalisbury)]

2caa80e72b57c62 is the suspicious commit mentioned in comment #50.

[Clay Weber (claydoh)]

Joseph, your kernel in comment #52 does work on my 2 affected laptops

[TK (tkrishan)]

3.19.0-12 - lp1440724 works for me on the Dell Latitude D630.

[Thomas (steffens12345)]

for me the same, 3.19.0.12 not ok, 3.19.0.11 OK. on a acer aspire 5920

[Jonas (joney)]

@Joseph - my CPU is 32 bit only (Intel Core Duo T2300), so I can't test the lp1440724v2 kernel you provided. Would it be possible for you to compile a i386/i686 kernel package?

[royden (ryts)]

If the fix was committed in linux-image 3.19.0.12.12 then it does not work for me.

Dell Intel Core 2 32-bit Intel 945GM

[Joseph Salisbury (jsalisbury)]

@royden, the fix was not committed in 3.19.0-12, it was committed to be in the next kernel release.

[TK (tkrishan)]

3.19.0-13 in the Vivid - Proposed repository fixes this issue for me on my Dell Latitude D630. Thanks!

[Jonas (joney)]

3.19.0-13 from Vivid - Proposed also fixes the issue for me. Thanks to the developers!

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 3.19.0-13.13

---------------
linux (3.19.0-13.13) vivid; urgency=low

  [ Andy Whitcroft ]

  * [Packaging] initscripts need installing when making the package
  * [Packaging] initscripts work around bug in debhelper systemd support

  [ Jay Vosburgh ]

  * SAUCE: fan: Proof of concept implementation
    - LP: #1439706

  [ Leann Ogasawara ]

  * Release Tracking Bug
    - LP: #1442165

  [ Upstream Kernel Changes ]

  * Revert "drm: fix mismerge in drm_crtc.c"
    - LP: #1440270, #1440392
  * e1000e: initial support for i219
    - LP: #1400955
  * e1000e: fix obscure comments
    - LP: #1400955
  * e1000e: remove calls to ioremap/unmap for NVM addr
    - LP: #1400955
  * d-i: Enable usb modules on arm64
  * drm/amdkfd: Initialize only amdkfd's assigned pipelines
  * storvsc: use cmd_size to allocate per-command data
  * storvsc: in responce to a scan event, scan the host
  * storvsc: force discovery of LUNs that may have been removed.
  * storvsc: fix a bug in storvsc limits
  * Drivers: hv: vmbus: Use get_cpu() to get the current CPU
  * Tools: hv: address compiler warnings for hv_fcopy_daemon.c
  * Tools: hv: do not add redundant '/' in hv_start_fcopy()
  * Drivers: hv: hv_balloon: Make adjustments in computing the floor
  * Drivers: hv: hv_balloon: Fix a locking bug in the balloon driver
  * Drivers: hv: hv_balloon: Don't post pressure status from interrupt
    context
  * Drivers: hv: vmbus: Implement a clockevent device
  * Drivers: hv: vmbus: Fix a bug in vmbus_establish_gpadl()
  * Drivers: hv: vmbus: Support a vmbus API for efficiently sending page
    arrays
  * hv: hv_fcopy: drop the obsolete message on transfer failure
  * Drivers: hv: check vmbus_device_create() return value in
    vmbus_process_offer()
  * Drivers: hv: rename sc_lock to the more generic lock
  * Drivers: hv: vmbus: serialize Offer and Rescind offer
  * Drivers: hv: vmbus: hv_process_timer_expiration() can be static
  * hyperv: netvsc.c: match wait_for_completion_timeout return type
  * hyperv: fix sparse warnings
  * powerpc/powernv: Add OPAL soft-poweroff routine
    - LP: #1439562
  * drivers/sbus/char/envctrl.c: ignore orderly_poweroff return value
    - LP: #1439562
  * kernel/reboot.c: add orderly_reboot for graceful reboot
    - LP: #1439562
  * powerpc/powernv: reboot when requested by firmware
    - LP: #1439562
  * powerpc/kernel: Make syscall_exit a local label
    - LP: #1439562
  * powerpc: Remove old compile time disabled syscall tracing code
    - LP: #1439562
  * powerpc: Add a proper syscall for switching endianness
    - LP: #1439562
  * powerpc/powernv: Remove "opal" prefix from pr_xxx()s
    - LP: #1439562
  * powerpc/powernv: Separate function for OPAL IRQ setup
    - LP: #1439562
  * powerpc/powernv: Add OPAL message notifier unregister function
    - LP: #1439562
  * powerpc/powernv: Support OPAL requested heartbeat
    - LP: #1439562
  * device: Add dev_of_node() accessor
    - LP: #1439562
  * drivers/core/of: Add symlink to device-tree from devices with an OF
    node
    - LP: #1439562
  * ipv6: Don't reduce hop limit for an interface
    - LP: #1441103
    - CVE-2015-2922
  * x86/microcode/int...

[Thomas (steffens12345)]

the update-manager installed today 3.19.0.13, it is ok, thanks