On Tue, 26 Jul 2011 08:03:47 -0400, John Baldwin wrote:
> On Monday, July 25, 2011 6:14:12 pm Baptiste Daroussin wrote:
>> On Mon, 25 Jul 2011 21:49:44 +0000, Baptiste Daroussin wrote:
>> > On Mon, 25 Jul 2011 15:19:42 -0400, John Baldwin wrote:
>> >> On Monday, July 25, 2011 2:42:59 pm Baptiste Daroussin wrote:
>> >>> On Mon, 25 Jul 2011 13:09:04 -0400, John Baldwin wrote:
>> >>> > On Sunday, July 24, 2011 9:48:02 am Baptiste Daroussin
wrote:
>> >>> >> Hi,
>> >>> >>
>> >>> >> Trying to upgrade one of my box from 8-stable to 9-current
>> lead
>> >>> >> be to some important problems.
>> >>> >>
>> >>> >> I'm have tried both from sources (svn buildworld etc.) and
>> from
>> >>> >> memdisk provided by allbsd.org.
>> >>> >>
>> >>> >> The motherboard is ASUS P5N-E SLI ACPI BIOS Revision 0901
>> >>> >>
>> >>> >> more informations here :
>> >>> >> http://people.freebsd.org/~bapt/P5N-E.dmidecode.txt and
>> >>> >> http://people.freebsd.org/~bapt/P5N-E.pciconv.txt
>> >>> >
>> >>> > Can you get a verbose dmesg from 8-stable?
>> >>>
>> >>> A boot -v from current memdisk is full of:
>> >>> (aprobe0:ata0:0:1:0): ATAPI_IDENTIFY. ACB: a1 00 00 00 00 40
00
>> 00
>> >>> 00
>> >>> 00 00 00
>> >>> (aprobe0:ata0:0:1:0): CAM status: Command timeout
>> >>>
>> >>> here is the dmesg from boot -v on 8-stable:
>> >>> http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable.txt
>> >>>
>> >>> the xpt_config message disapear by removing sbp from the
kernel
>> >>
>> >> It seems that you have an ATAPI floppy-drive device that 8
>> doesn't
>> >> like:
>> >>
>> >> afd0: setting PIO3
>> >> device_attach: afd0 attach returned 6
>> >>
>> >> Have you tried enabling ATA_CAM on 8 as a test, or removing
the
>> >> ATAPI floppy-drive as a test?
>> >
>> > Ok I'm dumb, I tested atapicam instead of ata_cam.
>> >
>> > I rebuild 8-stable kernel with ATA_CAM and it works (with lots
of
>> > warnings concerning the dvdrw).
>> >
>> > Here is the 8-stable dmesg with boot -v:
>> > http://people.freebsd.org/~bapt/P5NE-dmesg-8-stable-ata_cam.txt
>>
>> New informations it doesn't work either on -CURRENT without
ATA_CAM.
>
> Hmm, can you break into ddb on 9 and run 'show intrcnt' to see if
you
> have non-zero interrupt counts for IRQs 14 and 15?
the result is:
db> show intrcnt
cpu0: timer 4510
irq256: hdac0 1
cpu3: timer 29
cpu1: timer 3036
cpu2: timer 31
db>
I did break at the mountfrom> prompt
If I break before I only have the cpu0 and irq256 entries.
