Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 Sep 2009 14:54:07 +0300
From:      Andriy Gapon <avg@freebsd.org>
To:        John Baldwin <jhb@freebsd.org>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: amd64/138882: Can't install FreeBSD 7.2
Message-ID:  <4AB7695F.40702@freebsd.org>
In-Reply-To: <4AB3AC4E.4060506@freebsd.org>
References:  <200909171300.n8HD0GbZ059265@freefall.freebsd.org>	<20090918102700.7ba596a6.torfinn.ingolfsen@broadpark.no> <4AB3590A.5040805@FreeBSD.org> <4AB39719.5030709@icyb.net.ua> <4AB3AC4E.4060506@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
on 18/09/2009 18:50 Andriy Gapon said the following:
> on 18/09/2009 17:20 Andriy Gapon said the following:
>> I am debugging a somewhat related problem with head code and SB700 ohci.
>> The problem is that certain ports become unusable of there is a keyboard or mouse
>> attached to them during boot.
>> My findings so far:
>> 1) the problem happens only with ports provided by ohci0 (the very first PCI OHCI
>> device)
>> 2) the problem is that some configuration registers of ohci controller get
>> mysteriously changed after ohci driver configures them and before the first
>> interrupt gets generated by the controller; registers in question are
>> HcControlHeadED and HcDoneHead.
>>
>> Looks like perhaps either the controller doesn't get "sufficiently"
>> reset/re-initialized or firmware/SMM code touches the controller after handover
>> procedure completes.
> 
> My current suspicion is that ohci(4) doesn't clear some memory that it allocates
> for shared use with HC (hardware) and sets a HC register to point to that memory.
> So when HC goes to operation state and examines that memory and sees something
> that looks like valid data, HC uses it and goes bad way.
> 
> But this is just a hypothesis that I've just dreamed up.
> I am going to test it some time later.

This theory turned out to be incorrect, but investigation of it gave some insights
 that hopefully should become a basis for a fix.


-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AB7695F.40702>