From: Xavier Bestel <xavier.bestel@free.fr>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.11: nforce3 250gb lockups
Date: Fri, 17 Jun 2005 10:41:33 +0200 [thread overview]
Message-ID: <1118997693.30207.119.camel@gonzales> (raw)
In-Reply-To: <1118904850.5709.15.camel@localhost.localdomain>
Sorry for replying to myself, but this may interest someone.
Le jeudi 16 juin 2005 à 08:54 +0200, Xavier Bestel a écrit :
> Hi,
>
> I have a brand new computer, with an MSI K8N Neo (nforce3-based) which
> lockups quite easily. It seems it happens when I play audio for a while,
> or when accessing hd under load. With "nolapic", the boot stops when
> accessing hda, with something like "hda interrupt timeout" repeating on
> the screen. With "noapic nolapic", it boots normally but doesn't lockup
> less. The Ubuntu install CD lockups at boot even with "noapic nolapic".
>
> The kernel is the stock debian/sid 2.6.11-9-amd64-k8, the userspace is
> i386 (32bits). lspci and dmesg at the bottom of this mail. The only
> advices I found by googling were to try nolapic (which I did without
> success) or the binary drivers (which I won't try).
> Is there anything I can do, short of trying to return it to my
> reseller ?
As suggested by Denis Vlasenko <vda@ilport.com.ua> I disabled DMA for
harddisks (because I have ATA hds) in the BIOS, and now it works
flawlessly. No need for "no(l)apic". For the record, the drives are:
hda: WDC WD400BB-32BSA0, ATA DISK drive
hdb: HITACHI DVD-ROM GD-7500, ATAPI CD/DVD-ROM drive
hdc: ST340824A, ATA DISK drive
hdd: DVDRW IDE 16X, ATAPI CD/DVD-ROM drive
and an unused barracuda 160G on sda.
Xav
next prev parent reply other threads:[~2005-06-17 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 6:54 2.6.11: nforce3 250gb lockups Xavier Bestel
2005-06-17 8:41 ` Xavier Bestel [this message]
2005-06-17 8:59 ` Denis Vlasenko
-- strict thread matches above, loose matches on Subject: below --
2005-06-18 0:00 Kenneth Parrish
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=1118997693.30207.119.camel@gonzales \
--to=xavier.bestel@free.fr \
--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