From: Andrew Morton <akpm@digeo.com>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: wli@holomorphy.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, neilb@cse.unsw.edu.au
Subject: Re: 2.5.70-mm1 bootcrash, possibly RAID-1
Date: Wed, 28 May 2003 16:18:37 -0700 [thread overview]
Message-ID: <20030528161837.409099eb.akpm@digeo.com> (raw)
In-Reply-To: <20030528225913.GA1103@hh.idb.hist.no>
Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
> On Wed, May 28, 2003 at 04:35:44AM -0700, William Lee Irwin III wrote:
> >
> > This is unusual; I'm having trouble very close to this area. There is
> > a remote chance it could be the same problem.
> >
> > Could you log this to serial and get the rest of the oops/BUG? If it's
> > where I think it is, I've been looking at end_page_writeback() and so
> > might have an idea or two.
>
> I tried 2.5.70-mm1 on the dual celeron at home. This one has
> scsi instead of ide, so I guess it is a RAID-1 problem.
> This machine has root on raid-1 too. I believe there where
> several oopses in a row, I captured all of the last one
> thanks to a framebuffer with a small font. Here it is:
>
> Unable to handle kernel paging request at virtual address 8a8a8ab6
> *pde=0 OOPS 0000 [#1]
> EIP at put_all_bios+0x47/0x80
> (edx was the register containing 8a8a8a8a)
> Process swapper pid=0 threadinfo c1352000 task=c13f52d0
> Call trace:
> raid_end_bio_io
> raid1_end_request
That's POISON_BEFORE: "use of uninitialised memory", not "use of freed
memory".
I fiddled with the slab poisoning values, and shall undo that.
--
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-05-28 23:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 11:22 2.5.67-mm1 Andrew Morton
2003-04-08 13:01 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 13:17 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 15:31 ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 15:39 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:14 ` 2.5.67-mm1 Randy.Dunlap
2003-04-08 16:18 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 16:10 ` 2.5.67-mm1 Andrew Morton
2003-04-08 16:50 ` 2.5.67-mm1 Ed Tomlinson
2003-04-08 14:08 ` 2.5.67-mm1 William Lee Irwin III
2003-04-08 16:43 ` 2.5.67-mm1 Helge Hafting
2003-04-09 9:42 ` 2.5.67-mm1 cause framebuffer crash at bootup Helge Hafting
[not found] ` <20030409030534.619f7fa0.akpm@digeo.com>
2003-04-09 10:05 ` Andrew Morton
[not found] ` <20030409031845.185d853f.akpm@digeo.com>
2003-04-09 10:18 ` Andrew Morton
2003-04-09 20:30 ` Randy.Dunlap
2003-05-28 11:14 ` 2.5.67-mm1 bootcrash, possibly IDE or RAID Helge Hafting
2003-05-28 11:13 ` William Lee Irwin III
2003-05-28 11:34 ` 2.5.70-mm1 " Helge Hafting
2003-05-28 11:35 ` William Lee Irwin III
2003-05-28 22:59 ` 2.5.70-mm1 bootcrash, possibly RAID-1 Helge Hafting
2003-05-28 23:18 ` Andrew Morton [this message]
2003-05-28 23:30 ` Paul E. Erkkila
2003-05-29 1:08 ` Neil Brown
2003-05-29 7:14 ` Zwane Mwaikambo
2003-05-29 7:32 ` Zwane Mwaikambo
2003-05-30 1:59 ` Neil Brown
2003-05-31 16:13 ` Paul E. Erkkila
2003-05-29 4:27 ` Alain Toussaint
2003-05-29 13:22 ` John Stoffel
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=20030528161837.409099eb.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 \
--cc=wli@holomorphy.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