Bug 875327

Summary: kernel-3.6.2-1.fc16.x86_64 doesn't boot on Acer Aspire 5738z
Product: [Fedora] Fedora Reporter: Javier <mjcves>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
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-11-28 15:18:57 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg_kernel3.4.11-1.fc16.x86_64
none
dmesg_kernel3.6.2-1.fc16.x86_64
none
lspci_kernel3.4.11-1.fc16.x86_64.out
none
lspci_kernel3.6.2-1.fc16.x86_64.out
none
Hardware info none

Description Javier 2012-11-10 14:30:42 UTC 
Created attachment 642175 [details]
dmesg_kernel3.4.11-1.fc16.x86_64

Description of problem:
After updating to version 3.6.2-1.fc16.x86_64 of the kernel, the system does not boot, starting in emergency mode and displays "modprobe microcode failed". Starting with kernel 3.4.11-1.fc16.x86_64 it works fine, I have tried with kernel 3.6.6-1.fc16.x86_64, and does not boot, and sometimes is not posible to shutdown normally or do anything.

Version-Release number of selected component (if applicable):
Fedora 16, kernel 3.6.2-1.fc16.x86_64

How reproducible:
Always happens

Steps to Reproduce:
1.Install the kernel 3.6.2-1.fc16.x86_64 
2. Boot machine
  
Actual results:
Does not boot

Expected results:
System boots as always in Gnome 3

Additional info: 
I'll attach the dmesg and lspci outputs for kernels 3.6.2-1.fc16.x86_64 and 3.4.11-1.fc16.x86_64, and the hardware information

I don't know if it is related or the same as https://bugzilla.redhat.com/show_bug.cgi?id=845388 , but I see some differencies
Comment 1 Javier 2012-11-10 14:33:24 UTC 
Created attachment 642176 [details]
dmesg_kernel3.6.2-1.fc16.x86_64
Comment 2 Javier 2012-11-10 14:34:06 UTC 
Created attachment 642177 [details]
lspci_kernel3.4.11-1.fc16.x86_64.out
Comment 3 Javier 2012-11-10 14:34:32 UTC 
Created attachment 642178 [details]
lspci_kernel3.6.2-1.fc16.x86_64.out
Comment 4 Javier 2012-11-10 14:35:02 UTC 
Created attachment 642179 [details]
Hardware info
Comment 5 Javier 2012-11-24 22:38:12 UTC 
I have tested with the Live version of Fedora 17 and Fedora 18 LXDE. With F17 it failed starting but with F18 it worked fine.
Comment 6 Josh Boyer 2012-11-28 15:18:57 UTC 
According to comment #1, the system booted all the way to your rootfs and then started failing in various virtualbox related services.

Notably:

[   18.746904] mount[551]: mount: unknown filesystem type 'usbfs'
[   18.749171] systemd[1]: vbusbf.mount mount process exited, code=exited status=32

fails with a 3.6 kernel because usbfs was removed in the 3.5 kernel release.  You'll probably need to update your various vbox/dkms things.

Fedora doesn't provide vbox and there is nothing that indicates this is an actual kernel problem.
Comment 7 Javier 2012-12-06 10:03:26 UTC 
Thanks for the response, I fixed it editing the file /etc/fstab and commenting out the line 
none 			/vbusbf 		usbfs rw.devgid=501,devmode=664 0 0



(In reply to comment #6)
> According to comment #1, the system booted all the way to your rootfs and
> then started failing in various virtualbox related services.
> 
> Notably:
> 
> [   18.746904] mount[551]: mount: unknown filesystem type 'usbfs'
> [   18.749171] systemd[1]: vbusbf.mount mount process exited, code=exited
> status=32
> 
> fails with a 3.6 kernel because usbfs was removed in the 3.5 kernel release.
> You'll probably need to update your various vbox/dkms things.
> 
> Fedora doesn't provide vbox and there is nothing that indicates this is an
> actual kernel problem.