> On Nov 2, 2018, at 12:59 AM, Daniel Dickman <[email protected]> wrote:
>
>
>
>> On Oct 31, 2018, at 11:38 PM, Jonathan Gray <[email protected]> wrote:
>>
>>> On Wed, Oct 31, 2018 at 10:16:40PM +0100, Christian Weisgerber wrote:
>>> Jonathan Gray:
>>>
>>>> These machines appear to have a serial port so you should be able to get a
>>>> proper trace with the console on serial.
>>>
>>> Right. What do you need? Here's the ddb trace after the uvm_fault:
>>
>> Ah yes, that has been seen before when trying to run i386 on a recent
>> intel machine not seen with amd64. I ran into that when running i386 on
>> an x230 (ivy bridge) with 8gb physram as well. Doesn't occur with machines
>> that use inteldrm with intagp like x40.
>
> same problem here.
>
> dmesg at http://dickman.org/openbsd/dmesg/dmesg.dell
seems like 6.2 doesn’t work, but 6.1 works.
narrowing it down slightly:
- kernel from 20170625 seems to work
- kernel from 20170705 seems bad
This period of time covers about 300 commits (ie. see git log
a1ae353...e12511f).
this range includes the big update to sync inteldrm to linux 4.4.70 that
happened on july 1st, 2017.
so i don’t have complete evidence, but i strongly suspect this is the commit in
question:
https://github.com/openbsd/src/commit/e0b53cee
anything i should try?
