Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Can't boot -curent in qemu

On 14.04.12 15:34, Paul Goyette wrote:
> On Sat, 14 Apr 2012, Paul Goyette wrote:
>> On Sat, 14 Apr 2012, Christoph Egger wrote:
>>>>> This is a GENERIC kernel built from sources that were updated about 30
>>>>> minutes ago...
>>>> Yes, that is caused by my last commit that replaces amdtempbus with
>>>> amdnb_miscbus. njoly@ pointed to me pci/pchb.c where amdtempbus was
>>>> also used. I wasn't aware of that at all.
>>>> I am tempted to revert rev 1.32 of pci/pchb.c. But I want to test
>>>> that on monday before I commit.
>>> Paul: Reverting rev 1.32 and rev 1.27 of pci/pchb.c would
>>> that re-open PR 45268 for you?
>> Not sure  Let me see if I still have that machine.  (Seems I forgot to
>> include machine ID in the PR, so this will be hit-or-miss.)
> Yes, this brings back the problem from kern 45268.  I reverted
> pci/pchb.c 1.32 and 1.27, as well as pci/pchbvar.h 1.8 and booted a
> system running Phenom X2 1090T (ASUS M4A88T-M motherboard, with
> 880G/SB710 chipset.  Loading the amdtemp module does not attach the sensor.
> Just as a side note, I noticed that there is no amdtemp sensor found on
> my Bulldozer FX-8150 (M5A99X-EVO motherboard).

Here comes up the question, does it not attach due to an CPU errata or
due to the revert ?

One amdnb_miscX should attach on each northbridge function 3 device.
One amdtempX should attach on amdnb_miscX.
Can you see that in dmesg?


Home | Main Index | Thread Index | Old Index