From: Wakko Warner <wakko@animx.eu.org>
To: Jos Hulzink <josh@stack.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.40: some results...
Date: Sat, 5 Oct 2002 18:24:51 -0400 [thread overview]
Message-ID: <20021005182451.B15663@animx.eu.org> (raw)
In-Reply-To: <20021005214508.IKVD1253.amsfep12-int.chello.nl@there>; from Jos Hulzink on Sat, Oct 05, 2002 at 11:45:07PM +0200
> First one reaction: Whoooow this kernel boots / responds fast ! Nice job
> guys! No need to update this Dual PII 333 for the next century :)
>
> Anyway. It boots and runs, only "scheduling while atomic" sounds very bad to
> me. Furthermore the famous Debug: sleeping function called from illegal
> context at slab.c:1374 and friends, I think you have seen most of them
> already.
>
> I marked all places I found odd with "^^^^^" search for those and you'll find
> them. If any of these is new, please let me know, I'll provide details / test
> results on demand.
>
> Uptime is half an hour now, no ide problems yet. Time to stress the bitch.
> Unfortunately I'm out of CD-rw's so no burning tests for the weekend.
>
> I'm impressed, and back in the 2.5 testing business.
I can't get it to compile for me. ide and serial both bomb out. I'm
compiling as a module for both of these (I was going to test on an nfs
root/netboot machine and I modularize EVERYTHING! =)
If you want my .config and errors, I'll send them. There was a few things I
changed in the source to get it to compile (serial was ok after removing an
#if test) and ide had unresolved symbols (ide being a few ide modules)
I'm not at that machine at this time and have no access to it (but will
later today).
next prev parent reply other threads:[~2002-10-05 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 21:45 2.5.40: some results Jos Hulzink
2002-10-05 22:03 ` Jos Hulzink
2002-10-05 22:24 ` Wakko Warner [this message]
2002-10-05 23:24 ` Alan Cox
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=20021005182451.B15663@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=josh@stack.nl \
--cc=linux-kernel@vger.kernel.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