All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederik Nosi <fredi@e-salute.it>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel (2.4.19-pre8) hang
Date: 28 May 2002 22:03:53 +0200	[thread overview]
Message-ID: <1022616234.2427.34.camel@linux> (raw)
In-Reply-To: <1022610217.4123.133.camel@irongate.swansea.linux.org.uk>

Il mar, 2002-05-28 alle 20:23, Alan Cox ha scritto:
> On Tue, 2002-05-28 at 18:10, Andre Hedrick wrote: 
> > 99% bet it is a timing problem in the VIA mainboard.
> > VIA has always had problems first from attempts to allow it to do PIO5
> > which does not exist.  Basic hotrodding of the timings has always been a
> > problem.  Other issues include basic design flaws in the the VIA reference
> > docs for board makers.
> > 
> > If you are using quality junk^VIA mainboards, you will not have issues.

Sadly now I was booting again that box; this is what the bios test is
saying:

<bios>
Failure Predicted on Primary Master: QUANTUM FIREBALLlct10 15
Immediatly back-up your data and replace your hard disk drive.
A failure may be imminent
</bios>

Ok, my mainboard is an ASUS K7V-RM with the VIA's kx133 chipset (the
first chipset for athlon with agp 4x && 133 pci if it matters).
So:
Bios: Havard Medallion v6.0
chipset:
Via VT 8371 516 BGA north bridge
Via 82C686A south bridge

Integrated in the mainboard there is an yamaha audio chip witch I'm not
using
Other pieces of hardware are a Matrox g400 max video card that works
happily and a cheap eth, pcnet or something
My HD is a quantum fireball lct10 15 (15 Gb capacity)


> So why wasn't it showing up before. Obviously something we changed is
> triggering a situation that board or otherwise wasn't there before. 
> 

I will be happy if it was the case, but I think that it is really a
hardware problem :(
However, this box has worked with kernels from 2.0.X till the last
vanilla 2.4.19-pre8 . I've used the box with 2.4.19-pre8 from the day
the prepatch have seen the web till ~4 days ago with the same workload,
so if it was that the kernel is buggy, I will have noticed it from the
first days that I've installed it. And I've used this HD for 2 years to
now. A glorious death :)

However if you need info, tests to do or whatever I'm happy to do it.
Maybe this hd will help for something.


Thank you for your replies, you rock guys :)
Fredi


       reply	other threads:[~2002-05-28 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1022610217.4123.133.camel@irongate.swansea.linux.org.uk>
2002-05-28 20:03 ` Frederik Nosi [this message]
2002-05-28 22:24   ` Kernel (2.4.19-pre8) hang Alan Cox
2002-05-28 13:41 Frederik Nosi
2002-05-28 15:05 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-05-27 19:24 Frederik Nosi
2002-05-27 21:24 ` Alan Cox
2002-05-28 10:43   ` Frederik Nosi
2002-06-01 21:57   ` Olivier Galibert

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=1022616234.2427.34.camel@linux \
    --to=fredi@e-salute.it \
    --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 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.