From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-scsi@vger.kernel.org, wizard580@gmail.com,
sparclinux@vger.kernel.org,
"bugme-daemon@kernel-bugs.osdl.org"
<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 7130] New: loading driver eat all CPU and since some time may block all system disk IO (even can not reboot)
Date: Sat, 09 Sep 2006 11:04:15 -0500 [thread overview]
Message-ID: <1157817856.3462.7.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20060909083631.95a63528.akpm@osdl.org>
On Sat, 2006-09-09 at 08:36 -0700, Andrew Morton wrote:
> Does anyone else us the fcal driver?
>
> I'd suggest the next step would be to run a kernel profile, or just sysrq-P
> to find out where the CPU is stuck. Could a sparc person please talk the
> reporter through that process?
I'm not sure this is really worth it. Apart from trying to keep it
compiling, fcal has had no maintainer since the 2.2 kernel days. Since
no-one has the hardware or the inclination, it's not plugged into the
SCSI FC infrastructure and thus it's bitrotting. Now might be a good
time to declare it officially dead and remove it from the tree. Unless
someone actually wants to maintain it and bring it into the 21st
century?
James
next prev parent reply other threads:[~2006-09-09 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609091032.k89AW7bM017561@fire-2.osdl.org>
2006-09-09 15:36 ` [Bugme-new] [Bug 7130] New: loading driver eat all CPU and since some time may block all system disk IO (even can not reboot) Andrew Morton
2006-09-09 16:04 ` James Bottomley [this message]
2006-09-10 13:11 ` David Miller
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=1157817856.3462.7.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=wizard580@gmail.com \
/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