LSPCI:
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
00:01.0 PCI bridge: Acer Incorporated [ALI] Device 9602
00:04.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0)
00:05.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1)
00:11.0 SATA controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:12.2 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
00:13.2 USB Controller: ATI Technologies Inc SB7x0/SB8x0/SB9x0 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 41)
00:14.1 IDE interface: ATI Technologies Inc SB7x0/SB8x0/SB9x0 IDE Controller (rev 40)
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40)
00:14.3 ISA bridge: ATI Technologies Inc SB7x0/SB8x0/SB9x0 LPC host controller (rev 40)
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge (rev 40)
00:18.0 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] Family 10h Processor Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc M880G [Mobility Radeon HD 4200]
01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200]
03:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe (rev 01)
06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)

The above conflict in dmesg was generated by the Slackware64 2.6.37.6 kernel with the following append statement in LILO:

append="vt.default_utf8=0 pci=nobios pci=nomsi pcie_pme=nomsi pnpbios=off ecrc=off i8042.nopnp libata.ignore_hpa=1 memory_corruption_check=1 pci=usepirqmask"

I had the same exact conflict message with the new kernel 2.6.38.6 with "make oldconfig" (i.e. same config as "generic" on Slackware64 13.37).

I booted this time with i2c_piix4 blacklisted and so far the machine seems stable (but I will report back if I run into any problems).

I am more than willing to test any options and/or code you have for me, even if it means copying down the firmware on all my devices.

I am going to try Slackware (32bit) 13.37 soon and report back with the dmesg (memory map mainly) and any conflict messages from that kernel as well.  Thanks for your patience!

OK on the new 2.6.38.6 kernel it worked fine until I suspended it.  Upon resume, the screen was white and unresponsive.  Pressing the power button for a split second resulted in an orderly clean shutdown, so the problem didn't cause a kernel panic.  On this new kernel I have never specified any LILO append options.

Kernel config for Slackware64's generic SMP kernel can be found at: ftp://ftp.slackware.com/pub/slackware/slackware64-13.37/source/k/config-generic-2.6.37.6 and the one I am now running is http://www.puresimplicity.net/~delahunt/linux/acer/config.

I will try to provide dmesg memory mapping information when specifying pci=bios and pci=nobios to hopefully give good info about what the BIOS and what the devices want for their memory mappings to see if there is a disagreement.

OK, here are the memory mappings from dmesg:

Generic 64 bit kernel, "pci=bios"
http://www.puresimplicity.net/~delahunt/linux/acer/dmesg64-pcibios.txt

Generic 64 bit kernel, "pci=direct"
http://www.puresimplicity.net/~delahunt/linux/acer/dmesg64-pcidirect.txt

Generic 32 bit kernel, "pci=bios"
http://www.puresimplicity.net/~delahunt/linux/acer/dmesg-pcibios.txt

Generic 32 bit kernel, "pci=direct"
http://www.puresimplicity.net/~delahunt/linux/acer/dmesg-pcidirect.txt

Generic 64 bit kernel "make oldconfig" for 2.6.38.6 (going with default option on all except those with module option, for which I chose module) without any LILO append statement:
http://www.puresimplicity.net/~delahunt/linux/acer/dmesg64-test.txt

I hope the memory mappings prove useful.  Of the above, the Generic kernel images were loaded with /etc/modprobe.d/radeon.conf specifying no i2c and with i2c_piix4 blacklisted.  The last one ("test") I loaded without specifying that option and without blacklisting the module.

This may be a dumb question but I'm seeing that modesetting is the "NEW DRIVER" in the kernel config.  Slackware 13.37 should have sufficient userspace for it, but the help in the kernel says "work is under way for...." and lists my card (HD 4xxxx series).  Is work still under way?  Should I revert to non-modesetting?  The only real recent info is the ArchLinux wiki page, which recommends KMS disabled if one runs into problems, so I'll try that....

> OK on the new 2.6.38.6 kernel it worked fine until I suspended it.

so we can ignore the original sighting of the hard-lock-ups,
and now this bug is about resume from suspend resulting in a white screen?

As the system seems to have resumed, but the screen was white,
that would be a bug in the video driver.

Is this still an issue with a 3.0 kernel?

It's great that the kernel bugzilla is back.

Can you please verify if the problem still exists in the latest upstream
kernel?

> I can't verify it, as I gave away this computer.  I am sorry.

Get it. I'll close this bug.
please feel free to reopen it in case you can reproduce the problem again.