From: Daniel Smolik <marvin@mydatex.cz>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 esp connected CDROM failures
Date: Fri, 16 Mar 2007 20:21:44 +0000 [thread overview]
Message-ID: <45FAFC58.8040301@mydatex.cz> (raw)
In-Reply-To: <1173976389.16911.13.camel@dhcp-32-109.ord.redhat.com>
Tom 'spot' Callaway napsal(a):
> On Thu, 2007-03-15 at 18:01 -0700, David Miller wrote:
>
>>From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
>>Date: Thu, 15 Mar 2007 11:33:09 -0500
>>
>>
>>>While this isn't technically a blocker for Aurora, its a rather big
>>>annoyance. Not sure where to look on how to fix this one, but very
>>>willing and able to test. First test will be with a gcc34 built kernel
>>>to rule out compiler.
>>
>>Let me see if the same bug triggers with current trees on my
>>sparc64 sbus machines. I tested those, but I don't think I
>>hit CDROM's. :-/
>
>
> Dusted off an Ultra1 to test this, and I get the following from dmesg:
>
> sr 0:0:6:0: CD-ROM TOSHIBA XM-5401TASUN4XCD 1036 PQ: 0 ANSI:
> 2
> esp0: target 6 asynchronous
> sr0: scsi-1 drive
> Uniform CD-ROM driver: Revision: 3.20
> sr 0:0:6:0: Attached CD-ROM sr0
> sr0: CDROM (ioctl) error, command: <6>Get configuration 46 00 00 00 00
> 00 00 00 20 00
> sr: <<DEFERRED>> [descriptor]: sense key=0xf
> <<VENDOR>> ASC=0xf8 ASCQ
SC=0xf8 ASCQ=0x0
>
> The ioctl error repeats once more in the sequence...but the CDROM seems
> to work ok, as compared to sparc32, where it refuses to work.
>
I don't know if am I right but I have SS5 with 3 esp controllers and
atached external CD-ROM and it works without this messages.
Dan
--
Mydatex s r.o.
http://www.mydatex.cz
email: smolik@mydatex.cz
mob: 604200362
tel: 226210085
next prev parent reply other threads:[~2007-03-16 20:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 16:33 sparc32 esp connected CDROM failures Tom 'spot' Callaway
2007-03-16 1:01 ` David Miller
2007-03-16 19:47 ` Tom 'spot' Callaway
2007-03-16 20:21 ` Daniel Smolik [this message]
2007-03-16 20:52 ` David Miller
2007-03-16 21:32 ` Tom 'spot' Callaway
2007-03-16 21:38 ` Tom 'spot' Callaway
2007-03-16 21:42 ` 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=45FAFC58.8040301@mydatex.cz \
--to=marvin@mydatex.cz \
--cc=sparclinux@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.