This would be awesome, please do it.
Scott
Benno Rice wrote:
One of the things that I found useful both in starting the PowerPC port
and in doing the XScale stuff I'm working on is making the SYSINIT stuff
done by mi_startup() verbose. This generally requires hacking your own
code into mi_
L4Linux exists, but it seems to be more of a means for testing out
and developing the L4 microkernel, but would there be any practical
reason to sandbox the FreeBSD kernel and force it to run as a user-
land service on top of the L4::Pistachio kernel? (for example)
Well, you could do neat stuff
On Wed, 2006-05-10 at 11:49 -0500, Dan Nelson wrote:
> In the last episode (May 10), Iasen Kostov said:
> > On Wed, 2006-05-10 at 11:18 -0500, Dan Nelson wrote:
> > > In the last episode (May 10), Iasen Kostov said:
> > > > On Wed, 2006-05-10 at 15:32 +0300, Iasen Kostov wrote:
> > > > > On Wed, 20
> This would be awesome, please do it.
I agree, I've done something like this in a much more hackishly-way for
the XBox port as well, but your code is much cleaner than mine was :-)
Go for it, may others benefit from it!
--
Rink P.W. Springer- http://rink.nu
"R
John Baldwin wrote:
On Tuesday 09 May 2006 16:34, Eric Anderson wrote:
I have a Core Duo system (2 2GHz CPUs), that continually locks up (I
believe it panics) when exiting xorg with both CPU's enabled. If I have:
hint.apic.0.disabled="1"
in device.hints, I only use one CPU, however it exits
Hi guys:
To access sg_table in kernel address, I need to map the starting physical
address of a segment into a kernel address. As I know that, we can use
phystovirt()/bustovirt(), or kmap()/kmap_atomic() to map a bus/physical
address or a physical page into a kernel address in Linux, but I did
On Wed, May 10, 2006 at 04:36:24PM -0600, Scott Long wrote:
> >In my environment non-atomic updates of NFS export lists are not
> >acceptable. So, I decided to correct this problem. As the result
> >mountd, kern/vfs_export.c were completely rewritten, mount.h,
> >vfs_mount.c and nfs_srvsubs.c al
[EMAIL PROTECTED] wrote this message on Thu, May 11, 2006 at 17:45 +0800:
> To access sg_table in kernel address, I need to map the starting physical
> address of a segment into a kernel address. As I know that, we can use
> phystovirt()/bustovirt(), or kmap()/kmap_atomic() to map a bus/physical
>
On Wed, 2006-05-10 at 15:43 +0300, Iasen Kostov wrote:
> On Wed, 2006-05-10 at 15:32 +0300, Iasen Kostov wrote:
> > On Wed, 2006-05-10 at 15:28 +0300, Iasen Kostov wrote:
> > > Hello
> > > I (probably) have some problem with a hosting server machine halting
> > > about once a 30 to minute (probab
On Wed, 2006-05-10 at 15:43 +0300, Iasen Kostov wrote:
> On Wed, 2006-05-10 at 15:32 +0300, Iasen Kostov wrote:
> > On Wed, 2006-05-10 at 15:28 +0300, Iasen Kostov wrote:
> > > Hello
> > > I (probably) have some problem with a hosting server machine halting
> > > about once a 30 to minute (probab
hi!
i just bought an Intel Pentium D-930 (3ghz dual-core)
and wonder why i just only have CPU0 and CPU1, when i compile with SMP...
sysctl says:
machdep.cpu_idle_hlt: 0
is it right or i should see CPU 2 and 3 starting during the boot?
thanks for your help!
ps: i even compiled this option in ke
I think intel chips with dual core don't have hyperthreading. The
operating system sees the second core like it would with
hyperthreading only.
On May 11, 2006, at 12:00 PM, OxY wrote:
hi!
i just bought an Intel Pentium D-930 (3ghz dual-core)
and wonder why i just only have CPU0 and CPU1
thanks a lot for your help!
- Original Message -
From: "Shane Ambler" <[EMAIL PROTECTED]>
To: "FreeBSD Mailing Lists"
Sent: Thursday, May 11, 2006 7:34 PM
Subject: Re: enabling hyper-threading on intel dual-core
On 12/5/2006 1:30, "OxY" <[EMAIL PROTECTED]> wrote:
hi!
i just bough
Hello,
A few months ago I pointed out a problem with AMD64
dualcore, and I even tracked the problem down to a few
commits at a particular date and time... Now that 6.1
is finally released, I tried it, and the problem is
still there... the boot process will crash when
detecting the second SATA disk
930 is perfect, fast enough, no need to spend more money, thanks :)
- Original Message -
From: "Achim Patzner" <[EMAIL PROTECTED]>
To: "OxY" <[EMAIL PROTECTED]>
Cc: ;
Sent: Thursday, May 11, 2006 8:16 PM
Subject: Re: enabling hyper-threading on intel dual-core
i just bought an Intel
i just bought an Intel Pentium D-930 (3ghz dual-core)
and wonder why i just only have CPU0 and CPU1, when i compile with
SMP...
You would need a Pentium Extreme (840, 955 or 965) for this. And
quite a bit of cash.
Achim
___
freebsd-hackers@free
Eric Anderson wrote:
John Baldwin wrote:
On Tuesday 09 May 2006 16:34, Eric Anderson wrote:
I have a Core Duo system (2 2GHz CPUs), that continually locks up (I
believe it panics) when exiting xorg with both CPU's enabled. If I
have:
hint.apic.0.disabled="1"
in device.hints, I only use one
On Thursday 11 May 2006 16:45, Eric Anderson wrote:
> Eric Anderson wrote:
> > John Baldwin wrote:
> >> On Tuesday 09 May 2006 16:34, Eric Anderson wrote:
> >>> I have a Core Duo system (2 2GHz CPUs), that continually locks up (I
> >>> believe it panics) when exiting xorg with both CPU's enabled.
On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote:
> Julian Elischer wrote:
[...]
> >the above points to a filel that says "6.0 errata"
>
> Indeed. Where is the mention of current quota/bge/em/ufs problems? Don't
> tell me these will be shoved under the rug.
Send patches.
--
Simon L. Nielsen
On Thursday 11 May 2006 07:41, Eric Anderson wrote:
> John Baldwin wrote:
> > On Tuesday 09 May 2006 16:34, Eric Anderson wrote:
> >> I have a Core Duo system (2 2GHz CPUs), that continually locks up (I
> >> believe it panics) when exiting xorg with both CPU's enabled. If I
> >> have:
> >>
> >> hi
On 2006.05.11 20:53:42 -0400, Mike Jakubik wrote:
> Simon L. Nielsen wrote:
> >On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote:
> >
> >>Julian Elischer wrote:
> >>
> >[...]
> >
> >>>the above points to a filel that says "6.0 errata"
> >>>
> >>Indeed. Where is the mention of current q
John Baldwin wrote:
On Thursday 11 May 2006 16:45, Eric Anderson wrote:
Eric Anderson wrote:
John Baldwin wrote:
On Tuesday 09 May 2006 16:34, Eric Anderson wrote:
I have a Core Duo system (2 2GHz CPUs), that continually locks up (I
believe it panics) when exiting xorg with both CPU's enabled
Mike Jakubik wrote:
Patches? For what? It's too late now, 6.1 has been released. I sent
reminders to the RE team and i made it quite clear on the lists that the
quota issue should be described in the relnotes/errata before the
release. If the RE team chooses to ignore major bugs and pretend al
Simon L. Nielsen wrote:
On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote:
Julian Elischer wrote:
[...]
the above points to a filel that says "6.0 errata"
Indeed. Where is the mention of current quota/bge/em/ufs problems? Don't
tell me these will be shoved under the rug.
John Baldwin wrote:
On Thursday 11 May 2006 16:45, Eric Anderson wrote:
Eric Anderson wrote:
John Baldwin wrote:
On Tuesday 09 May 2006 16:34, Eric Anderson wrote:
I have a Core Duo system (2 2GHz CPUs), that continually locks up (I
believe it panics) when exiting xorg with both CPU's enabled
I hope you had a great Earth Day!
I thought you'd want to try this:
Adopt your earth and get a free screensaver!
Click here to get started:
http://friends.earthscreen.com/?r=kTFUNzQgFBdWBmINASkC&i=gmail&[EMAIL
PROTECTED]&p=1&z=1&tc=11
___
freebsd-ha
I hope you had a great Earth Day!
I thought you'd want to try this:
I'm getting a $25 gift card for Vivavi earth-friendly products. Get yours too.
Click here to get started:
http://friends.earthscreen.com/?r=MTFUNzQgFBdWBmINASkC&i=gmail&[EMAIL
PROTECTED]&p=8&z=1&tc=11
On 05/11/06 20:53, Mike Jakubik wrote:
> Simon L. Nielsen wrote:
>> On 2006.05.09 01:00:14 -0400, Mike Jakubik wrote:
>>> Julian Elischer wrote:
>>
>> [...]
>>
the above points to a filel that says "6.0 errata"
>>> Indeed. Where is the mention of current quota/bge/em/ufs problems?
>>> Don
Jonathan Noack wrote:
The *entire* errata page was from 6.0; it was a mistake. This wasn't
some "put on the rose-colored classes and gloss over major issues"
thing. It was a long release cycle and something was forgotten. C'est
la vie. It's always a good idea to check the most up-to-date vers
Mike Jakubik wrote:
Jonathan Noack wrote:
The *entire* errata page was from 6.0; it was a mistake. This wasn't
some "put on the rose-colored classes and gloss over major issues"
thing. It was a long release cycle and something was forgotten. C'est
la vie. It's always a good idea to check t
30 matches
Mail list logo
