lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440901052209k6785a2f6i755a758d087892f@mail.gmail.com>
Date:	Mon, 5 Jan 2009 22:09:03 -0800
From:	"Yinghai Lu" <yinghai@...nel.org>
To:	david@...g.hm
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Cyrill Gorcunov" <gorcunov@...il.com>,
	"Jiri Slaby" <jirislaby@...il.com>,
	"Andi Kleen" <andi@...stfloor.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: early exception error

On Mon, Jan 5, 2009 at 9:29 PM,  <david@...g.hm> wrote:
> On Mon, 5 Jan 2009, Yinghai Lu wrote:
>
>> david@...g.hm wrote:
>>>
>>> On Mon, 5 Jan 2009, Yinghai Lu wrote:
>>>
>>>> david@...g.hm wrote:
>>>>>
>>>>> On Mon, 5 Jan 2009, Yinghai Lu wrote:
>>>>>
>>>>>
>>>>> this motherboard is a Tyan Thunder K8S Pro S2882
>>>>>
>>>>> I just uploaded some snapshots of the bios screens
>>>>
>>>> please try to update the BIOS. the installed BIOS seems has problem...
>>>>
>>>> http://tyan.com/support_download_bios.aspx?model=S.S2882
>>>
>>> what problems are you seeing (i.e. what did I miss seeing that would
>>> have pointed me in this direction without eating everyone's time)
>>>
>>
>> you should get 4g ram instead of 3g according to e820.
>>
>> BIOS should set ram routing correctly according to iommu (gart) and
>> memhole etc.
>
> this seems to have solved the problem

can you post boot log and lspci -vvxxx ?

>
> I do have another of these systems if there is any desire to do any more
> troubleshooting (it would be really nice if things died with a better error
> message for example)

good,
0. setup serial cable between your two system. use minicom in your
first system to capture serial message from second system
1. apply attached patch
2. we need full boot log of your second system. please boot with "
debug console=uart8250,io,0x3f8,115200n8 pci=earlydump"

YH

View attachment "mminit_loglevel_2.patch" of type "text/x-patch" (1060 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ