From: Bernhard Rosenkraenzer <bero@arklinux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Total machine lockup w/ current kernels while installing from CD
Date: Sun, 14 May 2006 18:57:35 +0200 [thread overview]
Message-ID: <200605141857.37086.bero@arklinux.org> (raw)
In-Reply-To: <200605110322.14774.bero@arklinux.org>
On Thursday, 11. May 2006 03:22, Bernhard Rosenkraenzer wrote:
> Hi,
> I've built a CD that installs a customized system; basically what it does
> is boot from CD (iso9660) and run
>
> mke2fs -m0 -j -O dir_index,filetype,has_journal,sparse_super /dev/hda1
> mount -text3 /dev/hda1 /mnt/dest
> rpm -r /mnt/dest -ivh /RPMS/*
>
> This worked perfectly up until some recent kernel updates - with current
> kernels (both Linus and -mm branch), the system locks up totally at a
> random point during rpm installation (everything goes down, including the
> NumLock LED etc).
>
> I'm currently building some old kernels to see when this problem was
> introduced and sort out what patch did it.
> With 2.6.16-rc6, the problem occurs, but unlike later revisions it gives an
> error message before freezing:
>
> BUG: soft lockup detected on CPU#0!
>
> Pid: 421, comm: kjournald
> EIP: 0060:[<b01a2f52>] CPU: 0
> EIP is at journal_commit_transaction+0x92e/0xfcc
> EFLAGS: 00000297 Not tainted (2.6.16-rc6 #1)
> EAX: 00000001 EBX: c2d34788 ECX: 00000001 EDX: c785e000
> ESI: b3ff8d04 EDI: 000000f0 EBP: b683b840 DS: 007b ES: 007b
> CR0: 8005003b CR2: 0841f7fc CR3: 17217000 CR4: 000006d0
> [<b02bd52e>] schedule+0x2ee/0x5b6
> [<b01a6a88>] kjournald+0x201/0x213
> [<b0111089>] smp_apic_timer_interrupt+0x32/0x49
> [<b01a6937>] kjournald+0xb0/0x213
> [<b01a5ffa>] commit_timeout+0x0/0x9
> [<b012a789>] autoremove_wake_function+0x0/0x4b
> [<b01a6887>] kjournald+0x0/0x213
> [<b0101005>] kernel_thread_helper+0x5/0xb
I'm finally through compiling all kernels between the last good and first bad
one (slow hardware sucks ;) ) -- the problem was introduced in the patch from
2.6.16-rc5 to 2.6.16-rc6, and is apparently not present in any -mm releases
before 2.6.16-rc6.
I'll try to isolate which change between 2.6.16-rc5 and -rc6 causes it... But
it would be nice if someone who knows a bit more about the code involved
could look at it.
l
next prev parent reply other threads:[~2006-05-14 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 1:22 Total machine lockup w/ current kernels while installing from CD Bernhard Rosenkraenzer
2006-05-14 16:57 ` Bernhard Rosenkraenzer [this message]
2006-05-15 20:32 ` [FIXED] " Bernhard Rosenkraenzer
2006-05-15 20:45 ` Andrew Morton
2006-05-15 20:53 ` Bernhard Rosenkraenzer
2006-05-15 21:12 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200605141857.37086.bero@arklinux.org \
--to=bero@arklinux.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox