[SOLVED] Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-18 Thread Hans Petter Selasky
FYI Some intense debugging rounds revealed a bug in the HDA association parsing code. Hopefully the issue is fixed now: https://svnweb.freebsd.org/changeset/base/283064 --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mail

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-16 Thread Hans Petter Selasky
On 05/16/15 17:54, David Wolfskill wrote: On Sat, May 16, 2015 at 03:50:00PM +0200, Hans Petter Selasky wrote: ... Send output from bootverbose! Let's hunt this bug down :-) OK; after restoring r282650 & r282651, clearing /usr/obj, and performing a clean buildworld, kernel, and installwor

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-16 Thread David Wolfskill
On Sat, May 16, 2015 at 03:50:00PM +0200, Hans Petter Selasky wrote: > ... > Send output from bootverbose! Let's hunt this bug down :-) > OK; after restoring r282650 & r282651, clearing /usr/obj, and performing a clean buildworld, kernel, and installworld, the "smoke test" reboot yielded (a r

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-16 Thread David Wolfskill
On Sat, May 16, 2015 at 03:46:18PM +0200, Hans Petter Selasky wrote: > ... > > Can you collect output from booting with bootverbose set? From current > amd64 as of today. OK; I just copied it over; please see ; the dmesg in question is dmesg.boot.

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-16 Thread Hans Petter Selasky
On 05/16/15 15:37, David Wolfskill wrote: On Sat, May 16, 2015 at 03:27:57PM +0200, Hans Petter Selasky wrote: ... After reverting both 282650 & 282651, the resulting kernel built. Hi, I'm seeing two of my commits mentioned here, r282650 & r282651. Are these what is causing the problem? You

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-16 Thread Hans Petter Selasky
On 05/16/15 15:27, Hans Petter Selasky wrote: On 05/15/15 22:07, David Wolfskill wrote: On Fri, May 15, 2015 at 02:59:10PM -0400, John Baldwin wrote: ... Hummm, the only recent change is 281544, but that should be in your working kernel. Yes; that dates from 14 April, and I had been doing dai

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-16 Thread David Wolfskill
On Sat, May 16, 2015 at 03:27:57PM +0200, Hans Petter Selasky wrote: > ... > > After reverting both 282650 & 282651, the resulting kernel built. > > > > Hi, > > I'm seeing two of my commits mentioned here, r282650 & r282651. Are > these what is causing the problem? You are sure the built the ker

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-16 Thread Hans Petter Selasky
On 05/15/15 22:07, David Wolfskill wrote: On Fri, May 15, 2015 at 02:59:10PM -0400, John Baldwin wrote: ... Hummm, the only recent change is 281544, but that should be in your working kernel. Yes; that dates from 14 April, and I had been doing daily build/boots of head/i386 through thta period

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-15 Thread David Wolfskill
On Fri, May 15, 2015 at 02:59:10PM -0400, John Baldwin wrote: > ... > Hummm, the only recent change is 281544, but that should be in your working > kernel. Yes; that dates from 14 April, and I had been doing daily build/boots of head/i386 through thta period without incident. Absent something com

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-15 Thread John Baldwin
On Friday, May 15, 2015 11:39:56 AM David Wolfskill wrote: > On Fri, May 15, 2015 at 11:40:44AM -0400, John Baldwin wrote: > > On Saturday, May 09, 2015 07:27:51 AM David Wolfskill wrote: > > > Ref. -- > > > similar symptoms. And again, I

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-15 Thread David Wolfskill
On Fri, May 15, 2015 at 11:40:44AM -0400, John Baldwin wrote: > On Saturday, May 09, 2015 07:27:51 AM David Wolfskill wrote: > > Ref. -- > > similar symptoms. And again, I captured screenshots on a phone, but > > FreeBSD doesn't seem to r

Re: Deja vu: panic in hdaa_coonfigure() for i386, but not amd64 -- again

2015-05-15 Thread John Baldwin
On Saturday, May 09, 2015 07:27:51 AM David Wolfskill wrote: > Ref. -- > similar symptoms. And again, I captured screenshots on a phone, but > FreeBSD doesn't seem to recognize the (USB-attached) phone as something > that might act like a