public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: 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, 9 Sep 2006 08:36:31 -0700	[thread overview]
Message-ID: <20060909083631.95a63528.akpm@osdl.org> (raw)
In-Reply-To: <200609091032.k89AW7bM017561@fire-2.osdl.org>

On Sat, 9 Sep 2006 03:32:07 -0700
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=7130
> 
>            Summary: loading driver eat all CPU and since some time may block
>                     all system disk IO (even can not reboot)
>     Kernel Version: 2.6.17.12
>             Status: NEW
>           Severity: blocking
>              Owner: scsi_drivers-other@kernel-bugs.osdl.org
>          Submitter: wizard580@gmail.com
> 
> 
> Most recent kernel where this bug did not occur: 2.6.17.12
> Distribution: Debian SID/Unstable
> Hardware Environment: SUN UltraSparc2 E3500 FC-AL SCSI hard drives
> Software Environment: Debian with latest updates on 09.09.2006
> Problem Description: When I load a driver fcal, mu cpu will be 100% busy and 
> will never fred. modprobe fcal will never ends. If I do not restart 
> immediately, then since 2-4min I can not even reboot. Seems to there is a 
> block of all disk io. A top and so programs running fine, until exit. Start 
> again will fail.
> So... may be because of that, I can not see my FC-AL scsi hard drives.
> My hardware (if I did't mistaken):
> 1) X2652A FC-AL INTERFACE BOARD 3500.
> 2) X6731A FCAL GBIC MODULE 100MB/SEC
> P.S.: I do anything for seeing my hard drives in Debian. If I need to tell you 
> any info, or make a tests, just let me know. :)
> If anybody can quickly help, I will be blessed. :D My life is bet on this.
> P.P.S:
> hard drives I see in "pre boot 'bios' with probe-fcal-all command"
> 
> Steps to reproduce:
> modprobe fcal on a Sparc arch.
> 

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?

Thanks.


       reply	other threads:[~2006-09-09 15:36 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 ` Andrew Morton [this message]
2006-09-09 16:04   ` [Bugme-new] [Bug 7130] New: loading driver eat all CPU and since some time may block all system disk IO (even can not reboot) James Bottomley
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=20060909083631.95a63528.akpm@osdl.org \
    --to=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