hello list,

I have been running the test releases on my home system since they
started. Just to not have to patch xfs, and finally have multiple opens
on audio devices.

there have been some crashes though. now I found out, where the oopses
live. and there are lots of them :)

I write to you, because I read, the preempt feature was unstable in
concert with certain config options/drivers.

I cannot rule out faulty memory chips, as the system has the cheapest
ones, with the name of the manufacturer overwritten/engraved with
another name. they even fail the bios test: but then the system runs for
days, mostly when not watching any video.

chkrootkit has nothing suspicious to report.

attached excerpts from /var/log/messages: both with test11. the first
without the nvidia driver, the second with it. otherwise same config:
preemption, acpi, xfs, alsa etc.etc.

uname -a gives: (compiled with gcc3.3.2 from current debian unstable)
Linux lazy 2.6.0-test11 #4 Fri Nov 28 17:50:26 CET 2003 i686 GNU/Linux

the attachments:

messagesX - which has 2 consecutive oopses. I cant remember, what
happened then; but it looks like it ended in a reboot.  the preceding
messages were all from bttv. this may or may not be a coincidence.

messagesY - first messages were unnoticed, got noticed like that:
mozilla firebird froze.  other programs, that already ran, kept running,
but every attempt to start a new process failed with a memory fault
(thats the ksh talk).

not attached for size reasons .config; maybe grep -v "is not set" was
nice; will be delivered on request.

If the kernel is at fault, I hope this can help find the specifics.

regards.

hungerburg