You are not logged in.

#1 2007-06-26 08:41:00

cry0x
Member
Registered: 2007-04-11
Posts: 91

dmesg displaying during boot

I've been running Arch for a while now, about two years. Around a month ago I got a Macbook, so I've installed Arch onto it (naturally.)

I have an issue... mostly a pet-peeve, but I've never seen it on any of my other systems. During the startup, right after Arch begins to load modules and before (and during) starting daemons, bits of my dmesg start to display between the lines. More or less (this isn't verbatim, I'm simply pasting a random portion of dmesg as an example) it looks like this:

Loading Modules                               [done]
applesmc:  - Model with accelerometer
applesmc:  - Model without light sensors and backlight
applesmc:  - Model with 12 temperature sensors
applesmc: accelerometer successfully initialized.
applesmc: device successfully initialized.
applesmc: 1 fans found.
input: applesmc as /class/input/input5
applesmc: driver successfully loaded.
ACPI: SSDT 7EEB8C90, 022A (r1 APPLE   Cpu0Ist     3000 INTL 20050309)
ACPI: SSDT 7EEB7C10, 02A0 (r1 APPLE   Cpu0Cst     3001 INTL 20050309)
Monitor-Mwait will be used to enter C-1 state
Monitor-Mwait will be used to enter C-2 state
Loading Network                                  [done]
BUG: at kernel/mutex.c:311 __mutex_trylock_slowpath()
[<c03405e6>] mutex_trylock+0xd6/0x140
[<f8f2045d>] applesmc_mousedev_poll+0xd/0xe0 [applesmc]
[<c01307e3>] run_timer_softirq+0x143/0x1b0
[<f8f20450>] applesmc_mousedev_poll+0x0/0xe0 [applesmc]
[<c012c9b5>] __do_softirq+0x75/0xe0
[<c012ca57>] do_softirq+0x37/0x40
[<c012ccb9>] irq_exit+0x79/0x90
[<c0106e30>] do_IRQ+0x40/0x70
[<c0104cef>] common_interrupt+0x23/0x28
[<f8f3b95a>] acpi_processor_idle+0x210/0x3b2 [processor]
[<c010242d>] cpu_idle+0x7d/0xe0
[<c0407b05>] start_kernel+0x405/0x4b0
[<c0407230>] unknown_bootoption+0x0/0x260
Patching the VBIOS                            [done]


Why would this be happening? If you need more information about my setup, let me know.
Thanks in advance.


Who is this doin' this synthetic type of alpha beta psychedelic funkin'?

Offline

#2 2007-06-26 19:00:44

ataraxia
Member
From: Pittsburgh
Registered: 2007-05-06
Posts: 1,537

Re: dmesg displaying during boot

Looks like the applesmc module produces output when loaded, and also, that it's buggy enough to throw errors a few seconds later.

Offline

#3 2007-06-26 19:14:56

tardo
Member
Registered: 2006-07-15
Posts: 526

Re: dmesg displaying during boot

add quiet to your kernel line in your grub config... if it isn't there already.

Offline

#4 2007-06-26 22:21:18

cry0x
Member
Registered: 2007-04-11
Posts: 91

Re: dmesg displaying during boot

tardo wrote:

add quiet to your kernel line in your grub config... if it isn't there already.

Thankyou for the suggestion, but it appears that applesmc is causing it. If I don't add it to the modules array in rc.conf and modprobe by hand or rc.local, it does not make my console go FUBAR smile


Who is this doin' this synthetic type of alpha beta psychedelic funkin'?

Offline

#5 2008-05-20 17:18:56

sands
Member
Registered: 2008-05-19
Posts: 10

Re: dmesg displaying during boot

I am also getting those errors (in var/log/somefile).. Inorder to load applesmc in ubuntu it took something like 1sec. Here it is taking around 10secs..
It seems that applesmc module, is looking for all the apple devices, some of them are not even present.
Is there some way to configure applesmc to search for only specific devices?

Offline

#6 2008-05-20 22:40:06

phrakture
Arch Overlord
From: behind you
Registered: 2003-10-29
Posts: 7,879
Website

Re: dmesg displaying during boot

Um, that's a kernel bug. Please report it to the module maintainer.

Offline

#7 2008-05-20 23:30:39

sands
Member
Registered: 2008-05-19
Posts: 10

Re: dmesg displaying during boot

I compiled the kernel myself and installed it. Now, it is not taking that much time and I don't see the error messages too..
By the way, what is the use of compiling a kernel ourself?
Does this produce the kernel based on the sys config? like creating only required drivers stuff, instead of creating a generalized one.

Offline

Board footer

Powered by FluxBB