From: Andrew Morton <akpm@digeo.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: 2.5.64-mm7 - dies on smp with raid
Date: Sat, 15 Mar 2003 12:03:43 -0800 [thread overview]
Message-ID: <20030315120343.71faf732.akpm@digeo.com> (raw)
In-Reply-To: <3E736505.2000106@aitel.hist.no>
Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
> mm7 crashed where mm2 works.
> The machine is a dual celeron with two scsi disks with
> some raid-1 & raid-0 partitions.
>
> deadline or anicipatory scheduler does not make a difference.
> It dies anyway, attempting to kill init.
>
> Here's what I managed to write down before the 30 second reboot
> kicked in:
>
> EIP is at md_wakeup_thread
>
> stack:
> do_md_run
> autorun_array
> autorun_devices
> autostart_arrays
> md_ioctl
> dentry_open
> kmem_cache_free
> blkdev_ioctl
> sys_ioctl
> init
> init
>
> This happened during the boot process. The kernel is compiled
> with gcc 2.95.4 from debian testing. The machine uses devfs
>
A lot of md updates went into Linus's tree overnight. Can you get some more
details for Neil?
Here is a wild guess:
diff -puN drivers/md/md.c~a drivers/md/md.c
--- 25/drivers/md/md.c~a 2003-03-15 12:02:04.000000000 -0800
+++ 25-akpm/drivers/md/md.c 2003-03-15 12:02:14.000000000 -0800
@@ -2818,6 +2818,8 @@ int md_thread(void * arg)
void md_wakeup_thread(mdk_thread_t *thread)
{
+ if (!thread)
+ return;
dprintk("md: waking up MD thread %p.\n", thread);
set_bit(THREAD_WAKEUP, &thread->flags);
wake_up(&thread->wqueue);
_
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@digeo.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Neil Brown <neilb@cse.unsw.edu.au>
Subject: Re: 2.5.64-mm7 - dies on smp with raid
Date: Sat, 15 Mar 2003 12:03:43 -0800 [thread overview]
Message-ID: <20030315120343.71faf732.akpm@digeo.com> (raw)
In-Reply-To: <3E736505.2000106@aitel.hist.no>
Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
> mm7 crashed where mm2 works.
> The machine is a dual celeron with two scsi disks with
> some raid-1 & raid-0 partitions.
>
> deadline or anicipatory scheduler does not make a difference.
> It dies anyway, attempting to kill init.
>
> Here's what I managed to write down before the 30 second reboot
> kicked in:
>
> EIP is at md_wakeup_thread
>
> stack:
> do_md_run
> autorun_array
> autorun_devices
> autostart_arrays
> md_ioctl
> dentry_open
> kmem_cache_free
> blkdev_ioctl
> sys_ioctl
> init
> init
>
> This happened during the boot process. The kernel is compiled
> with gcc 2.95.4 from debian testing. The machine uses devfs
>
A lot of md updates went into Linus's tree overnight. Can you get some more
details for Neil?
Here is a wild guess:
diff -puN drivers/md/md.c~a drivers/md/md.c
--- 25/drivers/md/md.c~a 2003-03-15 12:02:04.000000000 -0800
+++ 25-akpm/drivers/md/md.c 2003-03-15 12:02:14.000000000 -0800
@@ -2818,6 +2818,8 @@ int md_thread(void * arg)
void md_wakeup_thread(mdk_thread_t *thread)
{
+ if (!thread)
+ return;
dprintk("md: waking up MD thread %p.\n", thread);
set_bit(THREAD_WAKEUP, &thread->flags);
wake_up(&thread->wqueue);
_
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-15 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 9:17 2.5.64-mm7 Andrew Morton
2003-03-15 9:17 ` 2.5.64-mm7 Andrew Morton
2003-03-15 10:13 ` 2.5.64-mm7 Russell King
2003-03-15 10:13 ` 2.5.64-mm7 Russell King
2003-03-15 17:38 ` 2.5.64-mm7 - dies on smp with raid Helge Hafting
2003-03-15 17:38 ` Helge Hafting
2003-03-15 20:03 ` Andrew Morton [this message]
2003-03-15 20:03 ` Andrew Morton
2003-03-15 20:42 ` Neil Brown
2003-03-15 20:42 ` Neil Brown
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=20030315120343.71faf732.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=neilb@cse.unsw.edu.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.