NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/55699: Panic certainly in iSCSI initiator

The following reply was made to PR kern/55699; it has been noted by GNATS.

From: David Holland <>
Subject: Re: kern/55699: Panic certainly in iSCSI initiator
Date: Wed, 9 Jun 2021 05:48:47 +0000

 not sent to gnats (send PR responses to gnats-bugs@)
 From: BERTRAND Jo?l <>
 To: Paul Goyette <>
 Subject: Re: kern/55699: Panic certainly in iSCSI initiator
 Date: Thu, 8 Oct 2020 17:24:29 +0200
 Paul Goyette a ?crit?:
 > On Wed, 7 Oct 2020, BERTRAND Jo?l wrote:
 >> Paul Goyette a ?crit?:
 >>> That confirms that the module is being auto-loaded and -unloaded
 >>> So now we just have to identify where it is being used-after-unload.
 >> ????Yes, I understand, but I don't see how this trouble can be related to
 >> bacula. I have checked in sources and I haven't find any line of code
 >> related to ab usb device.
 > Something in bacula is invoking usbdevs, either directly or via the
 > same ioctl.? Perhaps it is in some library dependency?? I don't know,
 > I don't use bacula.? But that's what triggers your crash.
 	Hi Paul,
 	A second workstation has paniced today with the same traceback (and
 _without_ any USB special device, only a keyboard, no mouse). This
 workstation doesn't run bacula. Thus, this bug is surely triggered by
 bacula but can occur without this application.
 	If I remember, I have seen on my server the same panic (similar
 traceback) last month, before I have installed bacula.
 	Something should be wrong around vfs.
 	Best regards,

Home | Main Index | Thread Index | Old Index