> -rc5-mm1 appears to be a trainwreck. It's a bit of a mystery - I've tried
> several further configs and it all works swimmingly.
Getting closer.
Without the patches:
proc-dont-lock-task_structs-indefinitely.patch
proc-dont-lock-task_structs-indefinitely-git-nfs-fix.patch
proc-dont-lock-task_structs-indefinitely-cpuset-fix.patch
it boots and works (except for the /proc/*/fd/* permission
complaints I made earlier to Eric). And I was able to run my SGI
specific application that generates the 50 such permission complaints.
With these patches, it still boots, and looks fine ... until
I fire up my SGI specific application, and then it dies.
Once it died with some complaint (lost now) from a swap
daemon. This latest time, it died with just:
Kernel panic - not syncing: Attempted to kill init!
So I think the above 3 patches make it easy for user space
to kill the kernel.
The SGI app is some rather largish tool used for system
monitoring and maintenance - I will have to stare at it
to reduce out any useful explanation of what it is doing
that is so painful here.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
