Bug 85823 - abi-ibcs crash
abi-ibcs crash
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
8.0
i686 Linux
high Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-08 06:35 EST by paolo bongiorno
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 11:40:37 EDT
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 paolo bongiorno 2003-03-08 06:35:36 EST
Description of problem:

On RH 8.0 second edition ibcs crash 

<1>Unable to handle kernel paging request at virtual address d09fd000
 printing eip:
00003c6d
*pde = 01aea067
*pte = 00000000
Oops: 0000
nfsd lockd sunrpc autofs 8139too mii iptable_filter ip_tables hisax isdn slhc st
abi-ibcs abi-svr4 lcall7 abi-util binfmt_coff mousedev keybdev hid input usb-
CPU:    0
EIP:    0023:[<00003c6d>]    Not tainted
EFLAGS: 00010246

EIP is at Using_Versions [] 0x3c6c (2.4.18-24.8.0)
eax: 00000005   ebx: 00000000   ecx: 00000000   edx: 0000000d
esi: 080fcb08   edi: 080fcb08   ebp: bffffa48   esp: bffff9f4
ds: 002b   es: 002b   ss: 002b
Process today (pid: 1013, stackpage=ccfc1000)
 Segmentation fault
Comment 1 Arjan van de Ven 2003-03-08 09:50:29 EST
It's strongly advised to not use linux-abi.
Comment 2 Bugzilla owner 2004-09-30 11:40:37 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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