On Jul 27, 2012, at 2:38 AM, Luigi Rizzo wrote:
The alternative way to avoid an 'unused' warning from the compiler
is an empty statement
(void)foo;
that the compiler hopefully optimizes away.
I learned the void-cast convention many years ago.
I used it throughout the libarchive
TB --- 2012-07-28 06:27:10 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-28 06:27:10 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
Fixed in a subsequent commit. Sorry.
On 28 July 2012 01:52, FreeBSD Tinderbox tinder...@freebsd.org wrote:
TB --- 2012-07-28 06:27:10 - tinderbox 2.9 running on
freebsd-current.sentex.ca
TB --- 2012-07-28 06:27:10 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0:
TB --- 2012-07-28 06:44:34 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-28 06:44:34 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
When updating ports (like databases/sqlite3 or graphics/png via
portmaster graphics/png), the installation process comes to a point
where a backup of the old port is created with bsdtar. The process hangs
then:
=== Starting build for graphics/png ===
=== All dependencies are up to date
===
On Sat, Jul 28, 2012 at 10:21 AM, O. Hartmann
ohart...@zedat.fu-berlin.de wrote:
When updating ports (like databases/sqlite3 or graphics/png via portmaster
graphics/png), the installation process comes to a point where a backup of
the old port is created with bsdtar. The process hangs then:
Hi,
On Fri, Jul 27, 2012 at 4:31 PM, Adrian Chadd adr...@freebsd.org wrote:
It looks like a case of lock held during call up the stack. This is
bad for so many reasons.
It also makes writing correctly locked drivers a pain in the ass as
the moment you unlock the driver before calling
On 28 July 2012 12:09, Arnaud Lacombe lacom...@gmail.com wrote:
How would a single ATH_LOCK() helps here ? AFAICS, the panic seem to
be a classical fallout from direct dispatch where you can re-enter the
driver from the driver itself through the network stack.
Take a look at iwn. It has a
Hi,
On Sat, Jul 28, 2012 at 4:04 PM, Adrian Chadd adr...@freebsd.org wrote:
On 28 July 2012 12:09, Arnaud Lacombe lacom...@gmail.com wrote:
How would a single ATH_LOCK() helps here ? AFAICS, the panic seem to
be a classical fallout from direct dispatch where you can re-enter the
driver from
On Fri, Jul 27, 2012 at 2:32 AM, Oliver Fromme o...@lurza.secnetix.de wrote:
Miroslav Lachman wrote:
I think it should be user configurable in /etc/periodic.conf if
somebody want to use INDEX or not.
It already is user configurable. My point is to change the
default, because the
On Wed, 25 Jul 2012, Luigi Rizzo wrote:
During some ipfw/dummynet cleanup i noticed that the libkern version of
inet_ntoa_r() is missing the buffer size argument that is present in
the libc counterpart.
Any objection if i fix it ?
And why exactly would you need it? What does libc do with
Hi,
On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
On Wed, 25 Jul 2012, Luigi Rizzo wrote:
During some ipfw/dummynet cleanup i noticed that the libkern version of
inet_ntoa_r() is missing the buffer size argument that is present in
the libc counterpart.
On Sat, Jul 28, 2012 at 2:41 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Sat, Jul 28, 2012 at 4:04 PM, Adrian Chadd adr...@freebsd.org wrote:
On 28 July 2012 12:09, Arnaud Lacombe lacom...@gmail.com wrote:
How would a single ATH_LOCK() helps here ? AFAICS, the panic seem to
be a
On Sat, Jul 28, 2012 at 3:35 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
On Wed, 25 Jul 2012, Luigi Rizzo wrote:
During some ipfw/dummynet cleanup i noticed that the libkern version of
inet_ntoa_r()
On Sat, 28 Jul 2012, Arnaud Lacombe wrote:
Hi,
On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
On Wed, 25 Jul 2012, Luigi Rizzo wrote:
During some ipfw/dummynet cleanup i noticed that the libkern version of
inet_ntoa_r() is missing the buffer size
Hi,
On Sat, Jul 28, 2012 at 6:44 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
On Sat, 28 Jul 2012, Arnaud Lacombe wrote:
Hi,
On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
On Wed, 25 Jul 2012, Luigi Rizzo wrote:
During some
Hi,
On Sat, Jul 28, 2012 at 6:44 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
Which again leaves me with the question - why does libc have it?
as for the semantic, theoretical, why, I would refer you to the
POSIX's comity, as inet_ntop() is part of it.
- Arnaud
On Jul 28, 2012, at 10:21 AM, O. Hartmann wrote:
When updating ports (like databases/sqlite3 or graphics/png via portmaster
graphics/png), the installation process comes to a point where a backup of
the old port is created with bsdtar. The process hangs then …
My operating system is
Hi,
On Sat, Jul 28, 2012 at 7:46 PM, Arnaud Lacombe lacom...@gmail.com wrote:
Hi,
On Sat, Jul 28, 2012 at 6:44 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
Which again leaves me with the question - why does libc have it?
as for the semantic, theoretical, why, I would refer you
Hi,
I updated to r238858 yesterday, but I was unable to load i915kms (I
tried loading it manually and putting it in /boot/loader.conf). The
computer becomes unresponsive and the screen turns black in either case.
I'm using the GENERIC kernel with WITNESS and INVARIANTS disabled.
Output of
TB --- 2012-07-29 00:59:25 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-29 00:59:25 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
Hi,
On Sun, 29 Jul 2012 09:53:50 +0800
Denny Lin dennyli...@hs.ntnu.edu.tw wrote:
I updated to r238858 yesterday, but I was unable to load i915kms (I
tried loading it manually and putting it in /boot/loader.conf). The
computer becomes unresponsive and the screen turns black in either
case.
On Sun, Jul 29, 2012 at 10:59:54AM +0700, Erich Dollansky wrote:
this seems to be wrong:
131 0x8167a000 7019 i915.ko
141 0x81682000 111c4drm.ko
From my machine:
21 0x817e4000 aee0 sem.ko
31 0x81a12000 9db3
On Sat, Jul 28, 2012 at 9:20 PM, Denny Lin dennyli...@hs.ntnu.edu.tw wrote:
On Sun, Jul 29, 2012 at 10:59:54AM +0700, Erich Dollansky wrote:
this seems to be wrong:
131 0x8167a000 7019 i915.ko
141 0x81682000 111c4drm.ko
From my machine:
21
Hi,
On Sun, 29 Jul 2012 12:20:13 +0800
Denny Lin dennyli...@hs.ntnu.edu.tw wrote:
On Sun, Jul 29, 2012 at 10:59:54AM +0700, Erich Dollansky wrote:
this seems to be wrong:
131 0x8167a000 7019 i915.ko
141 0x81682000 111c4drm.ko
From my machine:
So, I recently updated and encountered a panic on boot which is
reproducible, and wanted to see if anyone's encountered this before I
file a PR. I found a problem in (I think) recent changes to the e1000
driver. I'm running FreeBSD 10-CURRENT as a VirtualBox guest.
#v+
FreeBSD fork-pooh
Hi,
On Sat, 28 Jul 2012 21:49:18 -0700
Kevin Oberman kob6...@gmail.com wrote:
You are working too hard from old information. Do not attempt to load
i915kms.ko. Do not attempt to load drm2.ko. For the past months the
drivers have been fixed to automatically load all needed drivers and
kernel
On Sunday, 29 July 2012 at 0:53:55 -0400, David J. Weller-Fahy wrote:
So, I recently updated and encountered a panic on boot which is
reproducible, and wanted to see if anyone's encountered this before I
file a PR. I found a problem in (I think) recent changes to the e1000
driver. I'm
28 matches
Mail list logo
