Bug 789271

Summary: firstboot-text prevents system from booting
Product: [Fedora] Fedora Reporter: Hongqing Yang <hoyang>
Component: xorg-x11-driversAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: awilliam, tflink, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-17 17:27:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
anaconda log
none
anaconda xlog
none
program log
none
storage log
none
syslog
none
install log
none
install log syslog
none
X log none

Description Hongqing Yang 2012-02-10 08:52:56 UTC
Created attachment 560825 [details]
anaconda log

Description of problem:

install system with basic video driver, after reboot, get the text
"hda_intel:azx_get_response timeout, switching to simgle_cmd mode"


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install system with basic video driver mode
2. reboot after installation
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Hongqing Yang 2012-02-10 08:53:54 UTC
Created attachment 560826 [details]
anaconda xlog

Comment 2 Hongqing Yang 2012-02-10 08:54:32 UTC
Created attachment 560827 [details]
program log

Comment 3 Hongqing Yang 2012-02-10 08:54:59 UTC
Created attachment 560828 [details]
storage log

Comment 4 Hongqing Yang 2012-02-10 08:55:21 UTC
Created attachment 560829 [details]
syslog

Comment 5 Hongqing Yang 2012-02-10 08:55:49 UTC
Created attachment 560830 [details]
install log

Comment 6 Hongqing Yang 2012-02-10 08:56:25 UTC
Created attachment 560831 [details]
install log syslog

Comment 7 Hongqing Yang 2012-02-10 08:58:39 UTC
file this as F17Alpha Block according F17 Alpha release criteria article
"14.In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account "

Comment 8 Martin Gracik 2012-02-10 09:40:10 UTC
There is no firstboot-text in rawhide. I believe this has nothing to do with the firstboot application.

Comment 9 Adam Williamson 2012-02-10 17:56:29 UTC
Yeah, there's no firstboot-text app or service in F17 so far as I can tell, so I don't think this is a firstboot issue.

Hongqing, can you check if the problem here is some service hanging, or if it's simply X failing to start up? (Check /var/log/Xorg.0.log). Was this a DVD or network install? What version of libpciaccess is installed? Thanks!

Discussed at 2012-02-10 blocker review meeting. Agreed we need more information (see above) to make a blocker determination for this bug. Will revisit next week.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 10 Tim Flink 2012-02-12 19:36:16 UTC
OK, I think I know why this was filed against firstboot-text.

A similar issue was brought up in the firstboot-text bug that we hit in F16 (bz#737118) but as stated in bug 737118 comment 32, it is not an issue with firstboot and a different bug needs to be filed against alsa or pulseaudio.

Hongqing, can you give more details on the affects of this bug? Is it preventing you from logging into the installed system? What else is going on besides the log messages on the console @ login time?

Comment 11 Hongqing Yang 2012-02-13 03:26:59 UTC
With F17 Alpha TC2
Before reboot, I got the error on terminal window 2 "Oh no. Something has gone wrong." and the message at terminal window 1 ""hda_intel:azx_get_response timeout, switching to simgle_cmd mode". After reboot, I still hit the information at terminal window 1, but I could login now. There is VESA error in the Xlog.0.log.

Comment 12 Hongqing Yang 2012-02-13 03:28:16 UTC
Created attachment 561346 [details]
X log

Comment 13 Adam Williamson 2012-02-13 17:23:06 UTC
I don't see any errors in that X log?



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 14 Hongqing Yang 2012-02-15 06:53:32 UTC
(In reply to comment #13)
> I don't see any errors in that X log?
> 
> 
> 
> -- 
> Fedora Bugzappers volunteer triage team
> https://fedoraproject.org/wiki/BugZappers

sorry. I think I have mixed it with other guest. I have installed several guests,
there is no ERR in X log.

Comment 15 Hongqing Yang 2012-02-16 06:39:22 UTC
This is fixed with F17 Alpha RC2

Comment 16 Adam Williamson 2012-02-17 17:27:27 UTC
Discussed at 2012-02-17 blocker review meeting. As it's reported to be fixed in RC2, we will just close this instead.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers