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

Bug#866511: kernel BUG at nvme/host/pci.c



Control: tag -1 - moreinfo patch

On Thu, 2017-07-06 at 02:47 +0200, Andreas Pflug wrote:
> Am 05.07.17 um 19:31 schrieb Ben Hutchings:
> > Control: reassign -1 src:linux 4.9.30-2+deb9u2
> > Control: tag -1 upstream patch moreinfo
> > 
> > On Thu, 2017-06-29 at 19:30 +0200, Andreas Pflug wrote:
> > > Package: linux-image-4.9.0-3-amd64
> > > 
> > > Version: 4.9.30-2+deb9u2
> > > 
> > > When starting an ancient Windows Server 2003 virtual machine on a fully
> > > updated stretch host, the host will crash repeatably about 10 seconds
> > > after start. Kernel logging was implemented over netconsole, so I could
> > > capture the kernel output stating
> > > 
> > > kernel BUG at /build/linux-9uDFZV/linux-4.9.30/drivers/nvme/host/pci.c:495!
> > 
> > A single log line is rarely enough to be useful...
> > 
> > > Hardware is dual E5-2620v4 on Supermicro 10DRI-T with two SAMSUNG
> > > MZQLW960HMJP-00003 NVME disks (mdadm RAID-1).
> > > 
> > > drivers/nvme/host/pci.c wasn't changed up to 4.11.8, the crashing
> > > function nvme_setup_prps still the same in 4.12rc7, so I guess the bug
> > > is still there.
> > 
> > ...but I happened to see a fix that mentioned this function.
> > 
> > This should make its way into a stable update eventually, but perhaps
> > you could confirm that the attached patch fixes your problem by
> > following these instructions:
> > https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
> 
> The description of the patch seems very promising, but using the
> 4.9.30-2+deb9u2a~test kernel the bug happens as well.
> Log is attached, cut after 460 lines: the last trace on CPU15 is
> repeated all over again, eventually leading to "Fixing recursive fault
> but reboot is needed!"

Thanks for checking.

Ben.

-- 
Ben Hutchings
Man invented language to satisfy his deep need to complain. - Lily
Tomlin

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: