On 02/22/13 06:08, Claude Buisson wrote:
On 02/22/2013 09:21, Konstantin Belousov wrote:
<skipped>
You need to provide the dmesg from r246713 and r246712 to compare.
The note that r246711 snapshot exhibited this same problem makes
me sceptical.
Here are the verbose dmesg from r246712 and r246713;
For the sceptical:
root@fidel# cd /usr/src
root@fidel# grep "\$FreeBSD\:" sys/conf/files
# $FreeBSD: head/sys/conf/files 246586 2013-02-09 06:39:28Z delphij $
root@fidel# grep "\$FreeBSD\:" sys/ia64/ia64/dump_machdep.c
__FBSDID("$FreeBSD: head/sys/ia64/ia64/dump_machdep.c 246712 2013-02-12
16:51:43Z marcel $");
for r246712
root@fidel# cd /usr/src
root@fidel# grep "\$FreeBSD\:" sys/conf/files
# $FreeBSD: head/sys/conf/files 246713 2013-02-12 16:57:20Z kib $
root@fidel# grep "\$FreeBSD\:" sys/ia64/include/proc.h
* $FreeBSD: head/sys/ia64/include/proc.h 226112 2011-10-07 16:09:44Z
kib $
for r246713
The source is from svn0.us-east.freebsd.org
And obj/ has been rm'ed before each buildkernel
My own conclusion is that the rev number in:
FreeBSD-10.0-HEAD-r246711-JPSNAP-i386-i386-memstick.img
is bogus, and this can be easily checked by grepping for
kern/subr_bus_dma.c in
the BUILD.log as this file has been ADDED by r246713
CBu (working on this since Tuesday)
For whatever it is worth, I have experienced the identical problem on an
amd64 system.
-Nathan
_______________________________________________
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"
