/var/log/messages, kernel messages, what is this ?
Hi All, In my /var/log/messages, these messages keeps appearing: Sep 30 18:01:18 SoliD kernel: b5:ad:12:d9:3f:d5:a3:9a:c1:d9:b2:fb:e0:a8:ab:bb: Sep 30 18:01:18 SoliD kernel: 28:5d:d1:4e:56:0c:da:4d: Sep 30 18:01:18 SoliD kernel: bc:19:d7:53:bd:db:92:53: Sep 30 18:01:18 SoliD kernel: ab:21:40:9d:be:b2:17:91:bc:99:88:ef:e8:23:99:f7: Sep 30 18:01:18 SoliD kernel: e8:09:71:33:8f:94:b4:76: Sep 30 18:01:18 SoliD kernel: 6f:34:4e:e7:a7:60:36:59: Sep 30 18:01:56 SoliD kernel: fb:00:34:29:17:9d:b2:15:ff:20:dd:dc:06:10:b5:93: Sep 30 18:01:56 SoliD kernel: c1:29:be:e7:4a:de:d2:4e: Sep 30 18:01:56 SoliD kernel: 72:98:6c:b8:14:a6:44:17: almost twice every minute, 3-8 messages per second. There seems to be no pattern in the messages. What could be causing this, and what does these messages really tell ?
On Saturday 30 September 2006 12:27, Sylvester Lykkehus wrote:
Hi All,
In my /var/log/messages, these messages keeps appearing: Sep 30 18:01:18 SoliD kernel: b5:ad:12:d9:3f:d5:a3:9a:c1:d9:b2:fb:e0:a8:ab:bb: Sep 30 18:01:18 SoliD kernel: 28:5d:d1:4e:56:0c:da:4d: Sep 30 18:01:18 SoliD kernel: bc:19:d7:53:bd:db:92:53: Sep 30 18:01:18 SoliD kernel: ab:21:40:9d:be:b2:17:91:bc:99:88:ef:e8:23:99:f7: Sep 30 18:01:18 SoliD kernel: e8:09:71:33:8f:94:b4:76: Sep 30 18:01:18 SoliD kernel: 6f:34:4e:e7:a7:60:36:59: Sep 30 18:01:56 SoliD kernel: fb:00:34:29:17:9d:b2:15:ff:20:dd:dc:06:10:b5:93: Sep 30 18:01:56 SoliD kernel: c1:29:be:e7:4a:de:d2:4e: Sep 30 18:01:56 SoliD kernel: 72:98:6c:b8:14:a6:44:17:
almost twice every minute, 3-8 messages per second. There seems to be no pattern in the messages.
What could be causing this, and what does these messages really tell ?
Hi Sylvester, If you haven't done so, already, you might also want to check the list for the group that maintains your kernel. A little Google research leads me to believe it's been customized/optimized for solid modeling (MCAD). It isn't 'stock' SUSE and I've never seen it discussed here before, so you might have better luck if you broaden your inquiry. regards, Carl
Carl Hartung wrote:
Hi Sylvester,
If you haven't done so, already, you might also want to check the list for the group that maintains your kernel. A little Google research leads me to believe it's been customized/optimized for solid modeling (MCAD). It isn't 'stock' SUSE and I've never seen it discussed here before, so you might have better luck if you broaden your inquiry.
regards,
Carl
Hi Carl, The kernel is a 'stock' SUSE kernel (2.6.13-15.11-default) on SUSE 10.0. Sorry if the name 'SoliD' mislead you, it is actually just the hostname of the machine, which appears in the logs ;) //Sylvester
On Saturday 30 September 2006 13:18, Sylvester Lykkehus wrote:
The kernel is a 'stock' SUSE kernel (2.6.13-15.11-default) on SUSE 10.0. Sorry if the name 'SoliD' mislead you, it is actually just the hostname of the machine, which appears in the logs ;)
How funny! There /are/ specialized MCAD kernels out there with comparable names, so... learn something new everyday, eh? There aren't any 'whirring' or 'clicking' noises accompanying those messages, are there?... from inside the box? ;-) Carl
Carl Hartung wrote:
On Saturday 30 September 2006 13:18, Sylvester Lykkehus wrote:
The kernel is a 'stock' SUSE kernel (2.6.13-15.11-default) on SUSE 10.0. Sorry if the name 'SoliD' mislead you, it is actually just the hostname of the machine, which appears in the logs ;)
How funny! There /are/ specialized MCAD kernels out there with comparable names, so... learn something new everyday, eh?
There aren't any 'whirring' or 'clicking' noises accompanying those messages, are there?... from inside the box? ;-)
Carl
Hehe, indeed, woke my interest as well, had to do a google search for mcad ;) The box is some hundred kilometers away from me, so any such noises would not have alerted me. However, the last time I was at the machine, the was no whirring or clicking coming from it, though the messages still appeared. I was wondering, if loaded modules could produce this output, as I believe it started after loading a driver for a wireless NIC with a RaLink chipset on it. BR Sylvester
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2006-09-30 at 20:10 +0200, Sylvester Lykkehus wrote:
I was wondering, if loaded modules could produce this output, as I believe it started after loading a driver for a wireless NIC with a RaLink chipset on it.
Could they be mac addreses? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFHvpktTMYHG2NR9URAsOTAJ0dDy4v45bjIlOmQju7BZvb6/S7CwCeIHhk U/Us1pZAPPmG7+DSpeM7q1s= =n2hs -----END PGP SIGNATURE-----
On Sunday 01 October 2006 01:14, Carlos E. R. wrote:
The Saturday 2006-09-30 at 20:10 +0200, Sylvester Lykkehus wrote:
I was wondering, if loaded modules could produce this output, as I believe it started after loading a driver for a wireless NIC with a RaLink chipset on it.
Could they be mac addreses?
I thought so too, but mac addresses are 6 bytes long; his log shows 8- and 16-byte sequences. Cheers Leen
On Saturday 30 September 2006 20:24, Leendert Meyer wrote:
On Sunday 01 October 2006 01:14, Carlos E. R. wrote:
The Saturday 2006-09-30 at 20:10 +0200, Sylvester Lykkehus wrote:
I was wondering, if loaded modules could produce this output, as I believe it started after loading a driver for a wireless NIC with a RaLink chipset on it.
Could they be mac addreses?
I thought so too, but mac addresses are 6 bytes long; his log shows 8- and 16-byte sequences.
The sequence posted showed a 16 -> 8 -> 8 pattern, i.e.: Sep 30 18:01:18 SoliD kernel: b5:ad:12:d9:3f:d5:a3:9a:c1:d9:b2:fb:e0:a8:ab:bb: Sep 30 18:01:18 SoliD kernel: 28:5d:d1:4e:56:0c:da:4d: Sep 30 18:01:18 SoliD kernel: bc:19:d7:53:bd:db:92:53: Sep 30 18:01:18 SoliD kernel: ab:21:40:9d:be:b2:17:91:bc:99:88:ef:e8:23:99:f7: Sep 30 18:01:18 SoliD kernel: e8:09:71:33:8f:94:b4:76: Sep 30 18:01:18 SoliD kernel: 6f:34:4e:e7:a7:60:36:59: Sep 30 18:01:56 SoliD kernel: fb:00:34:29:17:9d:b2:15:ff:20:dd:dc:06:10:b5:93: Sep 30 18:01:56 SoliD kernel: c1:29:be:e7:4a:de:d2:4e: Sep 30 18:01:56 SoliD kernel: 72:98:6c:b8:14:a6:44:17: Sylvester, have you tried unloading the suspect module? ('rmmod modulename') Carl
Carl Hartung wrote:
On Saturday 30 September 2006 20:24, Leendert Meyer wrote:
On Sunday 01 October 2006 01:14, Carlos E. R. wrote:
The Saturday 2006-09-30 at 20:10 +0200, Sylvester Lykkehus wrote:
I was wondering, if loaded modules could produce this output, as I believe it started after loading a driver for a wireless NIC with a RaLink chipset on it.
Could they be mac addreses?
I thought so too, but mac addresses are 6 bytes long; his log shows 8- and 16-byte sequences.
The sequence posted showed a 16 -> 8 -> 8 pattern, i.e.:
Sep 30 18:01:18 SoliD kernel: b5:ad:12:d9:3f:d5:a3:9a:c1:d9:b2:fb:e0:a8:ab:bb: Sep 30 18:01:18 SoliD kernel: 28:5d:d1:4e:56:0c:da:4d: Sep 30 18:01:18 SoliD kernel: bc:19:d7:53:bd:db:92:53: Sep 30 18:01:18 SoliD kernel: ab:21:40:9d:be:b2:17:91:bc:99:88:ef:e8:23:99:f7: Sep 30 18:01:18 SoliD kernel: e8:09:71:33:8f:94:b4:76: Sep 30 18:01:18 SoliD kernel: 6f:34:4e:e7:a7:60:36:59: Sep 30 18:01:56 SoliD kernel: fb:00:34:29:17:9d:b2:15:ff:20:dd:dc:06:10:b5:93: Sep 30 18:01:56 SoliD kernel: c1:29:be:e7:4a:de:d2:4e: Sep 30 18:01:56 SoliD kernel: 72:98:6c:b8:14:a6:44:17:
Sylvester, have you tried unloading the suspect module? ('rmmod modulename')
Carl
I would be happy to try that, unfortunately, as posted earlier, the box is some hundreds kilometers away from me, and the module is to the only NIC attached to the machine ;) I have to wait until the next time i go visit it. BR Sylvester
On Sat, 2006-09-30 at 20:10 +0200, Sylvester Lykkehus wrote:
I was wondering, if loaded modules could produce this output, as I believe it started after loading a driver for a wireless NIC with a RaLink chipset on it.
Anything inside the kernel that calls "printk" can produce this output You are using the rt61 driver, right? (this is the only ralink driver I can find that prints out something like what you've posted) From looking at the source code, these are debugging prints, and it looks like they are shared encryption keys used on your wireless LAN I don't see any #ifdef's or anything else in there, so it doesn't look like they can be turned off without changing the source code
Anders Johansson wrote:
On Sat, 2006-09-30 at 20:10 +0200, Sylvester Lykkehus wrote:
I was wondering, if loaded modules could produce this output, as I believe it started after loading a driver for a wireless NIC with a RaLink chipset on it.
Anything inside the kernel that calls "printk" can produce this output
You are using the rt61 driver, right? (this is the only ralink driver I can find that prints out something like what you've posted) From looking at the source code, these are debugging prints, and it looks like they are shared encryption keys used on your wireless LAN
I don't see any #ifdef's or anything else in there, so it doesn't look like they can be turned off without changing the source code
Hi Anders, Yes, it is indeed the RT61 driver. I am currently thinking of trying ndiswrapper, instead of the driver provided by RaLink, because of instability issues ( as stated in an earlier post: http://lists.suse.com/archive/suse-linux-e/2006-Aug/4171.html ). Perhaps it will take care of both of my problems. BR Sylvester
participants (5)
-
Anders Johansson -
Carl Hartung -
Carlos E. R. -
Leendert Meyer -
Sylvester Lykkehus