Mailinglist Archive: opensuse-bugs (12986 mails)

< Previous Next >
[Bug 436895] Samsung R510 reboots on x86_64 - disabling ACPI components or mem=4GB helps
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 15 Jan 2009 09:39:21 -0700 (MST)
  • Message-id: <20090115163921.96277245390@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=436895

User trenn@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=436895#c39


Thomas Renninger <trenn@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |acpi@xxxxxxxxxxxxxxx,
| |andi-nbz@xxxxxxxxxxxxxx
Summary|Samsung R510 boot only |Samsung R510 reboots on
|Acpi=off |x86_64 - disabling ACPI
| |components or mem=4GB helps




--- Comment #39 from Thomas Renninger <trenn@xxxxxxxxxx> 2009-01-15 09:39:20
MST ---
This looks like a memory corruption or say memory setup problem, not an ACPI
problem.

Summary:
- x86_64 is broken, i386 works fine
- booting without any acpi modules loaded into single user mode only works
with pci=noacpi. Without the boot param -> reboot
- Booted into single user mode loading a specific acpi module -> reboot
- As pci=noacpi and the processor or thermal module do not have to do with
each other much, it looks like specific ACPI mem accesses trigger this,
especially because:
- mem=4GB works, but restricts the system to 3GB, instead of 4GB installed
mem
- The FADT's 64 bit addresses also have a problem. Disassembling the table
shows: "Invalid zero length subtable" messages in FACP1.dsl. But not using
them (taking the rsdt table) does change some behaviour, but do not fix the
reboot issue.

It is a hard reboot.
It looks like if ACPI pokes on specific memory addresses which trigger the hard
reboot.

From dmesg:
this already looks very suspicious:
Phoenix BIOS detected: BIOS may corrupt low RAM, working it around.

Maybe it's the PATables being wrong or wrongly setup?
Anyway, I can't fix this. Someone with more memory knowledge is needed. As this
is an Intel machine, CC'ing some Intel people, maybe someone already sees
something in dmesg output from comment #35

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >