From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc2-mm1
Date: Thu, 19 Oct 2006 01:48:57 +1000 [thread overview]
Message-ID: <45364CE9.7050002@yahoo.com.au> (raw)
In-Reply-To: <1161185599.18117.1.camel@dyn9047017100.beaverton.ibm.com>
Badari Pulavarty wrote:
> On Mon, 2006-10-16 at 23:06 -0700, Andrew Morton wrote:
>
>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc2/2.6.19-rc2-mm1/
>>
>>
>>- Added the hwmon and i2c trees to the -mm lineup. These are quilt-style
>> trees, maintained by Jean Delvare.
>
>
>
> LTP writev tests seems to lockup the machine. reiserfs issue ?
...
> BUG: soft lockup detected on CPU#2!
>
> Call Trace:
> <IRQ> [<ffffffff8024a4ba>] softlockup_tick+0xfa/0x120
> [<ffffffff8022e10f>] __do_softirq+0x5f/0xd0
> [<ffffffff80232067>] update_process_times+0x57/0x90
> [<ffffffff80217e84>] smp_local_timer_interrupt+0x34/0x60
> [<ffffffff802185db>] smp_apic_timer_interrupt+0x4b/0x80
> [<ffffffff80326ce0>] __copy_user_nocache+0x20/0x150
> [<ffffffff8020a7e6>] apic_timer_interrupt+0x66/0x70
> <EOI> [<ffffffff802b8de0>] reiserfs_get_block+0x0/0x10c0
> [<ffffffff80295198>] __block_prepare_write+0x158/0x470
> [<ffffffff802b8de0>] reiserfs_get_block+0x0/0x10c0
> [<ffffffff802954ca>] block_prepare_write+0x1a/0x30
> [<ffffffff802b7cea>] reiserfs_prepare_write+0xca/0x140
> [<ffffffff8024e9d2>] generic_file_buffered_write+0x2b2/0x610
This is likely to be a reiserfs interaction with the pagecache write
deadlock fixes. Chris Mason just now identified a couple of issues
and is going to work on a fix.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2006-10-18 15:49 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 6:06 2.6.19-rc2-mm1 Andrew Morton
[not found] ` <a44ae5cd0610170003r77595cc0p8ed66badde952859@mail.gmail.com>
2006-10-17 7:36 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-17 8:41 ` 2.6.19-rc2-mm1 Brice Goglin
2006-10-17 12:54 ` [PATCH] backlight users need to select BACKLIGHT_CLASS_DEVICE Andy Whitcroft
2006-10-17 13:17 ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-17 14:23 ` 2.6.19-rc2-mm1 Andy Whitcroft
2006-10-17 16:07 ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-17 18:22 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:44 ` 2.6.19-rc2-mm1 Dylan Taft
2006-10-17 15:45 ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-17 18:29 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-20 13:40 ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-17 19:37 ` 2.6.19-rc2-mm1 Jeremy Fitzhardinge
2006-10-17 20:22 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 10:05 ` 2.6.19-rc2-mm1 Michael Ellerman
2006-10-18 19:05 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-17 19:53 ` [2.6.19-rc2-mm1] error: too few arguments to function ‘crypto_alloc_hash’ Andrew James Wade
2006-10-17 21:19 ` Edward Shishkin
2006-10-18 16:53 ` Andrew James Wade
2006-10-18 15:33 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 15:48 ` Nick Piggin [this message]
2006-10-18 17:15 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 17:26 ` 2.6.19-rc2-mm1 Chris Mason
2006-10-18 17:32 ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:41 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 17:56 ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 17:58 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 18:14 ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 18:22 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 18:31 ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 23:59 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 22:44 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 23:01 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-18 23:25 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 0:07 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-19 0:21 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 15:28 ` 2.6.19-rc2-mm1 Badari Pulavarty
2006-10-19 12:32 ` 2.6.19-rc2-mm1 Andi Kleen
2006-10-19 16:18 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 16:57 ` 2.6.19-rc2-mm1 Andi Kleen
2006-10-18 18:27 ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 19:18 ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-18 19:33 ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-18 19:42 ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-18 20:20 ` 2.6.19-rc2-mm1 Rafael J. Wysocki
2006-10-18 20:26 ` 2.6.19-rc2-mm1 Cedric Le Goater
2006-10-18 22:23 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 16:05 ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-19 18:10 ` 2.6.19-rc2-mm1 Nick Piggin
2006-10-20 7:37 ` 2.6.19-rc2-mm1 Carsten Otte
2006-10-18 20:22 ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 18:42 ` 2.6.19-rc2-mm1 Gabriel C
2006-10-18 21:44 ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 22:29 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:41 ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 22:46 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-18 22:57 ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 23:04 ` 2.6.19-rc2-mm1 Jiri Kosina
2006-10-18 23:12 ` 2.6.19-rc2-mm1 Andrew Morton
2006-10-19 14:45 ` 2.6.19-rc2-mm1 // errors in verify_redzone_free() Mariusz Kozlowski
2006-10-19 17:03 ` Andrew Morton
2006-10-19 17:17 ` Jean Tourrilhes
2006-10-19 17:25 ` Andrew Morton
2006-10-19 17:47 ` Jean Tourrilhes
2006-10-19 18:31 ` Mariusz Kozlowski
2006-10-19 18:33 ` Jean Tourrilhes
2006-10-19 17:33 ` Mariusz Kozlowski
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=45364CE9.7050002@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
/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