You are not logged in.

#1 2012-09-01 00:25:48

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

dmesg: klogctl failed: Bad address

I'm trying to troubleshoot another problem and am getting the subject line message when I type dmesg.
Yes, under systemd.

Last edited by nomorewindows (2012-09-01 00:33:22)


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#2 2012-09-01 01:07:49

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,097
Website

Re: dmesg: klogctl failed: Bad address

nomorewindows wrote:

I'm trying to troubleshoot another problem and am getting the subject line message when I type dmesg.

A stack trace with debug symbols might be a good start if you expect anyone to know what's going on.

Offline

#3 2012-09-01 03:52:19

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: dmesg: klogctl failed: Bad address

gdb dmesg
(gdb) run
Starting program: /bin/dmesg
warning: Could not load shared library symbols for linux-gate.so.1
Do you need "set solib-search-path" or "set sysroot"?
dmesg: klogctl failed: Bad address


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#4 2012-09-01 04:04:58

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,097
Website

Re: dmesg: klogctl failed: Bad address

Reinstall util-linux. If you don't even get anything resembling a trace, it might just be a bad binary. klogctl isnt' even supposed to return EFAULT.

Last edited by falconindy (2012-09-01 04:06:01)

Offline

#5 2012-09-01 04:16:38

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: dmesg: klogctl failed: Bad address

Reinstalled, no change.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#6 2012-09-01 04:25:31

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,097
Website

Re: dmesg: klogctl failed: Bad address

So what is this "other problem"? What kernel are you running?

Offline

#7 2012-09-01 04:43:17

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: dmesg: klogctl failed: Bad address

I had a problem with OSS, downgraded it to most previous OSS, and got it to working again when I noticed it.  It wouldn't complie modules for my audio hardware.  dmesg also faults when starting/stopping OSS.  OSS was updated with the most recent kernel.  Most recent OSS works ok with linux-lts, but not with current linux kernel.  Strange.

Last edited by nomorewindows (2012-09-01 04:44:11)


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#8 2012-09-15 16:09:36

eric
Member
From: under heaven
Registered: 2004-02-11
Posts: 113

Re: dmesg: klogctl failed: Bad address

Is there more info about this, or maybe a fix?

I have the same problem, but only after an uptime of > 6 days... yesterday it was till working.
This happens with Btrfs and kernel-3.6.0-rc4.

I don't know if this has something to do with the failure of the dmesg command, but since a week I am using a wireless wifi usb (with Realtek 8192cu chip) that is spamming the logfile. The wifi is entering and leaving powersave mode every minute and each time it adds 4 lines to the logfile, so the dmesg output has become very big.

Offline

#9 2012-09-16 01:47:41

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: dmesg: klogctl failed: Bad address

Today there was an update to OSS 4.2-2007-1, it appears to still be working.  However, I've probably rebooted since the time that I've first posted this, but the dmesg problem still exists.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#10 2012-09-18 11:05:25

Da_Coynul
Member
From: United States of America
Registered: 2010-10-02
Posts: 80

Re: dmesg: klogctl failed: Bad address

Same problem here using 3.5.3-1-ARCH with systemd.  I am not using OSS or wireless on this box.  Like eric, I am seeing this after several days of uptime.

Offline

#11 2012-09-18 22:37:00

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: dmesg: klogctl failed: Bad address

Huh? 
cat /var/log/dmesg.log starts with kernel 3.4.4-3 not 3.5.3-1.
Whatever runs dmesg isn't reporting anymore.
stat /var/log/dmesg.log gives a date back in July, probably about the time that 3.4.4-3 was last in use.  Yep, checked /var/log/pacman.log and 3.4.4-3 was installed in July, so something changed after this kernel.  Had systemd in June, and probably started using it about that time, so it was before 3.4.4-3 that I had systemd.
I know I booted that kernel to test if the tuner card was working yet.  Don't think I was using that kernel extensively though, can't remember.  Had to use the 2.6.35 kernel just to use the radio part of the tuner.  Systemd would not work with the 2.6 kernel.
Linux-3.5.4-1 incoming, don't think it'll change with the finding that the last record comes from the 3.4 kernel.

Last edited by nomorewindows (2012-09-18 22:44:17)


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#12 2012-09-19 17:23:38

nomorewindows
Member
Registered: 2010-04-03
Posts: 3,015

Re: dmesg: klogctl failed: Bad address

With the linux update to 3.5.4-1, dmesg seems to accidently be working now.  At least, since I've rebooted.


I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.

Offline

#13 2012-09-22 17:53:26

Da_Coynul
Member
From: United States of America
Registered: 2010-10-02
Posts: 80

Re: dmesg: klogctl failed: Bad address

This is not fixed with the latest kernel update, but you can use:

#dmesg -C

as a temporary fix until the next dmesg: klogctl failed: Operation not permitted.

Offline

#14 2012-09-23 12:50:02

eric
Member
From: under heaven
Registered: 2004-02-11
Posts: 113

Re: dmesg: klogctl failed: Bad address

I've just rebooted and dmesg is working again.
Everything about the computer is still the same except a newer version of qt, but I don't think that has anything to do with this.

Thanks for the tip, I will try 'dmesg -C' when I need it.

-- Edit 2012-0930:

My uptime is at 6 days again, just like in my first post, but this time dmesg is working as expected (without -C).
The only change I've made are a newer version of Qt and a different wireless USB adapter. The old wireless USB adapter was spamming dmesg with 4 new lines every 90 seconds (for 6 days).
So maybe dmesg stopped working because it was 'full'?

Last edited by eric (2012-09-30 12:15:00)

Offline

Board footer

Powered by FluxBB