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

[John Baldwin]

On Saturday, May 09, 2015 07:27:51 AM David Wolfskill wrote:
> Ref. <http://docs.FreeBSD.org/cgi/mid.cgi?20150415134515.GQ1224> --
> 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 file system (I guess; I'm a bit new to
> "smartphones").
> 
> In this case, my starting-point was r282623; sources were updated to
> r282676.  I was able to update from:
> 
> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #55  r282623M/282623:1100072: Fri May  8 05:40:49 PDT 2015     root at g1-254.catwhisker.org:/common/S3/obj/usr/src/sys/CANARY  amd64
> 
> to
> 
> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #56  r282676M/282676:1100073: Sat May  9 05:50:15 PDT 2015     root at g1-254.catwhisker.org:/common/S3/obj/usr/src/sys/CANARY  amd64
> 
> without incident, but the update from:
> 
> FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1590  r282623M/282623:1100072: Fri May  8 06:40:11 PDT 2015     root at g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  i386
> 
> was only able to build; the panic occurs before we've found any disks,
> so I can't get a crash dump.  I do have a kdb prompt, though, so if
> someone has a suggestion for something to check, please let me know.
> (Mind, reading email will be rather awkward while the laptop is exploring
> the mysteries of a panic, so that might be worth bearing in mind.)
> 
> Just prior to the bactrace, I see:
> ...
> hdaa1: 30 411111f0 15 0  Speaker       None   1/8      Rear
> Kernel page fault with the following non-sleepable locks held:
> exclusive sleep mutex hdac1 (HDA driver mutex) r = 0 (0xcfef...
> src/sys/dev/sound/pci/hda/hdaa.c:1571
> 
> The most recent relevant entries in the backtrace are:
> hdaa_configure()
> hdaa_attach()
> device_attach()
> bus_generic_attach()
> hdacc_attach()
> device_attach()
> bus_generic_attach()
> hdac_attach2()
> run_interrupt_driven_config_hooks()
> boot_interrupt_driven_config_hooks()
> mi_startup()
> begin()
> 
> The panic message is "fatal trap 12: page fault while in kernel mode"
> ...
> fault code		= supervisor read, page not present
> ...
> current process		= 0 (swapper)
> ...
> Stopped at ... = hdaa_configure+0x14af:	movb	0x3,%dl

Can you do 'l *hdaa_configure+0x14af' in gdb against the kernel.debug?
Perhaps set 'hint.hdac.0.disabled=1' at the loader prompt as a temporary
workaround to boot if needed?

-- 
John Baldwin