Summary: | [ata] [burncd]: [patch] writing >1 session on ATAPI CDs fails | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Base System | Reporter: | John Hood <jh> | ||||||||
Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> | ||||||||
Status: | Closed Overcome By Events | ||||||||||
Severity: | Affects Only Me | CC: | ak, sos | ||||||||
Priority: | Normal | ||||||||||
Version: | 6.0-RELEASE | ||||||||||
Hardware: | Any | ||||||||||
OS: | Any | ||||||||||
Attachments: |
|
Description
John Hood
2006-06-14 23:20:27 UTC
Responsible Changed From-To: freebsd-bugs->sos Over to maintainer. On Wed, Jun 14, 2006 at 10:20:27PM +0000, FreeBSD-gnats-submit@FreeBSD.org wrote: > Thank you very much for your problem report. > It has the internal identification `kern/98962'. Hey Soren, Could you have another look at this? It's a real bug in the driver. It does happen to look a lot like the stale-TOC bug a lot of drives have (which you've already worked around), but is actually a bad interaction with GEOM. I'd like to see a fix for this get checked in. Thanks, --jh State Changed From-To: open->feedback Hello, can you see what the status is on the latest 6-stable and/or 7-current ? thanks! Responsible Changed From-To: sos->remko steal the ticket from Soren to get more information. On Mon, Dec 25, 2006 at 09:07:30PM +0000, Remko Lodder wrote:
> Old Synopsis: [ata] [patch] writing >1 session on ATAPI CDs fails
> New Synopsis: [ata] [burncd]: [patch] writing >1 session on ATAPI CDs fails
>
> State-Changed-From-To: open->feedback
> State-Changed-By: remko
> State-Changed-When: Mon Dec 25 21:06:33 UTC 2006
> State-Changed-Why:
> Hello, can you see what the status is on the latest 6-stable
> and/or 7-current ? thanks!
Since you didn't mention what fixes to check, I ended up cvsup-ing
6_RELENG as of about 20061228 0100 UTC and building and checking that.
The original bug I reported in the PR is still there, along with the
slow 'burncd fixate' and never-ending 'burncd blank' problems talked
about on -stable.
Applying the patch in the original PR fixes the multisession burn
problem, at least :)
I'll check the last snapshot of CURRENT and see what that does. I
expect it'll have the same problem; I'll report if it behaves
differently from 6_RELENG.
Scripts attached.
--jh
On Wed, Dec 27, 2006 at 10:56:42PM -0500, John Hood wrote:
> I'll check the last snapshot of CURRENT and see what that does. I
> expect it'll have the same problem; I'll report if it behaves
> differently from 6_RELENG.
On the 20061105 snapshot, I get the same behavior, plus this kernel printf:
Nov 5 20:44:04 kernel: acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x05
when 'burncd -m data file fixate' or 'burncd msinfo' exit (but not
when typing ^C at 'burncd blank', IIRC). Both the 6-stable test and
this test are on a Dell Latitude D610 with a DVD/CD-RW combo drive,
dmesg attached.
I didn't try patching it yet. I could also try testing it on the
machine that I did the original PR on, if that's desired.
--jh
State Changed From-To: feedback->open Note that feedback was received some time ago. Responsible Changed From-To: remko->mav Hi mav@ can you have a look please? For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped The burncd(8) was removed after import of new ata stack. |