Bug 665392

Summary: kernel 2.6.35.10-72.fc14.x86_64 hangs on boot
Product: [Fedora] Fedora Reporter: Andy Bentley <albiii>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: albiii, gansalmon, itamar, jonathan, josdekloe, kernel-maint, kmcmartin, madhu.chinakonda, wgianopoulos
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
HP Pavilion Laptop model dv7-2180, FC14, LUKS enabled, TPM enabled. Has been working fine for 2 yrs through several FC revs FC12, 13, now 14.
Last Closed: 2010-12-23 20:50:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andy Bentley 2010-12-23 14:53:53 UTC 
Description of problem:
yum update  - installed new kernel 
Have previously had luks(encrypted HD) & TPM on with no problems.
rebooted cleanly
grub prompt to select kernel <selected latetst, 2.6.35.10-72>
prompted for luks password <took it ok, didn't get reprompted>
Fedora logo shadow shows up and tip of logo begins to turn white to indicate that LUKS is decrypting the HD.
LUKS decrypt stalls ?  waited 45 min and, the kernel never booted.
rebooted selected older kernel, works fine.


Version-Release number of selected component (if applicable):
Suspecting is the 2.6.35.10-72.fc14.x86_64 kernel because I can select a previous kernel from grub boot, luks works, kernel boots, everything else seems to work ok.  I did a yum update and it reports that there is nothing to update <as of Dec 23 as of 14:00 zulu>

How reproducible:
every time

Steps to Reproduce:
1. ? have tpm and luks on ? <not sure if this has anything to do with the problem.. ???
2. yum update to kernel 2.6.35.10-72.fc14.x86_64
3. shutdown cleanly, reboot computer, enter LUKS password, HANG...
  
Actual results:
start computer, at grub prompt select kernel 2.6.35.10-72.fc14.x86_64, enter LUKS password, a shadow of the fedora logo is displayed (as usual), the lower left tip turns white(as usual), but the rest of the logo does not turn white, it just hangs there forever and no disk activity is seen. LUKS fails to decrypt HD under kernel 2.6.35.10-72.fc14.x86_64


Expected results:
start computer, at grub prompt select kernel 2.6.35.10-72.fc14.x86_64, enter LUKS password, a shadow of the fedora logo is displayed, the lower left tip turns white, the rest of the logo slowly turns white, the kernel boots, the user logon prompt is displayed, and users can log in and preform normal duties.

Additional info:
Comment 1 Andy Bentley 2010-12-23 15:58:12 UTC 
from var/logs/messages
----- YUM update --------------->
Dec 23 06:42:27 hostname yum[32540]: Updated: PackageKit-yum-0.6.11-1.fc14.x86_64
Dec 23 06:42:44 hostname yum[32540]: Updated: PackageKit-glib-0.6.11-1.fc14.x86_64
Dec 23 06:42:44 hostname dbus: [system] Reloaded configuration
Dec 23 06:42:44 hostname dbus: [system] Reloaded configuration
Dec 23 06:42:44 hostname dbus: [system] Reloaded configuration
Dec 23 06:42:44 hostname dbus: [system] Reloaded configuration
Dec 23 06:42:51 hostname yum[32540]: Updated: PackageKit-0.6.11-1.fc14.x86_64
Dec 23 06:43:22 hostname yum[32540]: Updated: selinux-policy-3.9.7-18.fc14.noarch
Dec 23 06:43:23 hostname yum[32540]: Updated: PackageKit-device-rebind-0.6.11-1.fc14.x86_64
Dec 23 06:43:24 hostname yum[32540]: Updated: PackageKit-gstreamer-plugin-0.6.11-1.fc14.x86_64
Dec 23 06:43:25 hostname yum[32540]: Updated: PackageKit-gtk-module-0.6.11-1.fc14.x86_64
Dec 23 06:44:22 hostname dbus: avc:  received policyload notice (seqno=2)
Dec 23 06:44:22 hostname dbus: avc:  received policyload notice (seqno=2)
Dec 23 06:44:22 hostname dbus: [system] Reloaded configuration
Dec 23 06:45:56 hostname yum[32540]: Updated: selinux-policy-targeted-3.9.7-18.fc14.noarch
Dec 23 06:45:57 hostname yum[32540]: Updated: PackageKit-yum-plugin-0.6.11-1.fc14.x86_64 
Dec 23 06:53:20 hostname smartd[2158]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Dec 23 07:23:19 hostname smartd[2158]: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors
Dec 23 07:30:41 hostname yum[351]: Updated: boost-system-1.44.0-4.fc14.x86_64
Dec 23 07:30:43 hostname yum[351]: Updated: boost-filesystem-1.44.0-4.fc14.x86_64
Dec 23 07:30:44 hostname yum[351]: Updated: boost-date-time-1.44.0-4.fc14.x86_64
Dec 23 07:30:46 hostname yum[351]: Updated: boost-regex-1.44.0-4.fc14.x86_64
Dec 23 07:30:47 hostname yum[351]: Updated: boost-thread-1.44.0-4.fc14.x86_64
Dec 23 07:30:49 hostname yum[351]: Updated: boost-wave-1.44.0-4.fc14.x86_64
Dec 23 07:30:50 hostname yum[351]: Updated: boost-graph-1.44.0-4.fc14.x86_64
Dec 23 07:30:52 hostname yum[351]: Updated: boost-test-1.44.0-4.fc14.x86_64
Dec 23 07:30:53 hostname yum[351]: Updated: boost-signals-1.44.0-4.fc14.x86_64
Dec 23 07:30:54 hostname yum[351]: Updated: boost-program-options-1.44.0-4.fc14.x86_64
Dec 23 07:30:56 hostname yum[351]: Updated: boost-python-1.44.0-4.fc14.x86_64
Dec 23 07:30:57 hostname yum[351]: Updated: boost-serialization-1.44.0-4.fc14.x86_64
Dec 23 07:30:59 hostname yum[351]: Updated: boost-iostreams-1.44.0-4.fc14.x86_64
Dec 23 07:31:01 hostname yum[351]: Updated: tkimg-1.4-1.fc14.x86_64
Dec 23 07:31:19 hostname yum[351]: Installed: kernel-2.6.35.10-72.fc14.x86_64
Dec 23 07:31:19 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:19 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:19 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:19 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:23 hostname auditd[1304]: config change requested by pid=399 auid=500 subj=unconfined_u:system_r:initrc_t:s0
Dec 23 07:31:23 hostname auditd[1304]: audit(1293107483.640:9222) config changed, auid=500 pid=399 subj=unconfined_u:system_r:initrc_t:s0 res=success
Dec 23 07:31:23 hostname yum[351]: Updated: setroubleshoot-server-3.0.15-1.fc14.x86_64
Dec 23 07:31:25 hostname yum[351]: Updated: setroubleshoot-plugins-3.0.8-1.fc14.noarch
Dec 23 07:31:26 hostname yum[351]: Updated: boost-1.44.0-4.fc14.x86_64
Dec 23 07:31:27 hostname yum[351]: Updated: xorg-x11-server-common-1.9.3-3.fc14.x86_64
Dec 23 07:31:29 hostname yum[351]: Updated: xorg-x11-server-Xorg-1.9.3-3.fc14.x86_64
Dec 23 07:31:29 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:29 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:29 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:29 hostname dbus: [system] Reloaded configuration
Dec 23 07:31:44 hostname yum[351]: Updated: setroubleshoot-3.0.15-1.fc14.x86_64
Dec 23 07:32:11 hostname yum[351]: Updated: boost-devel-1.44.0-4.fc14.x86_64
Dec 23 07:32:16 hostname yum[351]: Updated: kernel-headers-2.6.35.10-72.fc14.x86_64
Dec 23 07:32:17 hostname yum[351]: Updated: xerces-j2-2.9.0-5.fc14.noarch
Dec 23 07:32:18 hostname yum[351]: Updated: boost-math-1.44.0-4.fc14.x86_64
Dec 23 07:34:15 hostname kernel: [49336.143640] TCP lp registered

------------ shutdown------------->
Dec 23 07:35:35 hostname init: system-setup-keyboard main process (1210) killed by TERM signal
Dec 23 07:35:35 hostname init: tty (/dev/tty2) main process (2166) killed by TERM signal
Dec 23 07:35:35 hostname init: tty (/dev/tty3) main process (2168) killed by TERM signal
Dec 23 07:35:35 hostname init: tty (/dev/tty4) main process (2170) killed by TERM signal
Dec 23 07:35:35 hostname init: tty (/dev/tty5) main process (2172) killed by TERM signal
Dec 23 07:35:35 hostname init: tty (/dev/tty6) main process (2178) killed by TERM signal
Dec 23 07:35:35 hostname smartd[2158]: smartd received signal 15: Terminated
Dec 23 07:35:35 hostname smartd[2158]: smartd is exiting (exit status 0)
Dec 23 07:35:36 hostname abrtd: UnRegistered Analyzer plugin Kerneloops
Dec 23 07:35:36 hostname abrtd: UnRegistered Reporter plugin KerneloopsReporter
Dec 23 07:35:36 hostname abrtd: UnRegistered Action plugin KerneloopsScanner
Dec 23 07:35:36 hostname abrtd: UnRegistered Database plugin SQLite3
Dec 23 07:35:36 hostname abrtd: Got signal 15, exiting
Dec 23 07:35:36 hostname [CMA]: Received signal to stop CMA
Dec 23 07:35:36 hostname [CMA]: Shutting down cma
Dec 23 07:35:46 hostname kernel: [49426.656692] device eth0 left promiscuous mode
Dec 23 07:35:47 hostname acpid: exiting
Dec 23 07:35:47 hostname ntpd[1837]: ntpd exiting on signal 15
Dec 23 07:35:47 hostname NetworkManager[1431]: <info> caught signal 15, shutting down normally.
Dec 23 07:35:47 hostname NetworkManager[1431]: <info> Updating /etc/hosts with new system hostname
Dec 23 07:35:48 hostname NetworkManager[1431]: <info> (wlan0): now unmanaged
Dec 23 07:35:48 hostname NetworkManager[1431]: <info> (wlan0): device state change: 3 -> 1 (reason 36)
Dec 23 07:35:48 hostname NetworkManager[1431]: <info> (wlan0): cleaning up...
Dec 23 07:35:48 hostname NetworkManager[1431]: <info> (wlan0): taking down device.
Dec 23 07:35:48 hostname nm-dispatcher.action: nm_dispatcher_action: Invalid connection: '(null)' / 'connection setting not found' invalid: 1
Dec 23 07:35:48 hostname NetworkManager[1431]: <info> exiting (success)
Dec 23 07:35:49 hostname nm-dispatcher.action: Disconnected from the system bus, exiting.
Dec 23 07:35:49 hostname rtkit-daemon[2339]: Demoting known real-time threads.
Dec 23 07:35:49 hostname init: Disconnected from system bus
Dec 23 07:35:49 hostname rtkit-daemon[2339]: Successfully demoted thread 2534 of process 2528 (/usr/bin/pulseaudio).
Dec 23 07:35:49 hostname rtkit-daemon[2339]: Successfully demoted thread 2533 of process 2528 (/usr/bin/pulseaudio).
Dec 23 07:35:49 hostname rtkit-daemon[2339]: Successfully demoted thread 2532 of process 2528 (/usr/bin/pulseaudio).
Dec 23 07:35:49 hostname rtkit-daemon[2339]: Successfully demoted thread 2528 of process 2528 (/usr/bin/pulseaudio).
Dec 23 07:35:49 hostname rtkit-daemon[2339]: Demoted 4 threads.
Dec 23 07:35:49 hostname rpcbind: rpcbind terminating on signal. Restart with "rpcbind -w"
Dec 23 07:35:49 hostname auditd[1304]: The audit daemon is exiting.
Dec 23 07:35:49 hostname kernel: [49429.989616] type=1305 audit(1293107749.427:1166): audit_pid=0 old=1304 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1
Dec 23 07:35:49 hostname kernel: [49430.073043] type=1701 audit(1293107749.510:1167): auid=500 uid=500 gid=500 ses=1 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=7257 comm="gvfs-gdu-volume" sig=6
Dec 23 07:35:49 hostname cpuspeed: Disabling ondemand cpu frequency scaling governor
Dec 23 07:35:50 hostname kernel: Kernel logging (proc) stopped.
<------------ Complete shutdown-----------

nothing in /var/logs showing failed boot
Comment 2 Kyle McMartin 2010-12-23 16:18:21 UTC 
https://koji.fedoraproject.org/koji/taskinfo?taskID=2686028

try this.
Comment 3 Andy Bentley 2010-12-23 17:47:51 UTC 
That link does not resolve.... "The connection was reset" 
"The connection to the server was reset while the page was loading"

And I get a "This site is an untrusted server" the Cert says FEDORA CA.... looks like its forged.

other koji links resolve fine, without bad cert issue
http://koji.fedoraproject.org/koji/buildinfo?buildID=183791
Comment 4 Bill Gianopoulos 2010-12-23 18:10:02 UTC 
Duplicate of bug 664145?
Comment 5 Jos de Kloe 2010-12-23 20:44:00 UTC 
(In reply to comment #4)
> Duplicate of bug 664145?

Same bug happens on my acer aspire 7520 laptop.
This one does not use LUKS for the system partition, so there is no connection to the LUKS/encryption mentioned here.

I agree this probably is the same issue mentioned in bug 664145.
Comment 6 Kyle McMartin 2010-12-23 20:50:40 UTC 
Yes. The laptop model is a giveway. ;-P

*** This bug has been marked as a duplicate of bug 664145 ***
Comment 7 Bill Gianopoulos 2010-12-23 21:14:47 UTC 
(In reply to comment #6)
> Yes. The laptop model is a giveway. ;-P
> 
> *** This bug has been marked as a duplicate of bug 664145 ***

I knew that.  It is just I don't have the required privs to dup a bug that I didn't submit ;-)
Comment 8 Andy Bentley 2010-12-24 01:30:37 UTC 
If issue occurs on Acer Aspire 7520 per comment #5 ... what is to common chipset ?
Comment 9 Andy Bentley 2010-12-24 01:37:11 UTC 
What kernel will this be fixed in ?
Comment 10 Andy Bentley 2010-12-24 02:12:13 UTC 
What kernel will this be fixed in ?