public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Phil Stracchino <alaric@babcom.com>
To: Linux-KERNEL <linux-kernel@vger.kernel.org>
Subject: Re: CDROM troubles -- some progress, problem remains
Date: Sun, 6 May 2001 16:17:01 -0700	[thread overview]
Message-ID: <20010506161701.A778@babylon5.babcom.com> (raw)
In-Reply-To: <20010506030500.A26278@babylon5.babcom.com> <20010506144228.B13711@babylon5.babcom.com> <20010507000116.D506@suse.de>
In-Reply-To: <20010507000116.D506@suse.de>; from axboe@suse.de on Mon, May 07, 2001 at 12:01:16AM +0200

On Mon, May 07, 2001 at 12:01:16AM +0200, Jens Axboe wrote:
> On Sun, May 06 2001, Phil Stracchino wrote:
> > On Sun, May 06, 2001 at 03:05:00AM -0700, Phil Stracchino wrote:
> > > Hey folks,
> > > I'm seeing a problem with mounting CDs using a Toshiba XM-6401TA CDROM
> > > drive attached to an Adaptec AHA1542CF controller (scsi1) on kernel 2.4.3
> > > and 2.4.4.  The behavior seems to be fairly consistent as follows:
> > > 
> > > first mount and unmount works normally, no unusual events logged
> > > second mount and unmount works normally, no unusual events logged
> > > third mount locks up the machine.  looks like a kernel panic.
> > > 
> > > Any ideas?
> > 
> > 
> > Panic is confirmed.  This time, it lived long enough to log:
> >  
> > May  6 14:05:05 babylon5 kernel: Kernel panic: scsi_free:Bad offset
> > 
> > Since it involves the CDROM, the aha1542 driver is implicated.  Why it's
> > getting a bad offset, I don't understand enough about the SCSI drivers to
> > know; all the scsi_free calls in aha1542.c look identical to me.
> >  
> > Would any Linux SCSI gurus care to let me know any diagnostic procedures
> > recommended for nailing this one?
> 
> The panic should be fixed with attached patch.


The patch does indeed seem to prevent the panic, but not the underlying
problem.  Here's the results of a series of mount/umount operations after
applying the patch:

	*** CD inserted
VFS: Disk change detected on device sr(11,0)
	*** first mount (succeeded)
ISO 9660 Extensions: RRIP_1991A
	*** second mount (succeeded)
ISO 9660 Extensions: RRIP_1991A
	*** third mount (succeeded)
ISO 9660 Extensions: RRIP_1991A
	*** fourth and subsequent mounts failed
sr: ran out of mem for scatter pad
 I/O error: dev 0b:00, sector 252
isofs_read_super: bread failed, dev=0b:00, iso_blknum=63, block=126
sr: ran out of mem for scatter pad
 I/O error: dev 0b:00, sector 0
sr: ran out of mem for scatter pad
 I/O error: dev 0b:00, sector 64
sr: ran out of mem for scatter pad
 I/O error: dev 0b:00, sector 0
	*** the last manual mount attempt
sr: ran out of mem for scatter pad
 I/O error: dev 0b:00, sector 64
	*** at this point I logged out, then logged back in as a different
	    user
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
sr: ran out of mem for scatter pad
 I/O error: dev 0b:00, sector 0
sr: ran out of mem for scatter pad
 I/O error: dev 0b:00, sector 64
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers
Warning - running *really* short on DMA buffers

The kernel is continuing to spew these warnings.  At the time of finishing
this message, there are now 51 of them.



-- 
 Linux Now!   ..........Because friends don't let friends use Microsoft.
 phil stracchino   --   the renaissance man   --   mystic zen biker geek
    Vr00m:  2000 Honda CBR929RR   --   Cage:  2000 Dodge Intrepid R/T
 Previous vr00mage:  1986 VF500F (sold), 1991 VFR750F3 (foully murdered)

  reply	other threads:[~2001-05-06 23:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-06 10:05 CDROM troubles Phil Stracchino
2001-05-06 21:42 ` Phil Stracchino
2001-05-06 22:01   ` Jens Axboe
2001-05-06 23:17     ` Phil Stracchino [this message]
2001-05-09 17:54       ` CDROM troubles -- followup Phil Stracchino

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=20010506161701.A778@babylon5.babcom.com \
    --to=alaric@babcom.com \
    --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