Blank (but responsive) screen with mouse pointer after update

[Shaun Crampton]

Since the last kernel update, rebooting my laptop results in a normal boot until the login screen should appear, then I see a few lines of console output (typical bootup messages) at the top of the screen and the mouse pointer appears over the balck screen with console output. The mouse behaves as if the login screen was visible (but it isn't) and I was able to blind click on my username, log in and then open a terminal (via keyboard shortcut) and then execute commands. (I typed sudo reboot and then my password and the console messages updated to say "system going down for reboot NOW", then it rebooted.)

Pressing Ctrl-Alt-F1 switches to a tty as normal.

The problem doesn't occur every time, after a few reboots I got lucky and it booted normally. Doing a suspend/resume doesn't seem to cause the problem.

My laptop is a Samsung series 9 NP900X4C-A03US with Intel graphics (4000 series IIRC).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-21-generic 3.5.0-21.32
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: shaun 1956 F.... pulseaudio
Date: Sat Dec 29 14:28:57 2012
HibernationDevice: RESUME=UUID=e9e7a3d6-2d7f-4d2d-8880-ace10b4a942f
InstallationDate: Installed on 2012-09-26 (94 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-21-generic root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-21-generic N/A
 linux-backports-modules-3.5.0-21-generic N/A
 linux-firmware 1.95
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P03AAC
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP03AAC:bd07/12/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 900X3C/900X3D/900X4C/900X4D
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Dave Gilbert (ubuntu-treblig)]

Hi Shaun,
  Can you confirm which Linux version was the last version that didn't trigger the bug?
Also, can you state whether the logs you've attached are from a boot where this bad behaviour happened or from a normal boot?

Dave

[Shaun Crampton (fasaxc)]

The logs were from a successful boot. The previous version I had installed was 3.5.0-20-generic. I'll try to convince grub to give me a boot menu tomorrow and then alternate versions to see if I can absolutely confirm the kernel version as the cause. I'll also run apport-collect to attach the logs from a failed bootup to this bug.

[Shaun Crampton (fasaxc)]

Here's the output from ubuntu-bug for a failed bootup. I collected it by going to a tty and running ubuntu-bug --save.

[Shaun Crampton (fasaxc)]

I tried 5 reboots selecting the older 20-generic kernel from the grub menu with no sign of the problem. I tried 3 reboots with 21-generic and the first two both showed the problem. It looks like the problem was introduced between ubuntu versions 20 and 21.

[Dave Gilbert (ubuntu-treblig)]

Hi Shaun,
  It might also be worth trying something before 3.5.0-20, it had a bunch of graphics updates, but caused problems for some people, that needed another graphics fix in -21 - so it looks like that's also causing you problems.

I'd also ask you try the latest upstream kernel by following the instructions here:

https://wiki.ubuntu.com/Kernel/BugTriage/Responses#Please_Test_Latest_Upstream

Could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.8-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Shaun Crampton (fasaxc)]

I tried kernel v3.8-rc1-raring (even though I'm running quantal). It did boot to the login screen but
* the screen resolution was wrong (lower than usual)
* after logging in, there were a lot of visual artifacts (each time the launcher appeared for example it left behind a brown rectangle)
* my wifi didn't work one I logged in (probably just an issue with trying a mainline kernel?)

I'm not sure whether to call that fixed or not!

[penalvch (penalvch)]

Shaun Crampton, thank you for reporting this and helping make Ubuntu better. Could you please provide the full computer model as noted on the sticker of your laptop (ex. NP900X3A-A03US)?

[Shaun Crampton (fasaxc)]

Sure, it's NP900X4C-A03US

[Shaun Crampton (fasaxc)]

I just tested 23-generic and it also shows the problem. 2 successful boots from 5 attempts. About the same as before.

[penalvch (penalvch)]

Shaun Crampton, thank you for providing the requested information. Could you please specify the last Quantal kernel that allowed you to boot successfully?

[Shaun Crampton (fasaxc)]

3.5.0-20-generic was the last one that did not show the problem.

24-generic also fails.

[penalvch (penalvch)]

Shaun Crampton, thank you for providing the requested information. Could you please perform a commit bisect following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Robin Van Cauter (rvancauter)]

I also have this issue on my NP900X3C-A01BE.

I have found that it might have something todo with "lightdm" as I can get the login screen to popup when I go to tty and use the command 'sudo service lightdm restart'. Sometimes I get an internal error message that has something todo with apportcheckresume, KernelOop... even when I am not getting out of suspend mode (restart for example).

[Shaun Crampton (fasaxc)]

Haven't got around to the commit bisect but just thought I'd add that this is still a problem with 3.5.0-27-generic

[Shaun Crampton (fasaxc)]

I just updated to 13.04 and did 6 reboots without hitting this problem. I think it might have been fixed upstream.

[Shaun Crampton (fasaxc)]

FTR the 13.04 kernel that seems to be working so far is 3.8.0-19-generic #29-Ubuntu

[penalvch (penalvch)]

Shaun Crampton, did you need a backport to a release prior to Raring, or may we close this as Status Invalid?

[Shaun Crampton (fasaxc)]

I don't need a backport but I'm not the only reporter of the bug.

[Shaun Crampton (fasaxc)]

D'oh, I just saw the problem again after a reboot to install a new kernel 3.8.0-19-generic #30-Ubuntu. But I also had a kernel oops during that reboot. I reported the oops under Bug 1176380. I don't reboot often since suspend works well (apart from non-working lid switch) on this laptop.

[penalvch (penalvch)]

Shaun Crampton, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. 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:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Launchpad Janitor (janitor)]

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