public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Frings <stefan@edv-frings.de>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: cannot ls cdroms (_isofs_bmap block >= EOF)
Date: Mon, 27 Nov 2000 00:16:41 +0100	[thread overview]
Message-ID: <00112700180300.08780@notebook> (raw)

[1.] One line summary of the problem:  

cannot ls cdroms (_isofs_bmap block >= EOF)

[2.] Full description of the problem/report:

I cannot run ls on cdroms with kernel 2.4.0-test11. I get the 
message "_isofs_bmap block >= EOF". Kernel 2.0.4-test8 and test10 
work fine for me. I did not test other 2.4.0 versions. It makes no
difference if I compile isofs as "M" or "Y".

[3.] Keywords (i.e., modules, networking, kernel):

kernel, isofs, cdrom, bmap, mount, ls

[4.] Kernel version (from /proc/version):

2.4.0-test11

[6.] A small shell script or example program which triggers the
     problem (if possible)
     
mount /dev/hdc1 /mnt
dir /mnt
     
[7.1.] Software (add the output of the ver_linux script here)

Kernel modules		2.3.21
Gnu C			2.95.2
Gnu Make		3.79.1
Binutils		2.9.5.0.24
Dynamic Linker		ldd (GNU libc) 2.1.13
Procps			2.0.6
Mount			2.10q
Net-tools		1.56
Kbd			0.99
Sh-utils		2.0
Modules loaded		no modules loaded

[7.2.] Processor information (from /proc/cpuinfo):

AMD K6-2 366

[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)

Intel 82371AB PIIX 4 ACPI

[X.] Other notes, patches, fixes, workarounds:

I tried to use the isofs sources from version 2.4.0-test10 in 2.4.0-test11
they are not compatible. 
-
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-26 23:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 23:16 Stefan Frings [this message]
2000-11-26 23:33 ` PROBLEM: cannot ls cdroms (_isofs_bmap block >= EOF) Andries Brouwer

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=00112700180300.08780@notebook \
    --to=stefan@edv-frings.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox