Bug 211110 - kernel 2.6.18-1.2200.fc5 instantly reboots
Summary: kernel 2.6.18-1.2200.fc5 instantly reboots
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-10-17 14:11 UTC by Didier
Modified: 2015-01-04 22:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-10-20 11:13:54 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
dmesg output (19.58 KB, text/plain)
2006-10-17 14:11 UTC, Didier
no flags Details

Description Didier 2006-10-17 14:11:42 UTC
Description of problem:
When booting kernel 2.6.18-1.2200.fc5 (upgraded from 2.6.17-1.2187_FC5) : in
single user mode (other modes evidently not tested), after a few (5-30) random
keystrokes the kernel emits a sound (bell, I guess) and reboots.

Version-Release number of selected component (if applicable):
kernel-2.6.18-1.2200.fc5

How reproducible:
Always

Steps to Reproduce:
1. boot in single user
2. use keyboard for a few seconds
3. gasp in awe
  
Actual results:
Spontaneous reboot

Expected results:
No reboot

Additional info:
- Dell laptop, Inspiron 9300 (WUXGA, nVidia Go 6800)
- Removed all external hardware, minimum setup
- Made sure kernel not tainted with proprietary nvidia module (renamed before
reboot)
- Nothing logged to /var/log/messages (when the machine is up long enough to get
syslog started)

Comment 1 Didier 2006-10-17 14:11:42 UTC
Created attachment 138681 [details]
dmesg output

Comment 2 Dave Jones 2006-10-19 18:46:56 UTC
dmesg looks sane.  My first thought is possible hardware problems.

Can you try a run of memtest86+ on it ?

Comment 3 Didier 2006-10-19 20:38:35 UTC
Will run memtest86+ first thing in the morning (CET) ; nevertheless, reverting
back to 2.6.17-1.2187_FC5 returns to business as usual.

(I've got this hunch about blacklisting pcspkr ...)

Comment 4 Didier 2006-10-20 11:13:54 UTC
- A full run of memtest86+ revealed no defects ;

- Today, after the memtest run, I was unable to reproduce the erroneous
behaviour (though it was perfectly reproducible the day of my report).

- The only relevant (?) package update in the interim seems to be kudzu.

Sorry for the spam.



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