Bug 166516 - kernel BUG at kernel/timer.c:420!
kernel BUG at kernel/timer.c:420!
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Ingo Molnar
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-08-22 15:02 EDT by Aleksandar Milivojevic
Modified: 2010-06-07 00:59 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-07 00:59:27 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)
crash screen (manually retyped) (1.49 KB, text/plain)
2005-08-22 15:03 EDT, Aleksandar Milivojevic
no flags Details

  None (edit)
Description Aleksandar Milivojevic 2005-08-22 15:02:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050721 CentOS/1.0.6-1.4.1.centos4 Firefox/1.0.6

Description of problem:
The kernel just crashed on me.  Relatively soon after the boot.  The only thing I noticed (might be related, or might not) before crash was that automounter was hanging for extended period of time attempting to mount my home directory from NFS server.  The NFS server was OK and I could ping it from the PC where kernel crashed, and automounting of my home dir worked just fine from other PCs on the same network.  Basically, as automounter was hanging, I went for a lunch (if it doesn't mount my home dir by the time I get back, I'll try to figure out what's going on).  When I got back from the lunch, I found the crash dump screen.  Retyped the crash screen, rebooted the server, logged in, automouter mounted my home dir just fine this time, and kernel seems happy so far.

I'll attach the copy of the crash screen.  It was manually retyped, so might contain typos curtesy of me.

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


How reproducible:
Didn't try

Steps to Reproduce:
1. Nothing here, happened only once


Additional info:
Comment 1 Aleksandar Milivojevic 2005-08-22 15:03:48 EDT
Created attachment 117976 [details]
crash screen (manually retyped)
Comment 2 Jason Baron 2005-08-22 15:41:15 EDT
hmm, looks a bit like 140319. 
Comment 3 Aleksandar Milivojevic 2005-08-22 16:41:38 EDT
Sounds similar.  Also sounds like 152557 too.

However, there's couple of things different in my setup than in 140319 and
152557.  They might be just different manifestaion of the same problem, or they
may point to completely different problem.

The NFS server is an Solaris 9 box, and there's nothing in the server's log files.

I got oops by simply attempting to mount the partition (in 140319 oops happened
after partition was successfully mounted, then some heavy I/O on the server
performed, and then unmounted using "umount -f").

In 140319 the problem happens during heavy I/O on the server and manifests
itself as an already mounted file system becomming "frozen".  My server was in
relatively idle state (some very light I/O), and remote file system completely
failed to mount on the client.
Comment 4 Jason Baron 2005-08-22 16:46:28 EDT
how intermittent is this issue? just curious.
Comment 5 Aleksandar Milivojevic 2005-08-22 17:04:17 EDT
It happened total of one time to me.

I've got two boxes running 2.6.9-11.EL and mounting home directories over NFS
from Solaris server.  One works perfectly for a long time now, mostly generating
light load on NFS with occasional relatively high I/O (moving large files
around, uncompressing/untarring large archives, creating ISO images from files
stored on the server, and/or compiling larger packages).  Used to run RH7.3,
FC1, FC2, and FC3 on it in the past, with bunch of different kernels, no
problems at all.

The other is fresh installation (last week), almost no NFS load, and I got this
one single oops on it today.

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