From: Frans Pop <elendil@planet.nl>
To: linux-kernel@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [BUG] 2.6.24-rc5: 'sysctl table check failed' when turning on printer
Date: Sun, 6 Jan 2008 21:59:18 +0100 [thread overview]
Message-ID: <200801062159.20014.elendil@planet.nl> (raw)
In-Reply-To: <m1tzlqlmkd.fsf@ebiederm.dsl.xmission.com>
On Sunday 06 January 2008, Eric W. Biederman wrote:
> Short of two programs coming in and simultaneously trying to claim
> the parallel port and there being not exclusion in ppdev.c I don't
> have a clue what could cause the reported error.
That could well be the root cause as the full log shows:
Jan 6 01:21:02 faramir kernel: ppdev0: registered pardevice
Jan 6 01:21:03 faramir kernel: sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
Jan 6 01:21:03 faramir kernel: Pid: 11078, comm: hpijs Not tainted 2.6.24-rc6 #1
Jan 6 01:21:03 faramir kernel:
Jan 6 01:21:03 faramir kernel: Call Trace:
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c104>] set_fail+0x3f/0x47
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c5ba>] sysctl_check_table+0x4ae/0x4fb
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c0b6>] sysctl_check_lookup+0xc1/0xd0
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c5d0>] sysctl_check_table+0x4c4/0x4fb
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c0b6>] sysctl_check_lookup+0xc1/0xd0
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c5d0>] sysctl_check_table+0x4c4/0x4fb
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c0b6>] sysctl_check_lookup+0xc1/0xd0
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c5d0>] sysctl_check_table+0x4c4/0x4fb
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c0b6>] sysctl_check_lookup+0xc1/0xd0
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c5d0>] sysctl_check_table+0x4c4/0x4fb
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c0b6>] sysctl_check_lookup+0xc1/0xd0
Jan 6 01:21:03 faramir kernel: [<ffffffff8024c5d0>] sysctl_check_table+0x4c4/0x4fb
Jan 6 01:21:03 faramir kernel: [<ffffffff8023ca8d>] register_sysctl_table+0x52/0x9d
Jan 6 01:21:03 faramir kernel: [<ffffffff881ea7cb>] :parport:parport_device_proc_register+0xc3/0xe3
Jan 6 01:21:03 faramir kernel: [<ffffffff881e8da7>] :parport:parport_register_device+0x206/0x267
Jan 6 01:21:03 faramir kernel: [<ffffffff884151ae>] :ppdev:pp_irq+0x0/0x40
Jan 6 01:21:03 faramir kernel: [<ffffffff8841574f>] :ppdev:pp_ioctl+0x13f/0x77c
Jan 6 01:21:03 faramir kernel: [<ffffffff80296a55>] do_ioctl+0x55/0x6b
Jan 6 01:21:03 faramir kernel: [<ffffffff80296cae>] vfs_ioctl+0x243/0x25c
Jan 6 01:21:03 faramir kernel: [<ffffffff80296d18>] sys_ioctl+0x51/0x71
Jan 6 01:21:03 faramir kernel: [<ffffffff8020beee>] system_call+0x7e/0x83
Jan 6 01:21:03 faramir kernel:
Jan 6 01:21:03 faramir kernel: ppdev0: registered pardevice
Jan 6 01:22:10 faramir kernel: ppdev0: released pardevice because user-space forgot
Jan 6 01:22:10 faramir kernel: ppdev0: unregistered pardevice
Jan 6 01:22:11 faramir kernel: ppdev0: unregistered pardevice
Jan 6 03:24:57 faramir kernel: fuse exit
Sorry for not providing that info earlier, but the first time I had this
issue I had two print jobs after eachother and because of that I overlooked
the double registering.
I am printing through CUPS on a fairly standard Debian unstable system
running the KDE desktop.
next prev parent reply other threads:[~2008-01-06 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080106150722.GA15887@elte.hu>
2008-01-06 20:35 ` [BUG] 2.6.24-rc5: 'sysctl table check failed' when turning on printer Eric W. Biederman
2008-01-06 20:59 ` Frans Pop [this message]
2008-01-06 21:17 ` Eric W. Biederman
2008-01-06 0:24 Frans Pop
-- strict thread matches above, loose matches on Subject: below --
2007-12-16 20:19 Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200801062159.20014.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox