9.04 amd64 keeps rebooting on Amilo Pi 3525

[tnttrx]

OS: kubuntu 9.04
laptop: FJS Amilo Pi 3525
cpu: Intel P7350
chipset: Intel GM45
ram: 4GB DDR2 800MHz
hdd: WD Scorpio Blue 250GB
lan: Realtek RTL8101E/8102E

First reboot happened on time-zone choosing screen during first installation attempt.
Second reboot happened on username/password choosing screen during second installation attempt.
I've managed to install system from third installation attempt, but now I'm getting random reboots without any error messages: sometimes it reboots during the boot sequence, sometimes it runs for 15 or 20 minutes and reboots while it's idle.

My guess it's RTL8101E/8102E related (it's using r8169 driver).

Further information:
http://ubuntuforums.org/showthread.php?t=1137153

===========================
===========================

the situation is developing, but there's still no clear answer:
http://forum.de.ts.fujitsu.com/forum/viewtopic.php?f=90&t=39045

citation by neolojik from that tread:
=====================================
From my testing I found that I could reliably run a 64bit version of Linux either of these ways:
1) Booting with mem=4096m. This unfortunately causes the loss of the final 1GB of RAM which is allocated just after the 4GB boundary.
2) Booting with acpi=off. This disables all power saving and the ability to access thermal data, battery information and throttle the CPU. You can access all 4GB of RAM though.
3) Booting normally, but prevent the "processor" and "thermal" modules from loading. This leaves you with a half-working ACPI interface. You can access all ACPI information except for temperature data and CPU data. CPU throttling doesn't work.
Perhaps the issue does lie with the Realtek card, I don't know and I don't have any way to try and find out. Unfortunately I believe the only way to be certain would be for Fujitsu to fix it (which seems unlikely), for someone to physically remove the device from the motherboard (voiding their warranty, and likely damaging their motherboard in the process) or to disable it via the BIOS (which isn't possible as most of the options are hidden). I have looked into editing the BIOS but the Pi 3525 doesn't actually have a BIOS in the traditional sense.
The BIOS (or rather, firmware) is called Phoenix SecureCore which is actually based on UEFI (Unified Extensible Firmware Interface). UEFI / EFI is the new generation of firmware which solves a lot of old legacy problems. Going into further details would be a bit beyond the scope of this post, but google is your friend if you want to know more.
Regardless, the Phoenix BIOS editor won't open this new type of firmware so we can't un-hide all the hidden options. Unfortunately I know of no other way to hide a device from the Linux kernel.
As I said though; I'm happy with a PAE enabled 32bit kernel. Everything seems to be working just fine and I can access the full 4GB of RAM (minus the 32MB of GFX memory of course). 64bit has no benefit for me.
Though I do hope that Fujitsu change their minds and correct the problem.
=====================================

so, I guess I'll have to find out is it better to run 32-bit Linux with 4GB of RAM or 64-bit Linux with 3GB of RAM... :(

[tnttrx (trx-lists)]

seems it was BIOS-related bug:
http://forum.de.ts.fujitsu.com/forum/viewtopic.php?f=90&t=39045

update to BIOS version 1.10C solved the problem for me and majority users.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
I mark this as invalid because is due to a bios issue.
:)Fabio

[Ivan Zakharyaschev (imz)]

I'm having a similar problem (on a different computer: Samsung R510; with the same CPU: Intel P7350): http://ubuntuforums.org/showthread.php?t=1137153.

Mine network adapters are different, so that's not the cause:

$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07)
00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03)
00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03)
00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03)
00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03)
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03)
00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03)
00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03)
00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03)
00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03)
00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03)
00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93)
00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03)
00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03)
00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03)
01:00.0 VGA compatible controller: NVIDIA Corporation G98M [GeForce 9200M GS] (rev a1)
02:00.0 Network controller: Intel Corporation WiFi Link 5100
06:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 13)
$

I've noticed, too, that not loading the coretemp module (related to temperature) makes the boot more stable (but not completely).

I'll have to see whether there some updates fro my BIOS available.