Bug 10018 - General unreliability and kernel panics on Ultra2 Creator system
General unreliability and kernel panics on Ultra2 Creator system
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
6.1
sparc Linux
medium Severity high
: ---
: ---
Assigned To: Michael K. Johnson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-03-06 18:16 EST by Adam Keys
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-09-16 17:20:39 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 Adam Keys 2000-03-06 18:16:38 EST
Hardware:
Sun Ultra2 Creator
300 Mhz UltraSparc
384 MB RAM
Creator videocard
2 4 gig SCSI drives
hardware raid5 controller?
128 mb swap

The installation process goes smoothly enough.  I am using the default
GNOME workstation setup, enabling RAID0 and a network card.  I have not
yet experienced a crash during setup.  Once the setup is complete, the
machine reboots.  The machine lasts for anywhere between 1-30 minutes
after this reboot.  Several times I have gotten a kernel panic.  Programs
such as linuxconf and PAM have segfaulted, even less(1) or ping(1).

The kernel panic error looks like this:
Unable to handle kernel NULL pointer dereference
tsk->mm->context = <zeros>
tsk->mm->pgd = ffff8000000ec00
<smiley face>
swapper(0): Oops
TSTATE: <registers>
Aieee, killing interrupt handler
Kernel panic: Attempted to kill the idle task!
In swapper task - not syncing

The kernel is the default for Redhat 6.1 (2.2.12-something I beleive).

Good luck,
Adam Keys
Comment 1 Alan Cox 2000-08-22 14:49:21 EDT
Does this still occur with the 6.2 kernels ?
Comment 2 Alan Cox 2000-09-16 17:20:37 EDT
No reply, so hopefully not. If so - reopen this
Comment 3 Adam Keys 2000-09-18 09:20:33 EDT
As it turns out, the machine has two ethernet interfaces.  The first (eth0) is
built part of the SCSI controller.  It is a Sunlance, and this is the kernel
output:

sunlance.c:v1.12 11/Mar/99 Miguel de Icaza (miguel@nuclecu.unam.mx)
eth0: LANCE 08:00:20:8a:3d:31

Using the other ethernet interface (eth1) has been rock solid however.  I can't
find the output in /var/log/dmesg, but I know the sucker is there.

I have not had a chance to test this with the newer kernel.

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