On 09/27/13 15:38, Boris Samorodov wrote:
27.09.2013 16:59, Pietro Cerutti пишет:
On 2013-Sep-27, 05:57, Scott Long wrote:
On Sep 27, 2013, at 5:52 AM, Sergey V. Dyatko <sergey.dya...@gmail.com> wrote:
yes, these messages disappeared after revert 255870 and r255871
Hi,
Nothing that I changes should have affected the ahci driver. In
fact, I tested this driver specifically during my development. Can
you confirm that you built both kernel and modules from a clean state?
[tiger@laptop]:/usr/src%svn st
M sys/boot/i386/zfsboot/zfsboot.c
[tiger@laptop]:/usr/src%svn diff
Index: sys/boot/i386/zfsboot/zfsboot.c
===================================================================
--- sys/boot/i386/zfsboot/zfsboot.c (revision 255873)
+++ sys/boot/i386/zfsboot/zfsboot.c (working copy)
@@ -302,6 +302,7 @@
* region in the SMAP, use the last 3MB of 'extended' memory as a
* high heap candidate.
*/
+ high_heap_size = 0;
if (bios_extmem >= HEAP_MIN && high_heap_size < HEAP_MIN) {
high_heap_size = HEAP_MIN;
high_heap_base = bios_extmem + 0x100000 - HEAP_MIN;
[tiger@laptop]:/usr/src%
nothing more.
Yes, no local source changes, but are you loading the cam or ahci drivers
a loadable modules that might be out of sync now, or did you use a short-
cut for building your kernel, like NO_CLEAN?
I had the same problem with a clean src tree. After commenting out the
ahci line from my kernel conf file, I got these instead:
Sep 27 14:32:10 SN2000 kernel: ata3: setting up DMA failed
Sep 27 14:32:12 SN2000 kernel: ata3: FAILURE - zero length DMA transfer attempte
reverting those two commits solved the issue.
In my case just rebuilding and restarting of sysutils/hal helped.
sysutils/smartmontools needs the same treatment.
BTW thanks for finding this fix :)
--
Guido Falsi <m...@madpilot.net>
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
