Bug 155765 - oops on 2.6.9-5.0.5.ELsmp
oops on 2.6.9-5.0.5.ELsmp
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Baron
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-04-22 16:40 EDT by Brian Brock
Modified: 2013-03-06 00:58 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-26 12:01:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:420 normal SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 4 Update 1 2005-06-08 00:00:00 EDT

  None (edit)
Description Brian Brock 2005-04-22 16:40:12 EDT
Encountered an oops while rebooting a system running 2.6.9-5.0.5.ELsmp

system is a dual-processor i686, gathering details after I reboot it.
system is unresponsive at this point, trying to reproduce

EIP: 0060:[<c01f7121>]  Not tainted VLI

EIP is at vt_ioctl+0x15/0x12a1

Call Trace:
[<c01f1f4b>] tty_open+0x189/0x2a0
[<c0154b53>] filp_open+0x36/0x3c
[<c01f2dff>] tty_ioctl+0x370/0x3c2
[<c01650ba>] sys_ioctl+0x227/0x269
[<c0164941>] sys_fcntl64+0x6c/0x7d
[<c016494b>] sys_fcntl64+0x76/0x7d
[<c02c63fb>] syscall_call+0x7/0xb

not syncing - attempted to kill init
Comment 1 Brian Brock 2005-04-22 17:02:53 EDT
not immediately reproducible, will note if I find constraints.
Comment 2 Dave Jones 2005-04-24 20:52:11 EDT
This looks like one of the races Jason has been chasing recently.
Comment 3 Jason Baron 2005-04-26 12:01:26 EDT

*** This bug has been marked as a duplicate of 152600 ***
Comment 4 Tim Powers 2005-06-08 11:14:10 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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