mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Gennerat <christian.gennerat@vz.cit.alcatel.fr>
To: Niels Happel <nhappel@planet-interkom.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Possible ISOFS Bug in 2.4.0-test11-pre7
Date: Mon, 27 Nov 2000 17:08:38 +0100	[thread overview]
Message-ID: <3A228705.85D818A3@vz.cit.alcatel.fr> (raw)
In-Reply-To: <00112716562000.01054@ws-20>

Niels Happel a écrit :

> Hello everybody,
>
> first of all: I am new to the linux-kernel list, so I don't know wheather
> writing here is allowed for everybody or developers only.
>
> Anyway, here it is:
>
> Hardware (SCSI-only system):
>
> Tekram 390 U2W (SYM53C8XX support compiled into the kernel)
> IBM U2W SCSI disks
> HP DAT SCSI Streamer
> Pioneer SCSI DVD
> Yamaha SCSI CD R/W
>
> Using kernel 2.4.0-test10 and earlier everything works fine.
> Using 2.4.0-test11 with the same kernel configuration an error message
> occured while accessing one of the mounted SCSI CD-ROMs:
> "kernel: _isofs_bmap: block < 0"
> Mounting them works fine, accessing them gives that error message.
> It can't be an SCSI CD-ROM hardware failure, because the error message
> occured at both drives (Pioneer and Yamaha) and it doesn't matter which
> CD-ROM I am using.
>

Same problem with ide-cs + ide-cd modules (IDE - PCMCIA)
kernel: _isofs_bmap: block < 0"


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-27 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-27 15:56 Possible SCSI or ISOFS Bug in 2.4.0-test11 Niels Happel
2000-11-27 16:08 ` Christian Gennerat [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=3A228705.85D818A3@vz.cit.alcatel.fr \
    --to=christian.gennerat@vz.cit.alcatel.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nhappel@planet-interkom.de \
    /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

all inboxes | Powered by JetHome®