TB --- 2010-11-10 07:52:29 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-11-10 07:52:29 - starting HEAD tinderbox run for powerpc64/powerpc
TB --- 2010-11-10 07:52:29 - cleaning the object tree
TB --- 2010-11-10 07:52:59 - cvsupping the source tree
TB --- 2010-11-10 07:52:59 - /u
TB --- 2010-11-10 07:31:37 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-11-10 07:31:37 - starting HEAD tinderbox run for mips/mips
TB --- 2010-11-10 07:31:37 - cleaning the object tree
TB --- 2010-11-10 07:31:46 - cvsupping the source tree
TB --- 2010-11-10 07:31:46 - /usr/bin/c
on 10/11/2010 07:58 Andriy Gapon said the following:
>
> I've been doing some stress-testing for VM+ZFS on a kernel with
> WITNESS+INVARIANTS and I have already stumbled into some curious panics.
>
> Here's another one:
> Unread portion of the kernel message buffer:
> panic: uma_zalloc_arg: Retur
on 08/11/2010 14:13 Andriy Gapon said the following:
> on 08/11/2010 13:55 Andriy Gapon said the following:
>> I reliable got this panic when all I was doing is saving an attachment in
>> thunderbird 3 that ran in KDE 4 environment. Not sure what was going on
>> behind
>> the scenes, but shouldn'
I've been doing some stress-testing for VM+ZFS on a kernel with
WITNESS+INVARIANTS and I have already stumbled into some curious panics.
Here's another one:
Unread portion of the kernel message buffer:
panic: uma_zalloc_arg: Returning an empty bucket.
cpuid = 0
KDB: stack backtrace:
db_trace_self
on 09/11/2010 16:05 Kostik Belousov said the following:
> Easiest would be for DRM to provide wrappers for copyin/copyout that
> unlock, do operation and lock.
I am a little bit worried about this approach in general.
Driver state may be changed by a process running in parallel while the lock is
d
On Tue, Nov 9, 2010 at 3:58 PM, Kevin Oberman wrote:
>> Date: Tue, 9 Nov 2010 15:45:00 -0800
>> From: Garrett Cooper
>> Sender: owner-freebsd-curr...@freebsd.org
>>
>> On Tue, Nov 9, 2010 at 2:58 PM, C. P. Ghost wrote:
>> > On Mon, Nov 8, 2010 at 11:14 PM, John Baldwin wrote:
>> >> This patch c
> Date: Tue, 9 Nov 2010 15:45:00 -0800
> From: Garrett Cooper
> Sender: owner-freebsd-curr...@freebsd.org
>
> On Tue, Nov 9, 2010 at 2:58 PM, C. P. Ghost wrote:
> > On Mon, Nov 8, 2010 at 11:14 PM, John Baldwin wrote:
> >> This patch changes the Forth code for the Beastie menu to only display t
On Tue, Nov 9, 2010 at 2:58 PM, C. P. Ghost wrote:
> On Mon, Nov 8, 2010 at 11:14 PM, John Baldwin wrote:
>> This patch changes the Forth code for the Beastie menu to only display the
>> menu option to enable or disable ACPI if the loader detects ACPI. This
>> avoids
>> displaying a menu item p
On Mon, Nov 8, 2010 at 11:14 PM, John Baldwin wrote:
> This patch changes the Forth code for the Beastie menu to only display the
> menu option to enable or disable ACPI if the loader detects ACPI. This avoids
> displaying a menu item prompting to enable ACPI if the BIOS doesn't actually
> includ
On Tue, Nov 09, 2010 at 06:25:12PM +, Alexander Best wrote:
> On Fri Nov 5 10, Ulrich Spörlein wrote:
> > On Sat, 30.10.2010 at 23:22:44 +, Alexander Best wrote:
> > > hi there,
> > >
> > > with "options DDB" in my kernel conf i run into the following issue with
> > > my
> > > kernel mod
On 11/9/10 9:59 AM, Alan Cox wrote:
Julian Elischer wrote:
On 11/9/10 9:04 AM, Bakul Shah wrote:
On Tue, 09 Nov 2010 08:45:14 PST Julian
Elischer wrote:
During the discussion at MeetBSD the question came up as to what
the real
limiting factors were with regard to how much RAM a system could
on 09/11/2010 10:02 Alan Cox said the following:
> The kernel portion of the patch looks correct. If I were to make one
> stylistic
> suggestion, it would be to make the control flow of the outer and inner loops
> as
> similar as possible, that is,
>
>for (...
> if ((pdp[i] & PG_V) ==
On Fri Nov 5 10, Ulrich Spörlein wrote:
> On Sat, 30.10.2010 at 23:22:44 +, Alexander Best wrote:
> > hi there,
> >
> > with "options DDB" in my kernel conf i run into the following issue with my
> > kernel modules:
> >
> > link_elf_lookup_symbol: missing symbol hash table
> > KLD file snd_h
on 09/11/2010 20:14 Alexander Motin said the following:
> Hmm. There was not much changes in ATA last time and I can't expect what
> of them could affect PATA. Probe code wasn't changed for long time.
>
> This check was actually added after some ata(4) bug found two years ago.
> So I am not sure y
* Gary Jennejohn , 20101109 18:58:
> This may seem like a stupid comment, but I'd say that the "iso" does
> not imply UTF-8 support. In fact, there seem to be only ISO or code
> page keymaps under /usr/share/syscons/keymaps. But I'm no keymap
> expert.
Well,
Andriy Gapon wrote:
> on 09/11/2010 19:04 Alexander Motin said the following:
>> Andriy Gapon wrote:
>>> Since one of the recent updates (not sure which revision though) I started
>>> to get
>>> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
>>> message
>>> every other b
On Tue, Nov 9, 2010 at 3:45 PM, Ed Schouten wrote:
> * Renato Botelho , 20101109 17:08:
>> Well, few weeks ago I moved from ISO-8859-1 to UTF-8 on my Xorg
>> environment, and after reading this I decided to make a test.
>>
>> I rebuilt my 9.0-current (r215031) with
Julian Elischer wrote:
On 11/9/10 9:04 AM, Bakul Shah wrote:
On Tue, 09 Nov 2010 08:45:14 PST Julian
Elischer wrote:
During the discussion at MeetBSD the question came up as to what the
real
limiting factors were with regard to how much RAM a system could have.
it was put to us that the limi
On Tue, 9 Nov 2010 14:08:01 -0200
Renato Botelho wrote:
[snip stuff from Ed]
> Well, few weeks ago I moved from ISO-8859-1 to UTF-8 on my Xorg
> environment, and after reading this I decided to make a test.
>
> I rebuilt my 9.0-current (r215031) with option TEKEN_UTF8 in kernel
> config, and aft
* Renato Botelho , 20101109 17:08:
> Well, few weeks ago I moved from ISO-8859-1 to UTF-8 on my Xorg
> environment, and after reading this I decided to make a test.
>
> I rebuilt my 9.0-current (r215031) with option TEKEN_UTF8 in kernel
> config, and after configure my sysco
On 11/9/10 9:04 AM, Bakul Shah wrote:
On Tue, 09 Nov 2010 08:45:14 PST Julian Elischer wrote:
During the discussion at MeetBSD the question came up as to what the real
limiting factors were with regard to how much RAM a system could have.
it was put to us that the limit was currently around 51
on 09/11/2010 19:04 Alexander Motin said the following:
> Andriy Gapon wrote:
>> Since one of the recent updates (not sure which revision though) I started
>> to get
>> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
>> message
>> every other boot, i.e. not always.
>>
>>
On Tue, 09 Nov 2010 08:45:14 PST Julian Elischer wrote:
> During the discussion at MeetBSD the question came up as to what the real
> limiting factors were with regard to how much RAM a system could have.
> it was put to us that the limit was currently around 512 GB, though no-one
> at teh discus
Andriy Gapon wrote:
> Since one of the recent updates (not sure which revision though) I started to
> get
> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
> message
> every other boot, i.e. not always.
>
> I added some more debug code there and here's a tack trace:
>
>
On Tue, Nov 9, 2010 at 8:03 AM, Ed Schouten wrote:
> Hello Eir,
>
> * Eir Nym , 20101109 05:10:
>> I've compiled -CURRENT kernel with UTF-8 and CONS25 support. ( r214751 )
>>
>> in xterm emulation mode I have problems with bindings for some keys,
>> such
During the discussion at MeetBSD the question came up as to what the real
limiting factors were with regard to how much RAM a system could have.
it was put to us that the limit was currently around 512 GB, though no-one
at teh discussion knew what the mechanism of the limitation was or
what might
On Tuesday, November 09, 2010 9:10:28 am Alexander Best wrote:
> On Tue Nov 9 10, John Baldwin wrote:
> > On Tuesday, November 09, 2010 6:46:12 am Alexander Best wrote:
> > > hi there,
> > >
> > > i posted this message on freebsd-questions@, but nobody could help me
> > > with it.
> > > to me th
Since one of the recent updates (not sure which revision though) I started to
get
"Unable to set devclass" messages in boot dmesg. I'd say that I see the message
every other boot, i.e. not always.
I added some more debug code there and here's a tack trace:
driver bug: Unable to set devclass (c
on 09/11/2010 16:08 Lars Engels said the following:
> That's also an appreciated improvement, but what PCBSD does is that you
> can toggle several options, so when you select an option, the kernel is
> not loaded immediately after but you are still in the menu and can
> select / toggle another opti
On Tue, Nov 09, 2010 at 11:25:49AM +0200, Andriy Gapon wrote:
> on 08/11/2010 14:04 Kostik Belousov said the following:
> > On Mon, Nov 08, 2010 at 01:50:25PM +0200, Andriy Gapon wrote:
> >> on 05/11/2010 09:27 Andriy Gapon said the following:
> >>>
> >>> I use FreeSBD head and KDE 4 with all the b
on 09/11/2010 07:26 Lars Engels said the following:
> Maybe we should also import PCBSD's patches to the beastie menu?
> In PCBSD's beastie menu you can toggle some settings like "safe mode",
> and "ACPI", so the kernel is not loaded as soon as select an option.
>
> See
> http://trac.pcbsd.org/bro
El día Friday, November 05, 2010 a las 01:13:15AM +0200, Alexander Motin
escribió:
> Matthias Apitz wrote:
> > El día Friday, November 05, 2010 a las 12:46:50AM +0200, Alexander Motin
> > escribió:
> >> Matthias Apitz wrote:
> >>> mixer(1) let me set for recoding only 'mic' or 'rec'. I'm attachi
Andriy Gapon wrote:
So, here is the next version of the patch:
http://people.freebsd.org/~avg/amd64-minidump.4.diff
Changes since the last version:
1. libkvm - try to support both the new and the previous formats/versions of
amd64 minidump. I am not entirely sure about style in which I handled
On Tue Nov 9 10, John Baldwin wrote:
> On Tuesday, November 09, 2010 6:46:12 am Alexander Best wrote:
> > hi there,
> >
> > i posted this message on freebsd-questions@, but nobody could help me with
> > it.
> > to me this looks like a bug, so i assume posting it again here on
> > freebsd-current
On Tue, Nov 09, 2010 at 03:45:52PM +0200, Andriy Gapon wrote:
> on 09/11/2010 07:26 Lars Engels said the following:
> > Maybe we should also import PCBSD's patches to the beastie menu?
> > In PCBSD's beastie menu you can toggle some settings like "safe mode",
> > and "ACPI", so the kernel is not lo
On Tuesday, November 09, 2010 6:46:12 am Alexander Best wrote:
> hi there,
>
> i posted this message on freebsd-questions@, but nobody could help me with it.
> to me this looks like a bug, so i assume posting it again here on
> freebsd-current@ might be better.
>
> please keep in mind that the is
hi there,
i posted this message on freebsd-questions@, but nobody could help me with it.
to me this looks like a bug, so i assume posting it again here on
freebsd-current@ might be better.
please keep in mind that the issue here is not the fact that the second attempt
to unload sound.ko/netgraph.
Hello Eir,
* Eir Nym , 20101109 05:10:
> I've compiled -CURRENT kernel with UTF-8 and CONS25 support. ( r214751 )
>
> in xterm emulation mode I have problems with bindings for some keys,
> such as Home
> If I start vis(1) and press Home, I always get "^[[H" sequenc
On 08/11/10 06:37 PM, Etienne Robillard wrote:
Hi, why is this message happening with 8.1 and sometimes CURRENT ?
I tried recompiling the bootloader but the error still happens,
forcing user to hit Enter to enter manual boot.
Any takes ? :)
Many thanks,
Etienne
___
on 08/11/2010 14:04 Kostik Belousov said the following:
> On Mon, Nov 08, 2010 at 01:50:25PM +0200, Andriy Gapon wrote:
>> on 05/11/2010 09:27 Andriy Gapon said the following:
>>>
>>> I use FreeSBD head and KDE 4 with all the bells and whistles enabled.
>>> Apparently recent KDE update has enabled
41 matches
Mail list logo
