well no, as it happens, I have crashes with every 2.2 kernel so far.
longest uptime has been 27 days. I put it down to dodgy disks in the
quantums but... Most commen cause of the crash is tar (backup script)
and e2fs error
> Hrm... SMP has been slightly changed from 2.2.7 (which I use) to 2.2.10
> which behaves like the 2.3.x series. I notice that in 2.2.7 (with
> wmmon+smp) that any CPU intensive apps don't hop from CPU to CPU as often
> as it does with 2.2.10/2.3.x, perhaps this is Affecting you?
I don't know... but I ran the box in single cpu mode for a while and it
crashed faster (ie lower uptimes)
> you could use the system map with klogd then, when a OOPS occurs, you can
> tell where it occurred and what fuctions were called(?). This is logged to
> syslogd.
yeah it logged the oops but running ksymoops over it brings up
garbage...
> Can you give a detail description of your hardware? ie: model numbers,
> CPUs being used. It may help to locate the problem.
Ok.. detailed?? here we go
Mobo Asus PIIB-DS
dual PII-266 (there arn't any dodgy PII's with bugs floating around
are there??)
apart from the onboard adaptec there is the diamond fireport uses
the SYM53c875-J driver
if you want anything more than that.. I can include a dmesg output??
Cheers
Craig (really need a stable box and can't seem to get it :( )
-- Craig Armour c.armour@arts.uq.edu.au System Administrator Joyce Ackroyd Building Language Lab, University of Queensland phone 33656916- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/