Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Sep 2014 10:57:53 +0200
From:      dt71@gmx.com
To:        John Baldwin <jhb@freebsd.org>, Marcin Cieslak <saper@saper.info>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Xorg causes panics with "multiple" drivers (Was: panic: resource_list_alloc: resource entry is busy)
Message-ID:  <54140711.7020001@gmx.com>
In-Reply-To: <3819796.R7BYA2qqa8@ralph.baldwin.cx>
References:  <alpine.BSF.2.11.1409101241440.51386@m.saper.info> <1584874.3FXdLuYUQI@ralph.baldwin.cx> <alpine.BSF.2.11.1409122045070.62150@m.saper.info> <3819796.R7BYA2qqa8@ralph.baldwin.cx>

next in thread | previous in thread | raw e-mail | index | archive | help
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!




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54140711.7020001>