From: "Joel Soete" <soete.joel@tiscali.be>
To: Randolph Chung <randolph@tausq.org>
Cc: linux-ide@vger.kernel.org,
Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>,
parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Re: a fix for NS87415 on C3K broken
Date: Fri, 24 Sep 2004 18:17:46 +0200 [thread overview]
Message-ID: <4152E882000003C7@mail-7-bnl.tiscali.it> (raw)
In-Reply-To: <4152E8820000014C@mail-7-bnl.tiscali.it>
Hello Randolph,
Auto-reply for an update (sorry)
>
> >
> > > But when I try to use the ide-cdrom the system carsh with such oops:
> > > Backtrace:
> > > [<000000001017e0d8>] drain_array_locked+0x98/0x148
> > > [<000000001017e2c4>] cache_reap+0x13c/0x2b0
> > > [<000000001015e574>] worker_thread+0x284/0x330
> > > [<0000000010164714>] kthread+0x12c/0x138
> > > [<000000001010647c>] ret_from_kernel_thread+0x24/0x38
> >
> > maybe this will help:
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=109529103522064&w=2
> >
> Thanks for advise, it does the trick :)
>
> > but we are seeing some of these slab errors with this build that are
not
> > cdrom related too... :(
> >
> mmm On the N4k with some 2.6.9-rc2-pa6 release, I lso noticed a crash
with
> IAOQ refering to free_block () (eventhought that this system loop all
the
> night to make -j4 vmlinux without any pb; I just stop the loop and restart
> it later and ... panic() ?)
>
> > can you try compiling with slab debug (under kernel debugging)?
> >
> Of course and btw I will rebuild a 2.6.9-rc2-pa_7_ for the N4k too and
a
> 32b for a b180 and a chroot disk to test the new Carlos glibc build ;)
>
Well, I test the 2.6.9-rc2-pa7 with slab debug (before Matthew added sys
call) and build this kernel in a loop (now about 30 loop) without pb just
numerous:
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
applying fixup for 0x10124d08, fixup at 0x10469a68
any clue?
Thanks again,
Joel
---------------------------------------------------------------------------
Tiscali ADSL GO, 29,50 Euro/mois pendant toute une année, profitez-en...
http://reg.tiscali.be/adsl/welcome.asp?lg=FR
prev parent reply other threads:[~2004-09-24 16:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-16 16:17 NS87415 on C3K broken Grant Grundler
2004-09-16 22:50 ` Bartlomiej Zolnierkiewicz
2004-09-16 23:25 ` Grant Grundler
2004-09-17 0:43 ` Bartlomiej Zolnierkiewicz
2004-09-22 10:41 ` a fix for " Joel Soete
2004-09-22 16:37 ` Grant Grundler
2004-09-22 16:53 ` [parisc-linux] " Matthew Wilcox
2004-09-22 17:21 ` Joel Soete
2004-09-22 17:41 ` [parisc-linux] " Matthew Wilcox
2004-09-23 16:21 ` Joel Soete
2004-09-23 16:27 ` Randolph Chung
2004-09-24 7:04 ` Joel Soete
2004-09-24 16:17 ` Joel Soete [this message]
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=4152E882000003C7@mail-7-bnl.tiscali.it \
--to=soete.joel@tiscali.be \
--cc=bzolnier@elka.pw.edu.pl \
--cc=linux-ide@vger.kernel.org \
--cc=parisc-linux@parisc-linux.org \
--cc=randolph@tausq.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