I am also looking into it:
1. It happens only with libarchive 3.0.4 (3.0.3 works fine)
2. It happens only if archiving files located on ZFS (UFS works fine)
3. Backtrace:
#0 setup_acl_posix1e (a=0x801c45100, entry=0x801d69100, acl=0x801d8a000,
archive_entry_acl_type=256)
at
/base/head/lib
On Sat, Jul 28, 2012 at 10:15 PM, Greg 'groggy' Lehey wrote:
> 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
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 ru
Hi,
On Sat, 28 Jul 2012 21:49:18 -0700
Kevin Oberman 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 modules when X
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 10.0-CUR
Hi,
On Sun, 29 Jul 2012 12:20:13 +0800
Denny Lin 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:
> >
> > 2
On Sat, Jul 28, 2012 at 9:20 PM, Denny Lin 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 0x817e4
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
Hi,
On Sun, 29 Jul 2012 09:53:50 +0800
Denny Lin 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. I'm using the GENERIC
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 --- 2012-
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 pciconf
Hi,
On Sat, Jul 28, 2012 at 7:46 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Sat, Jul 28, 2012 at 6:44 PM, Bjoern A. Zeeb
> 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(
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 6:44 PM, Bjoern A. Zeeb
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
__
Hi,
On Sat, Jul 28, 2012 at 6:44 PM, Bjoern A. Zeeb
wrote:
> On Sat, 28 Jul 2012, Arnaud Lacombe wrote:
>
>> Hi,
>>
>> On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
>> wrote:
>>>
>>> On Wed, 25 Jul 2012, Luigi Rizzo wrote:
>>>
During some ipfw/dummynet cleanup i noticed that the libkern v
On Sat, 28 Jul 2012, Arnaud Lacombe wrote:
Hi,
On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
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
On Sat, Jul 28, 2012 at 3:35 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
> 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
On Sat, Jul 28, 2012 at 2:41 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Sat, Jul 28, 2012 at 4:04 PM, Adrian Chadd wrote:
>> On 28 July 2012 12:09, Arnaud Lacombe wrote:
>>
>>> How would a single ATH_LOCK() helps here ? AFAICS, the panic seem to
>>> be a classical fallout from direct dispatch where
Hi,
On Sat, Jul 28, 2012 at 6:14 PM, Bjoern A. Zeeb
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.
>>
>> Any objection if
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 it?
On Fri, Jul 27, 2012 at 2:32 AM, Oliver Fromme 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 current default is u
Hi,
On Sat, Jul 28, 2012 at 4:04 PM, Adrian Chadd wrote:
> On 28 July 2012 12:09, Arnaud Lacombe 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
On 28 July 2012 12:09, Arnaud Lacombe 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 single lock - IWN_L
Hi,
On Fri, Jul 27, 2012 at 4:31 PM, Adrian Chadd 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 ether_input() /
> i
On Sat, 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:
>
> ===>>> Starting build fo
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 da
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 --- 2012-
Fixed in a subsequent commit. Sorry.
On 28 July 2012 01:52, FreeBSD Tinderbox 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: Mon Mar 26 13:54:
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 --- 2012-
29 matches
Mail list logo
