Re: Kernel panic with usbverbose (?)

[Michael van Elst <mlelstv%serpens.de@localhost>]

On Sat, Oct 10, 2020 at 03:59:17PM +0200, Manuel Bouyer wrote:
> On Sat, Oct 10, 2020 at 02:30:43PM +0200, BERTRAND Joël wrote:
> > 11514445105-11514445168 (sd0 bn 11514445105; cn 5622287 tn 41 sn 17)
> > [  8900.078912] sd0d: error writing fsbn 11514445169 (sd0 bn
> > 11514445169; cn 5622287 tn 43 sn 17)
> > [  8909.342671] uvm_fault(0xffffffff8151f760, 0xffffba0020ad0000, 1) -> e
> > [  8909.342671] fatal page fault in supervisor mode
> > [  8909.342671] trap type 6 code 0 rip 0xffffffff8026aee8 cs 0x8 rflags
> > 0x10286 cr2 0xffffba0020ad0070 ilevel 0 rsp 0xffffba013cc18b90
> > [  8909.342671] curlwp 0xffff9974adb6e900 pid 0.175 lowest kstack
> > 0xffffba013cc162c0
> > [  8909.342671] panic: trap
> > [  8909.342671] cpu5: Begin traceback...
> > [  8909.342671] vpanic() at netbsd:vpanic+0x160
> > [  8909.342671] snprintf() at netbsd:snprintf
> > [  8909.342671] startlwp() at netbsd:startlwp
> > [  8909.342671] alltraps() at netbsd:alltraps+0xbb
> > [  8909.342671] dk_start() at netbsd:dk_start+0x102

> So your disk is bad, with write errors, and it looks like there is
> a bug in dk in this case

That's the iscsi disk. My guess is that re(4) somehow trashes memory
when you use jumbo frames.

That should of course be fixed. On the other hand, these are of
questionable benefit, especially for iscsi.


Greetings,
-- 
                                Michael van Elst
Internet: mlelstv%serpens.de@localhost
                                "A potential Snark may lurk in every tree."