Full information for the link you posted: https://marc.info/?l=openbsd-bugs&m=147289791725770&w=2
Another similar panic: http://marc.info/?l=openbsd-bugs&m=147280147503809&w=2 I'm not sure if this effectively fixed the problem for me, but since I changed 'Intel AHCI ROM' to 'BIOS Native Module' in the BIOS I have not seen it again. On Sat, Sep 24, 2016 at 02:11:27PM -0500, Brian Conway wrote: > These were brought to my attention off-list, my bad on searching tech@ > and misc@ and not bugs@: > > https://marc.info/?l=openbsd-bugs&m=144916404213169&w=2 > > https://marc.info/?l=openbsd-bugs&m=147289791725770&w=2 > > It's probably not much help due to the wide time window, but I forgot > to mention that the same hardware and configuration ran 5.9-stable > (and 5.8-stable before that) through many uneventful reboots. Thanks. > > Brian Conway > > On Fri, Sep 23, 2016 at 12:00 PM, Brian Conway <[email protected]> > wrote: > > Greetings. I apologize in advance if this report is not helpful due to > > a less conventional disk setup (root on USB flash, SR RAID 1 on two > > 2TB drives). I've had the following crash twice now with 6.0-stable > > when attempting to reboot, at the point where it would normally say > > "sd3 detached": > > > > syncing disks... done > > kernel: protection fault trap, code=0 > > Stopped at bufq_destroy+0x83: movq 0(%rdx),%rax > > ddb{0}> > > > > A freshly booted system can be rebooted all day long without issue, > > the problem seems to manifest when the system has been running NFS and > > Samba duties for a couple weeks and a low number of clients (< 5) are > > connected. Supporting info (ddb panic/trace/ps/registers, dmesg, > > disklabel, atactl) follows, thanks for your time. > > > > Brian >
