Bug#588672: marked as done (linux-image-2.6-amd64: parport driver sysctl table error - irritating kernel syslogs)
Your message dated Sun, 11 Jul 2010 11:28:10 +0200
with message-id <20100711092810.GA4289@galadriel.inutil.org>
and subject line Re: linux-image-2.6-amd64: parport driver sysctl table error - irritating kernel syslogs
has caused the Debian Bug report #588672,
regarding linux-image-2.6-amd64: parport driver sysctl table error - irritating kernel syslogs
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
588672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588672
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6-amd64
Version: 2.6.26+17+lenny1
Severity: normal
The parport driver sometimes fails to register. This can occur when turning on a printer or when a program tries to
print to a disconnected printer. The symptom is a set of messages like this in syslog output:
Jul 10 20:37:45 host kernel: [ 1077.075261] ppdev0: registered pardevice
Jul 10 20:38:15 host kernel: [ 1115.745885] sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
Jul 10 20:38:15 host kernel: [ 1115.745885] Pid: 3127, comm: hp Tainted: P 2.6.26-2-amd64 #1
Jul 10 20:38:15 host kernel: [ 1115.745885]
Jul 10 20:38:15 host kernel: [ 1115.745885] Call Trace:
Jul 10 20:38:15 host kernel: [ 1115.745885] [<ffffffff8024a64a>] set_fail+0x3f/0x47
Jul 10 20:38:15 host kernel: [ 1115.745885] [<ffffffff8024ab21>] sysctl_check_tab
...
The messages repeat every few seconds until the trigger process is stopped.
I believe this is described in https://bugzilla.kernel.org/show_bug.cgi?id=9749 and Alan Cox provides a patch in
https://bugzilla.kernel.org/attachment.cgi?id=21712
-- System Information:
Debian Release: 5.0.5
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages linux-image-2.6-amd64 depends on:
ii linux-image-2.6.26-2-amd64 2.6.26-24 Linux 2.6.26 image on AMD64
linux-image-2.6-amd64 recommends no packages.
linux-image-2.6-amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.6.30-1
On Sat, Jul 10, 2010 at 10:18:58PM -0400, Ralph A. Smith wrote:
> Package: linux-image-2.6-amd64
> Version: 2.6.26+17+lenny1
> Severity: normal
>
> The parport driver sometimes fails to register. This can occur when turning on a printer or when a program tries to
> print to a disconnected printer. The symptom is a set of messages like this in syslog output:
>
> Jul 10 20:37:45 host kernel: [ 1077.075261] ppdev0: registered pardevice
> Jul 10 20:38:15 host kernel: [ 1115.745885] sysctl table check failed: /dev/parport/parport0/devices/ppdev0/timeslice Sysctl already exists
> Jul 10 20:38:15 host kernel: [ 1115.745885] Pid: 3127, comm: hp Tainted: P 2.6.26-2-amd64 #1
> Jul 10 20:38:15 host kernel: [ 1115.745885]
> Jul 10 20:38:15 host kernel: [ 1115.745885] Call Trace:
> Jul 10 20:38:15 host kernel: [ 1115.745885] [<ffffffff8024a64a>] set_fail+0x3f/0x47
> Jul 10 20:38:15 host kernel: [ 1115.745885] [<ffffffff8024ab21>] sysctl_check_tab
> ...
>
> The messages repeat every few seconds until the trigger process is stopped.
>
> I believe this is described in https://bugzilla.kernel.org/show_bug.cgi?id=9749 and Alan Cox provides a patch in
> https://bugzilla.kernel.org/attachment.cgi?id=21712
Thanks for the report.
This was fixed in 2.6.30, so it's already corrected in the upcoming Squeeze kernel.
I've added the fix for Lenny as well, it will appear in the next stable point
update.
Cheers,
Moritz
--- End Message ---
Reply to: