On Sat, Apr 14, 2018 at 11:32:00PM -0500, Juan Morado wrote:
> Here's the text as best I can see it.
>
> uvm_fault (0xffffffffc1afca80, 0xffff8000008ca000, 0, 1) -> e
> kernel: page fault trap, code=0
> Stopped at ihidev_intr+0x18a: movzbl 0(%rsi,%rax,1),%eax
> ddb{0}>
>
> On the same hardware, I did occasionally get some errors logged to the
> console running 6.2, IIRC something about an invalid value from ihiddev,
> but it didn't crash or hang.
>
Can you show the output of "show reg" at ddb?
PS, this bug report leaves a lot to be desired...
-ml
> On Sat, Apr 14, 2018 at 8:06 PM, Mike Larkin <[email protected]> wrote:
>
> > On Sat, Apr 14, 2018 at 04:47:32PM -0500, Juan Morado wrote:
> > > On Fri, Apr 13, 2018 at 1:18 PM, Mike Larkin <[email protected]>
> > wrote:
> > >
> > > > On Thu, Apr 12, 2018 at 10:19:23PM -0500, Juan Morado wrote:
> > > > > Hi all,
> > > > >
> > > > > I searched the mail archives briefly but couldn't find a related
> > issue.
> > > > > Apologies if this is a duplicate.
> > > > >
> > > > > Since upgrading to OpenBSD 6.3 on my amd64 laptop, it has been
> > crashing
> > > > > whenever I touch the track pad.
> > > > >
> > > > > Touching the track pad after X starts generally causes the machine to
> > > > just
> > > > > hang, however, it also crashes during boot if the track pad is
> > touched
> > > > so I
> > > > > was able to get a dump from ddb.
> > > > >
> > > > > Output from dmesg follows. I also have bsd.0.core, bsd.0, bounds,
> > minfree
> > > > > files from the crash dump. If there is any interest in looking at
> > these,
> > > > > please advise the best way to share them.
> > > > >
> > > > > - JM
> > > > >
> > > > > ---
> > > >
> > > > Where's the panic string?
> > > >
> > >
> > > Hell if I know.
> > >
> > > Maybe kernel panic isn't the correct terminology? ddb is invoked anytime
> > I
> >
> > So what does it say on the screen when you are in ddb?
> >
> > > touch the track pad while booting. Touching the track pad once X starts
> > > causes the machine to become unresponsive. I don't recall if the dmesg
> > was
> > > taken immediately following the crash or not. As I mentioned I was able
> > to
> > > generate a dump and I can share those dump files.
> >
> >
> >
