ubuntu x86_64 upgrade 2.6.31-21 fails to show x logon screen but 2.6.31-20 works fine

Bug #549568 reported by rrogers
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

The summary says it all.
Attached are the Xorg.log file from the bad boot and the xorg.conf; which is probably what triggers the problem.
Ray

ProblemType: Bug
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: IXP [ATI IXP], device 0: ATI IXP AC97 [ATI IXP AC97]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rrogers 2690 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'IXP'/'ATI IXP rev 2 with ALC658D at 0xfe02a000, irq 17'
   Mixer name : 'Realtek ALC658D'
   Components : 'AC97a:414c4781'
   Controls : 38
   Simple ctrls : 24
CheckboxSubmission: 80e1bbdb688b7bda285048e81d855ec6
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
Date: Sat Mar 27 07:27:23 2010
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=7167d1b1-5f06-40a6-91a1-a19714dded01
MachineType: HP Pavilion 061 ED907AA-ABA a1228x
Package: linux-image-2.6.31-20-generic 2.6.31-20.58
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-20-generic root=UUID=fdbb64ef-1ffd-4afb-a9b6-1ed1e46e623a ro splash vga=791 quiet splash security=selinux selinux=1
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-20-generic N/A
 linux-firmware 1.26
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Uname: Linux 2.6.31-20-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 11/15/2005
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 3.13
dmi.board.name: Amberine M
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 1.03
dmi.chassis.type: 3
dmi.chassis.version: 1111
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr3.13:bd11/15/2005:svnHPPavilion061:pnED907AA-ABAa1228x:pvr0nx1114RE101AMBEM00:rvnASUSTekComputerINC.:rnAmberineM:rvr1.03:cvn:ct3:cvr1111:
dmi.product.name: ED907AA-ABA a1228x
dmi.product.version: 0nx1114RE101AMBEM00
dmi.sys.vendor: HP Pavilion 061

Revision history for this message
rrogers (rerogers) wrote :
Revision history for this message
rrogers (rerogers) wrote :

Apparently only one upload file at a time is allowed. Here is the second and then I will upload a good Xorg.x.log file for the -21 upgrade.

Revision history for this message
rrogers (rerogers) wrote :

And here is the Xorg.x.log file from the good -20 boot.

Revision history for this message
rrogers (rerogers) wrote :

The second half of message two is garbage (need more coffee)
It should have been:
Apparently only one upload file at a time is allowed. Here is the Xorg log file from the bad boot -21.

tags: added: karmic
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi rrogers,

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 549568

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.

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

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
rrogers (rerogers) wrote :

Hi jeremy,

     This problem is very similar to #495680. I will repeat part of my response there. Your first link is still ambiguous to me; but your second link seems to be resolved (or I misread the index) to be v2.6.33. I will follow the instructions and report tomorrow. Is it possible that the DVD .iso data is incorrect about the internal file dates in the "latest development release"?
"
Well I just keep back from the kernel updates that don't boot 2.6.31-21 is the most recent failure; whereas 2.6.31-20 works. You seem to have a problem that comes and goes with releases. I presume it has to do with "kernel mode setting" (or some such).
I just gave up on complaining. I figured some "update" would fix it; sometime; actually there always seems to be a recent update that works.
The web pages are ambiguous to me: "latest development release of Ubuntu" on page
http://cdimage.ubuntu.com/releases/
refers to 10.04 or karmic?
All of the karmac or 9.10 dates seem to be October 2009 and the 10..04 is a (rc).
"

Ray

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

rrogers,
    I am asking you to test the latest development release, which in this case is 10.04. It is an RC which means a release candidate. I am asking you to test the development branch to see if a rebase of the kernel from upstream stable has resolved the issue. If so, then I can possibly get one of the kernel Engineers to see which commit fixes the issue and determine if a backport to karmic is warranted. I hope this answers the questions.

~JFo

Revision history for this message
Bob Felstead (bob-felstead) wrote :

Hi all,

I'm having issues with the latest release of Kernel 2.6.31-21 on a 32bit system. after installing the update, the system wouldn't boot into X, I simply got the sh:grub> prompt. After some time at the command line I did manage to get the sytem to boot using the follwing commands, -

ismod ntfs
set root=(hd0,1)
loopback loop0 /ubuntu/disks/root.disk
set root=(loop0)
linux /boot/vmlinuz-2.6.31-14-generic root=/dev/sda1 loop=/ubuntu/disks/root.disk ro
initrd /bootinitrd.img-2.6.31-14-generic
boot

Then I rebuilt grub2 and re-booted the system -viola problem resolved. HOWEVER, I still can't boot into kernel 2.6.31-21 as the system hangs, -

[0.969559] kernel panic - not syncing:VFS:unable to mount root fs on unknown block (8,1)

Any ideas? I know that I'm not the only one with this issue.

Bob

Revision history for this message
rrogers (rerogers) wrote :

~JFo
I tried ubuntu-10.04-rc-dvd-amd64.iso. No joy in Mudville. The X11 screens were trashed. The console screens kept giving something like "drm:radeon .. fence.. errors". I don't want to clutter up this bug with the X.0.log and such. Let me know where I should report the failure. As of now I really wouldn't recommend 10.04 and X1300 card installations.
I tried to capture the apport but I couldn't find out where the --save went. I did copy out the /var directory to a USB stick.
Ray

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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

tags: added: kj-expired
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.