Bug 393024

Summary:	Booting with ACPI fails on Acer Extensa 5220
Product:	[openSUSE] openSUSE 11.0	Reporter:	Stefan Majewsky <majewsky>
Component:	Bootloader	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Critical
Priority:	P5 - None	CC:	holler
Version:	Factory
Target Milestone:	---
Hardware:	x86
OS:	openSUSE 11.0
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/var/log/boot.msg dmesg output hwinfo output ~/.xsession-errors

Description Stefan Majewsky 2008-05-21 10:07:21 UTC

Yesterday (20 May 2008) I did a `zypper dup` from openSUSE 11.0 Factory. After this update (kernel version number increased from 2.6.25.3 to 2.6.25.4) the kernel failed to boot. I examined the problem and found that the kernel can not boot until "acpi=off" is set in GRUB.

Additionally, starting Xorg now takes at least one minute: After about a half minute with an empty screen, a mouse cursor in form of a cross appears. At this time, I'm pressing Ctrl-Alt-F1. After another half minute, the terminal is shown (the mouse cursor is still there, but not movable any more). At this moment, Xorg resumes loading (with a noticeable hard drive load), so I switch back with Ctrl-Alt-F7. I can see KDE 4's splash screen, but the progress indicator halts at 50%. I have to switch back to the console, otherwise the startup is not completed.

I will be attaching .xsession-errors, boot.msg and dmesg after a clean reboot. Please comment if you need more information.

Comment 1 Stefan Majewsky 2008-05-21 10:17:36 UTC

Created attachment 217191 [details]
/var/log/boot.msg

Comment 2 Stefan Majewsky 2008-05-21 10:18:07 UTC

Created attachment 217192 [details]
dmesg output

Comment 3 Stefan Majewsky 2008-05-21 10:18:47 UTC

Created attachment 217193 [details]
hwinfo output

Comment 4 Stefan Majewsky 2008-05-21 10:19:18 UTC

Created attachment 217194 [details]
~/.xsession-errors

Comment 5 Hans-Peter Holler 2008-05-21 10:25:07 UTC


*** This bug has been marked as a duplicate of bug 391845 ***