From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Wed, 25 Oct 2017 11:43:22 +0300 (EEST) From: Meelis Roos To: Lorenzo Pieralisi cc: linux-alpha@vger.kernel.org, Linux Kernel list , linux-pci@vger.kernel.org Subject: Re: alpha boot hang - 4.14-rc* regression In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: (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. lspci -vvv from broken kernel with no libata loaded: 00:07.0 ISA bridge: ULi Electronics Inc. M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] (rev c3) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR-