From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Bernd Schubert" <bschubert@q-leap.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mkfs.ext2 triggered softlockup
Date: Wed, 16 May 2007 18:49:57 +0200 [thread overview]
Message-ID: <6bffcb0e0705160949m7486705s1b2fc5bbe8a025df@mail.gmail.com> (raw)
In-Reply-To: <f2fcc1$otm$2@sea.gmane.org>
Hi Bernd,
On 16/05/07, Bernd Schubert <bschubert@q-leap.de> wrote:
> Maybe you still remember my report about an mkfs.ext2 triggered ram disk
> corruption?
>
> http://lkml.org/lkml/2007/5/4/272
>
> Well, in principle I'm now doing the same stuff, only this time with another
> initrd, which mounts the root-fs over nfs.
>
> [ 1596.928552] BUG: soft lockup detected on CPU#2!
> [ 1596.933109]
> [ 1596.933110] Call Trace:
> [ 1596.933111] <IRQ> [<ffffffff8025167b>] softlockup_tick+0xd8/0xef
> [ 1596.933129] [<ffffffff802329f8>] run_local_timers+0x13/0x15
> [ 1596.933132] [<ffffffff80232a44>] update_process_times+0x4a/0x77
> [ 1596.933138] [<ffffffff8021434b>] smp_local_timer_interrupt+0x34/0x54
> [ 1596.933143] [<ffffffff802143cc>] smp_apic_timer_interrupt+0x61/0x78
> [ 1596.933147] [<ffffffff8020a29b>] apic_timer_interrupt+0x6b/0x70
> [ 1596.933151] <EOI> [<ffffffff80299dff>] free_buffer_head+0x24/0x3e
> [ 1596.933162] [<ffffffff80272a63>] kmem_cache_free+0x1f4/0x201
> [ 1596.933170] [<ffffffff80299dff>] free_buffer_head+0x24/0x3e
> [ 1596.933175] [<ffffffff80299ea1>] try_to_free_buffers+0x88/0x9f
> [ 1596.933181] [<ffffffff802565a9>] try_to_release_page+0x39/0x40
> [ 1596.933188] [<ffffffff8025b76d>] invalidate_mapping_pages+0x9d/0x121
> [ 1596.933196] [<ffffffff8025b800>] invalidate_inode_pages+0xf/0x11
> [ 1596.933200] [<ffffffff80299053>] invalidate_bdev+0x3b/0x3f
> [ 1596.933203] [<ffffffff8029c9ee>] kill_bdev+0x13/0x29
> [ 1596.933208] [<ffffffff8029d6e8>] __blkdev_put+0x62/0x141
> [ 1596.933213] [<ffffffff8029db62>] blkdev_put+0xb/0xd
> [ 1596.933218] [<ffffffff8029dbf7>] blkdev_close+0x2e/0x33
> [ 1596.933222] [<ffffffff8027a3c3>] __fput+0xc3/0x172
> [ 1596.933228] [<ffffffff8027a486>] fput+0x14/0x16
> [ 1596.933233] [<ffffffff80278c4f>] filp_close+0x61/0x6d
> [ 1596.933238] [<ffffffff80278ce7>] sys_close+0x8c/0xce
> [ 1596.933244] [<ffffffff8020965e>] system_call+0x7e/0x83
> [ 1596.933250]
Can you tell me which kernel version you are using?
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
next prev parent reply other threads:[~2007-05-16 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 16:43 Bernd Schubert
2007-05-16 16:49 ` Michal Piotrowski [this message]
2007-05-16 17:01 ` Bernd Schubert
2007-05-16 18:41 ` 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=6bffcb0e0705160949m7486705s1b2fc5bbe8a025df@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=bschubert@q-leap.de \
--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
all inboxes | Powered by JetHome®