Re: crash diagnostics
its possible to start w/o a swap. depends how much ram you have though .. i never build linux boxes with less then 64 or 128MB in those cases swap isn't that important so its easy to turn off.. it may be bad ram..there are a few memory testers out there for linux..try em out. nate On Sun, 30 Jan 2000, Werner Reisberger wrote: werner On Sat, Jan 29, 2000 at 11:31:30AM -0800, aphro wrote: werner try running your mahcine w/o a swap partition setup to see if the problem werner persists, (its just a shot in the dark..) you may have bad sectors on the werner drive where the swap partition resides. werner werner Is it possible to start linux w/o a swap partition? I checked the drive werner (UW-SCSI) with the diagnostic program of the Adaptec-Controller and didn't werner found any bad blocks. werner werner I think it's rather a problem with the RAM. I just checked a core after werner a program failed with seg fault. The message found (Cannot access memory werner in 0xa346e32) points to a RAM problem. I think I really have to exchange my werner RAM. werner werner Werner werner [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 9:31pm up 164 days, 9:40, 1 user, load average: 1.22, 1.14, 1.05
Re: crash diagnostics
On Sat, Jan 29, 2000 at 11:31:30AM -0800, aphro wrote: try running your mahcine w/o a swap partition setup to see if the problem persists, (its just a shot in the dark..) you may have bad sectors on the drive where the swap partition resides. Is it possible to start linux w/o a swap partition? I checked the drive (UW-SCSI) with the diagnostic program of the Adaptec-Controller and didn't found any bad blocks. I think it's rather a problem with the RAM. I just checked a core after a program failed with seg fault. The message found (Cannot access memory in 0xa346e32) points to a RAM problem. I think I really have to exchange my RAM. Werner
Re: crash diagnostics
try running your mahcine w/o a swap partition setup to see if the problem persists, (its just a shot in the dark..) you may have bad sectors on the drive where the swap partition resides. nate On Fri, 28 Jan 2000, Werner Reisberger wrote: werner I am still having occasional kernel panics and don't know why. Today an Oops werner happened some hours before the panic (when I did 'make zImage'). The Oops werner left the kswaps daemon as zombie and I had to reboot the system. Following werner is the output of the Oops. I would really appreciate if somebody could werner give me any hint what could be wrong with my Debian system. I can't analyze werner the data with ksymoops because I couldn't compile ksymoops and I probably werner would experience another crash if I would try it. werner werner ## werner Jan 28 16:28:43 quod kernel: Unable to handle kernel paging request at virtual address 858994b4 werner Jan 28 16:28:43 quod kernel: current-tss.cr3 = 00101000, %cr3 = 00101000 werner Jan 28 16:28:43 quod kernel: *pde = werner Jan 28 16:28:43 quod kernel: Oops: werner Jan 28 16:28:43 quod kernel: CPU:0 werner Jan 28 16:28:43 quod kernel: EIP:0010:[c0124962] werner Jan 28 16:28:43 quod kernel: EFLAGS: 00010287 werner Jan 28 16:28:43 quod kernel: eax: 858994a0 ebx: c02dc6b0 ecx: 0006 edx: ffe0 werner Jan 28 16:28:43 quod kernel: esi: 858994a0 edi: c5899500 ebp: c02dc6b0 esp: c000dfa8 werner Jan 28 16:28:43 quod kernel: ds: 0018 es: 0018 ss: 0018 werner Jan 28 16:28:43 quod kernel: Process kswapd (pid: 4, process nr: 4, stackpage=c000d000) werner Jan 28 16:28:43 quod kernel: Stack: 0030 c000c000 c0119fd2 c02dc6b0 000d 0006 c011ed13 0006 werner Jan 28 16:28:43 quod kernel:0030 c01a9078 c000c1c1 c011edbf 0030 0f00 c0003fb4 werner Jan 28 16:28:43 quod kernel:c0106000 9000 c0106513 0f00 c01d5fd8 werner Jan 28 16:28:43 quod kernel: Call Trace: [c0119fd2] [c011ed13] [c01a9078] [c011edbf] [c0106000] [c0106513] werner Jan 28 16:28:43 quod kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74 13 6a 00 e8 4c 01 werner ## werner werner I am running a kernel 2.2.10 with Hamm and the newer stuff needed for this werner kernel. I am guessing my problem is hardware dependend and I am going to werner exchange my quodry modules if I can't find any other cause for this troubles. werner werner I am having this kernel panics since my hosting provider had a power werner interruption. What kind of PC HW could get damaged by a power interruption werner resulting in such a behaviour I described? werner werner TIA, werner werner Werner werner werner werner -- werner Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null werner [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 11:28am up 162 days, 23:36, 2 users, load average: 1.03, 1.05, 1.01
crash diagnostics
I am still having occasional kernel panics and don't know why. Today an Oops happened some hours before the panic (when I did 'make zImage'). The Oops left the kswaps daemon as zombie and I had to reboot the system. Following is the output of the Oops. I would really appreciate if somebody could give me any hint what could be wrong with my Debian system. I can't analyze the data with ksymoops because I couldn't compile ksymoops and I probably would experience another crash if I would try it. ## Jan 28 16:28:43 quod kernel: Unable to handle kernel paging request at virtual address 858994b4 Jan 28 16:28:43 quod kernel: current-tss.cr3 = 00101000, %cr3 = 00101000 Jan 28 16:28:43 quod kernel: *pde = Jan 28 16:28:43 quod kernel: Oops: Jan 28 16:28:43 quod kernel: CPU:0 Jan 28 16:28:43 quod kernel: EIP:0010:[c0124962] Jan 28 16:28:43 quod kernel: EFLAGS: 00010287 Jan 28 16:28:43 quod kernel: eax: 858994a0 ebx: c02dc6b0 ecx: 0006 edx: ffe0 Jan 28 16:28:43 quod kernel: esi: 858994a0 edi: c5899500 ebp: c02dc6b0 esp: c000dfa8 Jan 28 16:28:43 quod kernel: ds: 0018 es: 0018 ss: 0018 Jan 28 16:28:43 quod kernel: Process kswapd (pid: 4, process nr: 4, stackpage=c000d000) Jan 28 16:28:43 quod kernel: Stack: 0030 c000c000 c0119fd2 c02dc6b0 000d 0006 c011ed13 0006 Jan 28 16:28:43 quod kernel:0030 c01a9078 c000c1c1 c011edbf 0030 0f00 c0003fb4 Jan 28 16:28:43 quod kernel:c0106000 9000 c0106513 0f00 c01d5fd8 Jan 28 16:28:43 quod kernel: Call Trace: [c0119fd2] [c011ed13] [c01a9078] [c011edbf] [c0106000] [c0106513] Jan 28 16:28:43 quod kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74 13 6a 00 e8 4c 01 ## I am running a kernel 2.2.10 with Hamm and the newer stuff needed for this kernel. I am guessing my problem is hardware dependend and I am going to exchange my quodry modules if I can't find any other cause for this troubles. I am having this kernel panics since my hosting provider had a power interruption. What kind of PC HW could get damaged by a power interruption resulting in such a behaviour I described? TIA, Werner
