similar to: [PATCH] Make ida(4) MPSAFE and a host of other fixes

Dear all, When running function 'testQAReport()', which uses function 'buildVignettes()' to create a pdf-file I get the following error: > source("testQAReport.R") > testQAReport() Error in .get_package_metadata(pkgdir) : Files 'DESCRIPTION' and 'DESCRIPTION.in' are missing. Since I did not get this error in earlier versions of R, could you

I have patches to add locking to the adv(4), adw(4), aha(4), ahb(4), aic(4), and bt(4) drivers so that they no longer use Giant. I would appreciate any testing folks are able to do. The patches are against HEAD but should apply to 8 or 9. Make sure you have INVARIANTS and INVARIANT_SUPPORT enabled for any initial testing that you do. Thanks!

So I have a patch to try and straighten out the ppbus/ppc interrupt stuff a bit. Rather than passing IRQ numbers around as ivars, etc., ppc is smart enough to let child devices ask for SYS_RES_IRQ rid 0 and let them use its assigned IRQ resource. It then uses an interrupt event to mange the list of child interrupt handlers which it invokes from its own interrupt handler. I don't

On Mon, Nov 10, 2008 at 10:01 AM, Fernan Aguero <fernan@iib.unsam.edu.ar> wrote: > > Date: Wed, 29 Oct 2008 14:05:22 -0300 > From: Fernan Aguero <fernan@iib.unsam.edu.ar> > To: Kirk Strauser <kirk@strauser.com> > Cc: freebsd-stable@freebsd.org, d@delphij.net, > John Baldwin <jhb@freebsd.org>, re@freebsd.org > Subject: Re: [FreeBSD] Fix for

In order to support the eventual MFC of a limited and experimental acpi(4) driver from -CURRENT, I have merged a few changes from -CURRENT to -STABLE including: - Power management interface (subr_power.c) - pmtimer(4) driver. Unlike -CURRENT this driver does not require 'device pmtimer' in the kernel config so that existing kernel configs do not have to be changed. - Updated

I just merged drm (Direct Rendering) from HEAD. - Support for latest Intel chips - Support and fixes for many AMD/ATI chips r500 and below - Support AMD/ATI IGP based chips (rs690/rs485) - Lots of code cleanups - Lots of other fixes and changes since the existing drm is 2+ years old If you are experiencing a "garbled" screen with

Hi, there's a regression going from 6.2 to 6.3, where it will panic upon booting the kernel within vm_fault. This problem has been discussed before, but I'm seeing it reliably on a RELENG_6 checkout from 5th of May. It affects multiple (but identical) systems, here's an verbose boot leading to the panic. Please note that 6.2 was running fine on these machines, they also boot

Hi I''ve got a (gentoo) box set up for xen, 2.6.21-xen kernel as per portage about 2 weeks ago. Already got all my guests set up and almost good to go, except for very erratic networking issues. Networking on the domU''s does not always work. I have set up two physical adapters, and bridged both (by use of the modified network-bridge script from the archives) adapters for use

Good morning, I'm having a bit of an issue getting a 3CR990B-TXM NIC detected and usable. Just wondering if anyone knows of any issues with this NIC chipset and/or with the motherboard chipset. The motherboard is a Biostar GeForce 6100 AM2 using an nVidia nForce 410 chipset and nVidia GeForce 6100 vide chipset. I've tried FreeBSD 6.1, 6.2, 6-STABLE (from Wed), and 7-CURRENT (from

Hi I installed the following driver. http://www.f.csce.kyushu-u.ac.jp/~shigeaki//software/freebsd-nfe.html Before I had the nve driver which was unstable on this server and on a prior server in both cases causing either spontaneous reboot or just a crash when under load. So far touchwood the nfe driver has stayed up and running at almost 3 days uptime and has had some stress. I know the driver

Hi, When I upgraded wine from 1.5.24 to 1.5.26, IDA 6.2 + IDAPython stopped working. IDA now does not open, giving me this error message: Traceback (most recent call last): File "C:\Python27\Lib\site.py", line 62, in <module> import os RuntimeError: unable to get file status from 'C:\Python27\Lib\os.py' I can run Python alone just fine though: $ wine

On Wed, Aug 28, 2013 at 01:23:32PM -0700, Andrew Morton wrote: > On Wed, 28 Aug 2013 12:53:17 -0700 Kent Overstreet <kmo at daterainc.com> wrote: > > > > > + while (1) { > > > > + spin_lock(&pool->lock); > > > > + > > > > + /* > > > > + * prepare_to_wait() must come before steal_tags(), in case > > > >

On Wed, Aug 28, 2013 at 01:25:50PM -0700, Andrew Morton wrote: > On Wed, 28 Aug 2013 12:55:17 -0700 Kent Overstreet <kmo at daterainc.com> wrote: > > > Fixup patch, addressing Andrew's review feedback: > > Looks reasonable. > > > lib/idr.c | 38 +++++++++++++++++++++----------------- > > I still don't think it should be in this file.

On Wed, Aug 28, 2013 at 01:50:42PM -0700, Andrew Morton wrote: > On Wed, 28 Aug 2013 13:44:54 -0700 Kent Overstreet <kmo at daterainc.com> wrote: > > > > > > What guarantees that this wait will terminate? > > > > > > > > It seems fairly clear to me from the break statement a couple lines up; > > > > if we were passed __GFP_WAIT we

On Wed, Aug 28, 2013 at 02:10:19PM -0700, Andrew Morton wrote: > On Wed, 28 Aug 2013 14:00:10 -0700 Kent Overstreet <kmo at daterainc.com> wrote: > > > On Wed, Aug 28, 2013 at 01:25:50PM -0700, Andrew Morton wrote: > > > On Wed, 28 Aug 2013 12:55:17 -0700 Kent Overstreet <kmo at daterainc.com> wrote: > > > > > > > Fixup patch, addressing

The remoteproc core uses a static ida named rproc_dev_index for assigning an automatic index number to a registered remoteproc. The ida core may allocate some internal idr cache layers and ida bitmap upon any ida allocation, and all these layers are truely freed only upon the ida destruction. The rproc_dev_index ida is not destroyed at present, leading to a memory leak when using the remoteproc

The virtio core uses a static ida named virtio_index_ida for assigning index numbers to virtio devices during registration. The ida core may allocate some internal idr cache layers and an ida bitmap upon any ida allocation, and all these layers are truely freed only upon the ida destruction. The virtio_index_ida is not destroyed at present, leading to a memory leak when using the virtio core as a

Hello, On Thu, Sep 17, 2015 at 07:15:44AM -0700, James Bottomley wrote: > I don't understand why you'd want to forbid DEFINE_IDA ... all it does I guess to require the use of explicit init / creation so that it's clear the data structure needs to be destroyed? > is pre-initialise a usually static ida structure. The initialised > structure will have a NULL bitmap cache

Hello, On Thu, Sep 17, 2015 at 09:48:37AM -0700, James Bottomley wrote: > Well, there's an easy fix for that. We could have ida_remove() actually > free the bitmap and not cache it if it's the last layer. That way ida > would naturally empty and we wouldn't need a destructor. Tejun, would > that work? Yeah, that definitely is one way to go about it. It kinda muddles