From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757404AbYAFU7b (ORCPT ); Sun, 6 Jan 2008 15:59:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753447AbYAFU7Y (ORCPT ); Sun, 6 Jan 2008 15:59:24 -0500 Received: from hpsmtp-eml18.kpnxchange.com ([213.75.38.118]:5395 "EHLO hpsmtp-eml18.kpnxchange.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752823AbYAFU7X (ORCPT ); Sun, 6 Jan 2008 15:59:23 -0500 From: Frans Pop To: linux-kernel@vger.kernel.org Subject: Re: [BUG] 2.6.24-rc5: 'sysctl table check failed' when turning on printer Date: Sun, 6 Jan 2008 21:59:18 +0100 User-Agent: KMail/1.9.7 References: <20080106150722.GA15887@elte.hu> In-Reply-To: Cc: "Eric W. Biederman" , Ingo Molnar MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801062159.20014.elendil@planet.nl> X-OriginalArrivalTime: 06 Jan 2008 20:59:20.0700 (UTC) FILETIME=[023753C0:01C850A7] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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: [] set_fail+0x3f/0x47 Jan 6 01:21:03 faramir kernel: [] sysctl_check_table+0x4ae/0x4fb Jan 6 01:21:03 faramir kernel: [] sysctl_check_lookup+0xc1/0xd0 Jan 6 01:21:03 faramir kernel: [] sysctl_check_table+0x4c4/0x4fb Jan 6 01:21:03 faramir kernel: [] sysctl_check_lookup+0xc1/0xd0 Jan 6 01:21:03 faramir kernel: [] sysctl_check_table+0x4c4/0x4fb Jan 6 01:21:03 faramir kernel: [] sysctl_check_lookup+0xc1/0xd0 Jan 6 01:21:03 faramir kernel: [] sysctl_check_table+0x4c4/0x4fb Jan 6 01:21:03 faramir kernel: [] sysctl_check_lookup+0xc1/0xd0 Jan 6 01:21:03 faramir kernel: [] sysctl_check_table+0x4c4/0x4fb Jan 6 01:21:03 faramir kernel: [] sysctl_check_lookup+0xc1/0xd0 Jan 6 01:21:03 faramir kernel: [] sysctl_check_table+0x4c4/0x4fb Jan 6 01:21:03 faramir kernel: [] register_sysctl_table+0x52/0x9d Jan 6 01:21:03 faramir kernel: [] :parport:parport_device_proc_register+0xc3/0xe3 Jan 6 01:21:03 faramir kernel: [] :parport:parport_register_device+0x206/0x267 Jan 6 01:21:03 faramir kernel: [] :ppdev:pp_irq+0x0/0x40 Jan 6 01:21:03 faramir kernel: [] :ppdev:pp_ioctl+0x13f/0x77c Jan 6 01:21:03 faramir kernel: [] do_ioctl+0x55/0x6b Jan 6 01:21:03 faramir kernel: [] vfs_ioctl+0x243/0x25c Jan 6 01:21:03 faramir kernel: [] sys_ioctl+0x51/0x71 Jan 6 01:21:03 faramir kernel: [] 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.