2009/2/11 Stefan Fritsch <s...@debian.org>: > > Somehow you ended up with the sid/unstable version of apache instead > of the lenny/testing version (which is 2.2.9-10+lenny2).
I did that on purpose, to see if Sid's was crashing like Lenny's was. And it is. >> crash output follows: >> >> Feb 11 06:52:45 pylon kernel: Unable to handle kernel paging > >> pylon kernel: Oops: Kernel access of bad area, sig: 11 [#1] Um, it's a segfault in the application. How is that different? NOTHING else is crashing this way. So it isn't the kernel. > It seems extremely unlikely to me that this is the same issue as bug > #511103. Please open a new bug instead of using this one. > > In fact, it looks more like a kernel issue. What is in apache error > log? Any messages about segfaults or resource shortage? If apache Yes, several in the error.log >> Kernel: Linux 2.6.28.4-pylon > > This is not a Debian kernel. Please try again with the Debian kernel. Tthe debian kernel does not boot at all, even after reconstructing the initrd a few times, so no, I won't, since there's no point. How about addressing the issue instead of blaming me? Don't take this the wrong way, but when the only application that's crashing in such a way takes down my machine when restarts, and I get blamed for it, that rather ticks me off, especially when I didn't build it myself. I'd understand if I had done so - in fact, I wouldn't be writing in a bug report, I'd suck it up and deal with it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
