[PLUG] boot failures

[Denis Heidtmann]

(Resend.  Wednesday's send did not get through.)

Occasionally when I boot my machine it hangs at the Ubuntu screen.  Pressing
the power button is the only cure.  Restarting usually goes fine.
 Sometimes there is an on-screen message which goes much too fast to read.
 I managed to take a video of the screen once when this occurred.  When I
get the failure,  I get the usual startup message: Boot from hd0.0 ext3 ...
 That stays on the screen for what seems like an unusually long time, then
the message "...nForce2_Smbus 0000:00:01.1: Error probing SMB2.  Starting up
..." appeared.

I looked in the dmesg for this, and I find:
...
[   27.564121] udev: starting version 151
[   27.568555] Adding 5574512k swap on /dev/sda5.  Priority:-1 extents:1
across:5574512k
[   27.667831] EDAC MC: Ver: 2.1.0 Jun  3 2010
[   27.706474] i2c i2c-0: nForce2 SMBus adapter at 0x600
[   27.706480] ACPI: resource nForce2_smbus [0x700-0x73f] conflicts with
ACPI region SM00 [0x700-0x73f]
[   27.706482] ACPI: If an ACPI driver is available for this device, you
should use it instead of the native driver
[   27.706485] nForce2_smbus 0000:00:01.1: Error probing SMB2.
[   27.712505] lp: driver loaded but no devices found
[   27.727096] k8temp 0000:00:18.3: Temperature readouts might be wrong -
check erratum #141
[   27.727199] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[   27.843374] EDAC amd64_edac:  Ver: 3.2.0 Jun  3 2010
[   27.857388] type=1505 audit(1276142598.664:2):  operation="profile_load"
pid=639 name="/sbin/dhclient3"
[   27.857623] type=1505 audit(1276142598.664:3):  operation="profile_load"
pid=639 name="/usr/lib/NetworkManager/nm-dhcp-client.action"
[   27.857754] type=1505 audit(1276142598.664:4):  operation="profile_load"
pid=639 name="/usr/lib/connman/scripts/dhclient-script"
[   27.861785] [Firmware Bug]: ACPI(IGPU) defines _DOD but not _DOS
[   27.862064] input: Video Bus as
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:11/LNXVIDEO:00/input/input5
...

This error message appears in dmesg every time, with and without the
failure, so it may be unrelated.

Ideas?

Thanks,
-Denis