From owner-freebsd-multimedia  Tue Mar  2 21:40:59 1999
Delivered-To: freebsd-multimedia@freebsd.org
Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id CE6A714EA5; Tue,  2 Mar 1999 21:40:53 -0800 (PST)
	(envelope-from ken@panzer.plutotech.com)
Received: (from ken@localhost)
          by panzer.plutotech.com (8.9.2/8.8.5) id WAA82810;
          Tue, 2 Mar 1999 22:40:30 -0700 (MST)
From: "Kenneth D. Merry" <ken@plutotech.com>
Message-Id: <199903030540.WAA82810@panzer.plutotech.com>
Subject: Re: CD-ROM problem on 3.0: Invalid argument?
In-Reply-To: <199903030201.TAA12937@pluto.plutotech.com> from Steven Grady at "Mar 2, 1999  6: 1:54 pm"
To: grady@xcf.berkeley.edu (Steven Grady)
Date: Tue, 2 Mar 1999 22:40:30 -0700 (MST)
Cc: freebsd-multimedia@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-multimedia@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Steven Grady wrote...
> Thanks for the information.  I turned on CAM debugging, and when
> I reproduced the problem, I found the following syslog data:
> 
>     [At this point, it was successfully reading the disc.]
>     (pass2:ahc0:0:2:0): READ(10). CDB: 28 0 0 0 d bd 0 0 a 0 
>     [Here I interrupted the read, and ran the program.]
>     (cd0:ahc0:0:2:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 
>     (cd0:ahc0:0:2:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
>     (cd0:ahc0:0:2:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 0 0 
>     [Here, I ran the program again.]
>     (cd0:ahc0:0:2:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
> 
> Each subsequent (failing) run of the cddb-id program generates the
> same single "READ CD RECORDED CAPACITY" message.

Weird.  It sounds like there may be a state-keeping type problem with the
driver in 3.0.  You should get a prevent removal and an allow removal each
time.  But evidently you aren't getting that...

> By the way, I also tried to boot with -v, but I get a reproducible
> page fault during boot.  The information I saved is that the bell
> turns on, and it enteres the debugger with the message:
>     Fatal trap 12; page fault in kernel mode
>     ...
>     Stopped at _ansi_put+0x92: movw %ax,0(%ecx)
> 
> Since I've never debugged a kernel before, I gave up booting with -v
> at this point.

Just put the following in your kernel config file:

options DDB

And then when you get a panic, type 'trace' at the DDB prompt.

> I'm looking forward to the arrival of the 3.1 discs -- maybe they will
> fix this problem.  But meanwhile, perhaps this information can shed
> some light on the bug.

There have been a number of changes in the CD driver since 3.0.   My guess
is that 3.1 may well fix your problem.  It's probably worth just waiting
for 3.1, since I suspect you'll be getting it soon.

If 3.1 doesn't fix the problem, we'll have to hunt this one down.

Ken
-- 
Kenneth Merry
ken@plutotech.com


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