crash on boot. ok, then black screen, panel intact
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Rebooted, error message, black desk, panel intact
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: plymouth 0.8.2-2ubuntu28
ProcVersionSign
Uname: Linux 3.2.0-17-
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CurrentDmesg:
[ 18.547042] [drm] nouveau 0000:01:00.0: Output VGA-1 is running on CRTC 0 using output A
[ 19.561779] tulip 0000:02:04.0: eth0: tulip_stop_rxtx() failed (CSR5 0xfc664010 CSR6 0xff972113)
[ 19.561794] net eth0: Setting full-duplex based on MII#1 link partner capability of 45e1
[ 27.176023] eth0: no IPv6 routers present
Date: Mon Feb 20 03:05:12 2012
DefaultPlymouth: /lib/plymouth/
ExecutablePath: /sbin/plymouthd
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Alpha i386 (20120201.1)
MachineType: MICRO-STAR INC. MS-6742
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /sbin/plymouthd --mode=boot --attach-to-session
ProcEnviron: PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/
UpgradeStatus: Upgraded to precise on 2012-02-19 (0 days ago)
UserGroups:
dmi.bios.date: 04/02/01
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Version 07.00T
dmi.board.name: MS-6742
dmi.board.vendor: MICRO-STAR INC.
dmi.board.version: 100
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Uknown Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-6742
dmi.product.
dmi.sys.vendor: MICRO-STAR INC.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #849414, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.