Re: kernel panic after some days
On Sun, 20 Jun 1999, Werner Reisberger wrote: On Sat, Jun 19, 1999 at 10:57:33AM -0500, Stephen Pitts wrote: You shouldn't be running 2.2.3, there are some filesystem corruption problems in the early 2.2.x releases. Upgrade to 2.2.10, that should be better. I upgraded to 2.2.8 Oddly enough, 2.2.8 had filesystem corruption problems (under very high loads) as well! 2.2.9 reverted to 2.2.7's filesystem code, which didn't have the problem.
Re: kernel panic after some days
On Sun, Jun 20, 1999 at 10:59:14PM -0500, Brad wrote: I upgraded to 2.2.8 Oddly enough, 2.2.8 had filesystem corruption problems (under very high loads) as well! 2.2.9 reverted to 2.2.7's filesystem code, which didn't have the problem. I would have used it but wasn't able to get a tar file without corruption. I will try it again, if possible 2.2.10. 2.2.8 obviously doesn't solve my problem. Today I saw the following in my log file: Jun 21 13:32:56 memo kernel: Unable to handle kernel paging request at virtual address 6f4d205f Jun 21 13:32:56 memo kernel: current-tss.cr3 = 05889000, %cr3 = 05889000 Jun 21 13:32:56 memo kernel: *pde = Jun 21 13:32:56 memo kernel: Oops: Jun 21 13:32:56 memo kernel: CPU:0 Luckily the machine didn't crash, but that's only a question of time. I am wondering if it would help to write down everything from the console about this kernel Oops? BTW, what's the difference between a kernel Oops and a panic, except that a panic brings the system every time to a halt. Every hint appreciated. -Werner
Re: kernel panic after some days
On Sat, Jun 19, 1999 at 10:57:33AM -0500, Stephen Pitts wrote: been written to a log file. Below is an excerpt which I found on the console: unable to handle kernel paging request at virtual address e7fde95c You shouldn't be running 2.2.3, there are some filesystem corruption problems in the early 2.2.x releases. Upgrade to 2.2.10, that should be better. I upgraded to 2.2.8 and found an interesting difference during start up. My machine has 128 MB RAM. The 2.2.3 kernel issues the kernel message Memory 63528/... k available ... The 2.2.8 kernel said Memory 128280/... k available ... Though the 2.2.3 kernel obviously didn't recognize the memory during startup properly, a top showed me the full amount of memory. I guess that this difference between the two kernels is at least partially responsibly for the kernel oops. Time will show :-/ -Werner
Re: kernel panic after some days
On Fri, Jun 18, 1999 at 08:39:11PM +0200, Werner Reisberger wrote: I am running a debian machine (PC PII 350 MHZ, 128 MB RAM) as an Internet server. Today the server crashed the second times after running one week without any problems. The crash was caused by a kernel panic. Nothing has been written to a log file. Below is an excerpt which I found on the console: unable to handle kernel paging request at virtual address e7fde95c current - tss.cr3=00101000, %cr3=00101000 *pde= Oops: 0002 CPU: 0 The panic happened when a cronjob was running (glimpse ...) which does a lot of IO and consumes a good amount of memory. Maybe connected with this problem is a kernel message which occasional appears at this times but doesn't cause a crash: Jun 5 05:47:25 memo kernel: attempt to access beyond end of device Jun 5 05:47:25 memo kernel: 08:0c: rw=0, want=67136178, limit=610438 Jun 5 05:47:26 memo kernel: EXT2-fs error (device 08:0c): ext2_free_blocks: Freeing blocks not in datazone - block = 67136177, count = 1 Some type of filesystem corruption, try booting in single-user mode and running e2fsck -c /dev/(whatever) to detect physical hard drive problems. I am running a kernel 2.2.3 with a hamm system. Could there be any incompatibility between this kernel version and parts of the hamm distribution? Should I deinstall glimpse and compile a binary myself on the system? I don't think glimpse itself is the problem. I switched to debian because I thought it would be at least as stable as Suse or RH, but unfortunately my experiences until now are bad. I had to reboot the system too many times. You shouldn't be running 2.2.3, there are some filesystem corruption problems in the early 2.2.x releases. Upgrade to 2.2.10, that should be better. Any hints appreciated. --Werner -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Stephen Pitts [EMAIL PROTECTED] webmaster - http://www.mschess.org
kernel panic after some days
I am running a debian machine (PC PII 350 MHZ, 128 MB RAM) as an Internet server. Today the server crashed the second times after running one week without any problems. The crash was caused by a kernel panic. Nothing has been written to a log file. Below is an excerpt which I found on the console: unable to handle kernel paging request at virtual address e7fde95c current - tss.cr3=00101000, %cr3=00101000 *pde= Oops: 0002 CPU: 0 The panic happened when a cronjob was running (glimpse ...) which does a lot of IO and consumes a good amount of memory. Maybe connected with this problem is a kernel message which occasional appears at this times but doesn't cause a crash: Jun 5 05:47:25 memo kernel: attempt to access beyond end of device Jun 5 05:47:25 memo kernel: 08:0c: rw=0, want=67136178, limit=610438 Jun 5 05:47:26 memo kernel: EXT2-fs error (device 08:0c): ext2_free_blocks: Freeing blocks not in datazone - block = 67136177, count = 1 I am running a kernel 2.2.3 with a hamm system. Could there be any incompatibility between this kernel version and parts of the hamm distribution? Should I deinstall glimpse and compile a binary myself on the system? I switched to debian because I thought it would be at least as stable as Suse or RH, but unfortunately my experiences until now are bad. I had to reboot the system too many times. Any hints appreciated. --Werner
