At Thu, 27 Nov 2003 13:56:03 -0400,
Bremner David wrote:
>
> /dev/pass0: flushing cache
> /dev/pass0: closing track
> - [unable to TEST UNIT READY]: Input/output error
>
Following up to myself again; are we annoyed yet?
Anyway, I remember reading about someone trying "burncd fixate" in a
simila
At Thu, 27 Nov 2003 08:54:53 -0400,
Bremner David wrote:
>
> I have a 5.1-current system of Nov 10, also using rev 1.23 of
> ata-lowlevel.c.
>
> Without atapicam in the kernel, it boots ok. With atapicam in the
> kernel it hangs at the messages (written down from the screen)
>
> (probe2:ata1:0:
At Thu, 27 Nov 2003 00:07:30 -0600,
Dan Nelson wrote:
>
> In the last episode (Nov 27), Bruce Evans said:
> > [Resending due to no response after 2 weeks.]
> >
> > Rev.1.23 of ata-lowlevel.c broke atapicam on my BP6 system as shown
> > by the enclosed boot -v messages (the system just hangs, appa
In the last episode (Nov 27), Bruce Evans said:
> [Resending due to no response after 2 weeks.]
>
> Rev.1.23 of ata-lowlevel.c broke atapicam on my BP6 system as shown
> by the enclosed boot -v messages (the system just hangs, apparently
> waiting for a disk interrupt that never arrives; there see
* Stuart Walsh, 2003-10-18 :
> I have an easily reproducable panic when using atapicam. Vague trace
This has nothing to do whatsoever with ATAPI/CAM! this is an inconsistency
between cam_periph.c and vfs_bio.c, you need to update the latter to rev.
1.418 or newer.
Thomas.
--
[EMAIL PROTEC
Le 2003-09-21, Sascha Holzleiter écrivait :
> i still have problems with atapicam and atang, while booting with
> atapicam i get these messages:
There is nothing abnormal with these messages.
> When trying to burn a disk with cdrecord i get the following panic:
> panic: mutex vm object not own
Le 2003-09-22, Matthias Andree écrivait :
> I'm getting complaints from ata or atapicam during boot-up, but my
>From CAM actually, and you can safely ignore them.
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebs
Le 2003-09-06, Petri Helenius écrivait :
> Should this work or is the work to port this to ATAng still undergoing?
This should work, but does not, so the work is still in progress...
> panic: mutex Giant not owned at ../../../dev/ata/atapi-cam.c:117
Please try this patch.
Index: atapi-cam.c
=
On Tue, 26 Aug 2003, Kenneth Culver wrote:
> I think some people are already tracking this down related to the recent
> update of the ata drivers.
It would be nice if those people would post regarding their progress. A
lot of people depend on atapicam.
Doug
--
This .signature sanitized fo
> free_hcb()
> atapi_action()
> xpt_run_dev_sendq()
> xpt_action()
> probe_start()
> ...
>
I think some people are already tracking this down related to the recent
update of the ata drivers.
Ken
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
My apologies to the list for not looking in /sys/conf/NOTES before
posting. I wasn't aware of the "split". :)
A.
msg52522/pgp0.pgp
Description: PGP signature
"Søren Schmidt" wrote:
> It seems Samuel Tardieu wrote:
> > Has the ATAPICAM patch entered the kernel sources already? I cannot
> > seem to find the option in LINT.
>
> No, Justin has called for a timeout on that
Why?
Supposedly the "hang on boot" problems have been taken care
of... it's be
No it hasn't, there are still patches.
Ken
On Tue, 19 Mar 2002, Samuel Tardieu wrote:
> Has the ATAPICAM patch entered the kernel sources already? I cannot
> seem to find the option in LINT.
>
> Sam
> --
> Samuel Tardieu -- [EMAIL PROTECTED] -- http://www.rfc1149.net/sam
>
>
> To Unsubscribe:
It seems Samuel Tardieu wrote:
> Has the ATAPICAM patch entered the kernel sources already? I cannot
> seem to find the option in LINT.
No, Justin has called for a timeout on that
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mes
14 matches
Mail list logo
