All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
To: sparclinux@vger.kernel.org
Subject: Re: sparc32 esp connected CDROM failures
Date: Fri, 16 Mar 2007 21:32:51 +0000	[thread overview]
Message-ID: <1174080771.3628.48.camel@localhost.localdomain> (raw)
In-Reply-To: <1173976389.16911.13.camel@dhcp-32-109.ord.redhat.com>

On Fri, 2007-03-16 at 13:52 -0700, David Miller wrote:
> From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
> Date: Fri, 16 Mar 2007 14:47:00 -0500
> 
> > 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.
> 
> Unfortunately that puts the ball in your or someone else's court,
> since I don't have any sparc32 systems and therefore any way to work
> on sparc32 bugs.

Well, it looks like I spoke too soon. CD1 worked, but CD2 gave me these
errors when I tried to read it:

attempt to access beyond end of device
sr0: rw=0, want\x1205604, limit\x1268440
attempt to access beyond end of device
sr0: rw=0, want\x1205608, limit\x1268440
attempt to access beyond end of device
sr0: rw=0, want\x1205612, limit\x1268440
attempt to access beyond end of device
sr0: rw=0, want\x1205616, limit\x1268440

Confirmed that the image and the CD is good (it reads fine in several
other machines).

CD1 was slightly smaller, perhaps thats why it slipped by?

~spot



  parent reply	other threads:[~2007-03-16 21:32 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
2007-03-16 20:52 ` David Miller
2007-03-16 21:32 ` Tom 'spot' Callaway [this message]
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=1174080771.3628.48.camel@localhost.localdomain \
    --to=tcallawa@redhat.com \
    --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.