[lkml]   [2003]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.4.18 fork & defunct child.

>Weird. Totally weird.
>Have you checked the systems for root kits? I'm really out of ideas
>here other than the usual hardwarehosed/systemcompromised. One thing
>I can vouch for is Slackware 8.1 working ok as is, we've installed
>dozens of that particular release and all the machines are still
>humming away in the wild nicely.
Thanks Tomas,
weird it is, it has me stumped. I'm no spring chicken with linux systems
and i also have a slackware 8.1 system running fine on PCchips hardware
for years. (well since slackware 8.1 came out, and before that it had
7). But this is the only machine i've ever run a distro kernel on.

umounting /proc removes the problem.
what could be in there in proc that would be causing it? something
misrepresented about the memory? or some other resource?

One thing i have noticed is that this happens:
kernel: PCI_IDE: unknown IDE controller on PCI bus 00 device f9,
VID=8086, DID=24cb
kernel: PCI: Device 00:1f.1 not available because of resource collisions
on boot.

I sent some more info about the problem earlier to linux-kernel.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:58    [W:0.041 / U:0.668 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site