LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware Current Mystery Boot Messages (https://www.linuxquestions.org/questions/slackware-14/slackware-current-mystery-boot-messages-685810/)

Woodsman 11-24-2008 03:09 PM
Slackware Current Mystery Boot Messages
 
This past weekend I spent significant time with Slackware Current. I installed Current in both my testing partitions and in a VirtualBox 1.6.6 machine. The former is an update process, the latter is a fresh installation.

After updating and installing I noticed several odd messages during booting with the huge kernel that I never previously had seen.

VirtualBox Current
1. request region #1
2. i2c_core: exports duplicate symbol i2c_smbus_xfer (owned by kernel)
3. piix4_smbus 0000:00:07.0: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr
4. Error: Driver 'isp1760' is already registered, aborting . . .

Non Virtual (Real) Current
2. i2c_core: exports duplicate symbol i2c_smbus_xfer (owned by kernel)
4. Error: Driver 'isp1760' is already registered, aborting . . .
5. memory length for this resource is less than required

In both systems I eliminated mystery messages 1, 2, 4, and 5 by disabling the CONFIG_USB_ISP1760_HCD USB Host Controller Driver kernel option and recompiling.

Edit: Disabling ACPI in the virtual machine configuration disables all four messages. Leaving ACPI support enabled but adding acpi=off as a boot loader option in the virtual machine does not disable the messages and NFS hangs forever.

Edit: Adding acpi=off in the non virtual (real) machine boot loader option does not disable the messages.

I am unable to eliminate mystery message 3, which appears only in the virtual machine. The message is part of the dmesg dump.

I ran lspci in the virtual machine and there is a PIIX4 controller listed (last item):

Code:
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter
00:03.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 40)
00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service
00:05.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 01)
00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
I have the VirtualBox machine configured to use the PIIX3 controller for the hard drive. I'm unsure where the PIIX4 controller is getting configured. (Edit: I discovered that the PIIX4 controller is created when the VM is configured to start with ACPI enabled.)

The mystery messages appear harmless, but like many mystery messages, curiosity reigns. After much web surfing to investigate, I still do not understand how to remedy this problem. Why are this messages appearing now and never previously? When I last tested Current the kernel version was 2.6.24.7, not 2.6.27.7. The messages never appeared then. Is there an easy fix?

Thanks again.

SqdnGuns 11-26-2008 12:08 AM
Thanks for your updates Woodsman.

I don't have a clue but this may stick in my brain housing group for future reference.

Jeebizz 11-26-2008 11:49 AM
I wonder if these messages appear in a non-emulated enviornment? If so then you should also maybe give a heads up to Pat about this. I wish I could give out more advice.

Woodsman 11-26-2008 02:01 PM
Quote:
I wonder if these messages appear in a non-emulated enviornment? If so then you should also maybe give a heads up to Pat about this. I wish I could give out more advice.
I updated my original post to reflect that the messages appear in the non-emulated environment and adding acpi=off as a boot loader option does not eliminate the messages. The only way I eliminate the messages in the real environment is to disable the CONFIG_USB_ISP1760_HCD USB Host Controller Driver kernel option and recompile.

I will notify Pat but I prefer to obtain useful feedback from some other Slackers here in this thread before bothering him. Normally I don't like to forward potential bug reports unless I have a clue about the cause and even better, a solution.

I ask anybody on the development team to take a look at this. I'm available to help troubleshoot and test. As I wrote previously, the messages all appear to be harmless, but they are annoying. I suspect many people will ask what these messages mean. I don't know.


All times are GMT -5. The time now is 05:15 AM.