On 2021-12-11 5:39 a.m., Mark Kettenis wrote:
>> Date: Sat, 11 Dec 2021 05:10:41 -0700
>> From: Ted Bullock
>
> The are several reasons why that test can fail though. It can be an
> endian-ness issue or on sparc64 it could also be an IOMMU issue where
> the wrong address is programmed into the h
On Sat, Dec 11, 2021 at 10:25:13AM +, Visa Hankala wrote:
> > Some of these "missing" entries may be caused by transitive lock order
> > relations that are not handled by the lock order printer.
> >
> > I have somewhere a diff that improves the situation. Let's see if I can
> > find it...
>
>
On Sat, Dec 11, 2021 at 09:58:54AM +0100, Mark Kettenis wrote:
> This one may be harmless. The first backtrace is from executing
> init(8), which only happens once and happens in a somewhat strange
> manner.
This happens in some /usr/src/regress/misc/posixtestsuite test.
It needs pkg_add posixtes
> Date: Sat, 11 Dec 2021 05:10:41 -0700
> From: Ted Bullock
>
> On 2021-12-11 4:41 a.m., Mark Kettenis wrote:
> >> Date: Fri, 10 Dec 2021 17:24:58 -0700
> >> From: Ted Bullock
> > So the real problem is:
> >
> >> [drm] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
> >> [drm] *ER
On Sat, Dec 11, 2021 at 12:41:46PM +0100, Mark Kettenis wrote:
> > Date: Fri, 10 Dec 2021 17:24:58 -0700
> > From: Ted Bullock
> >
> > On 2021-12-10 12:53 a.m., Jonathan Gray wrote:
> > > On Thu, Dec 09, 2021 at 10:01:30PM -0700, Ted Bullock wrote:
> > >> Thoughts folks? This is clearly going to
On 2021-12-11 4:41 a.m., Mark Kettenis wrote:
Date: Fri, 10 Dec 2021 17:24:58 -0700
From: Ted Bullock
So the real problem is:
[drm] *ERROR* radeon: ring test failed (scratch(0x15E4)=0xCAFEDEAD)
[drm] *ERROR* radeon: cp isn't working (-22).
drm:pid0:r100_startup *ERROR* failed initializing CP
> Date: Fri, 10 Dec 2021 17:24:58 -0700
> From: Ted Bullock
>
> On 2021-12-10 12:53 a.m., Jonathan Gray wrote:
> > On Thu, Dec 09, 2021 at 10:01:30PM -0700, Ted Bullock wrote:
> >> Thoughts folks? This is clearly going to impact all big endian + radeon
> >> gear.
> >>
> >> Actually, I bet that t
On Sat, Dec 11, 2021 at 09:37:08AM +, Visa Hankala wrote:
> On Sat, Dec 11, 2021 at 09:58:54AM +0100, Mark Kettenis wrote:
> > > Date: Sat, 11 Dec 2021 01:13:32 +0100
> > > From: Alexander Bluhm
>
> > > witness: lock order reversal:
> > > 1st 0xfd886921d8d8 vmmaplk (&map->lock)
> > > 2n
On Sat, Dec 11, 2021 at 09:58:54AM +0100, Mark Kettenis wrote:
> > Date: Sat, 11 Dec 2021 01:13:32 +0100
> > From: Alexander Bluhm
> > witness: lock order reversal:
> > 1st 0xfd886921d8d8 vmmaplk (&map->lock)
> > 2nd 0x800022c54130 nfsnode (&np->n_lock)
> > lock order data w2 -> w1 miss
> Date: Sat, 11 Dec 2021 01:13:32 +0100
> From: Alexander Bluhm
>
> Hi,
>
> I have turned on witness during a full regress run on amd64. It
> found two issues. Basically I am posting this as baseline, so I
> can see if things get better or worse. If someone wants to fix
> them, I can dig into
10 matches
Mail list logo
