Red Hat Bugzilla – Bug 60988
Newburn Kernel failures on beetle running Hampton beta 2
Last modified: 2007-04-18 12:40:50 EDT
Description of Problem: On a beetle running Hampton beta2 (2.4.18-0.1) w/ bios
A04, 2GB ram, 2GB swap. Frequent kernel failures while running newburn.
Attached is KERNEL file from newburn logs.
Version-Release number of selected component (if applicable):
How Reproducible: Everytime
Steps to Reproduce:
1. Install hampton beta2 on a beetle
2. Run newburn and note kernel failures
Actual Results: Kernel failures
Expected Results: No kernel failures
Created attachment 48124 [details]
Kernel file from newburn error log
This isn't a hardware failure; this is a failure in the NFS-COMPILE test
that looks like a configuration problem.
Do you have a working kernel tree available at /usr/src/linux?
I have a /usr/src/linux symbolic link to the /usr/src/2.4.18-0.1 kernel tree
that was placed there by a custom/everything install.
Anything showing up in /var/log/messages?
Regressed this issue w/ beta3 by running newburn and did not see any kernel
failures during the 22 hours before newburn caused a kernel oops. The kernel
failures I had seen with beta2 began almost immediately at a frequency of
roughly 5 per hour. I will regress again once newburn runs without oopsing at
all, but they seemed to have stopped with beta3.
Have you posted the oops after 22 hours with beta3 kernel somewhere?
Yes, I posted that ksymoops output to bug 61033 on 3/22. I am regressing this
issue, 61033 as it relates to pe500sc (beetle), and 60989 right now with
On a beetle with beta4 installed, newburn ran for 3 days without kernel failure
closing as "fixed" then