Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265191AbUBAC47 (ORCPT ); Sat, 31 Jan 2004 21:56:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265193AbUBAC47 (ORCPT ); Sat, 31 Jan 2004 21:56:59 -0500 Received: from post.tau.ac.il ([132.66.16.11]:62915 "EHLO post.tau.ac.il") by vger.kernel.org with ESMTP id S265191AbUBAC44 (ORCPT ); Sat, 31 Jan 2004 21:56:56 -0500 Date: Sun, 1 Feb 2004 04:54:46 +0200 From: Micha Feigin To: linux-kernel@vger.kernel.org Subject: Re: oops with 2.6.1-rc1 and rc-3 Message-ID: <20040201025446.GD32642@luna.mooo.com> Mail-Followup-To: linux-kernel@vger.kernel.org References: <1075537924.17730.88.camel@laptop-linux> <401B6F7A.5030103@gmx.de> <1075540107.17727.90.camel@laptop-linux> <401B7312.3060207@gmx.de> <1075542685.25454.124.camel@laptop-linux> <401B86EB.50604@gmx.de> <20040131231134.GA6084@digitasaru.net> <20040201002641.GB31914@luna.mooo.com> <401C5AEC.8060602@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <401C5AEC.8060602@gmx.de> User-Agent: Mutt/1.5.5.1+cvs20040105i X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.23.0.3; VDF: 6.23.0.53; host: localhost) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3472 Lines: 69 On Sun, Feb 01, 2004 at 02:48:28AM +0100, Prakash K. Cheemplavam wrote: > This happened once with rc-1 vanilla and once with rc-3 (haven't used > rc2 long enough.) Never happened with a earlier kernel. The message > repeats eternally itself making the system next to unusuable. > > Any idea how to fix it? > > I am using siimage ide driver. > > Prakash > > Feb 1 02:34:48 tachyon handlers: > Feb 1 02:34:48 tachyon [] (ide_intr+0x0/0x190) > Feb 1 02:34:48 tachyon [] (snd_intel8x0_interrupt+0x0/0x210) > Feb 1 02:34:48 tachyon Disabling IRQ #11 > Feb 1 02:34:48 tachyon irq 11: nobody cared! This irq message has been reported by several people (including me), I don't think there is a solution yet. AFAIK its not swsusp related. > Feb 1 02:34:48 tachyon Call Trace: > Feb 1 02:34:48 tachyon [] __report_bad_irq+0x2a/0x90 > Feb 1 02:34:48 tachyon [] note_interrupt+0x6c/0xb0 > Feb 1 02:34:48 tachyon [] do_IRQ+0x121/0x130 > Feb 1 02:34:48 tachyon [] common_interrupt+0x18/0x20 > Feb 1 02:34:48 tachyon [] do_softirq+0x40/0xa0 > Feb 1 02:34:48 tachyon [] do_IRQ+0xfd/0x130 > Feb 1 02:34:48 tachyon [] common_interrupt+0x18/0x20 > Feb 1 02:34:48 tachyon [] generic_unplug_device+0x26/0x80 > Feb 1 02:34:48 tachyon [] blk_run_queues+0x7a/0xb0 > Feb 1 02:34:48 tachyon [] __wait_on_buffer+0xbf/0xd0 > Feb 1 02:34:48 tachyon [] autoremove_wake_function+0x0/0x50 > Feb 1 02:34:48 tachyon [] autoremove_wake_function+0x0/0x50 > Feb 1 02:34:48 tachyon [] submit_logged_buffer+0x38/0x60 > Feb 1 02:34:48 tachyon [] kupdate_one_transaction+0x1b3/0x210 > Feb 1 02:34:48 tachyon [] reiserfs_journal_kupdate+0x75/0xb0 > Feb 1 02:34:48 tachyon [] flush_old_commits+0x144/0x1d0 > Feb 1 02:34:48 tachyon [] do_exit+0x293/0x500 > Feb 1 02:34:48 tachyon [] reiserfs_write_super+0x82/0x90 > Feb 1 02:34:48 tachyon [] sync_supers+0xac/0xc0 > Feb 1 02:34:48 tachyon [] wb_kupdate+0x36/0x120 > Feb 1 02:34:48 tachyon [] tty_write+0x1d3/0x3f0 > Feb 1 02:34:48 tachyon [] tty_read+0x18e/0x200 > Feb 1 02:34:48 tachyon [] schedule+0x31d/0x590 > Feb 1 02:34:48 tachyon [] reparent_to_init+0xf0/0x180 > Feb 1 02:34:48 tachyon [] __pdflush+0xcb/0x1b0 > Feb 1 02:34:48 tachyon [] pdflush+0x0/0x20 > Feb 1 02:34:48 tachyon [] pdflush+0xf/0x20 > Feb 1 02:34:48 tachyon [] wb_kupdate+0x0/0x120 > Feb 1 02:34:48 tachyon [] kernel_thread_helper+0x0/0xc > Feb 1 02:34:48 tachyon [] kernel_thread_helper+0x5/0xc > Feb 1 02:34:48 tachyon I didn't check it in the kernel but at first sight it looks like regular disks updates. I don't know what it goes into a loop. Are you sure that you don't have something that keeps updating the disk? > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/