Date: Fri, 26 Sep 2014 14:47:02 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: dt71@gmx.com, Marcin Cieslak <saper@saper.info> Subject: Re: Xorg causes panics with "multiple" drivers (Was: panic: resource_list_alloc: resource entry is busy) Message-ID: <6194383.JuC2mSLzHG@ralph.baldwin.cx> In-Reply-To: <282186928.pUbQA97aum@ralph.baldwin.cx> References: <alpine.BSF.2.11.1409101241440.51386@m.saper.info> <54140711.7020001@gmx.com> <282186928.pUbQA97aum@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, September 15, 2014 11:25:47 AM John Baldwin wrote: > On Saturday, September 13, 2014 10:57:53 AM dt71@gmx.com wrote: > > John Baldwin wrote on 09/12/2014 23:06: > > > 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. > > > > Who is to blame? The user who tried to manually load an unsupported > > combination of modules, or the system, which should have handled things > > gracefully (whether by automatically unloading the first driver, or > > producing a soft-error upon loading the 2nd driver)? > > > > On a side-note, I also had a "resource_list_alloc: resource entry is busy" > > panic right after switching from the 10.0-supported Xorg to the "new" > > Xorg; > > I exited Xorg, enabled "FreeBSD_new_Xorg", ran "pkg upgrade", then ran > > "startx", and got the panic. Surely this wasn't my fault! > > I can turn the panic into a resource allocation failure, but specifically > with KMS I am unsure if it will actually be better. FYI, I wrote a test for the patch I sent to make this not panic and verified it worked ok and committed it. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6194383.JuC2mSLzHG>