Problem reporting without dmesg????? Sorry, but I am reaching for my d key.
Solene Rapenne <sol...@perso.pw> wrote: > On Fri, Oct 04, 2019 at 11:38:52AM -0400, Daniel Dickman wrote: > > > > > > > On Oct 4, 2019, at 9:56 AM, Solene Rapenne <sol...@perso.pw> wrote: > > > > > > Hi, > > > > > > did someone else did experience freezes issues recently? I had two > > > freezes in > > > one day. > > > > > > First time I was doing heavy CPU use and assumed something went wrong, or > > > heat > > > I don't know. Second time, I was thinking about typing something in a > > > mail, the > > > system was totally idle. > > > > Hi Solene, I’m not sure if this is related but I’m seeing console freezes > > on my i386 laptop. > > > > I’m not using X, just the console. And I believe I’ve experienced these > > freezes with and without drm enabled. > > > > The symptoms for me are the keyboard stops working for certain letters. And > > then the console freezes completely shortly after that. > > > > I’m able to recover from this by switching to a different console and then > > doing “kill -9” on the stuck ksh process. > > > > When your system freezes, are you able to switch to a different console? Or > > can you still ssh into it? > > > > I’m not sure if it’s a hardware issue on my end or some bug and wasn’t > > exactly sure how to debug this as I can’t reproduce easily. > > > > Things I tried: > > 1) using historical kernels, but all the kernels I tried so far don’t solve > > the problem. > > > > 2) ktracing the ksh processes on each console to see if there’s something > > obvious that triggers the problem. I’m working on getting some traces but I > > haven’t managed so far because the freezes are so random. > > > > Things I’m thinking of trying: > > > > 1) installing a different OS to check if it’s a hardware problem. > > > > 2) reinstalling 6.4 and 6.5 to see if I see the same problem. If yes then > > likely a hardware problem because I used those releases in the past without > > any issues. > > > > When it freezes, network stops responding and switching to tty doesn't > work. > > I can't reproduce this, so the sad state of using another OS or a > previous OpenBSD version would waste my time not working on -current. >