From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Subject: kernel: sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
Date: Fri, 30 May 2008 11:05:15 -0400 [thread overview]
Message-ID: <20080530150515.GA30397@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
Well, that's umm, special.
I wonder if powering off the printer isn't causing the sysctl to be removed,
causing the next power-on to look like a new device ?
Eric, you poked around the sysctl paths in parport last year, any ideas?
Dave
--
http://www.codemonkey.org.uk
[-- Attachment #2: Type: message/rfc822, Size: 7118 bytes --]
From: bugzilla@redhat.com
To: kernel-maint@redhat.com
Subject: [Bug 449112] New: kernel:<3>sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
Date: Fri, 30 May 2008 10:15:51 -0400
Message-ID: <bug-449112-176318@bugzilla.redhat.com>
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=449112
Summary: kernel:<3>sysctl table check failed:
/dev/parport/parport0/devices/ppdev0/timeslice Sysctl
already exists
Product: Fedora
Version: rawhide
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: kernel
AssignedTo: kernel-maint@redhat.com
ReportedBy: selinux@gmail.com
QAContact: extras-qa@fedoraproject.org
Description of problem:
Get the following in dmesg. I had "printed" to an HP5MP printer from firefox,
but the printer was powered off. I turned on the printer, and I believe got these.
ppdev0: registered pardevice
sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice
Sysctl already exists
Pid: 3921, comm: hp Not tainted 2.6.26-0.44.rc4.git2.fc10.i686 #1
[<c04407ae>] set_fail+0x33/0x40
[<c0440bc4>] sysctl_check_table+0x409/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c043148c>] __register_sysctl_paths+0xa7/0xf9
[<c04314fc>] register_sysctl_paths+0x1e/0x20
[<c043150d>] register_sysctl_table+0xf/0x11
[<f8db831f>] parport_device_proc_register+0xa9/0xc7 [parport]
[<f8db6b2c>] parport_register_device+0x1c1/0x1eb [parport]
[<f8dfe328>] pp_ioctl+0x12e/0x6b2 [ppdev]
[<f8dfe8ac>] ? pp_irq+0x0/0x43 [ppdev]
[<c04982ac>] vfs_ioctl+0x50/0x69
[<c04984fe>] do_vfs_ioctl+0x239/0x24c
[<c04df7dc>] ? selinux_file_ioctl+0x35/0x38
[<c0498551>] sys_ioctl+0x40/0x5b
[<c0404c3a>] syscall_call+0x7/0xb
=======================
ppdev0: registered pardevice
sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice
Sysctl already exists
Pid: 3921, comm: hp Not tainted 2.6.26-0.44.rc4.git2.fc10.i686 #1
[<c04407ae>] set_fail+0x33/0x40
[<c0440bc4>] sysctl_check_table+0x409/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c0440bda>] sysctl_check_table+0x41f/0x445
[<c043148c>] __register_sysctl_paths+0xa7/0xf9
[<c04314fc>] register_sysctl_paths+0x1e/0x20
[<c043150d>] register_sysctl_table+0xf/0x11
[<f8db831f>] parport_device_proc_register+0xa9/0xc7 [parport]
[<f8db6b2c>] parport_register_device+0x1c1/0x1eb [parport]
[<f8dfe328>] pp_ioctl+0x12e/0x6b2 [ppdev]
[<f8dfe8ac>] ? pp_irq+0x0/0x43 [ppdev]
[<c04982ac>] vfs_ioctl+0x50/0x69
[<c04984fe>] do_vfs_ioctl+0x239/0x24c
[<c04df7dc>] ? selinux_file_ioctl+0x35/0x38
[<c0498551>] sys_ioctl+0x40/0x5b
[<c0404c3a>] syscall_call+0x7/0xb
=======================
ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: unregistered pardevice
ppdev0: unregistered pardevice
Version-Release number of selected component (if applicable):
kernel-2.6.26-0.44.rc4.git2.fc10.i686
How reproducible:
Don't know....
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-05-30 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 15:05 Dave Jones [this message]
2008-05-30 18:19 ` kernel: sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists Eric W. Biederman
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=20080530150515.GA30397@redhat.com \
--to=davej@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.