From owner-freebsd-current  Sun Aug 29  2:17:38 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 826B614EB8
	for <current@FreeBSD.ORG>; Sun, 29 Aug 1999 02:17:30 -0700 (PDT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id LAA16076;
	Sun, 29 Aug 1999 11:15:03 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Cc: current@FreeBSD.ORG
Subject: Re: No longer able to rip CD data under -current. 
In-reply-to: Your message of "Sun, 29 Aug 1999 02:10:17 PDT."
             <409.935917817@localhost> 
Date: Sun, 29 Aug 1999 11:15:03 +0200
Message-ID: <16074.935918103@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Trouble could be if ripit picks up from stat(2) before
it opens the device, we don't know the underlying blocksize
until after open, floppy drives for instance support many
different sectorsizes.

What is the name of the port you're using ?

In message <409.935917817@localhost>, "Jordan K. Hubbard" writes:
>> 
>> This could be another si_bsize casualty.
>> 
>> Try this patch
>
>Nope, it still occurs.  You're definitely in the right ballpark
>though since I added some printfs and it's this check:
>
>	} else if (ssp->dss_secshift != -1) {
>		if (bp->b_bcount & (ssp->dss_secsize - 1))
>			goto bad_bcount;
>
>Which is now failing.
>
>- Jordan
>

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message