Re: kern/156799: HEAD panic: Multiple IRQs for PCI interrupt 0.31.INTA: 19 and 16

2011-07-28 Thread Arnaud Lacombe
The following reply was made to PR kern/156799; it has been noted by GNATS. From: Arnaud Lacombe To: bug-follo...@freebsd.org, lacom...@gmail.com Cc: Subject: Re: kern/156799: HEAD panic: Multiple IRQs for PCI interrupt 0.31.INTA: 19 and 16 Date: Fri, 29 Jul 2011 01:26:07 -0400 still

kern/160873: igb(4) from HEAD fails to build on 7-STABLE

2011-09-21 Thread Arnaud Lacombe
>Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Sep 21 16:30:06 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release: >Organization: n/a >Environment: >Descriptio

kern/160992: buf_ring(9) statistics accounting not MPSAFE

2011-09-24 Thread Arnaud Lacombe
>Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Sep 24 20:20:10 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:9-CURRENT >Organization: n/a >Environment: >D

kern/160994: buf_ring(9): MD assumption in MI code

2011-09-24 Thread Arnaud Lacombe
ate-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Sep 24 20:20:11 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release: >Organization: n/a >Environment: >Description: `struct buf_ring', de

kern/161553: Timestamp missing from msgbuf

2011-10-13 Thread Arnaud Lacombe
Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Oct 13 18:00:22 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:10-current >Organization: n/a >Environment: >Description: There is many case r

Re: kern/161553: Timestamp missing from msgbuf

2011-10-13 Thread Arnaud Lacombe
The following reply was made to PR kern/161553; it has been noted by GNATS. From: Arnaud Lacombe To: bug-follo...@freebsd.org, lacom...@gmail.com Cc: Subject: Re: kern/161553: Timestamp missing from msgbuf Date: Thu, 13 Oct 2011 14:07:08 -0400 --0016e6dab5204d792204af320221 Content-Type

kern/161755: Kernel fails to report negative malloc type statistics

2011-10-17 Thread Arnaud Lacombe
eywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Oct 17 20:00:26 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:10-current >Organization: n/a >Environment: >Description

misc/165208: Incorrect unit/description in `vm.vmtotal' output

2012-02-16 Thread Arnaud Lacombe
ords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 16 18:00:24 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:8-STABLE >Organization: n/a >Environment: % uname -a FreeBSD sh

misc/165373: Obvious use-after-free in ipfw_nat()

2012-02-21 Thread Arnaud Lacombe
ate-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 21 20:30:11 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:10-current >Organization: n/a >Environment: >Description: ipfw_nat() read

kern/167381: ichwd(4) misuses `bootverbose'

2012-04-27 Thread Arnaud Lacombe
Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 27 22:30:10 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:10-current >Organization: n/a >Environment: >Description: ichwd(4) should be

kern/168244: [regression] Unable to manually remove permanent ARP entries

2012-05-22 Thread Arnaud Lacombe
eywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 23 02:00:14 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:9-RELEASE >Organization: n/a >Environment: >Description

kern/168245: [regression] Permanent ARP entry not deleted on interface configuration failure

2012-05-22 Thread Arnaud Lacombe
>Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 23 02:10:15 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:9.0-RELEASE >Organization: n/a &g

kern/168246: Multiple em(4) not working with qemu

2012-05-22 Thread Arnaud Lacombe
ate-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed May 23 02:20:01 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:9.0-RELEASE >Organization: n/a >Environment: >Description: It would seem

misc/155765: [patch]`buildworld' does not honors WITHOUT_JAIL

2011-03-21 Thread Arnaud Lacombe
ords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Mar 21 23:00:01 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:9-current >Organization: n/a >Environment: >Des

bin/156729: make(1) do not respect.ORDER not in non-parallel mode

2011-04-29 Thread Arnaud Lacombe
>Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 29 23:20:07 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:8.2-STABLE >Organization: n >Environment: >Description:

Re: bin/156729: make(1) do not respect.ORDER not in non-parallel mode

2011-04-29 Thread Arnaud Lacombe
The following reply was made to PR bin/156729; it has been noted by GNATS. From: Arnaud Lacombe To: bug-follo...@freebsd.org, lacom...@gmail.com Cc: Subject: Re: bin/156729: make(1) do not respect.ORDER not in non-parallel mode Date: Fri, 29 Apr 2011 19:27:24 -0400 [If someone could edit the

Re: bin/156729: make(1) do not respect.ORDER not in non-parallel mode

2011-04-29 Thread Arnaud Lacombe
The following reply was made to PR bin/156729; it has been noted by GNATS. From: Arnaud Lacombe To: bug-follo...@freebsd.org, lacom...@gmail.com Cc: Subject: Re: bin/156729: make(1) do not respect.ORDER not in non-parallel mode Date: Fri, 29 Apr 2011 22:05:23 -0400 Disabling compat-mode

kern/156799: HEAD panic: Multiple IRQs for PCI interrupt 0.31.INTA: 19 and 16

2011-05-03 Thread Arnaud Lacombe
>Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue May 03 17:50:06 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:9-current >Organization: n/a >Environment

Re: kern/156799: HEAD panic: Multiple IRQs for PCI interrupt 0.31.INTA: 19 and 16

2011-05-03 Thread Arnaud Lacombe
The following reply was made to PR kern/156799; it has been noted by GNATS. From: Arnaud Lacombe To: bug-follo...@freebsd.org, lacom...@gmail.com Cc: Subject: Re: kern/156799: HEAD panic: Multiple IRQs for PCI interrupt 0.31.INTA: 19 and 16 Date: Tue, 3 May 2011 14:00:39 -0400 non

kern/169665: Add missing smb(4)/smbus(4)/ichsmb(4) modules

2012-07-05 Thread Arnaud Lacombe
>Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Jul 05 17:10:11 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:-current >Organization: n/a >Environment: All in the title &

Re: kern/169665: Add missing smb(4)/smbus(4)/ichsmb(4) modules

2012-07-05 Thread Arnaud Lacombe
The following reply was made to PR kern/169665; it has been noted by GNATS. From: Arnaud Lacombe To: bug-follo...@freebsd.org, lacom...@gmail.com Cc: Subject: Re: kern/169665: Add missing smb(4)/smbus(4)/ichsmb(4) modules Date: Thu, 5 Jul 2012 13:17:26 -0400 --20cf3020787461163304c41852f0

misc/169796: kenv(1) output is unreadable

2012-07-11 Thread Arnaud Lacombe
Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jul 12 02:40:00 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Arnaud Lacombe >Release:many. >Organization: n/a >Environment: FreeBSD coltar 9.0-STABLE FreeBSD 9.0-STABLE >De

Re: bin/169796: kenv(1) output is unreadable

2012-07-12 Thread Arnaud Lacombe
The following reply was made to PR bin/169796; it has been noted by GNATS. From: Arnaud Lacombe To: bug-follo...@freebsd.org, lacom...@gmail.com Cc: Subject: Re: bin/169796: kenv(1) output is unreadable Date: Thu, 12 Jul 2012 10:01:19 -0400 No, it is not resolved. The problem is not whatever

Re: misc/169796: kenv(1) output is unreadable

2012-07-13 Thread Arnaud Lacombe
How shall I ask this ? Please, re-open this issue. kenv(1) must escape control character, at least when STDOUT_FILENO is a terminal. Thanks, - Arnaud ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To un

Re: misc/169796: kenv(1) output is unreadable

2012-07-13 Thread Arnaud Lacombe
The following reply was made to PR bin/169796; it has been noted by GNATS. From: Arnaud Lacombe To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Cc: Subject: Re: misc/169796: kenv(1) output is unreadable Date: Fri, 13 Jul 2012 11:53:50 -0400 How shall I ask this ? Please, re

Re: misc/169796: kenv(1) output is unreadable

2012-07-15 Thread Arnaud Lacombe
tails of the issue. Please re-open the issue. - Arnaud On Fri, Jul 13, 2012 at 11:53 AM, Arnaud Lacombe wrote: > How shall I ask this ? Please, re-open this issue. > > kenv(1) must escape control character, at least when STDOUT_FILENO is > a terminal. > &

Re: misc/169796: kenv(1) output is unreadable

2012-07-15 Thread Arnaud Lacombe
The following reply was made to PR bin/169796; it has been noted by GNATS. From: Arnaud Lacombe To: freebsd-gnats-sub...@freebsd.org, freebsd-bugs@freebsd.org Cc: Jaakko Heinonen Subject: Re: misc/169796: kenv(1) output is unreadable Date: Sun, 15 Jul 2012 21:16:00 -0400 Hi, I guess this