[Bug 207431] Using scanimage triggers ata2: FAILURE - odd-sized DMA transfer attempt

2016-10-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207431 Michael Osipov <1983-01...@gmx.net> changed: What|Removed |Added CC||1983-01...@gmx

[Bug 207431] Using scanimage triggers ata2: FAILURE - odd-sized DMA transfer attempt

2016-04-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207431 Mark Linimon changed: What|Removed |Added Keywords||regression -- You are receiving th

[Bug 207431] Using scanimage triggers ata2: FAILURE - odd-sized DMA transfer attempt

2016-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207431 --- Comment #2 from Charles Ziegler --- Correction - mustek and mustek2 should read microtek and microtek2, respectively. -- You are receiving this mail because: You are on the CC list for the bug.

[Bug 207431] Using scanimage triggers ata2: FAILURE - odd-sized DMA transfer attempt

2016-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207431 --- Comment #1 from Charles Ziegler --- Here is some additional information. Some testing uncovered the mustek and mustek2 devices in graphics/sane-backends appear to be responsible for these errors. Mustek2 is responsible for the "ata2:

[Bug 207431] Using scanimage triggers ata2: FAILURE - odd-sized DMA transfer attempt

2016-02-22 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207431 Bug ID: 207431 Summary: Using scanimage triggers ata2: FAILURE - odd-sized DMA transfer attempt Product: Base System Version: 10.2-RELEASE Hardware: amd64