On 24/05/22(Tue) 14:16, Martin Pieuchot wrote:
> On 19/05/22(Thu) 13:33, Alexander Bluhm wrote:
> > On Tue, May 17, 2022 at 05:43:02PM +0200, Martin Pieuchot wrote:
> > > Andrew, Alexander, could you test this and report back?
> >
> > Panic "vref used where vget required" is still there. As
Hi,
weekly bump. Anyone (maybe jcs@) has an idea on how to debug this?
Cheers and thanks
Matthias
* Claudio Miranda wrote:
> Greetings,
>
> I'm the person whom Matthias linked to. Seems as though we're having
> the same issue with the touchpad in spite of them being different
>
On Tue, 31 May 2022 at 15:37:21 +0200, Matthias Schmidt wrote:
> Hi,
>
> weekly bump. Anyone (maybe jcs@) has an idea on how to debug this?
You could enable IHIDEV_DEBUG in ihidev.c and see if it logs
anything when the touchpad freezes.
Hi Joshua,
* joshua stein wrote:
> On Tue, 31 May 2022 at 15:37:21 +0200, Matthias Schmidt wrote:
> > Hi,
> >
> > weekly bump. Anyone (maybe jcs@) has an idea on how to debug this?
>
> You could enable IHIDEV_DEBUG in ihidev.c and see if it logs
> anything when the touchpad freezes.
Thanks,
I accidentally updated a router to -current instead of 7.1 and hit this.
(Thanks sysupgrade - it was running a 7.0-stable kernel before...)
Unfortunately it runs with ddb.panic=0 and this time it hanged, I won't
have time to figure anything out with it when I get it back online, but
might be able
Hi all,
while playing around with TCP Large Receive Offloading for ix I have
configure httpd and relayd on test box.
Same second I've start relayd box panic.
This is latest snapshot and it easely reproduciable..
r420-1# cat /etc/httpd.conf
prefork 4
server "default" {
listen on
On 2022-05-31 23:27 +01, Stuart Henderson wrote:
> I accidentally updated a router to -current instead of 7.1 and hit this.
> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
Hmm? Are you saying running just running 'sysupgrade', without any flags, moves
you from 7.0-stable to
On 1.6.2022. 0:27, Stuart Henderson wrote:
> I accidentally updated a router to -current instead of 7.1 and hit this.
> (Thanks sysupgrade - it was running a 7.0-stable kernel before...)
>
> Unfortunately it runs with ddb.panic=0 and this time it hanged, I won't
> have time to figure anything out