OK, just to clarify: The kernel is 5.3 with the official patches applied, no other modifications.
I read through the changes for 5.4 and certainly, there has been a ton of work done, and I will upgrade soon. Nothing listed in the changes seems like it would directly address a problem like this, so I'd guess it's not a bug though. It certainly *seems* like it could be a hardware problem that's just not throwing an error (yet). So, I guess what I'm asking everyone is: Other than what I've done, what are some ways I can investigate this further to determine where the problem lies? For example, let's say it *is* a failing hard drive in the softraid, and the system just hasn't failed the drive yet, because the operations still complete, just really slowly. What tools/techniques could I use to see that a process is waiting for a disk operation that's taking forever to complete? Thanks, -John On Sat, Nov 30, 2013 at 9:39 PM, Kenneth R Westerback < kwesterb...@rogers.com> wrote: > On Sat, Nov 30, 2013 at 07:04:44PM -0600, Shawn K. Quinn wrote: > > On Sat, Nov 30, 2013, at 03:55 PM, Kenneth R Westerback wrote: > > > On Sat, Nov 30, 2013 at 04:02:58PM -0500, John Hynes wrote: > > > > OpenBSD 5.3 (GENERIC.MP) #0: Fri Sep 13 04:11:52 EDT 2013 > > > > j...@hytronix-gw1.hytronix.com:/usr/src/sys/arch/amd64/compile/ > > > > GENERIC.MP > > > > > > Try 5.4 or -current. > > > > > > Issues with non-home-compiled kernels are more interesting. > > > > I thought as long as it was an unmodified GENERIC or GENERIC.MP that the > > issue was still valid. Is this no longer the case? > > > > -- > > Shawn K. Quinn > > skqu...@rushpost.com > > > > Sure - but if it's unmodified, why compile a new one? And John did > not state in his email that it was unmodified. > > .... Ken
