Re: FYI: main (bad9fa56620e based): some unexpected SIGSEGV's using poudriere-devel to build armv7 ports on aarch64 (cortex-a72) system

2021-03-10 Thread Olivier Houchard
Hi Mark, On Tue, Mar 09, 2021 at 03:39:42PM -0800, Mark Millard via freebsd-arm wrote: > After using poudriere to build ports for native cortex-a72 > on the MACCHIATObin Double Shot (and similarly for > cortex-a57 on the OverDrive 1000) I attempted to do my > usual bulk build targeting cortex-a7 v

Re: panic on boot after SVN r328988

2018-02-16 Thread Olivier Houchard
Hi Michael, On Fri, Feb 16, 2018 at 10:13:07AM -0500, Michael Butler wrote: > On 02/16/18 10:05, Andrey V. Elsukov wrote: > > On 16.02.2018 17:44, Michael Butler wrote: > >>> do you have some specific optimization flags in make.conf? > >>> Can you show the output of `head -40 /var/run/dmesg.boot`?

Re: ARM pcpu changes, was Re: [patch] i386 pmap sysmaps_pcpu[] atomic access

2013-03-01 Thread Olivier Houchard
On Fri, Mar 01, 2013 at 02:20:16PM +0100, Svatopluk Kraus wrote: > On Tue, Feb 26, 2013 at 1:39 PM, Konstantin Belousov > wrote: > > On Tue, Feb 26, 2013 at 09:06:51PM +1300, Andrew Turner wrote: > >> Does anyone know if it is only curthread that needs to be atomic? If so > >> this should work. Re

Re: [patch] i386 pmap sysmaps_pcpu[] atomic access

2013-02-26 Thread Olivier Houchard
On Mon, Feb 25, 2013 at 04:26:14PM -0500, John Baldwin wrote: > On Monday, February 25, 2013 7:47:47 am Olivier Houchard wrote: > > On Mon, Feb 25, 2013 at 07:09:20PM +1300, Andrew Turner wrote: > > > On Thu, 21 Feb 2013 10:43:49 -0500 > > > John Baldwin wrote:

Re: [patch] i386 pmap sysmaps_pcpu[] atomic access

2013-02-25 Thread Olivier Houchard
ite. For now, we are using the Privileged one to store pcpu > > > pointer (curthread is correctly set during each context switch). > > > Thus, using a coprocessor register means that reading of curthread > > > is not a single instruction implementation now. After we figured >

Re: [patch] turning devctl into a "multiple openable" device

2011-11-30 Thread Olivier Houchard
On Wed, Nov 30, 2011 at 06:04:50PM +0200, Kostik Belousov wrote: > > > I wonder why the waiting_threads stuff is needed at all. The cv could > > > be woken up unconditionally everytime. What is the reason for the cv_wait > > > call in cdevpriv data destructor ? You cannot have a thread doing e.g. >

Re: [patch] turning devctl into a "multiple openable" device

2011-11-30 Thread Olivier Houchard
On Wed, Nov 30, 2011 at 05:46:36PM +0200, Kostik Belousov wrote: > On Wed, Nov 30, 2011 at 10:05:11AM -0500, John Baldwin wrote: > > On Wednesday, November 30, 2011 7:43:20 am Baptiste Daroussin wrote: > > > Hi all, > > > > > > With the help of cognet, I wrote a patch to turn devctl into a multipl

Re: Crossbuild failure on 8-stable

2011-06-30 Thread Olivier Houchard
On Thu, Jun 30, 2011 at 11:22:36AM +0200, Hans Petter Selasky wrote: > Hi, > > Trying to cross build ARM fails in the following way on 8-stable: > > 8.2-STABLE FreeBSD 8.2-STABLE #1: Wed Jun 29 13:09:23 UTC 2011 > > make toolchain TARGET=arm > > Is this perhaps also an issue in 9-current? > >

Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8

2011-03-14 Thread Olivier Houchard
On Mon, Mar 14, 2011 at 02:01:38AM +0300, Yuri Pankov wrote: > Hi, > > I'm getting the following panic trying to boot March 5 snapshot on > HP Pavilion DV8 notebook (8.2-RELEASE GENERIC kernel seems to boot on > the same hardware just fine): > > run_interrupt_driven_hooks: still waiting after 60

Re: bind fails with sig11 on start / pthread failure on ARM?

2010-02-19 Thread Olivier Houchard
> > Strange: Not so much, the first values for ras_start/end were chosen to be immediate values, so you could just mov them, but the new one aren't. Try something like the patch attached instead (untested, I have no arm setup here, but you'll get the idea). Regards, Olivier Index: contrib/bind

Re: 5.1-RELEASE panic, trace included

2003-06-14 Thread Olivier Houchard
On Sat, Jun 14, 2003 at 04:36:28PM +0200, Maxime Henrion wrote: > Pawel Jakub Dawidek wrote: > > On Sat, Jun 14, 2003 at 02:28:33AM -0400, Robert Watson wrote: > > +> If you have the kernel.debug for this kernel, could you send the gdb -k > > +> output of: > > +> > > +> l *in6_pcbbind+0x2a7 > >

Re: SB Live goes silent after pcm commit

2003-02-25 Thread Olivier Houchard
On Tue, Feb 25, 2003 at 11:13:23PM +0100, ?yvind Rakv?g wrote: > I believe the commit Feb 20 17:31:11 2003 UTC on > src/sys/dev/sound/pci/emu10k1.c broke something. > > With a kernel built from 17:00 sources sound works, from 19:00 there is > only the sound of silence. Everything looks OK, xmms, m

Re: [Fwd: panic: don't do that ?]

2003-02-12 Thread Olivier Houchard
to address it by unloading the > affected module and loading it again, but... that'll panic the system. AFAIK, The device being busy issue is fixed by Brian Feldman's recent commit. You can find the patch here : http://people.FreeBSD.org/~cognet/dsp.c.diff Cheers, Olivier Houchard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: ?deleted include file sys/sys/bus_private.h

2002-10-02 Thread Olivier Houchard
I placed a copy of bus_private.h in the trm directory > and it compiles and the driver works... > > all's well that ends well? > > hopefully the Tekram DC395U/W will be officially > committed Hi, Could you please try this one: http://www.ci0.org/trm/trm.

Re: TekRam 395U[W] is ready for commit

2002-09-25 Thread Olivier Houchard
fixes are. By the way the version you downloaded is not the last one, which may be found at http://www.ci0.org/trm (I don't really remember what the diff are, certainly mainly style changes). Cheers. Olivier Houchard To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: gvim weird linkage

2002-03-09 Thread Olivier Houchard
On Sat, Mar 09, 2002 at 10:41:32PM +0200, Vallo Kallaste wrote: > On Sat, Mar 09, 2002 at 02:19:40PM +, Simon Dick <[EMAIL PROTECTED]> wrote: > > > > Any hints? Seems like some environment configuration problem or > > > latent bug somewhere.. > > > > I just rebuild my current today and gvim