From: Chris Rankin <rankincj@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: tim@cyberelk.net
Subject: Linux 2.6.26.3: parallel port trouble
Date: Wed, 3 Sep 2008 12:02:03 -0700 (PDT) [thread overview]
Message-ID: <378641.67469.qm@web52912.mail.re2.yahoo.com> (raw)
Everyone,
I'm seeing some strange output in the dmesg log with a 2.6.26.3 UP kernel when it prints to an old HP OfficeJet parallel port printer:
ppdev0: registered pardevice
sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
Pid: 3268, comm: hpijs Not tainted 2.6.26.3 #1
[<c0129dd8>] set_fail+0x30/0x39
[<c012a1f2>] sysctl_check_table+0x411/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c011c802>] __register_sysctl_paths+0xa0/0x102
[<c011c87e>] register_sysctl_paths+0x1a/0x1c
[<d9955458>] parport_device_proc_register+0xa2/0xbc [parport]
[<d99537e1>] parport_register_device+0x1f8/0x220 [parport]
[<d993f2f7>] pp_ioctl+0x11e/0x76e [ppdev]
[<d993f947>] pp_irq+0x0/0x89 [ppdev]
[<c0167e85>] vfs_ioctl+0x49/0x5f
[<c01680d3>] do_vfs_ioctl+0x238/0x24a
[<c0168111>] sys_ioctl+0x2c/0x43
[<c0102c36>] syscall_call+0x7/0xb
=======================
ppdev0: registered pardevice
...
ppdev0: unregistered pardevice
ppdev0: released pardevice because user-space forgot
ppdev0: unregistered pardevice
ppdev0: registered pardevice
sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
Pid: 6643, comm: hpijs Not tainted 2.6.26.3 #1
[<c0129dd8>] set_fail+0x30/0x39
[<c012a1f2>] sysctl_check_table+0x411/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c012a209>] sysctl_check_table+0x428/0x44f
[<c011c802>] __register_sysctl_paths+0xa0/0x102
[<c011c87e>] register_sysctl_paths+0x1a/0x1c
[<d9955458>] parport_device_proc_register+0xa2/0xbc [parport]
[<d99537e1>] parport_register_device+0x1f8/0x220 [parport]
[<d993f2f7>] pp_ioctl+0x11e/0x76e [ppdev]
[<d993f947>] pp_irq+0x0/0x89 [ppdev]
[<c0167e85>] vfs_ioctl+0x49/0x5f
[<c01680d3>] do_vfs_ioctl+0x238/0x24a
[<c0168111>] sys_ioctl+0x2c/0x43
[<c0102c36>] syscall_call+0x7/0xb
=======================
ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: unregistered pardevice
The printer is still printing, so I'm guessing that these warnings aren't too serious - yet. But they worry me.
Cheers,
Chris
reply other threads:[~2008-09-03 19:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=378641.67469.qm@web52912.mail.re2.yahoo.com \
--to=rankincj@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@cyberelk.net \
/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
all inboxes | Powered by JetHome®