Hi
My system was dumping core when I tried to invoke X with the recently
released nVidia drivers installed (similar to Kris's problem?). Upon
creating a kernel without INVARIANTS and INVARIANT_SUPPORT options, X
runs well. My question is, of the X/nVidia success stories, were kernels
built wit
On Friday, 6 December 2002 at 15:27:29 -0600, Dan Nelson wrote:
>
> I haven't seen this one reported yet.
>
> FreeBSD dan.emsphone.com 5.0-RC FreeBSD 5.0-RC #228: Thu Dec 5 17:28:33 CST 2002
> [EMAIL PROTECTED]:/usr/src/sys/i386/compile/DANSMP i386
>
> lock order reversal
> 1st 0xc2d454b0 vn
On 07-Dec-2002 Robert Watson wrote:
> BTW, one upshot of this whole event is that we should probably be
> hard-coding the lock order of all important locks rather than allowing it
> to be automatically determined. We'd uncover problems of this sort much
> faster and much more easily, and it would
On Sat, Dec 07, 2002 at 08:58:26AM -0500, Robert Watson wrote:
> On Fri, 6 Dec 2002, Kris Kennaway wrote:
>
> > On Fri, Dec 06, 2002 at 07:18:03PM -0800, Lars Eggert wrote:
> >
> > > >I'm getting this too:
> >
> > After discussing this with various people on IRC, it was determined that
> > this
On Sat, Dec 07, 2002 at 07:24:02PM +0200, Vallo Kallaste wrote:
> On Fri, Dec 06, 2002 at 10:26:24PM -0500, Alexander Kabaev
> <[EMAIL PROTECTED]> wrote:
>
> > On Fri, 6 Dec 2002 23:26:52 +0200
> > Vallo Kallaste <[EMAIL PROTECTED]> wrote:
> >
> > > I've built it yesterday together with a lots of
On Sat, Dec 07, 2002 at 11:43:54PM +0100, Cliff Sarginson wrote:
> Hello,
> I know there has been some exchanges over these problems, but I am not
> sure I yet understand if a problem remains (I am obviously writing
> because one seems to :)
>
> I have on one of the systems here Linux, FreeBSD-Sta
Hello,
I know there has been some exchanges over these problems, but I am not
sure I yet understand if a problem remains (I am obviously writing
because one seems to :)
I have on one of the systems here Linux, FreeBSD-Stable and
FreeBSD-Current. All upto-date as of a few days ago. They all seemed
On 2002-12-07 23:10:18 (+0100), Cliff Sarginson <[EMAIL PROTECTED]> wrote:
> On Sat, Dec 07, 2002 at 08:41:35PM +0100, Philip Paeps wrote:
> > On 2002-11-25 01:49:34 (+0100), Philip Paeps <[EMAIL PROTECTED]> wrote:
> > Perhaps someone can make sense of this? I'm happy I can read my mail now,
> > w
I've tried the sun and blackdown jdk14 ports on -stable and had no
success in running even the demos that come with the jdk. Is this a just
me problem or do those jdks just not work?
James.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the mes
On Sat, Dec 07, 2002 at 08:41:35PM +0100, Philip Paeps wrote:
> On 2002-11-25 01:49:34 (+0100), Philip Paeps <[EMAIL PROTECTED]> wrote:
>
> Perhaps someone can make sense of this? I'm happy I can read my mail now,
> without having to kick the power button every so often, but I'd prefer to
> store
On Sat, 7 Dec 2002, Archie Cobbs wrote:
> Bruce Evans wrote:
> > Er, it should be obvious that growfs can't reasonably work on the mounted
> > partitions. growfs.1 doesn't exist, but growfs.8 already has the warning
> > in a general form:
> >
> > Currently growfs can only enlarge unmou
On Sat, 7 Dec 2002, Robert Watson wrote:
> On Sun, 8 Dec 2002, Bruce Evans wrote:
> > Er, it should be obvious that growfs can't reasonably work on the mounted
> > partitions. growfs.1 doesn't exist, but growfs.8 already has the warning
> > ...
>
> Hmm. I guess one of the interesting questions i
Hello,
cvsupped to current yesterday and tried to give the nvidia drivers another
shot on my current installation (-stable works fine). but it looks like it
can't set the right AGP mode (didn't try the freebsd-native AGP driver, but
will try that one too).
this is a snippet from my XFree.log on s
Bruce Evans wrote:
> > So in summary my recommendation is to add a big warning to the
> > growfs(1) man page that is should not be run on the root partition,
> > even if you have booted single-user mode and haven't mounted / yet.
> > I.e., to grow a root partition, you must boot from a different pa
Hello,
i cvsupped -current yesterday, rebuilt the whole XFree86-port and noticed
_tons_ of warnings from gcc in one header file
/usr/include/sys/time.h:133 (and :150)
ISO C89 forbids long long integer constant
if C89 is from 1989, how come that gcc is complaing about such an old
standard? there s
On Sat, 7 Dec 2002, Archie Cobbs wrote:
> Bruce Evans wrote:
> > > So in summary my recommendation is to add a big warning to the
> > > growfs(1) man page that is should not be run on the root partition,
> > > even if you have booted single-user mode and haven't mounted / yet.
> > > I.e., to gro
Some of you who use CVSup in checkout mode to update our source
trees have reported problems with "src/contrib/gcc/INSTALL" that
look like this:
> Delete src/contrib/gcc/INSTALL
> Cannot delete "/usr/src/contrib/gcc/INSTALL": Directory not empty
This was apparently caused by a recent gcc import
Doug,
Did you get a chance to test a SK 9843 on current? Can you reproduce
the panic's I'm getting? I have the same PHY as you mentioned in the
last message I received from you.
Thanks,
Robert
=> More on my gigE/current saga...
=>
=> Current panics shortly after I load the if_sk driver, or at bo
On 2002-11-25 01:49:34 (+0100), Philip Paeps <[EMAIL PROTECTED]> wrote:
> 2. This one's the most irritating. I use Mutt as my mailclient using
> Maildirs for storage. It occasionally happens that Mutt just 'hangs'
> reading a directory, and there's no way for me to kill it. Ps axl shows it
> as
On Fri, 6 Dec 2002, Archie Cobbs wrote:
> Julian Elischer wrote:
> > I put a copy of / in /usr
> > then from the fixit, I mounted /usr as / and ran growfs from there..
> > the trick is to not do it while / is mounted.
>
> / wasn't mounted yet when I ran growfs:
>
> > > I ran growfs after booting
Please use this e-mail when replying
E_ MAIL. [EMAIL PROTECTED]
To: Kindly Contributor
Subject: Save My Family and Fortune
Tell. 002379669996
This letter may come to you as a surprise as we have not met, but it is a serious
matter.
I am desperately in need of help. I am Mr. Toma sa
I've stumbled across a new 1.4ghz Athlon Thunderbird processor. I need a
motherboard to go with it. This system will be running 5.0 exclusively
unless it blows up, in which case it will run 4-stable. It's a workstation,
but I don't need integrated graphics or sound, and using SDRAM would be
On Fri, Dec 06, 2002 at 10:26:24PM -0500, Alexander Kabaev
<[EMAIL PROTECTED]> wrote:
> On Fri, 6 Dec 2002 23:26:52 +0200
> Vallo Kallaste <[EMAIL PROTECTED]> wrote:
>
> > I've built it yesterday together with a lots of other stuff. Using
> > other -march values than i686 is unofficially claimed
Thanks for reminding me about your userland change to background
fsck. I have tried it out and concur that it is the right approach
until we manage to get the general solution in the kernel. I
suggest that you propose it to release engineering and if approved
check it in.
Kirk McKusick
=-
IPsec: Initialized Security Association Processing.
IP Filter: v3.4.29 initialized. Default = pass all, Logging = enabled
wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard0
wi0: 802.11 address: 00:02:2d:04:df:e4
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent Firmware: Statio
In message <[EMAIL PROTECTED]>, Kirk McKusick wr
ites:
>Adding a two minute delay before starting background fsck
>sounds like a very good idea to me. Please send me your
>suggested change.
BTW, I've been using a fsck_ffs modificaton for a while now that
does something like the disabled kernel I/O
BTW, one upshot of this whole event is that we should probably be
hard-coding the lock order of all important locks rather than allowing it
to be automatically determined. We'd uncover problems of this sort much
faster and much more easily, and it would provide better documentation of
the intended
On Sun, 8 Dec 2002, Bruce Evans wrote:
> On Fri, 6 Dec 2002, Archie Cobbs wrote:
>
> > So in summary my recommendation is to add a big warning to the
> > growfs(1) man page that is should not be run on the root partition,
> > even if you have booted single-user mode and haven't mounted / yet.
>
On Fri, 6 Dec 2002, Kris Kennaway wrote:
> On Fri, Dec 06, 2002 at 07:18:03PM -0800, Lars Eggert wrote:
>
> > >I'm getting this too:
>
> After discussing this with various people on IRC, it was determined that
> this is not the place where the reversal is occurring, but since witness
> doesn't h
greeting,all:
under -CURRENT.after successed build hotspot(client & server) and run
java -version get :
Java HotSpot(TM) Client VM warning: os::allocate_thread_local_storage:
pthread_key = 0x
sizep == 0x0010
Java HotSpot(TM) Client VM warning: os::thread_local_storage_at: can't
find
On Fri, 6 Dec 2002, Archie Cobbs wrote:
> So in summary my recommendation is to add a big warning to the
> growfs(1) man page that is should not be run on the root partition,
> even if you have booted single-user mode and haven't mounted / yet.
> I.e., to grow a root partition, you must boot from
greeting,all:
under -CURRENT.after successed build hotspot(client & server) and
run java -version get :
Java HotSpot(TM) Client VM warning: os::allocate_thread_local_storage:
pthread_key = 0x
sizep == 0x0010
Java HotSpot(TM) Client VM warning: os::thread_local_storage_at: can't
find
32 matches
Mail list logo
