All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: oops with 2.6.1-rc1 and rc-3
Date: Sun, 01 Feb 2004 02:48:28 +0100	[thread overview]
Message-ID: <401C5AEC.8060602@gmx.de> (raw)
In-Reply-To: <20040201002641.GB31914@luna.mooo.com>

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 [<c02a6b50>] (ide_intr+0x0/0x190)
Feb  1 02:34:48 tachyon [<c03248c0>] (snd_intel8x0_interrupt+0x0/0x210)
Feb  1 02:34:48 tachyon Disabling IRQ #11
Feb  1 02:34:48 tachyon irq 11: nobody cared!
Feb  1 02:34:48 tachyon Call Trace:
Feb  1 02:34:48 tachyon [<c010b0aa>] __report_bad_irq+0x2a/0x90
Feb  1 02:34:48 tachyon [<c010b19c>] note_interrupt+0x6c/0xb0
Feb  1 02:34:48 tachyon [<c010b451>] do_IRQ+0x121/0x130
Feb  1 02:34:48 tachyon [<c0109854>] common_interrupt+0x18/0x20
Feb  1 02:34:48 tachyon [<c0124080>] do_softirq+0x40/0xa0
Feb  1 02:34:48 tachyon [<c010b42d>] do_IRQ+0xfd/0x130
Feb  1 02:34:48 tachyon [<c0109854>] common_interrupt+0x18/0x20
Feb  1 02:34:48 tachyon [<c0281056>] generic_unplug_device+0x26/0x80
Feb  1 02:34:48 tachyon [<c028121a>] blk_run_queues+0x7a/0xb0
Feb  1 02:34:48 tachyon [<c016605f>] __wait_on_buffer+0xbf/0xd0
Feb  1 02:34:48 tachyon [<c011e1c0>] autoremove_wake_function+0x0/0x50
Feb  1 02:34:48 tachyon [<c011e1c0>] autoremove_wake_function+0x0/0x50
Feb  1 02:34:48 tachyon [<c020dbb8>] submit_logged_buffer+0x38/0x60
Feb  1 02:34:48 tachyon [<c020e1a3>] kupdate_one_transaction+0x1b3/0x210
Feb  1 02:34:48 tachyon [<c020e275>] reiserfs_journal_kupdate+0x75/0xb0
Feb  1 02:34:48 tachyon [<c0210ed4>] flush_old_commits+0x144/0x1d0
Feb  1 02:34:48 tachyon [<c0122583>] do_exit+0x293/0x500
Feb  1 02:34:48 tachyon [<c01fe942>] reiserfs_write_super+0x82/0x90
Feb  1 02:34:48 tachyon [<c016b94c>] sync_supers+0xac/0xc0
Feb  1 02:34:48 tachyon [<c014b526>] wb_kupdate+0x36/0x120
Feb  1 02:34:48 tachyon [<c02602d3>] tty_write+0x1d3/0x3f0
Feb  1 02:34:48 tachyon [<c026008e>] tty_read+0x18e/0x200
Feb  1 02:34:48 tachyon [<c011c86d>] schedule+0x31d/0x590
Feb  1 02:34:48 tachyon [<c01214c0>] reparent_to_init+0xf0/0x180
Feb  1 02:34:48 tachyon [<c014bb4b>] __pdflush+0xcb/0x1b0
Feb  1 02:34:48 tachyon [<c014bc30>] pdflush+0x0/0x20
Feb  1 02:34:48 tachyon [<c014bc3f>] pdflush+0xf/0x20
Feb  1 02:34:48 tachyon [<c014b4f0>] wb_kupdate+0x0/0x120
Feb  1 02:34:48 tachyon [<c0107284>] kernel_thread_helper+0x0/0xc
Feb  1 02:34:48 tachyon [<c0107289>] kernel_thread_helper+0x5/0xc
Feb  1 02:34:48 tachyon


  reply	other threads:[~2004-02-01  1:48 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30  4:24 Software Suspend 2.0 Nigel Cunningham
2004-01-30 10:04 ` Måns Rullgård
2004-01-30 10:22   ` Nigel Cunningham
2004-01-30 10:25   ` Nigel Cunningham
2004-01-31 18:09     ` Micha Feigin
2004-02-05  0:47     ` Software Suspend 2.0 [for 2.6.2 resend] Hugang
2004-01-31  6:22 ` [Swsusp-devel] Software Suspend 2.0 Luke-Jr
2004-01-31  6:37   ` Nigel Cunningham
2004-01-31  6:48     ` Joseph Pingenot
2004-01-31  6:56       ` Nigel Cunningham
2004-01-31  7:16         ` Joseph Pingenot
2004-01-31  7:28           ` Nigel Cunningham
2004-01-31  7:38             ` Joseph Pingenot
2004-01-31  7:48               ` Nigel Cunningham
2004-01-31  8:32               ` Nigel Cunningham
2004-01-31  9:03                 ` Prakash K. Cheemplavam
2004-01-31  9:08                   ` Nigel Cunningham
2004-01-31  9:19                     ` Prakash K. Cheemplavam
2004-01-31  9:51                       ` Nigel Cunningham
2004-01-31 10:43                         ` Prakash K. Cheemplavam
2004-01-31 10:48                           ` Prakash K. Cheemplavam
2004-01-31 13:25                           ` Måns Rullgård
2004-01-31 23:11                             ` Joseph Pingenot
2004-01-31 22:15                               ` Måns Rullgård
2004-02-01  0:26                               ` Micha Feigin
2004-02-01  1:48                                 ` Prakash K. Cheemplavam [this message]
2004-02-01  2:54                                   ` oops with 2.6.1-rc1 and rc-3 Micha Feigin
2004-02-01 10:36                                     ` Prakash K. Cheemplavam
2004-02-01 11:37                                       ` Prakash K. Cheemplavam
2004-01-31  9:35         ` [Swsusp-devel] Software Suspend 2.0  Éric Brunet
2004-01-31  9:38           ` Nigel Cunningham
2004-01-31  7:22     ` Luke-Jr
2004-01-31  7:31       ` Nigel Cunningham
2004-01-31  8:09         ` Luke-Jr
2004-01-31  8:11           ` Luke-Jr
2004-01-31  8:18           ` Nigel Cunningham
2004-01-31 15:23 ` Sebastian Kugler
2004-02-01  7:08 ` Hugang
2004-02-02 17:01   ` swsusp2 on ppc [Re: Software Suspend 2.0] Marco Giordani
2004-02-03  1:37     ` Hugang
2004-02-03 12:07       ` Marco Giordani
     [not found] <BF1FE1855350A0479097B3A0D2A80EE0020AEB18@hdsmsx402.hd.intel.com>
2004-02-01 19:49 ` oops with 2.6.1-rc1 and rc-3 Len Brown
2004-02-02  8:45   ` Prakash K. Cheemplavam
2004-02-02 18:59     ` Len Brown
2004-02-02 20:51       ` Prakash K. Cheemplavam
2004-02-02 20:54         ` Prakash K. Cheemplavam

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=401C5AEC.8060602@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.