Bug 855682 - timeout: killing during init
Summary: timeout: killing during init
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-09 22:55 UTC by la_antorcha_guia
Modified: 2012-11-29 14:17 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-29 14:17:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
lspci (12.53 KB, text/plain)
2012-11-29 14:14 UTC, la_antorcha_guia
no flags Details

Description la_antorcha_guia 2012-09-09 22:55:27 UTC
Description of problem:
udevd[175]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0005:family:0006:model:000A:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000F,00
' [267]
udevd[175]: '/sbin/modprobe -bv x86cpu:vendor:0005:family:0006:model:000A:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000F,0010,0013,0016,0017,0018,00
' [267] terminated by signal 9 (Killed)
Welcome to ^[[0;34mFedora release 16 (Verne)


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


How reproducible:
boot

Steps to Reproduce:
1.boot
2.
3.
  
Actual results:
slow boot (with timeout)

Expected results:
fast boot


Additional info:

via c7-D 1.5ghz cpu

Comment 1 Josh Boyer 2012-09-10 12:55:26 UTC
What kernel version is this with?

Comment 2 la_antorcha_guia 2012-09-10 14:55:12 UTC
3.4.9-2.fc16.i686.PAE #1 SMP Thu Aug 23 18:41:34 UTC 2012 i686 i686 i386 GNU/Linux

kernel-PAE-3.4.9-2.fc16.i686

Comment 3 Josh Boyer 2012-09-17 19:29:39 UTC
Were you resuming from a suspend when this happened, or was this just during a normal boot?

Comment 4 la_antorcha_guia 2012-09-18 08:02:19 UTC
reboot or normal boot

Comment 5 Dave Jones 2012-10-23 15:38:33 UTC
# Mass update to all open bugs.

Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.

Please retest with this kernel, and let us know if your problem has been fixed.

In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with.  Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.

If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
different problem. 
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).

Comment 6 la_antorcha_guia 2012-10-30 10:03:07 UTC
boot.log:

.%G.%Gudevd[177]: timeout: killing '/sbin/modprobe -bv x86cpu:vendor:0005:family:0006:model:000A:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000F,0010
,0013,0016,0017,0018,0019,001A,001D,0034,0069,0080,00A2,00A3,00A6,00A7,00A8,00A9,00AA,00AB,00AC,00AD
' [268]


udevd[177]: '/sbin/modprobe -bv x86cpu:vendor:0005:family:0006:model:000A:feature:,0000,0001,0002,0003,0004,0005,0006,0007,0008,0009,000B,000C,000D,000F,0010,0013,0016,0017,0018,00
19,001A,001D,0034,0069,0080,00A2,00A3,00A6,00A7,00A8,00A9,00AA,00AB,00AC,00AD
' [268] terminated by signal 9 (Killed)



Welcome to .[0;34mFedora release 16 (Verne).[0m!

Comment 7 Josh Boyer 2012-11-28 16:48:11 UTC
please provide the output of dmesg and 'sudo lscpi -nnvv'

Comment 8 la_antorcha_guia 2012-11-29 14:13:11 UTC
Upgraded to Fedora 17, no problem now.

If you want output of lspci see file.

Comment 9 la_antorcha_guia 2012-11-29 14:14:01 UTC
Created attachment 654299 [details]
lspci

Comment 10 Josh Boyer 2012-11-29 14:17:31 UTC
(In reply to comment #8)
> Upgraded to Fedora 17, no problem now.
> 
> If you want output of lspci see file.

OK.  Thanks for letting us know.


Note You need to log in before you can comment on or make changes to this bug.