system crashing with 5.2 and 5.0 but not with 4.8

[Matthew Dillon]

EHCI has some sort of niggling problem that I haven't been able to track
down.  I may try to re-port that piece from FreeBSD, if the infrastructure
hasn't diverged too much.  The code in the original port was extremely
fragile.

-Matt

On Sat, Feb 9, 2019 at 9:56 AM <spuelmaschien at email.de> wrote:

> On 10/10/18 7:06 AM, Aaron LI wrote:
> > On Sun, 7 Oct 2018 13:11:42 +0200
> > spuelmaschien at email.de wrote:
> >
> >> Hallo,
> >>
> >> my HP Microserver N40L (Turion2) keeps crashing while or shortly after
> >> installing any 5.x version of DragonFly.
> >> I reinstalled 4.8 and this is running for several days now.
> >>
> >> A memcheck run from a KNOPPIX CD test was successfull.
> >> KNOPPIX itself was also running for several days.
> >>
> >> Below are two ocr-ed screen photographs of these crashes. I do not know
> >> how to keep that text in a more elegant way.
> >>
> >> Now this is kind of a dilemma.
> >> - hardware ok -> run another OS
> >> - hardware defect -> renew server, run dfly ...
> >>
> >> Hopefully there's a better solution.
> >
> > Hi Sascha,
> >
> > According to your panic log below, both were happened during the
> installation
> > phase and related to the EHCI (USB 2.0).
> >
> > Did you use the same USB stick and the same USB port on the machine for
> 4.8,
> > 5.0 and 5.2 installations?  If yes, this is a strange and serious bug.
> >
> > I don't remember there were any EHCI related changes after 4.8.  Maybe
> others
> > have better knowledge about this.
> >
> >
>
> Hallo Aaron,
>
> Finally i did setup the external SATA port to install directly onto
> the SSD which i used via a SATA - USB adapter taken from an
> external harddisk.
> Now it's running without any problems since then and is still running.
> The SSD meanwhile went into the case.
>
> For the external SATA port i had to find a modified BIOS for the HP
> microserver. There are some fans who have the knowledge to modify
> the BIOS and activate the port ...
>
> Thank's for your useful hints.
>
> Tschuess,
>     Sascha
>
>
>
>
>
>
>
>
>
> >> ================= 1 ======================
> >> | /mnt/boot/kernel/radeonkmsfwTAHITI_rlc.ko copy-ok
> >>
> >> panic: Bad link elm 0xffffff8125709368 prev->next != elm
> >> cpuid = 1
> >> Trace beginning at frame 0xffffff81258d2870
> >> panic() at panic+0x236 0xffffffff805ec136
> >> panic() at panic+0x236 0xffffffff805ec136
> >> _callout_stop() at _callout_stop+0x3c3 0xffffffff80610973
> >> callout_reset[) at callout_reset+0x96 0xffffffff80610bd6
> >> ehci_interrupt() at ehci_interrupt+0x198 0xffffffff821aa3d8
> >> ithread_handler() at ithread_handler+0x2e9 0xffffffff805bal09
> >> Debugger("panic")
> >> CPU1 stopping CPUs: 0x00000001
> >> stopped
> >> Stopped at Debugger+0x7c: movb $0,0xd31929(%rip)
> >> db> |
> >> ================= 1 ======================
> >>
> >> ================= 2 ======================
> >> ,-<<< Executing ‘/shin/newfs_hammer -f -L ROoT
> /dev/serno/2011090623F8.s2d'
> >> panic: Bad link elm 0xfffff80125b47368 prev->next != elm
> >> cpuid = 1
> >> Trace beginning at frame 0xfffff80125ccbB870
> >> panic() at panic+0x236 @xffffffff805f8666
> >> panie() at panic+0x236 0xffffffff805f8666
> >> _callout_stop() at _callout_stop+0x3d3 0xffffffff8061d803
> >> callout_reset() at callout_reset+0x96 0xfffffff8061d916
> >> ehci_interrupt() at ehei;interrupt+0x198 0xffffffff822973c8
> >> ithread_handler() at ithread_handler+0x2e9 0xffffffff805c5d09
> >> Debugger("panic")
> >> CPU1 stopping CPUs: 0x00000001
> >> stopped
> >> Stopped at Debugger+0x7c: movb $0,0xe67a49(%rip)
> >> db> |
> >> ================= 2 ======================
> >
> >
> > Cheers,
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20190209/c121cdca/attachment.htm>