From: "b@netzentry.com" <b@netzentry.com>
To: recbo@nishanet.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: Wed, 03 Dec 2003 18:57:49 -0800 [thread overview]
Message-ID: <3FCEA2AD.5040805@netzentry.com> (raw)
>Bob wrote:
>Local APIC locked up with nforce2 and VIA,
>impossibly serious with nforce2 and non-amd
>offboard ide controller cards. BIOS flash made
>problems go away.
>
>I experienced the lockups when using promise and
>siig sis ide hd controller pci cards. I still had problems
>with a 3ware card.
>
>Flashing the bios solved all problems. Now I run
>both the via and nforce2 mboards with APIC and
>Local APIC on in kernel. I'm running six ide drives,
>four on a 3ware pci hd controller card using ide-scsi.
>
>I got sound working on nforce2, and nvidia ti4200
>agp8 vid card(nvidia drivers crash X but agpgart
>with X "nv" instead of "nvidia" works in 2D well),
>but not usb. The sound config problem was fixed
>by "ln -s sound/dsp2 /dev/dsp". The apps only
>look for /dev/dsp.
>
>-Bob
Do you think that motherboard maker was really at fault or
did they genuinely fix a grotesque error. Were any changes
in the BIOS-change-list relevant to fixing up this APIC
problem in Linux?
Can you provide the following:
- which motherboard
- which bios revs (the broken one and the fixed one)
- which kernel are you running (is it vanilla, from a dist,
recompiled)
- lspci
- cat /proc/interrupts
- dmesg
- .config from kernel (if not stock from dist)
I really, really hope this problem can be solved without
a BIOS upgrade because getting board manufacturers to do
anything is very difficult.
next reply other threads:[~2003-12-04 2:58 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 2:57 b [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 13:07 NForce2 pseudoscience stability testing (2.6.0-test11) Dan Creswell
2003-12-04 12:17 b
2003-12-04 15:19 ` Craig Bradney
2003-12-04 16:32 ` Josh McKinney
2003-12-04 17:08 ` Julien Oster
2003-12-04 17:55 ` Josh McKinney
2003-12-05 13:28 ` Pat Erley
2003-12-04 9:09 b
2003-12-04 8:59 b
2003-12-04 5:37 b
2003-12-04 7:00 ` Craig Bradney
2003-12-04 5:11 Allen Martin
2003-12-04 20:04 ` Jesse Allen
2003-12-04 20:41 ` Craig Bradney
2003-12-04 20:55 ` Craig Bradney
2003-12-04 22:03 ` Bob
2003-12-04 1:41 b
2003-12-04 2:45 ` Jesse Allen
2003-12-04 7:42 ` Prakash K. Cheemplavam
2003-12-04 4:45 ` Josh McKinney
2003-12-04 11:47 ` ross.alexander
[not found] <fa.nmlihqm.16j6n38@ifi.uio.no>
[not found] ` <fa.f27m7i8.1vk0j84@ifi.uio.no>
2003-12-04 1:08 ` walt
2003-12-03 1:32 Allen Martin
2003-12-03 1:23 b
2003-12-03 1:30 ` Ian Kumlien
2003-12-03 0:58 Allen Martin
2003-12-03 1:09 ` Ian Kumlien
[not found] <3FCD21E1.5080300@netzentry.com>
2003-12-03 0:28 ` Craig Bradney
2003-12-03 0:48 ` Prakash K. Cheemplavam
2003-12-03 8:15 ` Craig Bradney
2003-12-03 17:09 ` bill davidsen
[not found] ` <200312031709.MAA18860@gatekeeper.tmr.com>
2003-12-03 17:37 ` Prakash K. Cheemplavam
2003-12-03 0:47 ` Ian Kumlien
[not found] <WSA7.6D.39@gated-at.bofh.it>
[not found] ` <WTYM.3ua.7@gated-at.bofh.it>
[not found] ` <WVoa.73O.17@gated-at.bofh.it>
2003-11-30 13:06 ` Lenar Lõhmus
2003-11-29 10:25 bug in -test11 make xconfig Christopher Sawtell
2003-11-29 11:18 ` NForce2 pseudoscience stability testing (2.6.0-test11) Craig Bradney
2003-11-29 16:34 ` Julien Oster
2003-11-29 16:47 ` Craig Bradney
2003-11-29 16:54 ` Craig Bradney
2003-12-07 11:32 ` Jussi Laako
2003-12-07 15:49 ` Prakash K. Cheemplavam
2003-12-01 18:30 ` Pavel Machek
2003-12-01 20:20 ` Craig Bradney
[not found] <001a01c3b515$b6030de0$0f00a8c0@client.attbi.com>
2003-11-28 15:13 ` ross.alexander
2003-11-28 16:46 ` Alistair John Strachan
2003-11-28 18:13 ` Julien Oster
2003-11-28 18:24 ` Prakash K. Cheemplavam
2003-11-29 2:55 ` Josh McKinney
2003-11-29 16:33 ` Julien Oster
2003-11-29 17:15 ` Josh McKinney
2003-12-02 10:13 ` ross.alexander
2003-12-02 21:12 ` Josh McKinney
2003-12-03 16:23 ` Julien Oster
2003-11-28 18:00 ` Julien Oster
2003-11-28 18:18 ` Prakash K. Cheemplavam
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=3FCEA2AD.5040805@netzentry.com \
--to=b@netzentry.com \
--cc=linux-kernel@vger.kernel.org \
--cc=recbo@nishanet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).