Mailinglist Archive: opensuse-kernel (109 mails)

< Previous Next >
Re: [opensuse-kernel] Kernel 2.6.34-rc2 hangs on one of three systems
  • From: Jeff Mahoney <jeffm@xxxxxxxx>
  • Date: Thu, 25 Mar 2010 15:44:25 -0400
  • Message-id: <4BABBD19.301@xxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/25/2010 03:09 PM, Larry Finger wrote:
On 03/25/2010 01:50 PM, Johannes Obermayr wrote:
Am Donnerstag, 25. März 2010 17:15:41 schrieb Johannes Obermayr:
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

Is this due to missing disk drivers in initrd? The missing modules from
mkinited
also reinforce this idea. What are the PCI ID's in the first line of 'lspci
-nnv"? On my computer, it shows up as "00:06.0 IDE interface [0101]: nVidia
Corporation MCP67 IDE Controller [10de:0560] (rev a1) (prog-if 8a [Master SecP
PriP])", where 10de:0560 are the important numbers. With those, we can
determine
which driver 2.6.34 uses for your disk.

No. This is way, way too early. Disks aren't even in the picture yet.
The initrd is loaded after all the initcalls have completed.

- -Jeff

- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAkurvRkACgkQLPWxlyuTD7KgIQCdGj6X3eShd1Gub7yZMdTi+plW
U44Ani/1Zi1JmToa4KBJjg8DQBIdVJRX
=YPnN
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-kernel+help@xxxxxxxxxxxx

< Previous Next >