From: William Lee Irwin III <wli@holomorphy.com>
To: Thomas Molina <tmolina@cox.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5 Problem Status Report
Date: Tue, 10 Sep 2002 19:29:33 -0700 [thread overview]
Message-ID: <20020911022933.GA3530@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209102057340.944-100000@dad.molina>
On Tue, Sep 10, 2002 at 09:00:30PM -0500, Thomas Molina wrote:
> 2.5 Kernel Problem Reports as of 10 Sep
> Problem Title Status Discussion
> qlogicisp oops no further discussion 2.5.33
> PCI and/or starfire.c broken no further discussion 2.5.33
> __write_lock_failed() oops no further discussion 2.5.33
Since 3 of these are things I reported...
qlogicisp.c oops is some longstanding error recovery issue and/or ISR
bug. axboe@suse.de has been taking my bugreports. There is a lack of
general interest in and information about this device.
PCI/starfire.c breakage has to do with PCI-PCI bridges appearing on
machines with multiple PCI buses. The bus numbering scheme used by
the bridges creates clashes with various other bus' numbers or something
like that. It's likely more visible on NUMA-Q since the bus numbers are
used for port I/O remapping. I'm unaware of the amount of reliance on
bus numbers in other circumstances. colpatch@us.ibm.com is handling it.
__write_lock_failed() oops is tasklist_lock starvation. The starving
writer had spun with interrupts off for so long the NMI oopser went
off. dhowells@redhat.com is looking into it and I have backup plans.
Cheers,
Bill
next prev parent reply other threads:[~2002-09-11 2:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 2:00 2.5 Problem Status Report Thomas Molina
2002-09-11 2:29 ` William Lee Irwin III [this message]
2002-09-11 18:33 ` Thomas Molina
2002-09-11 20:23 ` William Lee Irwin III
2002-09-11 4:00 ` Robert Love
2002-09-11 7:07 ` Oleg Drokin
2002-09-11 7:26 ` Ingo Molnar
2002-09-11 7:28 ` Oleg Drokin
2002-09-11 7:38 ` Ingo Molnar
2002-09-11 8:05 ` Oleg Drokin
2002-09-11 10:25 ` Jens Axboe
2002-09-11 10:29 ` Jens Axboe
2002-09-11 10:47 ` Oleg Drokin
2002-09-11 10:58 ` Jens Axboe
2002-09-11 11:07 ` Jens Axboe
2002-09-11 11:16 ` Oleg Drokin
2002-09-11 11:17 ` Jens Axboe
2002-09-11 11:49 ` Jens Axboe
2002-09-11 12:10 ` Oleg Drokin
2002-09-11 15:38 ` Oleg Drokin
2002-09-11 15:46 ` Ingo Molnar
2002-09-11 15:52 ` Ingo Molnar
2002-09-11 17:49 ` Oleg Drokin
2002-09-11 8:07 ` Thomas Molina
2002-09-11 8:12 ` Oleg Drokin
2002-09-11 9:18 ` Adrian Bunk
2002-09-11 7:12 ` Ingo Molnar
2002-09-11 8:04 ` Axel Siebenwirth
2002-09-11 9:21 ` Clemens Schwaighofer
-- strict thread matches above, loose matches on Subject: below --
2002-08-25 11:21 Thomas Molina
2002-08-26 16:42 ` Greg KH
2002-08-26 21:32 ` Thomas Molina
2002-08-02 2:39 2.5 Problem Status report Thomas Molina
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=20020911022933.GA3530@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tmolina@cox.net \
/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