crash after rebooting from Ubuntu 11.04

Bug #791089 reported by Alex Colorado on 2011-06-01
116
This bug affects 22 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: acpi-support

I have several partitions, 1 with Win 7, 1 with Ubuntu 10.04 and 1 with Ubuntu 11.04.
When I reboot from Ubuntu 11.04, the PC crashes/reboots itself. If I shutdown from Ubuntu 11.04, on restart the PC crashes during POST. After the crash/reboot, everything works fine.

Here are the different scenarios:
Reboot from Ubuntu 11.04 back into Ubuntu 11.04: No issue.
Reboot from Ubuntu 11.04 into other OS: Crash and reboot after more or less 40 seconds
Reboot from Ubuntu 11.04 and wait in grub2 menu screen: Crash and reboot after more or less 40 seconds.
Shutdown from Ubuntu 11.04: Crash and reboot during POST. No issues afterwards in Windows or Ubuntu
Reboot or shutdown from Windows 7: No issues

Version: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2

It seems to affect a few users (someone posted this issue in Ubuntu forums)
I chose acpi-support as the culprit package, but it was really a shot in the dark.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: alex 1486 F.... pulseaudio
 /dev/snd/controlC0: alex 1486 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xefff4000 irq 21'
   Mixer name : 'Analog Devices AD1988B'
   Components : 'HDA:11d4198b,10438266,00100400'
   Controls : 44
   Simple ctrls : 25
Card1.Amixer.info:
 Card hw:1 'HW121NUSB'/'Plantronics HW121N-USB at usb-0000:00:0b.0-6, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB047f:c247'
   Controls : 8
   Simple ctrls : 4
Card2.Amixer.info:
 Card hw:2 'NVidia_1'/'HDA NVidia at 0xebffc000 irq 16'
   Mixer name : 'Nvidia GPU 16 HDMI/DP'
   Components : 'HDA:10de0016,10de0101,00100100'
   Controls : 16
   Simple ctrls : 4
CurrentDmesg:
 [ 31.984969] EXT4-fs (sda7): re-mounted. Opts: errors=remount-ro,commit=60,commit=0
 [ 32.261730] EXT4-fs (sda6): re-mounted. Opts: errors=remount-ro,commit=60,commit=0
 [ 36.384006] eth0: no IPv6 routers present
DistroRelease: Ubuntu 11.04
HibernationDevice: RESUME=UUID=b93ad851-db83-40cc-aa9a-fbf1c9f31fff
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 003: ID 047f:c247 Plantronics, Inc.
 Bus 002 Device 002: ID 046d:c049 Logitech, Inc. G5 Laser Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer INC. P5N-T DELUXE
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_NZ:en
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-10-generic-pae root=UUID=215176fb-f8ea-4740-8aa3-f14c505af78c ro acpi_enforce_resources=lax quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic-pae 2.6.38.7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-10-generic-pae N/A
 linux-backports-modules-2.6.38-10-generic-pae N/A
 linux-firmware 1.52
RfKill:

Tags: natty running-unity
Uname: Linux 2.6.38-10-generic-pae i686
UpgradeStatus: Upgraded to natty on 2011-06-07 (41 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare
dmi.bios.date: 03/19/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-T DELUXE ACPI BIOS Revision 1702
dmi.board.name: P5N-T DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-TDELUXEACPIBIOSRevision1702:bd03/19/2010:svnASUSTeKComputerINC.:pnP5N-TDELUXE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-TDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5N-T DELUXE
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK Computer INC.

Alex Colorado (alex-kiwikiwi) wrote :
Alex Colorado (alex-kiwikiwi) wrote :
description: updated
description: updated
Jevan Moss (jevan-moss) wrote :

I am experiencing the same issue with exactly the same symptoms using Ubuntu 11.04 x64. I would add that the crash/reboot occurs roughly 40 seconds after doing seemingly anything other than re-launching an Ubuntu 11.04 based OS, including live CDs of other unrelated distros.

If the reboot occurs after launching Windows 7, the only record in the event viewer is a log of an unexpected shutdown.

Steve Langasek (vorlon) wrote :

acpi-support is a deprecated package for handling runtime acpi events; it is uninvolved with reboot handling. Reassigning to the kernel.

affects: acpi-support (Ubuntu) → linux (Ubuntu)
Jevan Moss (jevan-moss) wrote :
Jevan Moss (jevan-moss) wrote :
Jevan Moss (jevan-moss) wrote :

I've added the two logs of my own. It should be noted that I'm now running the UGR modified version of Ubuntu instead of stock, but the issue is unchanged.

summary: - unexpected reboot after rebooting or shuting down from Ubuntu 11.04
+ unexpected reboot after rebooting or shutting down from Ubuntu 11.04

I'd also like to note, based off of the forum thread conversation on this, that everyone affected appears so far to have an Asus motherboard. I also believe they are all very similar boards with many common chips and design elements.

My MoBo is an ASUS P5N32-E SLI.

I have this issue on two computers (both almost identical). Issue began after upgrading to Natty 11.04.

Alex Colorado (alex-kiwikiwi) wrote :

My Mobo is an ASUS P5N-T DeLuxe (SLI)

Jevan Moss (jevan-moss) wrote :

My motherboard is an Asus P5N-E SLI.

Shawn Booth (shawn-booth1970) wrote :

I am also having this problem. My motherboard is an Asus P5N-E SLI.

desher (sjtdesh) wrote :

Same problem, on a pc with a Asus P5n32-e SLI plus. The issue occurs only with 11.04, I've even tried to install a Debian Squeeze and everything works fine.

Arkangyl (arkangyl-gabriel) wrote :

Just updating that this issue still exists in the kernel just released today 2.6.38.10. Thanks.

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

apport-collect 791089

and then change the status of the bug back to 'New'.

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

apport information

tags: added: apport-collected natty running-unity
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

I have now run the command:
apport-collect 791089

Changed in linux (Ubuntu):
status: Incomplete → New
Brad Figg (brad-figg) on 2011-07-19
Changed in linux (Ubuntu):
status: New → Confirmed
PR (pradd) wrote :

Same problem here on P5n32-e sli, if I can provide any logs that may be of use please ask. Hoping for a resolution before my F1 key wears out!!

Cheers
  Chris

Danie l Halperin (ds-halperin) wrote :

I have the exact same problem with Ubuntu 11.04 x64, Windows 7 x64 and an Asus P5N-D motherboard.

summary: - unexpected reboot after rebooting or shutting down from Ubuntu 11.04
+ crash after rebooting or shutting down from Ubuntu 11.04

Minor update that might help track this down (I hope).

After shutting down (N/A to a reboot / restart), if you completely remove power to your PSU via an on-off switch on it, etc., the computer will not bios crash / double post on the next computer boot. I do not know why of course, but it must reset or refresh something that Ubuntu is doing.

John Mason (merc68k) wrote :

I have the same problem with the same board, but I run ArchLinux. Since it seems to also affect Ubuntu and Fedora (http://forums.fedoraforum.org/showthread.php?p=1502068#post1502068), I suspect a kernel or module issue.

I've thought I've had a funny hardware issue for months and tried different CPUs and various hardware solutions all with no impact. I also have been having Windows randomly rebooting while starting up.

Turns out, this is caused by something in the Kernel or OS. After the OS has loaded, if I restart (either cleanly or with the hardware reset button), the next time the PC POSTs, it will automatically restart after about 1 minute, UNLESS I load Linux again!

I tested this a few ways and it happens every time, I went into the BIOS after rebooting, and waited one minute and 10 seconds, reboot. I paused the POST screen with shift+pause/break, and it rebooted after one minute 10 seconds. I timed the Windows bootup and after 1 minute 10 seconds, same deal again.

I tried the same thing with powering the system off completely, and if I was last in Linux, I get an error at POST, saying the last POST failed. If I watch closely on power on, I see my video card BIOS for a split second immediately after powering up, then the monitor loses signal and it flashes up again, and then POSTs.

I suspect somehow some timer is being set by the kernel that causes a reboot, and this somehow also survives powering off. So when powered off for more than 1 minute, this happens immediately, or after rebooting, it takes about 1 minute.

Also I've tried booting from a Linux Mint 11 (based on Ubuntu 11 I believe) live CD and have the same result.

Can you try rebooting from Ubuntu, entering your BIOS setup screen and waiting 1-2 minutes? I think you'll see the "magic" reboot...

I've only just discovered what's going on here today, so I'm still trying to find out how to fix it... but I'm "glad" to hear someone else has this issue. I'm glad I'm not dealing with a hardware issue either, as my machine is rock solid otherwise.

 I wonder if it's maybe a bug in the P5N-D BIOS...?

John Mason (merc68k) wrote :

PS, my kernel is 2.6.39-ARCH and it's 64 bit.

John Mason (merc68k) wrote :

I've found the cause of this.

I looked at my loaded modules for anything nvidia-specific and the first hit was nv_tco.

Looked at the source for this module (http://lxr.free-electrons.com/source/drivers/watchdog/nv_tco.c) and it seems to handle some hardware watchdog timer for Nvidia chipsets (as I have on my P5N-D).

I disabled this module from loading, rebooted, and then rebooted again, and no more spontaneous reboots. I haven't tried any cold boots yet but I suspect that problem will be gone too.

I guess maybe I should file a bug against this module...

Alex Colorado (alex-kiwikiwi) wrote :

Wow, thanks John!!! I had lost all hope, but you are spot on I think.

I haven't tested thoroughly, but I have done a restart without a spontaneous reboot!

   gksudo gedit /etc/modprobe.d/blacklist.conf

add

   blacklist nv_tco

I suppose these patches are related to this:
https://patchwork.kernel.org/patch/949952/

THe BIOS is supposed to disabled the watchdog, but it doesn't!

Alex Colorado (alex-kiwikiwi) wrote :

Any ideas how to reassign this bug to nv_tco?
When I search for it it doesn't find it, but it does find watchdog... Is that the package that contains that module?

John Mason (merc68k) wrote :

Oh, is there a BIOS setting for the watchdog? I don't remember seeing one.

In my case (Archlinux) this module comes with the kernel:

---
pacman -Qo ./modules/3.0-ARCH/kernel/drivers/watchdog/nv_tco.ko.gz

./modules/3.0-ARCH/kernel/drivers/watchdog/nv_tco.ko.gz is owned by linux 3.0.1-1
---

I just upgraded to kernel 3.0 last night, I wonder if by any chance this is fixed now. That patch you referenced looks like it could be the cause of this issue, but I'm sure this has been going on much longer than a month -- I would say more like 6 months to a year for me.

Arkangyl (arkangyl-gabriel) wrote :

OK, I read everything over there and may post my question there too in case it gets missed here.

One, does blacklisting this module cause any system changes, other issues, missing *anything*, etc. I need to be aware of as I would hate to "solve" (work around) one problem only to add some other issue or oddity.

Two, assuming this gets fixed wherever it needs to be fixed, I also assume I would want to un-blacklist this module at that point. How would I go about doing that, or is it as simple as just going into the .conf file and deleting the line that added the module?

Three, the work around for the module getting blacklisted, would this approach also apply to other distros (Linux Mint, PCLinuxOS, etc. as this is present in both of those also) that are having the same issue?

Alex Colorado (alex-kiwikiwi) wrote :

@John
> Oh, is there a BIOS setting for the watchdog?
I'm not saying there is a BIOS option. I think the upon boot/restart, the BIOS is supposed to disable the tco watchdog/timer.

@Arkangyl
I'm no expert on this but if you search about nvidia (or intel) TCO timers, you will find this:

"timeout timer as part of the TCO feature in the CPU that will trigger a reboot signal after the second timeout which could be caused by heat or by any software lockup."

It seems it's a protection mechanism, obviously, disable at your own risk

To re-enable the module just remove it from the blacklist.
The easy and quick way I found to remove that module was to blacklist it. If you find a better one, let us know!

I'm trying to see how the watchdog can be configured. Maybe some config option will prevent it from leaving the timer enabled after a reboot.

John Mason (merc68k) wrote :

@Alex

  Okay, yes I agree that the watchdog/timer should be reset on reboot; it seems silly that it would remain enabled after the BIOS initializes.

A config option would be fine for clean reboots, but it persists even after a hardware reset once it's been set up, so I think the best option would be either for the BIOS to reset it, or maybe there is a facility when setting up the watchdog for whether it should remain initialized after reboots (but I doubt it).

PR (pradd) wrote :

Superb John,

nv_tco added to blacklist & reboot problem resolved. I do agree however that this module would be better enabled - does need fixing first tho, I imagine there is "some" risk not having this module enabled but a bigger risk is hardware damage from these constant false boots IMHO.

Cheers
  Chris

John Mason (merc68k) wrote :

Glad to hear this is working for everyone else! Personally I can't think of a time that my system has locked hard and this watchdog would have actually come in handy, most times I'd have hit the reset button myself before waiting one minute for it to kick in. I guess it would be useful for a production system though.

I'm not sure where to take this next; how can we identify whether the problem is with the module itself or some flaw in the Asus BIOS...?

Bjorn Helgaas (bjorn-helgaas) wrote :

Blacklisting the nv_tco module is not a good long-term solution.

A recent upstream commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=6b01d30eef64456ad9e261d2173266a3244da8e1 looks like it could be a fix for this issue.

Could somebody affected by this problem build a kernel with that change and test it?

vista killer (vistakiller) wrote :

I have the same problem with an asus P5N32-E sli in kubuntu 11.04 and to kubuntu 11.10. Yesterday i have upgrade to 11.10 and the problem still exist with the new kernel 3.0.9
There is a same bug report here

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/794702

nickkkname (yehgoo) wrote :

The 'same' on ASUS motherboard with nForce 790i SLI chipset. This command prevented sudden reboot after restarting or shutting down from Ubuntu 11.04 as John previously described. Agreed that this is not a solution of course, should to be a bug fix that resolve the problem in core which cause it. Thanks for all.

command:
sudo sh -c "echo 'blacklist nv_tco' >> /etc/modprobe.d/blacklist-watchdog.conf"

...reboot twice.

rumpl (rumplstielz) wrote :

Made the above entry in the blacklist-watchdog on ubuntu 11.10 beta and: kernel crash when rebooting.

Had to reinstall the kernel, because the system won't come up after implementing the blacklist entry with initramfs... This is getting a serious bug.
Still have to check if the same happens when I put the entry in blacklist.conf instead of blacklist-watchdog

rumpl (rumplstielz) on 2011-10-22
summary: - crash after rebooting or shutting down from Ubuntu 11.04
+ crash after rebooting or shutting down from Ubuntu 11.04 & 11.10
rumpl (rumplstielz) wrote :

worked!

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest release candidate kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). 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 by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

tags: added: needs-upstream-testing
rumpl (rumplstielz) wrote :

will do, because the solution I did with the "fedora" fix did give some "special" behaviours.
When rebooting, no problem. When shutting down and afterwards booting windows (dual boot) or even 11.10, my machine reboots while booting and I am having the same "press F1, there was a POST failure" issue again.

tags: added: kernel-fixed-upstream-v3.2-rc2
Pascal Bergmann (pbergmann) wrote :

Mainline kernel 3.2-rc2 seems to fix this. It takes some time to pass the BIOS bootlogo but I don't get any reboots for now.
Ubuntu 11.10 (64), Asus P5N-D, NVIDIA GTX 580.

Fated Snowfox (linuxfox) wrote :

Mobo: P5N-D,
GFX: ATI Radeon HD 5670
Mem: 6GB
Kernel: ubuntu 3.0.0-13-generic-pae #22-Ubuntu SMP (Ubuntu 11.10 32)

As per this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089/comments/43 I blacklisted nv_tco and found the following:

No POST crashing on warm or cold start.
Far /far/ more responsive desktop.
Clean shutdown (system shuts down without dropping to console to display errors, get the pretty graphical dots)

There is definitely a fault with that watchdog module and the P5N-D, which has relieved me immensely; I thought it may have been hardware and was expecting to have to replace my machine.

appe (christoffer-appe) wrote :

I also have this problem using Asus P5N-E SLI motherboard. Hope it gets sorted, subscribed this post.

Alex Colorado, thank you reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

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

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

summary: - crash after rebooting or shutting down from Ubuntu 11.04 & 11.10
+ crash after rebooting from Ubuntu 11.04
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
David Sharpe (nimnio) wrote :

I am experiencing the same symptoms with Ubuntu 11.10. I have an Asus P5N-D motherboard.

David Sharpe, please execute the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

Changed in linux (Ubuntu):
importance: Undecided → Medium
Ashley Cooper (ashley-cooper) wrote :

Hi - this happens to me too. Very new to linux (<1 year) - Dual boot windows7 64 bit with linux mint 64bit (currently) also happened with ubuntu 11.10 (why i tried mint, still happens!) - asus p5n32-e sli motherboard, 8GB ram, nvidia gtx, etc.

Every reboot from linux to try and get back into windows for a few legacy programs causes a POST fail "press f1 to continue" etc. as previously mentioned. Two reboots later and windows loads fine. I havent disabled nv_tco yet, hoping for a better solution?
let me know if you want more apport information and how to provide this. Many thanks for your help.

David Sharpe (nimnio) wrote :

Cooper, yehgoo's suggestion worked for me. I entered

sudo sh -c "echo 'blacklist nv_tco' >> /etc/modprobe.d/blacklist-watchdog.conf"

on the command line, which just appends "blacklist nv_tco" to the "/etc/modprobe.d/blacklist-watchdog.conf" list. No problems so far. I too, would like a better solution, but that's Linux for you.

Ashley Cooper, please execute the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

David Sharpe, please stop posting comments to this report. If you have a problem in Ubuntu, please perform the requested actions already asked of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/791089/comments/65 .

David Sharpe (nimnio) wrote :

All right, this will be my last comment: I already did what you requested, and you are subscribed.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/984511

Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: daniel 2415 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfe024000 irq 22'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043829e,00100002'
   Controls : 43
   Simple ctrls : 21
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=4ceef0d7-ca49-4188-8f7d-d1ac6c397462
InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release amd64 (20110720.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
 Bus 002 Device 003: ID 0408:3000 Quanta Computer, Inc. Optical dual-touch panel
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_IE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-31-generic root=UUID=855819f5-9e84-4dc0-9f79-03e7ad867661 ro vga=771 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-31-generic N/A
 linux-backports-modules-3.2.0-31-generic N/A
 linux-firmware 1.79.1
RfKill:

Tags: precise running-unity
Uname: Linux 3.2.0-31-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-09-08 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/02/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N-D ACPI BIOS Revision 0502
dmi.board.name: P5N-D
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-DACPIBIOSRevision0502:bd04/02/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-D:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

tags: added: precise

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

dannyboy9201, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

tags: removed: precise
To post a comment you must log in.