[Gigabyte H87-HD3] Unexpected crash in commandline mode Ubuntu 12.10 (initctl: Event failed)

Bug #1250043 reported by ThomasSpr
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Installation Ubuntu 12.10 on a PC with GTX 770. The OS wouldn't boot probably because of driver bugs, it would display only purple lines at the top of the screen.
Tried booting in recovery mode, option resume, got to the command line. After login at the command line the system crashes without notice and the screen goes black. This happens in a timing window of ~30 seconds to 2 minutes (tried a few times to get this bug report). There is a message on the screen but the screen goes black to fast to read it.

After trying a while I managed to read it, the errormessage is:
"initctl: Event failed"
Hope it helps ;)

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic x86_64
ApportVersion: 2.6.1-0ubuntu3
Architecture: amd64
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
CurrentDmesg:
 [ 15.720614] r8169 0000:03:00.0: >eth0: link down
 [ 15.720874] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 15.721031] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
 [ 17.480027] r8169 0000:03:00.0: >eth0: link up
 [ 17.480283] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Date: Mon Nov 11 11:51:20 2013
HibernationDevice: RESUME=UUID=5a6f96c1-ee6f-4a7c-9e17-02c8d631b2c7
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H87-HD3
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=561ff017-9203-44cb-9880-b0abbbb59605 ro recovery nomodeset
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-17-generic N/A
 linux-backports-modules-3.5.0-17-generic N/A
 linux-firmware 1.95
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87-HD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd05/09/2013:svnGigabyteTechnologyCo.,Ltd.:pnH87-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH87-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: H87-HD3
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Revision history for this message
ThomasSpr (thomas-spr) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
ThomasSpr (thomas-spr) wrote : Re: Unexpected crash in commandline mode Ubuntu 12.10

After trying for a while it seems like the error message is:

"initctl: Event failed"

summary: - Unexpected crash in commandline mode Ubuntu 12.10
+ Unexpected crash in commandline mode Ubuntu 12.10 (initctl: Event
+ failed)
description: updated
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Unexpected crash in commandline mode Ubuntu 12.10 (initctl: Event failed)

Can you see if this issue also exists with the latest Trusty build:

http://cdimage.ubuntu.com/daily-live/current/

Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
ThomasSpr (thomas-spr) wrote :

I will test the issue with this build as soon as I can (probably in 8 hours).

Should I reduced some partitions and keep the 12.10 version on the system and install the trusty build OR should I just remove the 12.10 version and install the trusty build in the space currently occupied by the 12.10 version?

Revision history for this message
ThomasSpr (thomas-spr) wrote :

Just tested with latest Trusty build (resized a Windows partition to get it on another harddrive), the "initcl: Event failed" error message appeared before I could log in, after I tried booting from recovery mode. (Normal booting etc. just showed blinking underscore cursor)

Revision history for this message
penalvch (penalvch) wrote :

ThomasSpr, is there a prior version of Ubuntu where you can boot into the OS without this problem (ex. Precise)?

tags: added: bios-outdated-f5 needs-upstream-testing regression-potential
tags: added: trusty
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
ThomasSpr (thomas-spr) wrote :

Sorry that it took so long, I tried it with 10.10 and didn't succeed. I will try 12.04 (Precise) but not sure when I will get to it, sorry.

Revision history for this message
Natsisthanasis (natsisthanasis) wrote :

I want to built a new system with Gigabyte H87-HD3 motherboard, and I am not happy finding this bug.
Has anyone installed Ubuntu or any linux distro withouts problems?

penalvch (penalvch)
summary: - Unexpected crash in commandline mode Ubuntu 12.10 (initctl: Event
- failed)
+ [Gigabyte H87-HD3] Unexpected crash in commandline mode Ubuntu 12.10
+ (initctl: Event failed)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.