at boot get piix4_smbus error, Ubuntu installed in VirtualBox

Bug #642801 reported by Pol_
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Low
Unassigned

Bug Description

Binary package hint: debian-installer

at very first live CD boot I get a "piix4_smbus [...] smbus have address unintialized - upgrade BIOS or use force_addr=0xaddr" error.
Then after the first reboot it disappears.

Ubuntu 10.10 is the beta made available around August the 31st. It is installed in a VIrtual Box 3.2.6 OSE r63112 (latest from PPA at that time).

Only non-conventional Guest installation I did was to disable the VT-x/AMD-V functionality.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: debian-installer (not installed)
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic i686
Architecture: i386
Date: Sun Sep 19 15:32:55 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
MemoryUsage:
 total used free shared buffers cached
 Mem: 1025720 395568 630152 0 33580 196272
 -/+ buffers/cache: 165716 860004
 Swap: 305148 0 305148
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=7f35e3bf-3eae-4290-a029-0790ec7ef8bc ro quiet splash
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: debian-installer
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Pol_ (paulemile-purnelle) wrote :
Revision history for this message
Pol_ (paulemile-purnelle) wrote :
Revision history for this message
Pol_ (paulemile-purnelle) wrote :

update : I still have the error on any boot. It is just faster to disappear from screen.

Colin Watson (cjwatson)
affects: debian-installer (Ubuntu) → linux (Ubuntu)
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Pol_,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Pol_ (paulemile-purnelle) wrote :

I patched with the latest mainline build (September 29th) and still have the issue. I even have 3 more errors showing on screen at start-up now. Screen-shot to follow

Revision history for this message
Pol_ (paulemile-purnelle) wrote :

here is the version I used for the screen-shot

pol@pol-desktop:~$ uname -a
Linux pol-desktop 2.6.36-020636rc6-generic #201009291126 SMP Wed Sep 29 12:42:36 UTC 2010 i686 GNU/Linux

tags: removed: needs-upstream-testing
summary: - at live CD boot and the first boot after installation I get piix4_smbus
- error, then never anymore
+ at boot get piix4_smbus error, Ubuntu installed in VirtualBox
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
RuiDC (ruidc) wrote :

problem hasn't gone away

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Verified in Trusty in live environment via Trusty. The message is largely innocuous, as I've seen this in every version of VirtualBox available in a Ubuntu host, with every version of Ubuntu as a guest since Maverick. It would be nice if the message either wouldn't appear at all during boot, or whatever it's complaining about is dealt with.

lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04

apt-cache policy virtualbox
virtualbox:
  Installed: 4.2.16-dfsg-3ubuntu1
  Candidate: 4.2.16-dfsg-3ubuntu1
  Version table:
 *** 4.2.16-dfsg-3ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages
        100 /var/lib/dpkg/status

tags: added: trusty
tags: added: biot-stop-nagging
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
penalvch (penalvch)
tags: added: bot-stop-nagging
removed: biot-stop-nagging
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.