> > (Added linux-pci to CC)
> >
> > > > I run Gentoo Linux on my alphas, with latest git kernels for test.
> > > > 4.13.0 worked well on 3 alphas but 4.13.0-09217-g5969d1bb3082 hangs on
> > > > boot on all 3 of them. Tried bisecting on PC164, got into unrelated
> > > > stuff, so probably it does not trigger always. Retried bisecting on
> > > > DS10L. On the first try I got that the same keel where I first saw bad
> > > > was the culprit, another bisect led me to
> > > > 0e4c2eeb758a91e68b9eaf7a4bee9bd5ed97ff2b which looks more related.
> > > >
> > > > This is how the crash looks on console:
> > > >
> > > > * Starting udev ...
> > > > starting version 225
> > > > [ ok ]
> > > > * Generating a rule to create a /dev/root symlink ...
> > > > [ ok ]
> > > > * Populating /dev with existing devices through uevents ...
> > > > [ ok ]
> > > >
> > > > halted CPU 0
> > > >
> > > > halt code = 5
> > > > HALT instruction executed
> > > > PC = fffffc00009bf914
> > > > boot failure
> > > > >>>
> > > >
> > > > What else can I do to debug this?
> > >
> > > Booting with debug ignore_loglevel I get also this:
> > [...]
> > > So maybe it is related pcspkr loading, or the just loaded libata or
> > > floppy...
> >
> > removing libata modules and rebooting fixes it - so it seems to be
> > loading of libata.
>
> Can you please cherry-pick:
>
> commit b1f9e5e355e9 ("ide: fix IRQ assignment for PCI bus order probing")
>
> from mainline and let us know if that solves the issue ?
No, still breaks the same way (b1f9e5e355e9 patched on top of
0e4c2eeb758a).
4.14.0-rc5-00095-g1c9fec470b81 was also still broken the same way (tried
on Sunday).
--
Meelis Roos (mroos@xxxxxxxx)
