Date: Fri, 12 Sep 2014 17:06:39 -0400 From: John Baldwin <jhb@freebsd.org> To: Marcin Cieslak <saper@saper.info> Cc: freebsd-current@freebsd.org Subject: Re: panic: resource_list_alloc: resource entry is busy Message-ID: <3819796.R7BYA2qqa8@ralph.baldwin.cx> In-Reply-To: <alpine.BSF.2.11.1409122045070.62150@m.saper.info> References: <alpine.BSF.2.11.1409101241440.51386@m.saper.info> <1584874.3FXdLuYUQI@ralph.baldwin.cx> <alpine.BSF.2.11.1409122045070.62150@m.saper.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, September 12, 2014 08:57:55 PM Marcin Cieslak wrote: > On Fri, 12 Sep 2014, John Baldwin wrote: > >> at /usr/src/sys/dev/pci/vga_pci.c:318 > >> > >> 318 return (bus_alloc_resource(dev, type, rid, start, end, count, > > > > flags)); > > > >> Current language: auto; currently minimal > >> (kgdb) p *rid > >> $1 = 0 > > > > Hmm, type 1 is SYS_RES_IRQ. IRQ resources should not be marked reserved. > > > > Oh, some other child of vgapci has already allocated the IRQ. That seems > > odd. > > > > Can you get 'devinfo -r' output before you kldload i915kms and again after > > doing the kldload? (No need to run startx) > > Please note I originally loaded "i915.ko", not "i915kms.ko" Oh, that is probably your problem. X loaded i915kms automatically and i915 and i915kms do not get along. i915 had already allocated the IRQ when i915kms tried to alloc the same IRQ causing the issue. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3819796.R7BYA2qqa8>