From: Randy Dunlap <randy.dunlap@oracle.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org, scsi <linux-scsi@vger.kernel.org>
Subject: Re: 2.6.21 broke arm scsi on qemu -M volatilepb
Date: Thu, 10 May 2007 21:20:46 -0700 [thread overview]
Message-ID: <20070510212046.477dfed1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200705102359.11315.rob@landley.net>
[adding linux-scsi]
On Thu, 10 May 2007 23:59:10 -0400 Rob Landley wrote:
> Booting a 2.6.20 kernel under qemu works fine and gets me to a shell prompt,
> but booting a 2.6.21.1 kernel cycles endlessly on scsi, going:
>
> Loading iSCSI transport class v2.0-724.
> PCI: enabling device 0000:00:0c.0 (0140 -> 0143)
> sym0: <895a> rev 0x0 at pci 0000:00:0c.0 irq 0
> sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.2.3
> scsi 0:0:0:0: ABORT operation started.
> scsi 0:0:0:0: ABORT operation timed-out.
> scsi 0:0:0:0: DEVICE RESET operation started.
> scsi 0:0:0:0: DEVICE RESET operation timed-out.
> scsi 0:0:0:0: BUS RESET operation started.
> scsi 0:0:0:0: BUS RESET operation timed-out.
> scsi 0:0:0:0: HOST RESET operation started.
> sym0: SCSI BUS has been reset.
> ...
> And so on.
>
> If you're interested in reproducing this, download the most recent
> http://landley.net/hg/firmware snapshot (links up top), run "./build.sh
> armv4l", and when that's done "cd build" and "./run-armv4l.sh".
>
> Is this a known issue? A quick google for "arm scsi 2.6.21" didn't turn up
> anything relevant...
>
> Rob
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2007-05-11 4:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 3:59 2.6.21 broke arm scsi on qemu -M volatilepb Rob Landley
2007-05-11 4:20 ` Randy Dunlap [this message]
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=20070510212046.477dfed1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rob@landley.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 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.