From: Frans Pop <elendil@planet.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
tglx@tglx.de, mingo@elte.hu
Subject: Re: Warning/Oops report of the week of September 16th, 2008
Date: Sat, 27 Sep 2008 17:21:41 +0200 [thread overview]
Message-ID: <200809271721.43075.elendil@planet.nl> (raw)
In-Reply-To: <20080926112815.0f8e9de6@lxorguk.ukuu.org.uk>
On Friday 26 September 2008, Alan Cox wrote:
> parport: quickfix the proc registration bug
>
> From: Alan Cox <alan@redhat.com>
>
> Ideally we should have a directory of drivers and a link to the
> 'active' driver. For now just show the first device which is
> effectively the existing semantics without a warning.
>
> Signed-off-by: Alan Cox <alan@redhat.com>
Thanks Greg, but I'm afraid that still gives me the error:
ppdev0: registered pardevice
sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice
Sysctl already exists
Pid: 7104, comm: hpijs Not tainted 2.6.27-rc7 #21
Call Trace:
[<ffffffff8024d2ac>] set_fail+0x48/0x53
[<ffffffff8024d7a1>] sysctl_check_table+0x4ea/0x531
[<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
[<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
[<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
[<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
[<ffffffff8024d7ba>] sysctl_check_table+0x503/0x531
[<ffffffff8023b378>] ? sysctl_set_parent+0x24/0x39
[<ffffffff8023c66e>] __register_sysctl_paths+0xee/0x29e
[<ffffffff80314f05>] ? sprintf+0x68/0x6a
[<ffffffff8023c847>] register_sysctl_paths+0x29/0x2b
[<ffffffff8023c85c>] register_sysctl_table+0x13/0x15
[<ffffffffa00f79d4>] parport_device_proc_register+0xcc/0xf0 [parport]
[<ffffffffa00f5a07>] parport_register_device+0x25c/0x296 [parport]
[<ffffffffa03c9a3b>] ? pp_irq+0x0/0x4b [ppdev]
[<ffffffffa03c93e2>] pp_ioctl+0x16f/0x7c8 [ppdev]
[<ffffffff80282894>] ? free_pages_and_swap_cache+0x57/0x72
[<ffffffff8029abbe>] vfs_ioctl+0x2a/0x78
[<ffffffff8029ae63>] do_vfs_ioctl+0x257/0x274
[<ffffffff8029aed5>] sys_ioctl+0x55/0x78
[<ffffffff8020c1eb>] system_call_fastpath+0x16/0x1b
ppdev0: registered pardevice
ppdev0: unregistered pardevice
ppdev0: unregistered pardevice
Cheers,
FJP
prev parent reply other threads:[~2008-09-27 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 16:22 Arjan van de Ven
2008-09-17 0:40 ` Jay Cliburn
2008-09-24 22:36 ` Frans Pop
2008-09-24 22:45 ` Linus Torvalds
2008-09-24 22:57 ` Arjan van de Ven
2008-09-24 23:00 ` Linus Torvalds
2008-09-24 23:12 ` Frans Pop
2008-09-24 23:18 ` Linus Torvalds
2008-09-26 10:28 ` Alan Cox
2008-09-27 15:21 ` Frans Pop [this message]
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=200809271721.43075.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@tglx.de \
--cc=torvalds@linux-foundation.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 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®