Re: crashes without trace--module problem?
I have finally confirmed that the problem was the ath5k driver (stays up
days without it, crashes, usually within a day, with it). Upgrading the
the latest trunk kernel (2.6.29) seems to have fixed it.
I'm still curious if there is any more direct way of tracing such
crashes, or of figuring out why they should be happening so long after
On Sun, 2009-03-29 at 11:45 -0700, Ross Boylan wrote:
> I have a new system running Lenny, amd64 architecture and 8 core Xeon
> chips. It has been crashing regularly, often after less than 24 hours
> There are indications the problem might be related to the ath5k wireless
> driver; details below. Google shows ath5k oops has lots of hits, but
> they seem to concern errors loading or unloading the driver.
> Could the kernel or Debian be loading or unloading this, or any other,
> driver without user intervention?
> The crashes are particularly frustrating because there is generally no
> indication in the logs of their cause. I have routed the logs to
> another machine, but they still doesn't show anything. We've been
> unable to get a serial console working.
> The system ran memtest+ without error for several days; we pulled the
> disks and put on a different OS (CentOS?) and that ran for a couple of
> days too.
> Any other ideas about what could be causing this, or at least how we
> could get debug information?
> We suspected some anacron triggered job might be causing trouble. Is
> there a way to find out what jobs will be run when, or at least getting
> them logged when they start?