Date: Tue, 11 Jul 2017 19:53:04 -0400 From: Michael Butler <imb@protected-networks.net> To: Warner Losh <imp@bsdimp.com> Cc: FreeBSD Current <current@freebsd.org> Subject: Re: Panic on boot after upgrade from r320827 -> r320869 Message-ID: <adbeefe6-9539-4151-0cd3-ab57b8657885@protected-networks.net> In-Reply-To: <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net> References: <20170710115109.GD1177@albert.catwhisker.org> <20170711121311.GI1177@albert.catwhisker.org> <CANCZdfqRMybt2yzr8GrZCKtvh7WSkeorKXJ%2Bt5wtDSSY75S8fg@mail.gmail.com> <b1b65804-9752-942c-dbfd-075a4c5d6317@protected-networks.net> <CANCZdfp09QLQRgENS73JqbH-UwkjXvUB2j21xNes0zyeWc02VA@mail.gmail.com> <954e8793-7e17-8ae4-8449-39c742e0d432@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/11/17 13:13, I wrote: >> Take sdhci out of the kernel and try again. If that works, it tells us >> one >> thing (need to troubleshoot sdhci stuff more). If not it tells us another >> (need to troubleshoot CAM more), do we get errors with the ATA_IDENTIFY >> command? Does it try multiple times per AHCI port? What AHCI device do >> you >> have? You may need to scroll back with the screen-lock / pageup keys >> to see >> these messages. [ .. snip .. ] > I'll try this tonight when I'm back at home. The laptop concerned uses > the ICH-7M part in "legacy mode" so it doesn't do AHCI at all :-( Without sdhci and mmc, it actually boots but everything KDE aborts with signal 6 :-( I'm not prepared to rebuild the ~1900 ports on this box to pursue this further, imb
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?adbeefe6-9539-4151-0cd3-ab57b8657885>