[STAGING] X doesn't start with 2.6.37-6+

Bug #681294 reported by Jean-Baptiste Lallement
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Unassigned
Natty
Fix Released
High
Unassigned

Bug Description

Last known good version: 2.6.37-5
Broken with 2.6.37-6, 2.6.37-7

Steps to reproduce: Boot with 2.6.37-6

The system boots correctly but X doesn't start. The screen changes from 'Aubergine' to completely 'black' when switching from plymouth to gdm.

The system doesn't seem completely dead because there is disk activity but the keyboard doesn't respond and I can not switch to a console.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.37-5-generic 2.6.37-5.14
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.37-5.14-generic 2.6.37-rc2
Uname: Linux 2.6.37-5-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: ALC259 Analog [ALC259 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: j-lallement 1476 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 43'
   Mixer name : 'Realtek ALC259'
   Components : 'HDA:10ec0269,1043841c,00100100'
   Controls : 11
   Simple ctrls : 7
Date: Thu Nov 25 10:55:29 2010
HibernationDevice: RESUME=UUID=e9927661-6c64-4396-9c5d-d1163fdabcec
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: ASUSTeK Computer INC. 1015PE
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-5-generic root=UUID=735f474c-c76d-4426-bab7-d566feb59bcf ro quiet splash
RelatedPackageVersions: linux-firmware 1.40
RfKill:

SourcePackage: linux
StagingDrivers: rt2860sta
Title: [STAGING]
dmi.bios.date: 05/31/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd05/31/2010:svnASUSTeKComputerINC.:pn1015PE:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PE
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :
description: updated
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

2.6.36-7 is broken too.
I confirm that the system is not dead because I can ssh into it.
Let me know which useful information I can collect while the system is in this state.

summary: - [STAGING] X doesn't start with 2.6.37-6
+ [STAGING] X doesn't start with 2.6.37-6+
description: updated
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Jean-Baptiste,

If you could also please 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel Källming (daniel-kallming) wrote :

Hi,

I had the same problem with the same kernels on an atom-based machine with Intel gfx, but after some update today to 2.6.37-7 (I have not tested any mainline kernel) X starts normally again.

tags: added: iso-testing
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Interestingly enough, X starts correctly with 2.6.37-7 #19-ubuntu when booted from a LiveCD, but doesn't work when the system is installed.
Reported also on a Dell Mini9

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: removed: needs-upstream-testing
Revision history for this message
Daniel Källming (daniel-kallming) wrote :

Apparently still black screens sometimes on the atom machine (hp mini 5101) with 2.6.37-7-generic #19-Ubuntu SMP

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

X Starts correctly in failsafe mode however the following error is displayed in the X.log:
FBDEV(0): FBIOPUTCMAP: Invalid argument

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Another discovery, this only happens on cold start.

If I power on the netbook and boot directly to a normal session, the screen is black
If I boot to recovery mode and select failsafe X, wait for X to start, then do a warm restart and choose the normal X session, then X starts just fine.

This looks like a problem of initialization of video driver.

Changed in linux (Ubuntu):
status: Confirmed → Triaged
tags: added: regression-release
Changed in linux (Ubuntu Natty):
importance: Undecided → High
Revision history for this message
Andy Whitcroft (apw) wrote :

There is a patch in the latest Natty kernel (post alpha-1) which fixes some initialisation issues. Could you test that kernel and report back herre. Thanks.

Revision history for this message
Daniel Källming (daniel-kallming) wrote :

2.6.37-8 #21-Ubuntu SMP seems to manage to start x correctly on every boot, for me.

Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

I confirm the fix with kernel 2.6.37-8 #21

Thanks.

Changed in linux (Ubuntu Natty):
status: Triaged → Fix Released
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.