https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
Andriy Gapon changed:
What|Removed |Added
Assignee|b...@freebsd.org|s...@freebsd.org
--
You are receiv
On Mon, 22 Apr 2019 a bug that doesn't want repl...@freebsd.org wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #21 from Andriy Gapon ---
(In reply to Domagoj Hranjec from comment #20)
And my point is that I am not sure if you have actually tested reading from the
e
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #21 from Andriy Gapon ---
(In reply to Domagoj Hranjec from comment #20)
And my point is that I am not sure if you have actually tested reading from the
end of the disk with the older FreeBSD. I am not sure that the older FreeB
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #20 from Domagoj Hranjec ---
The point is that the disk and the data on it is good and functional. The issue
seems that ATA_CAM implementation does not address the data on the disk in the
correct way.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #19 from Andriy Gapon ---
(In reply to Domagoj Hranjec from comment #18)
You can use dd to read the whole disk or ranges of it.
--
You are receiving this mail because:
You are the assignee for the bug.
On Sun, 21 Apr 2019 a bug that doesn't want repl...@freebsd.org wrote:
Created attachment 203861
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203861&action=edit
dmesg log with 8.4 livefs disk
I've booted the FreeBSD 8.4 livefs disk.
Disk is correctly configured:
ad3: FAILURE - SETF
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #18 from Domagoj Hranjec ---
Created attachment 203861
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203861&action=edit
dmesg log with 8.4 livefs disk
I've booted the FreeBSD 8.4 livefs disk.
Disk is correctly conf
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #17 from Andriy Gapon ---
(In reply to Mikhail Teterin from comment #16)
The commands are too different. ATAPI_IDENTIFY is a special command to request
disk description, parameters, etc. READ_DMA is a normal read data from media
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #16 from Mikhail Teterin ---
(In reply to Andriy Gapon from comment #15)
BTW, Andriy, I suspect, the problem I describe in Bug #237261 is related... The
endless loop is the same -- although the failing operation is different.
I
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #15 from Andriy Gapon ---
(In reply to Domagoj Hranjec from comment #14)
I guess it was a while ago.
Another thing I would try is completely disabling geom tasting (if the system
would still come up after that) or all unneeded g
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #14 from Domagoj Hranjec ---
Disk size is correctly deduced. Disk worked perfectly with the old atadisk
driver.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #13 from Andriy Gapon ---
(In reply to Domagoj Hranjec from comment #12)
Is the disk size determined correctly? It seems that the errors are from
reading sectors at the end of reported disk size.
Maybe forcing a PIO mode might h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #12 from Domagoj Hranjec ---
Created attachment 203744
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203744&action=edit
dmesg log with disk errors after patch
After applying the patch, the result is following:
disk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #11 from Andriy Gapon ---
(In reply to Mikhail Teterin from comment #10)
The code already chooses the right mode.
The problem is that the disk fails SETFEATURES SET TRANSFER MODE command even
for the right mode.
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
Mikhail Teterin changed:
What|Removed |Added
CC||m...@freebsd.org
--- Comment #10
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #9 from Andriy Gapon ---
Created attachment 203540
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=203540&action=edit
possible patch, not tested
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
--- Comment #8 from Andriy Gapon ---
In Linux, ata_dev_set_mode() function has several conditions for ignoring
errors from ata_dev_set_xfermode(). Examples:
- Don't fail an MWDMA0 set IFF the device indicates it is in MWDMA0
- if the device
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202712
Domagoj Hranjec changed:
What|Removed |Added
Summary|System doesn't recognize|[cam] [ata] System doesn't
19 matches
Mail list logo
