Date: Mon, 11 Jan 2021 14:28:35 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 252575] panic: camq_remove: Attempt to remove out-of-bounds index -2 from queue Message-ID: <bug-252575-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252575 Bug ID: 252575 Summary: panic: camq_remove: Attempt to remove out-of-bounds index -2 from queue Product: Base System Version: 12.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: pen@lysator.liu.se Just had a server crash on me: Hardware: HP ProLiant DL380G9 with HP H241 HBA:s (ciss) with a couple of external D6020 JBOD SAS boxes filled with 10TB drives. The server crashes at night when backups (writing to it) are running. Stays up fairly well during daytime. ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request ciss0: WARNING: completing non-busy request panic: camq_remove: Attempt to remove out-of-bounds index -2 from queue 0xfffff8010745e838 of size 5 cpuid =3D 3 time =3D 1610229478 KDB: stack backtrace: #0 0xffffffff80c1e9a7 at kdb_backtrace+0x67 #1 0xffffffff80bd171d at vpanic+0x19d #2 0xffffffff80bd1573 at panic+0x43 #3 0xffffffff80370f76 at camq_remove+0xf6 #4 0xffffffff803742e8 at xpt_run_devq+0x168 #5 0xffffffff803738f6 at xpt_action_default+0x836 #6 0xffffffff803a50b9 at dastart+0x2f9 #7 0xffffffff80375cf2 at xpt_run_allocq+0x172 #8 0xffffffff803a6d68 at dastrategy+0x88 #9 0xffffffff80b176e6 at g_disk_start+0x336 #10 0xffffffff80b1ab0c at g_io_request+0x27c #11 0xffffffff80b1ab0c at g_io_request+0x27c #12 0xffffffff82567b37 at zio_vdev_io_start+0x2a7 #13 0xffffffff82563f1c at zio_execute+0xac #14 0xffffffff8256384a at zio_nowait+0xca #15 0xffffffff8253e678 at vdev_queue_io_done+0x148 #16 0xffffffff82567e01 at zio_vdev_io_done+0x151 #17 0xffffffff82563f1c at zio_execute+0xac I'm guessing this is due to some drive having problems. Currently unclear w= hich though. Trying to upgrade to 12.2 and we'll see if it behaves better... --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252575-227>