On 03/25/2010 02:51 PM, Jeff Mahoney wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/25/2010 12:15 PM, Johannes Obermayr wrote:
Am Donnerstag, 25. März 2010 16:43:56 schrieb Larry Finger:
On 03/25/2010 10:16 AM, Johannes Obermayr wrote:
Hi,
I installed Kernel 2.6.34-rc2 on three systems (all 11.2 with Kernel:HEAD repo). Two of them do not have any problems - they seem even a bit faster compared to 2.6.33.
But on one system (MSI K7T Turbo [MS-6330] with a AMD Duron 900) the kernel hangs at an early stage (all flavors). It is so early that I cannot provide any logs and only the reset button works then.
Can you please tell me what I have to do for providing useful information?
Btw. I am not really familiar with kexec and kdump ...
Does the boot splash screen come up? If so, hit ESC to clear it, then report the last line output. If that line is "Loading basic drivers", you might try adding "ipv6.disable=1" to the GRUB option line before booting.
I use every time "splash=0"
The other options are to set up netconsole or a serial console to capture the boot log.
Larry
What I can read on screen without times (I hope there are not any typos ...):
CR: 0000000000000000 ---[ end trace 17c212293c363a9e ]--- Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: swapper Tainted: G D W 2.6.34-rc2-2-desktop # 1 Call Trace: [<c02061ab>] try_stack_unwind+0x14b/0x170 [<c020503f>] dump_trace+0x3f/0xf0 [<c0205dbb>] show_trace_log_lvl+0x4b/0x60 [<c0205de8>] show_trace+0x18/0x20 [<c064c810>] dump_stack+0x6d/0x72 [<c064c861>] panic+0x4c/0xe8 [<c0244288>] find_new_reaper+0x78/0x80 [<c0245390>] forget_original_parent+0x30/0x270 [<c02455db>] exit_notify+0xb/0x170 [<c0245aee>] do_exit+0x17e/0x380 [<c0650856>] oops_end+0x86/0xc0 [<c022624f>] bad_area_nosemaphore+0xf/0x20 [<c064fc7a>] error_code+0x66/0x6c [<c0991c0f>] memmap_init+0x19/0x2c [<c020112f>] do_one-initcall+0x2f/0x190 [<c0964460>] do_basic_setup+0x3f/0x4d [<c09644dd>] kernel_init+0x6f/0xfa [<c02033ff>] kernel_thread_helper+0x6/0x10
This is a secondary oops. It's probably still in memmap_init, since it looks like something fell apart while finishing the oops.
Capturing the output on a serial console would really help a lot here.
His disk driver should be OK. His box uses via_pata.ko, which is in the initrd. Larry -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org