TB --- 2013-07-18 02:03:56 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 02:03:56 - 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 --- 2013
TB --- 2013-07-18 02:00:53 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 02:00:53 - 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 --- 2013
TB --- 2013-07-18 02:26:51 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 02:26:51 - 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 --- 2013
TB --- 2013-07-18 01:38:47 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 01:38:47 - 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 --- 2013
TB --- 2013-07-18 00:50:37 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-18 00:50:37 - 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 --- 2013
Yea thank you guys, I got it to work now.
- Martin
On Jul 16, 2013, at 11:42 AM, hiren panchasara
wrote:
> On Mon, Jul 15, 2013 at 8:27 PM, wen heping wrote:
>> I build 9-STABLE on head today, while failed many times last month.
>
> There were some intermittent issues but *recent* stable/9 sh
TB --- 2013-07-17 23:43:10 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-07-17 23:43: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 --- 2013
Hi,
I'm having panics or hard freezes when starting X with an Intel
video card. The machine is able to start old X+twm without problems but
when I try gnome3 (in normal or fallback mode, doesn't matter) the
machine panics or hard freezes.
This doesn't happen when running X with vesa
Hi,
I'm having panics or hard freezes when starting X with an Intel
video card. The machine is able to start old X+twm without problems but
when I try gnome3 (in normal or fallback mode, doesn't matter) the
machine panics or hard freezes.
This doesn't happen when running X with vesa
On Wed, Jul 17, 2013 at 07:39:30PM +0200, Michael Schmiedgen wrote:
> On 07/16/13 22:48, Joel Dahl wrote:
> > Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it
> > hangs when I do a shutdown from an xterm. The screen just goes black and
> > the fan never spins down. It d
On 07/16/13 22:48, Joel Dahl wrote:
Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it
hangs when I do a shutdown from an xterm. The screen just goes black and the
fan never spins down. It doesn't respond to ping.
X220, 10.0-CURRENT #0 r253368 amd, powerd running. In
On 17 July 2013 04:26, Andriy Gapon wrote:
> on 16/07/2013 22:40 Adrian Chadd said the following:
>> :( So it's a deadlock. Ok, so what's next?
>
> A creative process...
Wonderful. :)
> One possibility is to add getnewvnode_reserve() calls before the ZFS
> transaction
> beginnings in the place
On 7/17/13 11:26 AM, Freddie Cash wrote:
On Wed, Jul 17, 2013 at 7:50 AM, Bob Bishop mailto:r...@gid.co.uk>> wrote:
Hi,
On 17 Jul 2013, at 15:17, Kurt Lidl wrote:
>> On 7/16/2013 2:12 PM, Alan Cox wrote:
>>> ... The Haswell line of CPUs is widely reported to
support
Alexander Motin wrote:
> I don't know what to say. I am now using HDMI audio from NVIDIA card to
> quite old external 5.1 receiver with XBMC every day, and I haven't
> noticed lags.
>
> The only potentially related effect I have noticed is that my receiver
> eats first second or about that of
On Wed, Jul 17, 2013 at 7:50 AM, Bob Bishop wrote:
> Hi,
>
> On 17 Jul 2013, at 15:17, Kurt Lidl wrote:
>
> >> On 7/16/2013 2:12 PM, Alan Cox wrote:
> >>> ... The Haswell line of CPUs is widely reported to
> support DIMMs twice as large, and it's due in September. That would
> make the
Hi,
On 17 Jul 2013, at 15:17, Kurt Lidl wrote:
>> On 7/16/2013 2:12 PM, Alan Cox wrote:
>>> ... The Haswell line of CPUs is widely reported to
support DIMMs twice as large, and it's due in September. That would
make the systems of late 2013 hold up to 1536GB of memory.
>>
>> I'd point
On 7/16/2013 2:12 PM, Alan Cox wrote:
... The Haswell line of CPUs is widely reported to
support DIMMs twice as large, and it's due in September. That would
make the systems of late 2013 hold up to 1536GB of memory.
I'd point you at stuff like the Supermicro X8BQ6 series of mainboards.
QP E5-
> Date: Wed, 17 Jul 2013 12:07:11 +0200
> From: Michael Schmiedgen
> To: Joel Dahl
> Cc: curr...@freebsd.org
> Subject: Re: Lenovo x220 - hangs on shutdown
> Message-ID: <51e66ccf.2040...@gmx.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 16.07.2013 22:48, Joel Dahl wr
on 16/07/2013 22:40 Adrian Chadd said the following:
> :( So it's a deadlock. Ok, so what's next?
A creative process...
One possibility is to add getnewvnode_reserve() calls before the ZFS transaction
beginnings in the places where a new vnode/znode may have to be allocated within
a transaction.
On 16.07.2013 22:48, Joel Dahl wrote:
Yesterday I upgraded my Lenovo x220 to the latest current (r253368). Now it
hangs when I do a shutdown from an xterm. The screen just goes black and the
fan never spins down. It doesn't respond to ping.
My build is from Sunday. I never type 'shutdown', bu
On Wed, Jul 17, 2013 at 09:16:55AM +0200, Jeremie Le Hen wrote:
> Hi,
>
> Early May I set ddb_enable="YES" (crashinfo_enable="YES" by default).
> Upon panic, it created the following kind of files:
>
> -rw--- 1 root wheel 549 Jun 26 22:09 info.0
> -rw--- 1 root wheel 15185018
Hi,
Early May I set ddb_enable="YES" (crashinfo_enable="YES" by default).
Upon panic, it created the following kind of files:
-rw--- 1 root wheel 549 Jun 26 22:09 info.0
-rw--- 1 root wheel 1518501888 Jun 26 22:09 vmcore.0
-rw--- 1 root wheel 196981 Jun 26 22:09 co
22 matches
Mail list logo