Ubuntu

[Dell Vostro 460]: System is unresponsive after Unity login screen.

Reported by Jeff Marcom on 2012-06-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
Precise
Medium
Unassigned

Bug Description

Apport log atttached: apport.linux-image-3.2.0-23-generic.CdwdYl.apport

System seems to work fine if you switch to tty2-9. However if you log in through Unity,the system fails to bring up the desktop environment. Mouse movements, keyboard actions are unresponsive after logging in. I've tried also booting the 12.04 image from a usb key and using the "Try ubuntu" option and the issue is still valid.

I was able to grab the apport dump via crtl alt f2 terminal.

lsb-release info:
12.04 Precise, kernel version 3.2.0.23.

This issue is not a problem with 11.10 or 11.04.
---
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
DistroRelease: Ubuntu 12.04
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-meta
Tags: precise precise precise
Uname: Linux 3.5.0-030500rc6-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Jeff Marcom (jeffmarcom) wrote :
tags: added: amd64 apport-bug precise
summary: - [Dell Vostro 460]: Unresponsive after Unity login screen.
+ [Dell Vostro 460]: System is unresponsive after Unity login screen.
Daniel van Vugt (vanvugt) wrote :

Jeff, could you please try logging into tty2-9 and running:
   unity --reset

Warning: That will reset any options you've configured in CCSM back to defaults. But for some people, it does solve this problem.

Changed in unity (Ubuntu):
status: New → Incomplete
Jeff Marcom (jeffmarcom) wrote :

After the issue occurs, I am unable to access tty9. The keyboard and system are both unresponsive at this point. Running unity --reset before issue occurs has no effect.

Changed in unity (Ubuntu):
status: Incomplete → Confirmed
Jeff Marcom (jeffmarcom) wrote :

I was able t reproduce the situation and quickly switch to tty9 before the lock up occured. I am still unable to type anything in any tty, however I see the following errors printed to the screen:

BUG: soft lockup - CPU#0 stuck for 22s [apport-gpu-error 2777]

and

BUG: soft lockup - CPU#1 stuck for 22s [compiz-error:2290]

It will do this for every logical cpu.

Daniel van Vugt (vanvugt) wrote :

Thanks Jeff. That appears to be a kernel message. If you're sure "BUG: soft lockup ..." is directly related to this bug then we should assign it to the Linux kernel, or the graphics driver.

Changed in unity (Ubuntu):
status: Confirmed → Incomplete
tags: added: rls-q-incoming
Jeff Marcom (jeffmarcom) on 2012-06-11
affects: unity (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → New
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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.5-rc2-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
tags: added: kernel-da-key

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

apport-collect 1009585

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Ara Pulido (apulido) on 2012-06-13
tags: added: needs-uptream-testing regression-release
removed: needs-upstream-testing

Removing the rls-q-incoming tag until we have proper confirmation against Quantal.

tags: removed: rls-q-incoming
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium

@Jeff - Please provide the log files for this bug and test with the upstream kernel when you get a chance

Jeff Marcom (jeffmarcom) wrote :

@Brad, I can't pull the apport logs with X, because it tries to open firefox. Is there a way around this?

Jeff Marcom (jeffmarcom) wrote :

I tried updating to quantal rc3 3.5.0 kernel version. X now starts, system is completely unresponsive. I can't switch tty.

Jeff Marcom (jeffmarcom) on 2012-06-22
Changed in linux (Ubuntu):
status: Incomplete → New
Brad Figg (brad-figg) wrote :

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

apport-collect 1009585

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Precise):
status: New → Incomplete
tags: added: bot-stop-nagging
removed: needs-uptream-testing
Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Can you also confirm this bug still exists with the -rc6 kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc6-quantal/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Precise):
status: Confirmed → Incomplete
Jeff Marcom (jeffmarcom) wrote :

Bug still exists in 3.5 rc6.

Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
Brad Figg (brad-figg) wrote :

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

apport-collect 1009585

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Precise):
status: New → Incomplete
Jeff Marcom (jeffmarcom) wrote :

I tried running running apport through an SSH session so that I would have access to firefox for openid authentication.

I don't think I can grab the required logs due to the nature of this bug.

tags: added: apport-collected
description: updated
Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
Changed in linux (Ubuntu):
status: New → Confirmed
Changed in linux (Ubuntu Precise):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

tags: added: performing-bisect
Joseph Salisbury (jsalisbury) wrote :

We can perform a bisect to find the exact commit that caused this regression. Can you test the following kernels and report back if either exhibit this bug:

v3.0 latest: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.0.37-oneiric/
v3.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-oneiric/
v3.2-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc1-oneiric/

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Precise):
status: Confirmed → Incomplete
Jeff Marcom (jeffmarcom) wrote :

This particular system was certified with 3.0. Kernel 3.1 worked without issue. The 3.2 rc1 presented the bug.

Changed in linux (Ubuntu):
status: Incomplete → New
Changed in linux (Ubuntu Precise):
status: Incomplete → New
Brad Figg (brad-figg) wrote :

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

apport-collect 1009585

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Precise):
status: New → Incomplete
Jeff Marcom (jeffmarcom) on 2012-07-19
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

I started a kernel bisect between v3.1 and v3.2-rc1. The first test kernel is up to comit:
37be944a0270402f9cda291a930b0286f6dc92f5

The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1009585

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Precise):
status: Confirmed → Incomplete
Jeff Marcom (jeffmarcom) wrote :

Installed: Linux 201009-6589 3.1.0-030100-generic #201207191900 SMP Thu Jul 19 18:03:29 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

This does not seem to have the bug. I was able to log into unity and run firefox and system-settings fine.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
Jeff Marcom (jeffmarcom) wrote :

Sorry Joseph, I think grub was loading the base 3.2.0.23 when I thought I was testing rc1.

In any event I went through the following path and found the first instance I saw where the bug was introduced:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc1-oneiric/ <- Good
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc2-oneiric/ <- Good
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc4-oneiric/ <- Good
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc5-oneiric/ <- Good
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc6-precise/ <- BAD

Again, really sorry for the confusion. Hope this help a bit.

Jeff Marcom (jeffmarcom) wrote :
Changed in linux (Ubuntu):
status: Confirmed → New
Changed in linux (Ubuntu Precise):
status: Confirmed → New
Brad Figg (brad-figg) wrote :

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

apport-collect 1009585

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.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Precise):
status: New → Incomplete
Jeff Marcom (jeffmarcom) on 2012-07-19
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

I restarted the bisect between rc5 and rc6. The first test kernel is up to commit:
b0d78ee89c4ac1e99dda52f304baf82bd2a6c946

The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1009585

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Changed in linux (Ubuntu Precise):
status: Confirmed → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Jeff Marcom (jeffmarcom) wrote :

That seems to have fixed the issue Joseph. Thanks!

Changed in linux (Ubuntu Precise):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

The next test kernel is built up to commit:
2cfab8d74ebfbe06ce2947117945c4f45a5915ec

The test kernel can be downloaded from:
http://people.canonical.com/~jsalisbury/lp1009585

Can you test that kernel and report back if it has the bug or not?

Thanks in advance!

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers