public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matthew Walker" <mwalker@kydance.net>
To: "Chris Gianelloni" <wolf31o2@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] vanilla-sources 2.4.21 problems...
Date: Tue, 22 Jul 2003 09:56:45 -0600 (MDT)	[thread overview]
Message-ID: <35804.216.190.203.130.1058889405.squirrel@squirrelmail.kydance.net> (raw)
In-Reply-To: <1058877715.2796.5.camel@vertigo>

As I said in my second message, the bug link is:

http://bugs.gentoo.org/show_bug.cgi?id=25010


Chris Gianelloni said:
> I have had absolutely zero problems with vanilla-sources.  The fact that
> we make no changes from the Linus kernel on vanilla sources leads me to
> believe that you're having a problem with the kernel itself.  What bug
> number is it, please?  If this is an actual bug in the kernel, it would
> definitely need to be reported upstream.
>
> --
> Chris Gianelloni
> Developer, Gentoo Linux
>
> On Mon, 2003-07-21 at 19:22, Matthew Walker wrote:
>> I'm writing up a bug report on this right now, but I thought I'd see if
>> anyone else was having the issue.
>>
>> I've got two servers I've tried to install 2.4.21 on now, both of which
>> hang
>> during boot just after listing the IDE drives/SCSI controllers. This is
>> disturbing, since 2.4.21 is listed as Stable, and it definately isn't, at
>> least for me.
>>
>> Anyone else had issues with 2.4.21?
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
>


-- 
 Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=utoxin&p=main

--
gentoo-dev@gentoo.org mailing list


      reply	other threads:[~2003-07-22 15:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-21 23:22 [gentoo-dev] vanilla-sources 2.4.21 problems Matthew Walker
2003-07-21 23:35 ` Matthew Walker
2003-07-22 12:41 ` Chris Gianelloni
2003-07-22 15:56   ` Matthew Walker [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=35804.216.190.203.130.1058889405.squirrel@squirrelmail.kydance.net \
    --to=mwalker@kydance.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=wolf31o2@gentoo.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