Can't reboot "intel 5400" based systems with FEDORA 10

jf.argentino · 04-20-2009, 12:11 PM

Hello,

I have two system based on dual XEON + intel 5400 chipset one DELL T7400 and another one based on a TYAN Tempest i5400 mobo (don't be jealous they're not mines). They run FEDORA 10 up-to-date (kernel are 2.6.27.21-170.2.56.fc10.i686.PAE) just fine for a while now, the only thing it's that they never reboot.

If I run the "reboot" command, they never start again, I have to press a long time the power switch to stop them and power on again.
On the TYAN mobo, I can see that the POST goes until the extended memory test then go back to the POST beginning and loop undefinitly...

I take a (quick) look into the TYAN BIOS setup but I don't find anything revelant until now, but as I'm not a hardware expert I'm maybe missing an important option to set.

For the DELL bios setup, which is more straightforward (there's far less option we can set), I found nothing too.

In the "dmesg" of the TYAN system I've these warnings / errors:

Code:

DMI present.
Phoenix BIOS detected: BIOS may corrupt low RAM, working it around.
last_pfn = 0x140000 max_arch_pfn = 0x1000000
x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
mtrr: your BIOS has set up an incorrect mask, fixing it up.
kernel direct mapping tables up to 38000000 @ 10000-15000
NX (Execute Disable) protection: active
...
pci_express 0000:0a:02.0:pcie21: allocate port service
aer 0000:00:01.0:pcie01: AER service couldn't init device: no _OSC support
aer 0000:00:05.0:pcie01: AER service couldn't init device: no _OSC support
aer 0000:00:09.0:pcie01: AER service couldn't init device: no _OSC support
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
...
input: Macintosh mouse button emulation as /devices/virtual/input/input2
Driver 'sd' needs updating - please use bus_type methods
Driver 'sr' needs updating - please use bus_type methods
ata_piix 0000:00:1f.1: version 2.12
...
microcode: CPU7 updated from revision 0x0 to 0xa07, date = 04092008 
p4-clockmod: Unknown p4-clockmod-capable CPU. Please send an e-mail to <cpufreq@vger.kernel.org>
...
Bluetooth: SCO socket layer initialized
mtrr: type mismatch for d8000000,2000000 old: write-back new: write-combining
eth0: no IPv6 routers present

(the full dmesg output is attached).
I don't know where to start looking at. Does anybody have an idea?
Tell me if you need that I cat some "proc" or "sys" files.

One last precision, I've updated the DELL BIOS, I will see if there's an update for the TYAN one.

Thank you

business_kid · 04-20-2009, 03:21 PM

I would get on somehow and look at a successful boot in /var/log/messages and then look at the reboot in the same log. What's going to happen next when the problem starts?

Just FYI, some 64 bit motherboards in my job won't boot if anything is plugged into the usb bus. If you think your installation is clean, get a POST card and try that (Power On Self Test) It will stick on a number like 85. You look up 85 in your bios and it might say "Going off to play with the hard drives. . . " which at least gives a clue.

BTW, the stock kernel doesn' seem to suit your box. Better roll your own. One size does not always fit all.

jf.argentino · 04-21-2009, 11:43 AM

Quote:

What's going to happen next when the problem starts?

Not sure to understand your question, but after hanging, if I power-down then power up again, it there's no problem, I'll do a dmesg / /var/log/message with a "normal" boot, and a boot after a hang to see if there's a difference...

Quote:

some 64 bit motherboards in my job won't boot if anything is plugged into the usb bus

My "reboot" problem is systematic, and I just test it with a PS2 keyboard (so no more USB peripherals), and same result... I precise it again (maybe it wasn't clear enough in my first post), the problem append only for software reboot. If I shutdown, then power up, it always run fine.

Quote:

BTW, the stock kernel doesn' seem to suit your box. Better roll your own

I'll try that ASAP.
I just try to reboot during the grub menu displaying by pressing CTRL+ALT+DEL and same result.
I precise that I'm using a 32bits distribution...

jf.argentino · 04-22-2009, 05:23 AM

I've just updated the BIOS and now the tyan one reboot.

business_kid · 04-23-2009, 11:38 AM

Quote:

Originally Posted by jf.argentino

I've just updated the BIOS and now the tyan one reboot.

Glad to hear it.

There's some kernel option about not using some low memory. Certain BIOS screw it up. May be worth a look