From: Pedro Pla <pedropla@holidaymarketing.com>
To: Pedro Pla <pedropla@holidaymarketing.com>
Cc: linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: Problem with SMP and NCCH-DL motherboard
Date: Wed, 27 Jul 2005 10:46:05 +0800 [thread overview]
Message-ID: <42E6F56D.3030305@holidaymarketing.com> (raw)
In-Reply-To: <42E5E19E.2090003@holidaymarketing.com>
Hi Again,
I've done some further tests disabling hyperthreading which then lets me
disable apic on the motherboard and when I disable these I can boot a
kernel compiled with smp, however it boots detecting only 1 cpu rather
than the 2 on the motherboard. If I then reenable APIC in the bios with
hyperthreading still disabled it fails in the same way, so the problem
seems to be with APIC. Any ideas what more I can try?
Thanks in advance!!
Pedro
Pedro Pla wrote:
>Hello,
>
>I'm running a system with an Asus NCCH-DL motherboard with dual Nocona
>Xeon 3.2 GHZ cpu's, when I boot the system with a single cpu kernel with
>acpi not compiled in it works fine, however when I try to boot a kernel
>with smp it gives a timeout detecting the cpus and then the machine
>reboots after I think trying to work out the irq tables, I say I think
>because it happens so fast that I can barely see what is on the screen
>before it reboots.
>
>I've tried recompiling the kernel with many different options both in
>and out and the only one that lets me boot is a single cpu without acpi,
>apic and hpet, I tried googling for similar problems but haven't been
>able to find anything that applies. I've also tried using an EM64T
>kernel in case it had to do with the Nocona being incompatible with smp
>in 32bit mode but that didn't seem to work and gave the same error.
>
>Is it a kernel problem or a hardware issue? I tried swapping cpu's in
>case one was broken but that didn't help, I also tried flashing the bios
>to the latest one from Asus in case there was some issue with that but
>no luck either.
>
>Also in case this is helpful in locating the problem, when I get it to
>boot a single cpu 2.6.12.1 kernel without acpi or apic I get the
>following errors with the PCI:
>
>NET: Registered protocol family 16
>PCI: PCI BIOS revision 2.10 entry at 0xf1d30, last bus=4
>PCI: Using configuration type 1
>SCSI subsystem initialized
>PCI: Probing PCI hardware
>PCI: Probing PCI hardware (bus 00)
>PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
>Boot video device is 0000:01:00.0
>PCI: Transparent bridge - 0000:00:1e.0
>PCI: Using IRQ router PIIX/ICH [8086/25a1] at 0000:00:1f.0
>PCI: IRQ 0 for device 0000:00:1f.1 doesn't match PIRQ mask - try
>pci=usepirqmask
>PCI: Found IRQ 11 for device 0000:00:1f.1
>PCI: Cannot allocate resource region 0 of device 0000:01:00.0
>
>Any ideas or advice would be greatly appreciated.
>
>Best regards,
>Pedro
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
next parent reply other threads:[~2005-07-27 2:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42E5E19E.2090003@holidaymarketing.com>
2005-07-27 2:46 ` Pedro Pla [this message]
2005-08-01 1:43 ` GOT IT WORKING - Problem with SMP and NCCH-DL motherboard Pedro Pla
2005-07-26 3:05 Pedro Pla
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=42E6F56D.3030305@holidaymarketing.com \
--to=pedropla@holidaymarketing.com \
--cc=linux-kernel@vger.kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).