LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page /var/log/syslog messages.
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 02-25-2006, 10:58 AM   #1
gbowden
Member
 
Registered: Dec 2003
Location: Spain
Distribution: Slackware 14.1 64bit - multilib
Posts: 148

Rep: Reputation: 28
/var/log/syslog messages.

Hi, I get these messages when I shutdown/restart my computer and wonder if they're anything to be worried about.

Code:
Feb 25 15:06:45 GB-NET kernel: idr_remove called for id=4 which is not allocated.
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e4c>] sub_remove+0xdd/0xe6
Feb 25 15:06:45 GB-NET kernel:  [<c01245ce>] autoremove_wake_function+0x0/0x3a
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e73>] idr_remove+0x1e/0x84
Feb 25 15:06:45 GB-NET kernel:  [<c01ed603>] release_dev+0x5a4/0x5bd
Feb 25 15:06:45 GB-NET kernel:  [<c0112d04>] __wake_up+0x14/0x1e
Feb 25 15:06:45 GB-NET kernel:  [<c01ecde3>] init_dev+0x3a9/0x4a8
Feb 25 15:06:45 GB-NET kernel:  [<c01ed7c5>] tty_open+0x1a9/0x26c
Feb 25 15:06:45 GB-NET kernel:  [<c014acf2>] chrdev_open+0xd7/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c014ac1b>] chrdev_open+0x0/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c0142e1a>] __dentry_open+0xb4/0x180
Feb 25 15:06:45 GB-NET kernel:  [<c0142fa4>] nameidata_to_filp+0x1f/0x31
Feb 25 15:06:45 GB-NET kernel:  [<c0142f19>] filp_open+0x33/0x3b
Feb 25 15:06:45 GB-NET kernel:  [<c0143049>] get_unused_fd+0x4c/0x91
Feb 25 15:06:45 GB-NET kernel:  [<c0143116>] do_sys_open+0x37/0xb0
Feb 25 15:06:45 GB-NET kernel:  [<c01431a0>] sys_open+0x11/0x15
Feb 25 15:06:45 GB-NET kernel:  [<c0102ab9>] syscall_call+0x7/0xb
Feb 25 15:06:45 GB-NET kernel: idr_remove called for id=4 which is not allocated.
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e4c>] sub_remove+0xdd/0xe6
Feb 25 15:06:45 GB-NET kernel:  [<c01245ce>] autoremove_wake_function+0x0/0x3a
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e73>] idr_remove+0x1e/0x84
Feb 25 15:06:45 GB-NET kernel:  [<c01ed603>] release_dev+0x5a4/0x5bd
Feb 25 15:06:45 GB-NET kernel:  [<c0112d04>] __wake_up+0x14/0x1e
Feb 25 15:06:45 GB-NET kernel:  [<c01ecde3>] init_dev+0x3a9/0x4a8
Feb 25 15:06:45 GB-NET kernel:  [<c01ed7c5>] tty_open+0x1a9/0x26c
Feb 25 15:06:45 GB-NET kernel:  [<c014acf2>] chrdev_open+0xd7/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c014ac1b>] chrdev_open+0x0/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c0142e1a>] __dentry_open+0xb4/0x180
Feb 25 15:06:45 GB-NET kernel:  [<c0142fa4>] nameidata_to_filp+0x1f/0x31
Feb 25 15:06:45 GB-NET kernel:  [<c0142f19>] filp_open+0x33/0x3b
Feb 25 15:06:45 GB-NET kernel:  [<c0143049>] get_unused_fd+0x4c/0x91
Feb 25 15:06:45 GB-NET kernel:  [<c0143116>] do_sys_open+0x37/0xb0
Feb 25 15:06:45 GB-NET kernel:  [<c01431a0>] sys_open+0x11/0x15
Feb 25 15:06:45 GB-NET kernel:  [<c0102ab9>] syscall_call+0x7/0xb
Feb 25 15:06:45 GB-NET kernel: idr_remove called for id=4 which is not allocated.
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e4c>] sub_remove+0xdd/0xe6
Feb 25 15:06:45 GB-NET kernel:  [<c01245ce>] autoremove_wake_function+0x0/0x3a
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e73>] idr_remove+0x1e/0x84
Feb 25 15:06:45 GB-NET kernel:  [<c01ed603>] release_dev+0x5a4/0x5bd
Feb 25 15:06:45 GB-NET kernel:  [<c0112d04>] __wake_up+0x14/0x1e
Feb 25 15:06:45 GB-NET kernel:  [<c01ecde3>] init_dev+0x3a9/0x4a8
Feb 25 15:06:45 GB-NET kernel:  [<c01ed7c5>] tty_open+0x1a9/0x26c
Feb 25 15:06:45 GB-NET kernel:  [<c014acf2>] chrdev_open+0xd7/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c014ac1b>] chrdev_open+0x0/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c0142e1a>] __dentry_open+0xb4/0x180
Feb 25 15:06:45 GB-NET kernel:  [<c0142fa4>] nameidata_to_filp+0x1f/0x31
Feb 25 15:06:45 GB-NET kernel:  [<c0142f19>] filp_open+0x33/0x3b
Feb 25 15:06:45 GB-NET kernel:  [<c0143049>] get_unused_fd+0x4c/0x91
Feb 25 15:06:45 GB-NET kernel:  [<c0143116>] do_sys_open+0x37/0xb0
Feb 25 15:06:45 GB-NET kernel:  [<c01431a0>] sys_open+0x11/0x15
Feb 25 15:06:45 GB-NET kernel:  [<c0102ab9>] syscall_call+0x7/0xb
Feb 25 15:06:45 GB-NET kernel: idr_remove called for id=4 which is not allocated.
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e4c>] sub_remove+0xdd/0xe6
Feb 25 15:06:45 GB-NET kernel:  [<c01245ce>] autoremove_wake_function+0x0/0x3a
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e73>] idr_remove+0x1e/0x84
Feb 25 15:06:45 GB-NET kernel:  [<c01ed603>] release_dev+0x5a4/0x5bd
Feb 25 15:06:45 GB-NET kernel:  [<c0112d04>] __wake_up+0x14/0x1e
Feb 25 15:06:45 GB-NET kernel:  [<c01ecde3>] init_dev+0x3a9/0x4a8
Feb 25 15:06:45 GB-NET kernel:  [<c01ed7c5>] tty_open+0x1a9/0x26c
Feb 25 15:06:45 GB-NET kernel:  [<c014acf2>] chrdev_open+0xd7/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c014ac1b>] chrdev_open+0x0/0xf0
Feb 25 15:06:45 GB-NET kernel:  [<c0142e1a>] __dentry_open+0xb4/0x180
Feb 25 15:06:45 GB-NET kernel:  [<c0142fa4>] nameidata_to_filp+0x1f/0x31
Feb 25 15:06:45 GB-NET kernel:  [<c0142f19>] filp_open+0x33/0x3b
Feb 25 15:06:45 GB-NET kernel:  [<c0143049>] get_unused_fd+0x4c/0x91
Feb 25 15:06:45 GB-NET kernel:  [<c0143116>] do_sys_open+0x37/0xb0
Feb 25 15:06:45 GB-NET kernel:  [<c01431a0>] sys_open+0x11/0x15
Feb 25 15:06:45 GB-NET kernel:  [<c0102ab9>] syscall_call+0x7/0xb
Feb 25 15:06:45 GB-NET kernel: idr_remove called for id=4 which is not allocated.
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e4c>] sub_remove+0xdd/0xe6
Feb 25 15:06:45 GB-NET kernel:  [<c01245ce>] autoremove_wake_function+0x0/0x3a
Feb 25 15:06:45 GB-NET kernel:  [<c01b0e73>] idr_remove+0x1e/0x84
Feb 25 15:06:45 GB-NET kernel:  [<c01ed603>] release_dev+0x5a4/0x5bd
Feb 25 15:06:45 GB-NET kernel:  [<c012fc96>] free_hot_cold_page+0xb4/0xc2
Feb 25 15:06:45 GB-NET kernel:  [<c026aec4>] skb_queue_purge+0x2c/0x35
Feb 25 15:06:45 GB-NET kernel:  [<c02681a3>] sk_free+0x8a/0xb4
Feb 25 15:06:45 GB-NET kernel:  [<c014538a>] invalidate_inode_buffers+0xc/0x37
Feb 25 15:06:45 GB-NET kernel:  [<c0265d01>] sock_destroy_inode+0x13/0x16
Feb 25 15:06:45 GB-NET kernel:  [<c01579d0>] destroy_inode+0x38/0x4a
Feb 25 15:06:45 GB-NET kernel:  [<c01eda26>] tty_release+0x9/0xd
Feb 25 15:06:45 GB-NET kernel:  [<c0144645>] __fput+0x94/0x12c
Feb 25 15:06:45 GB-NET kernel:  [<c0143206>] filp_close+0x4c/0x55
Feb 25 15:06:45 GB-NET kernel:  [<c01166e4>] put_files_struct+0x5d/0x92
Feb 25 15:06:45 GB-NET kernel:  [<c01170fe>] do_exit+0x18d/0x2df
Feb 25 15:06:45 GB-NET kernel:  [<c01172df>] sys_exit_group+0x0/0x11
Feb 25 15:06:45 GB-NET kernel:  [<c0102ab9>] syscall_call+0x7/0xb
Thanks.
 
Old 02-25-2006, 12:02 PM   #2
druuna
LQ Veteran
 
Registered: Sep 2003
Posts: 10,532
Blog Entries: 7

Rep: Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405Reputation: 2405
Hi,

This is a 'bug' in some 2.6 kernels, should be fixed from 2.6.13 onward (I'm not 100% sure about this).

Feed your searchengine with idr_remove called for id= and read all about it

PS: Doesn't look like something you have to worry about too much.

Hope this helps.
 
Old 02-25-2006, 05:00 PM   #3
gbowden
Member
 
Registered: Dec 2003
Location: Spain
Distribution: Slackware 14.1 64bit - multilib
Posts: 148

Original Poster
Rep: Reputation: 28
Thanks, I'm currently running the 2.6.15.4 kernel, this doesn't show up on the 2.4.x series kernels.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Redirecting the kernel messages to file other than /var/log/messages jyotika_b83 Linux - General 3 04-28-2005 06:39 PM
No output to /var/log/messages or ~syslog eelriver Slackware 5 07-18-2004 05:13 AM
HELP!!!! /var/log/messages & syslog 350MB and growing!! nemat0de Mandriva 1 05-29-2004 06:08 AM
syslog and firestarter - log messages to another file than messages mule Linux - Newbie 0 08-07-2003 03:35 AM
/var/adm/messages & syslog Khalid Linux - General 0 11-08-2001 05:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:52 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration