From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Herbert Poetzl <herbert@13thfloor.at>,
"Georg C. F. Greve" <greve@fsfeurope.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: PROBLEM: Kernel 2.6.10 crashing repeatedly and hard
Date: Fri, 31 Dec 2004 10:55:53 +0000 [thread overview]
Message-ID: <20041231105553.C29868@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.58.0412302052430.2280@ppc970.osdl.org>; from torvalds@osdl.org on Thu, Dec 30, 2004 at 08:53:45PM -0800
On Thu, Dec 30, 2004 at 08:53:45PM -0800, Linus Torvalds wrote:
> On Fri, 31 Dec 2004, Herbert Poetzl wrote:
> >
> > maybe this can provide more information (let me know if
> > you need an ASCII version, I'll transcribe it by hand then)
>
> Same thing. Some slab corruption causing problems at free time. The
> real problem happened much earlier, so the oops isn't all that useful.
> What would be useful is if you can pinpoint what triggers it and/or when
> it started happening..
2.6.10-rc3 maybe... depending on whether you want to look at this oops
with a proprietary iSCSI module loaded...
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-December/026159.html
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-December/026164.html
However, the fact that this person can't reproduce the slab corruption
without this iSCSI module loaded may be telling, but since you're also
chasing such a problem, it may not have anything to do with their iSCSI
stuff.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-12-31 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-30 0:31 PROBLEM: Kernel 2.6.10 crashing repeatedly and hard Georg C. F. Greve
2004-12-30 16:23 ` Georg C. F. Greve
[not found] ` <v3rda2-hjn.ln1@news.it.uc3m.es>
2004-12-30 17:53 ` Sandro Dentella
2004-12-30 19:50 ` Michael Tokarev
2004-12-30 20:54 ` berk walker
2005-01-01 13:39 ` Helge Hafting
2004-12-30 20:40 ` Linus Torvalds
2004-12-30 22:04 ` Georg C. F. Greve
2004-12-30 22:23 ` Linus Torvalds
2004-12-31 4:16 ` Herbert Poetzl
2004-12-31 4:53 ` Linus Torvalds
2004-12-31 10:55 ` Russell King [this message]
2004-12-31 9:58 ` Georg C. F. Greve
2005-01-01 20:06 ` Alan Cox
2005-01-02 20:11 ` Linus Torvalds
2005-01-02 20:32 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 10:21 Nick Warne
2004-12-31 11:46 Manfred Spraul
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=20041231105553.C29868@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greve@fsfeurope.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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