On Tue, 2017-10-03 at 12:42 -0700, Vagrant Cascadian wrote:
> On 2017-10-03, Ben Hutchings wrote:
> > On Tue, 2017-10-03 at 11:28 -0700, Vagrant Cascadian wrote:
> > > Control: found 4.13.4-1 4.14~rc3-1~exp1
> > > 
> > > On 2017-10-02, Debian Bug Tracking System wrote:
> > > > This is an automatic notification regarding your Bug report
> > > > which was filed against the src:linux package:
> > > > 
> > > > #843448: linux-image-4.8.0-1-armmp-lpae: fails to boot on
> > > > Odroid-Xu4 with rootfs on USB
> > > 
> > > It seems only partially fixed...
> > > 
> > > With 4.13.4-1 it usually detects the USB device, but I've gotten
> > > several
> > > boots where it kernel panics on mounting swap (an lvm volume on
> > > the USB
> > > device) or sometimes on unmounting swap as part of powerdown or
> > > reboot. Not really any better luck with 4.14~rc3-1~exp1.
> > 
> > [...]
> > 
> > Is this still the same bug?
> 
> Could be different. Though I have infrequently seen something
> more-or-less identical to the originally reported issue with the
> "connect debounce" messages with the fixed 4.13 and 4.14 kernels; I
> haven't been able to reproduce them to capture a log just yet...
> 
> 
> > Can you send the panic messages?
> 
> Attached should be a few logs with different panic/exception
> messages.
> 
> It doesn't cover all of the failure cases I've seen, as I haven't
> managed to capture the logs of all of the boots I've done...

These logs are showing three very different crashes:

1. Null dereference in bio_integrity_advance() during SCSI request
   completion (odxu4a-oops.log, odxu4a-swap-panic.log)
2. WARN at the bottom of rcu_check_callbacks() (odxu4a-swap-trace.log)
3. Null dereference in xhci_irq() (odxu4a-swap-panic-4.13.log)

They all seem to be associated with initialisation of USB host and
device drivers, but none of them are obviously related to this bug
report.  So I think these should be treated as 3 new bugs.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
                                    A fail-safe circuit will destroy
others.

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

Reply via email to