All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank von Daak <f.vondaak@kpage.de>
To: linux-smp@vger.kernel.org
Subject: Re: Dual Core CPU on Abit NI8-Board
Date: Thu, 6 Apr 2006 08:27:54 +0200	[thread overview]
Message-ID: <200604060827.54951.f.vondaak@kpage.de> (raw)
In-Reply-To: <200604051405.13901.f.vondaak@kpage.de>

Hi!

I'ld like to sum up, what I've tried to solve my smp(?)-problem:

- I've bootet my vanilla 2.6.17-rc1 kernel with the following options appended 
in "lilo.conf":
1. noapic
2. pci=noacpi
3. pci=biosirq
4. pci=routeirq
5. pci=conf1
6. acpi=off

and I've tried to combine most of the options together. (very much reboots as 
you can believe :-})

- I've started my x-server with just one geforce card.
- I've disconnected the SLI-bridge from my card and put the board into normal 
(not sli)-mode. (In this case the board has one 16xPCIe and one 1XPCIe-Slot. 
In the other case it hase two 16XPCIe-slots, and the gra.-cards are sharing 
one irq)
- I've removed PREEMPT from the kernel
- I've tried kernel 2.6.16.1 and installed a 64Bit Debian with 2.6.15
- I've removed the usb-module so that the graphics-adapters don't have to 
share an irq with usb
- I've upgraded my motherboard-bios to the latest version
- I've tried some different bios-settings (low cpuid for example)
- I've contacted nvidia - they also have not heard about this problem

The result was always the same:
If I start the kernel with ACPI the system is running rock solid, but I have 
just one cpu-core.
If I start with disabled ACPI the system is hard-crashing after a short while. 
(Sometimes it is crashing without starting an OpenGL-app!)


So I have no more ideas at the moment...
Should I go and buy a new motherboard?

Greetings
Frank

-- 
Name:	Frank von Daak
eMail:	f.vondaak@kpage.de	Homepage: http://www.kpage.de
"It takes a revolution, to make a solution!
    Bob Marley"

  reply	other threads:[~2006-04-06  6:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05  6:28 Dual Core CPU on Abit NI8-Board Frank von Daak
2006-04-05  6:39 ` cerise
2006-04-05  7:13   ` Frank von Daak
2006-04-05 16:57     ` cerise
     [not found] ` <cbe23c50604050011i3bcd433dxbf0bf826ba679324@mail.gmail.com>
2006-04-05  8:39   ` Frank von Daak
2006-04-05  9:43     ` Frank von Daak
     [not found]       ` <cbe23c50604050315u3daad82x14beed5ed16c43fd@mail.gmail.com>
2006-04-05 12:05         ` Frank von Daak
2006-04-06  6:27           ` Frank von Daak [this message]
2006-04-06 20:39             ` Frank von Daak
2006-04-06 20:58               ` Randy.Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2006-04-07  5:07 Frank von Daak
2006-04-07  9:19 ` Frank von Daak

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=200604060827.54951.f.vondaak@kpage.de \
    --to=f.vondaak@kpage.de \
    --cc=linux-smp@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.