I do not know whether there is something equivalent in the i386 tree...
> Basically, there is a process running in your kernel which has no
> knowledge of a root filesystem. I don't see anything common between
> kernel_thread() and your kernel messages to suspect any others
> in the generic kernel tree - maybe its a result of a patch
> you applied?
No. The oops (or a lot of them when standard booting) happens with
'clean' 2.4.0-test1-ac18+ up to test2 (was at least not in test1-ac10 I
mean not that reproducable). I do not know when it was broken...
And there are others who encountered it eg (debian is running on his
system too):
====quote on====
> I am running Debian (Woody) as well and have multiple OOPSen as well.
I don't get any
> lockups, just lots of nasty messages. I read the Changes file and saw
no clue there. The
> programs will start fine after login, just not from the startup
scripts...except chrony, which is a
> guaranteed OOPS, but I don't really need that prog, so I just got rid
of it. I know this does not
> help much, except to say that you are not the only one.
>
>
> Glenn C. Hofmann
====quote off====
(this is what happens when using start-stop-daemon to start programs ->
oops)
I am no kernel hacker, I simply do not in which part of the kernel the
bug is in...
Regards,
Soeren.
----
I'm not under the alkafluence of inkahol that some thinkle peep I am.
It's just the drunker I sit here the longer I get.
-
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/