On Tue, Jun 22, 2010 at 6:56 AM, Alex Keda wrote:
> On 22.06.2010 03:26, Alexander Best wrote:
>>
>> i experienced the same problem running r209391. this might have to do
>> something with a fs being full. i saw these warnings during buildworld
>> when eventuall / ran out of space:
>>
>> Jun 21 21
Howdy,
I tried upgrading from r209351 to r209434 and got a panic related to the
timer stuff while booting. You can see the panic and the backtrace here:
http://people.freebsd.org/~dougb/timer-panic-1.jpg
http://people.freebsd.org/~dougb/timer-panic-2.jpg
http://people.freebsd.org/~dougb/timer-pan
On 06/22/10 12:55, Doug Barton wrote:
> Howdy,
>
> I tried upgrading from r209351 to r209434 and got a panic related to the
> timer stuff while booting. You can see the panic and the backtrace here:
>
> http://people.freebsd.org/~dougb/timer-panic-1.jpg
> http://people.freebsd.org/~dougb/timer-pa
On Wednesday 31 March 2010 14:52:53 Giorgos Keramidas wrote:
> On Tue, 30 Mar 2010 15:10:58 -0400, John Baldwin wrote:
> > On Tuesday 30 March 2010 11:48:58 am Giorgos Keramidas wrote:
> >> +.It Va DEBUG_FLAGS
> >> +Defines a set of debugging flags that will be used to build all
> >> userland +bin
Doug Barton wrote:
> On 06/22/10 12:55, Doug Barton wrote:
>> Howdy,
>>
>> I tried upgrading from r209351 to r209434 and got a panic related to the
>> timer stuff while booting. You can see the panic and the backtrace here:
>>
>> http://people.freebsd.org/~dougb/timer-panic-1.jpg
>> http://people.f
I saw similar behaviour a couple of years ago when I switched from
using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
The problem ended up being a change in the linker script used by GNU
ld for linking kernel modules. It used to always put some magic
symbols used by the linker t
On 06/22/10 13:10, Alexander Motin wrote:
> Doug Barton wrote:
>> On 06/22/10 12:55, Doug Barton wrote:
>>> Howdy,
>>>
>>> I tried upgrading from r209351 to r209434 and got a panic related
>>> to the timer stuff while booting. You can see the panic and the
>>> backtrace here:
>>>
>>> http://peopl
On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
> I saw similar behaviour a couple of years ago when I switched from
> using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
> The problem ended up being a change in the linker script used by GNU
> ld for linking kernel mod
Doug Barton wrote:
> On 06/22/10 13:10, Alexander Motin wrote:
>> Doug Barton wrote:
>>> On 06/22/10 12:55, Doug Barton wrote:
Howdy,
I tried upgrading from r209351 to r209434 and got a panic related
to the timer stuff while booting. You can see the panic and the
backtrace
On 06/22/10 14:17, Alexander Motin wrote:
> Run `sysctl kern.eventtimer.timer2=i8254`, then after few seconds check
> messages to see if system liked this timer (it should fall back
> automatically if it's not),
Seems ok. Here is what I got on the console, no error messages in
/var/log/all.
sysct
Doug Barton wrote:
> On 06/22/10 14:17, Alexander Motin wrote:
>> Run `sysctl kern.eventtimer.timer2=i8254`, then after few seconds check
>> messages to see if system liked this timer (it should fall back
>> automatically if it's not),
>
> Seems ok. Here is what I got on the console, no error mess
Dear developers,
I would like to do a call for testing for my ZFS v15 patch.
As the user/group quotas feature is too much attractive for my needs,
I couldn't resist and have created (and debugged + tested) a ZFS v15
patch for head (applies cleanly against stable/8 as well).
It is a backport of s
Hey all,
Screenshot of panic message is attached. Machine is a VM running under
Parallels Server Bare Metal 4. The cdrom device was enabled but not
connected during boot. System was attempting to boot into single user mode.
This occurred after a fresh install of 8.0-RELEASE.
Let me know how I can
Hi,
I'm creating a new thread on this issue.
On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
> I saw similar behaviour a couple of years ago when I switched from
> using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
> The problem ended up being a change in the linker
On Wed, Jun 23, 2010 at 02:38:06AM +0200, Hans Petter Selasky wrote:
> It appears many kmods are broken because the linker is stripping away static
> data declared with the section attribute in FreeBSD 8.1-RC1.
>
>
>
> I added those lines to the LDFLAGS in Makefile.kmod in the cuse4bsd port
> m
on 23/06/2010 02:41 Nicholas Mills said the following:
> Hey all,
>
> Screenshot of panic message is attached. Machine is a VM running under
> Parallels Server Bare Metal 4. The cdrom device was enabled but not
> connected during boot. System was attempting to boot into single user mode.
> This oc
on 23/06/2010 03:38 Hans Petter Selasky said the following:
> Hi,
>
> I'm creating a new thread on this issue.
>
> On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
>> I saw similar behaviour a couple of years ago when I switched from
>> using gcc 4.0.2 to gcc 4.3.0 to compile some out-
On Wednesday 23 June 2010 08:47:52 Andriy Gapon wrote:
> on 23/06/2010 03:38 Hans Petter Selasky said the following:
> > Hi,
> >
> > I'm creating a new thread on this issue.
> >
> > On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
> >> I saw similar behaviour a couple of years ago when I
18 matches
Mail list logo
