lenovo w540 hangs after boot

Bug #1397793 reported by Mike Carifio
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I've installed utopic on 14.10. After I boot, I get about 15s of unity and then the system hangs. It's difficult to give you any more data. I've reinstalled a few times to no avail.

Tags: lenovo utopic
Revision history for this message
Mike Carifio (carifio) wrote :

Bug #1336690 is probably related.

Revision history for this message
Mike Carifio (carifio) wrote :

Bug #1386518 is related. I get a "hard cpu lockup cpu 5" or a message to that effect. Will try an upstream kernel.

Revision history for this message
penalvch (penalvch) wrote :

Mike Carifio, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1397793

As well, is this reproducible in the latest release of Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ ?

affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Mike Carifio (carifio) wrote :

fromn apport-cli

Revision history for this message
penalvch (penalvch) wrote :

Mike Carifio, thank you for reporting this and helping make Ubuntu better. However, your crash report is manually attached. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
importance: Low → Undecided
status: Incomplete → Invalid
Revision history for this message
Mike Carifio (carifio) wrote :

Related http://www.phoronix.com/scan.php?page=news_item&px=MTg1MDc

Certainly isn't invalid or low. But I will try to resubmit in the proscribed way.

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.