On 20/08/12 19:26, Petter Reinholdtsen wrote: > If the kernel can crash, it is a bug in the kernel.
Well, something in the initscripts could be telling the kernel to do something bad. Maybe to do with the rootfs, or swap. Then it might be acceptable for the kernel to panic and that wouldn't be a kernel bug. Probably some initscript is at fault here, but since I don't know which one yet, I filed against sysvinit until we know where to reassign it. > If fsck can cause the kernel [to crash], this might be a bug in fsck. I'm not sure that fsck itself causes this. Because if I boot a shell instead of /sbin/init, and run initscripts manually (including fsck), it doesn't panic. I think when sysvinit runs initscripts in parallel, it does some buffering of console output, so that makes it hard to know what was running at the time of the panic. I think fsck must have already finished running when the panic happens (or else we wouldn't see it mentioned?). Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/503284cd.4080...@pyro.eu.org
