From: Bryce Harrington <bryce@osdl.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.19-rc1-mm1: fs/file.c138 on ia64
Date: Tue, 10 Oct 2006 22:38:01 -0700 [thread overview]
Message-ID: <20061011053801.GA16050@osdl.org> (raw)
In-Reply-To: <20061010181553.21a5141f.akpm@osdl.org>
On Tue, Oct 10, 2006 at 06:15:53PM -0700, Andrew Morton wrote:
> On Tue, 10 Oct 2006 18:08:26 -0700
> Bryce Harrington <bryce@osdl.org> wrote:
> > We've noticed a new ia64 issue on the 2.6.19-rc1-mm1 kernel. It has not
> > occurred on other 2.6.19 kernels we've tested. We aslo encountered this
> > BUG only on ia64; the x86 and x86_64 systems booted without issue.
> > Apologies if this is already known; I didn't spot it in the list
> > archives.
> >
> > http://crucible.osdl.org/runs/2511/sysinfo/ita01.console.log
> >
> > Freeing unused kernel memory: 1840kB freed
> > kernel BUG at fs/file.c:138!
>
> Was that with
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc1/2.6.19-rc1-mm1/hot-fixes
> applied?
Vadim Lobanov <vlobanov@speakeasy.net> writes:
> Dave, Olof, Linas, Bryce,
>
> Could you please test the patch at the bottom of the email to see if it
> makes your computers happy again, if you have the time and inclination
> to do so?
I've run the tests with the hotfix and with Vadim's patch. Here are the
results of compiling, booting, and running the hotplug-cpu test on it:
run patch(es) result
2511 2.6.19-rc1-mm1 BUG at fs/file.c:138
2519 2.6.19-rc1-mm1 + hot-fix PASS
2521 2.6.19-rc1-mm1 + vadim's patch PASS
2520 2.6.19-rc1-mm1 + hot-fix + vadim's patch patch doesn't apply
Results available at http://crucible.osdl.org/runs/$run/
Thanks,
Bryce
next prev parent reply other threads:[~2006-10-11 5:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 17:44 [PATCH] Check for online cpus before bringing them up Srivatsa Vaddagiri
2006-03-17 1:08 ` Andrew Morton
2006-03-17 1:16 ` Shaohua Li
2006-03-17 8:46 ` Srivatsa Vaddagiri
2006-03-17 9:04 ` Andrew Morton
2006-03-17 14:13 ` Srivatsa Vaddagiri
2006-03-18 14:09 ` Ashok Raj
2006-03-21 1:08 ` Shaohua Li
2006-03-21 1:25 ` Ashok Raj
2006-03-21 1:36 ` Shaohua Li
2006-10-06 23:10 ` Status on CPU hotplug issues Bryce Harrington
2006-10-06 23:29 ` Andrew Morton
2006-10-07 0:00 ` Bryce Harrington
2006-10-07 10:35 ` Pavel Machek
2006-10-07 20:42 ` Bryce Harrington
2006-10-08 18:29 ` Heiko Carstens
2006-10-08 19:14 ` Pavel Machek
2006-10-11 1:08 ` [BUG] 2.6.19-rc1-mm1: fs/file.c138 on ia64 Bryce Harrington
2006-10-11 1:15 ` Andrew Morton
2006-10-11 5:38 ` Bryce Harrington [this message]
2006-10-07 10:24 ` Status on CPU hotplug issues Pavel Machek
2006-10-07 20:25 ` Bryce Harrington
2006-10-08 19:13 ` Pavel Machek
2006-10-09 7:42 ` Bryce Harrington
2006-10-07 21:57 ` Pavel Machek
2006-10-09 21:40 ` Randy Dunlap
2006-10-23 22:26 ` Bryce Harrington
2006-11-08 5:35 ` Randy Dunlap
2006-11-08 5:52 ` Bryce Harrington
2006-03-17 12:21 ` [PATCH] Check for online cpus before bringing them up Ashok Raj
2006-03-17 13:59 ` Srivatsa Vaddagiri
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=20061011053801.GA16050@osdl.org \
--to=bryce@osdl.org \
--cc=akpm@osdl.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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