On Tue, Apr 24, 2018 at 02:25:24PM +0200, Alexander Bluhm wrote:
> On Tue, Apr 24, 2018 at 08:18:42PM +1000, Jonathan Gray wrote:
> > After spending some time trying to track this down I have come up with
> > the diff below and included it in ~jsg/radeon.diff.4 can you confirm
> > that it works for
On Tue, Apr 24, 2018 at 08:18:42PM +1000, Jonathan Gray wrote:
> After spending some time trying to track this down I have come up with
> the diff below and included it in ~jsg/radeon.diff.4 can you confirm
> that it works for you as well?
With this diff my machine boots fine. No monitor connect,
On Tue, Apr 24, 2018 at 01:53:07PM +0200, Mark Kettenis wrote:
> > Date: Tue, 24 Apr 2018 20:18:42 +1000
> > From: Jonathan Gray
> >
> > On Wed, Apr 18, 2018 at 06:55:35PM +0200, Alexander Bluhm wrote:
> > > On Thu, Apr 19, 2018 at 12:10:04AM +1000, Jonathan Gray wrote:
> > > > That's with the bi
> Date: Tue, 24 Apr 2018 20:18:42 +1000
> From: Jonathan Gray
>
> On Wed, Apr 18, 2018 at 06:55:35PM +0200, Alexander Bluhm wrote:
> > On Thu, Apr 19, 2018 at 12:10:04AM +1000, Jonathan Gray wrote:
> > > That's with the big radeon update diff as well?
> >
> > That was current. Boots fine.
> >
On Wed, Apr 18, 2018 at 06:55:35PM +0200, Alexander Bluhm wrote:
> On Thu, Apr 19, 2018 at 12:10:04AM +1000, Jonathan Gray wrote:
> > That's with the big radeon update diff as well?
>
> That was current. Boots fine.
>
> With ~jsg/radeon.diff.2 it still crashes. I have checked, it is
> the diff
On Fri, Apr 20, 2018 at 10:28:22AM +1000, Jonathan Gray wrote:
> On Thu, Apr 19, 2018 at 09:46:54AM -0700, Carlos Cardenas wrote:
> > On Thu, Apr 19, 2018 at 03:03:51PM +1000, Jonathan Gray wrote:
> > > On Wed, Apr 18, 2018 at 06:59:42PM -0700, Carlos Cardenas wrote:
> > > > On Thu, Apr 19, 2018 at
On Thu, Apr 19, 2018 at 09:46:54AM -0700, Carlos Cardenas wrote:
> On Thu, Apr 19, 2018 at 03:03:51PM +1000, Jonathan Gray wrote:
> > On Wed, Apr 18, 2018 at 06:59:42PM -0700, Carlos Cardenas wrote:
> > > On Thu, Apr 19, 2018 at 09:35:19AM +1000, Jonathan Gray wrote:
> > > > On Wed, Apr 18, 2018 at
On Thu, Apr 19, 2018 at 03:03:51PM +1000, Jonathan Gray wrote:
> On Wed, Apr 18, 2018 at 06:59:42PM -0700, Carlos Cardenas wrote:
> > On Thu, Apr 19, 2018 at 09:35:19AM +1000, Jonathan Gray wrote:
> > > On Wed, Apr 18, 2018 at 03:29:10PM -0700, Carlos Cardenas wrote:
> > > > Howdy.
> > > >
> > > >
On Wed, Apr 18, 2018 at 08:30:16PM +1000, Jonathan Gray wrote:
> On Wed, Apr 18, 2018 at 11:40:06AM +0200, Alexander Bluhm wrote:
> > Hi,
> >
> > my i386 regression test machine crashed with the Tue Apr 17 snapshot
> > in radeondrm_attachhook().
>
> So the machine doesn't have /etc/firmware/radeo
On Wed, Apr 18, 2018 at 06:59:42PM -0700, Carlos Cardenas wrote:
> On Thu, Apr 19, 2018 at 09:35:19AM +1000, Jonathan Gray wrote:
> > On Wed, Apr 18, 2018 at 03:29:10PM -0700, Carlos Cardenas wrote:
> > > Howdy.
> > >
> > > Please excuse this poor bug report, I'm not able to obtain more info as
>
On Thu, Apr 19, 2018 at 09:35:19AM +1000, Jonathan Gray wrote:
> On Wed, Apr 18, 2018 at 03:29:10PM -0700, Carlos Cardenas wrote:
> > Howdy.
> >
> > Please excuse this poor bug report, I'm not able to obtain more info as
> > the system locks hard (below is transcribed by hand).
> >
> > On a clean
On Wed, Apr 18, 2018 at 03:29:10PM -0700, Carlos Cardenas wrote:
> Howdy.
>
> Please excuse this poor bug report, I'm not able to obtain more info as
> the system locks hard (below is transcribed by hand).
>
> On a clean install, with the latest snap (as of time of email):
> OpenBSD 6.3-current (
Howdy.
Please excuse this poor bug report, I'm not able to obtain more info as
the system locks hard (below is transcribed by hand).
On a clean install, with the latest snap (as of time of email):
OpenBSD 6.3-current (GENERIC.MP) #207: Wed Apr 18 11:37:15 MDT 2018
CPU: AMD A8-7670K Radeon R7 aka
On Thu, Apr 19, 2018 at 12:10:04AM +1000, Jonathan Gray wrote:
> That's with the big radeon update diff as well?
That was current. Boots fine.
With ~jsg/radeon.diff.2 it still crashes. I have checked, it is
the diff with
if (rdev->rio_mem_size > 0)
bus_space_unmap(rdev-
On Wed, Apr 18, 2018 at 03:09:08PM +0200, Alexander Bluhm wrote:
> On Wed, Apr 18, 2018 at 10:29:30PM +1000, Jonathan Gray wrote:
> > sys/dev/pci/drm/drm_linux.h rev 1.85 should help
>
> I have compiled and successfully booted a kernel with that commit.
>
> bluhm
>
That's with the big radeon up
On Wed, Apr 18, 2018 at 10:29:30PM +1000, Jonathan Gray wrote:
> sys/dev/pci/drm/drm_linux.h rev 1.85 should help
I have compiled and successfully booted a kernel with that commit.
bluhm
On Wed, Apr 18, 2018 at 02:15:50PM +0200, Alexander Bluhm wrote:
> On Wed, Apr 18, 2018 at 08:30:16PM +1000, Jonathan Gray wrote:
> > On Wed, Apr 18, 2018 at 11:40:06AM +0200, Alexander Bluhm wrote:
> > > my i386 regression test machine crashed with the Tue Apr 17 snapshot
> > > in radeondrm_attach
On Wed, Apr 18, 2018 at 08:30:16PM +1000, Jonathan Gray wrote:
> On Wed, Apr 18, 2018 at 11:40:06AM +0200, Alexander Bluhm wrote:
> > my i386 regression test machine crashed with the Tue Apr 17 snapshot
> > in radeondrm_attachhook().
>
> So the machine doesn't have /etc/firmware/radeon/R100_cp.bin
On Wed, Apr 18, 2018 at 08:30:16PM +1000, Jonathan Gray wrote:
> On Wed, Apr 18, 2018 at 11:40:06AM +0200, Alexander Bluhm wrote:
> > Hi,
> >
> > my i386 regression test machine crashed with the Tue Apr 17 snapshot
> > in radeondrm_attachhook().
>
> So the machine doesn't have /etc/firmware/radeo
On Wed, Apr 18, 2018 at 11:40:06AM +0200, Alexander Bluhm wrote:
> Hi,
>
> my i386 regression test machine crashed with the Tue Apr 17 snapshot
> in radeondrm_attachhook().
So the machine doesn't have /etc/firmware/radeon/R100_cp.bin ?
I have an i386 laptop that loads r100 microcode which works.
Hi,
my i386 regression test machine crashed with the Tue Apr 17 snapshot
in radeondrm_attachhook().
uvm_fault(0xd0ccfb70, 0xd11e, 0, 1) -> e
kernel: page fault trap, code=0
Stopped at pmap_page_remove_pae+0x18: cmpl$0,0x48(%edi)
pmap_page_remove_pae(d11e0800) at pmap_page_remov
21 matches
Mail list logo
