All of lore.kernel.org
 help / color / mirror / Atom feed
From: SPATZ1@t-online.de (Frank Schneider)
To: zaitcev@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: A tester is needed with dual P3 and USB
Date: Tue, 28 Aug 2001 01:09:11 +0200	[thread overview]
Message-ID: <3B8AD317.D6434681@t-online.de> (raw)
In-Reply-To: <20010827182204.A25212@devserv.devel.redhat.com> <20010828014211.A29068@netppl.fi>

Pekka Pietikainen schrieb:
> 
> On Mon, Aug 27, 2001 at 06:22:04PM -0400, Pete Zaitcev wrote:
> > Hi, All:
> >
> > I received a complaint that a UP kernel hangs on boot if USB is
> > enabled. SMP works. An SMP kernel started with "nosmp" hangs too.
> > The reporter is, umm, how shall I put it... is a power user.
> > I need someone to help me to track the problem down, because
> > I am curious. I heard of SMP hangs before, but a UP hang is
> > a novel idea.
> >
> > The box is VA Linux 1000 (similar to IBM Netfinity 4000r).
> > Kernel is 2.4.8-ac10.
> Doesn't VA use one of those Intel boards which have the problem
> with theis BIOS, which is seen as a hang with the adaptec driver?

Thats the problem i can reproduce here (ASUS-P2B-DS with Dual PIII/850,
USB and AHA2940U2W-SCSI onboard, Kernel 2.4.2/3-SMP), SMP-Kernels with
option "nosmp" simply stop when they try to access the SCSI-System, the
aic7xxx-driver loads (no matter if build-in or module), but stucks at
initializing the first device.
No Ooop or crash, it simply does nothing any more.

But a "real" UP-Kernel (i used the one from RH7.1, 2.4.2-UP) has no
problems with booting here.

Solong..
Frank.

--
Frank Schneider, <SPATZ1@T-ONLINE.DE>.                           
... -.-


  reply	other threads:[~2001-08-27 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 22:22 A tester is needed with dual P3 and USB Pete Zaitcev
2001-08-27 22:42 ` Pekka Pietikainen
2001-08-27 23:09   ` Frank Schneider [this message]
2001-08-27 23:44   ` [PATCH] disableapic option Kurt Garloff

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=3B8AD317.D6434681@t-online.de \
    --to=spatz1@t-online.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.