Bug 51753 - kernel panic on boot
kernel panic on boot
Status: CLOSED WORKSFORME
Product: Red Hat Public Beta
Classification: Retired
Component: kernel (Show other bugs)
roswell
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Pete Zaitcev
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-14 15:45 EDT by Mark Robinson
Modified: 2007-04-18 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-25 19:02:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mark Robinson 2001-08-14 15:45:23 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3) Gecko/20010801

Description of problem:
Everytime I boot RH7.2 I get a kernel panic right after starting up USB
related services

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


How reproducible:
Always

Steps to Reproduce:
1. boot Linux, any init level


Actual Results:  kernel panic, no useful backtrace data.  but always a
panic after stating USB.  EG. mouse-light goes on, and kernel panic. 
Install works fine though

Expected Results:  normal boot, with USB

Additional info:

I have a VIA KT133A based mobo(ga-zxr 3.0) with USB.  As well as a USB mouse
Comment 1 Arjan van de Ven 2001-08-14 15:49:20 EDT
Does it print any lines wit
0010:<number>
or
0068:<number> in it ?
does it boot if you pass "nousb" as option in grub/lilo ?
same for "nobiospnp"
Comment 2 Mark Robinson 2001-08-15 04:40:36 EDT
the error prints out register info as well as
[<ec9089b2>],...
like messages

I can't test it any furthur as I have installed Debian, maybe in a week I'll try
it again.
Comment 3 Pete Zaitcev 2002-01-25 19:01:57 EST
If the interest is lost, I have no choice but to close.

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