From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: John Huttley <john@mwk.co.nz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.4.16 Bug] major failure
Date: Tue, 11 Dec 2001 12:17:54 +0100 [thread overview]
Message-ID: <20011211121754.E4618@emma1.emma.line.org> (raw)
In-Reply-To: <1008054620.1453.0.camel@albatross.hisdad.org.nz>
In-Reply-To: <1008054620.1453.0.camel@albatross.hisdad.org.nz>
On Tue, 11 Dec 2001, John Huttley wrote:
> I wish to report a major failure.
> with 2.4.16 and 2.4.17-pre8
> on PII-450 x2 SMP system, Gigabyte BXDS board
> (has adaptec scsi chip on it)
> using IDE disk, scsi tape (DDS-4)
>
> My system boots to X.
> I swap to VC1 and start tarring up a lot of mp3's.
>
> It works fine if i leave it to complete.
>
> If I go to X and then back to VC1, the system will lock solid.
> No num lock, no magic sysreq, no ping.
If it wasn't for SMP, I'd say try to boot with "disableapic", but I have
no clues whether this will break SMP or wreak other havoc.
At least, since around 2.4.10, booting my Uniprocessor Duron on a
Gigabyte 7ZXR board breaks at the same occasion. At the time I reported
that, I was told to take this to the XFree guys, then that IOAPIC stuff
on UP was unstable.
I tend to believe that some bug sneaked in around those 2.4.10 versions.
Can you tell what kernel versions were the last that work OK for you
when switching from X11 to virtual console?
(Remeber to Cc: John Huttley on replies, he said he's not on the list.)
next prev parent reply other threads:[~2001-12-11 11:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 7:10 John Huttley
2001-12-11 11:17 ` Matthias Andree [this message]
2001-12-11 11:27 ` Bruce Harada
2001-12-11 21:01 [2.4.16 bug] Major failure John Huttley
2001-12-11 21:16 Grover, Andrew
2001-12-12 5:09 ` John Huttley
2001-12-12 8:47 John Huttley
2001-12-12 17:14 ` Marcelo Tosatti
2001-12-12 18:49 Grover, Andrew
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=20011211121754.E4618@emma1.emma.line.org \
--to=matthias.andree@stud.uni-dortmund.de \
--cc=john@mwk.co.nz \
--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
all inboxes | Powered by JetHome®