lock order reversal
1st 0xd3a5c11c process lock @ ../../../vm/vm_glue.c:469
2nd 0xc0e3fe30 lockmgr interlock @ ../../../kern/kern_lock.c:239
This is on relatively old (~ three months) sources. The first lock is
from swapout_procs(); I assume the second lock actually refers to the
call to lockm
On Mon, Sep 17, 2001 at 04:21:28PM -0700, John Baldwin wrote:
>
> On 17-Sep-01 Wilko Bulte wrote:
> > Is it me or.. ?
...
> > ../../../kern/imgact_elf.c:945: warning: passing arg 1 of `fill_fpregs' from
> > incompatible pointer type
> > ../../../kern/imgact_elf.c:963: warning: passing arg 10 of
Hi...
One simple question.
Can -CURRENT work with 3Com HomeConnect ADSL Modem Dual Link?
tq
/john
Live Free OR Die
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
John Indra wrote:
>
> Hi...
>
> One simple question.
> Can -CURRENT work with 3Com HomeConnect ADSL Modem Dual Link?
depends how it connects to the system.
>
> tq
>
> /john
> Live Free OR Die
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body
John Indra wrote:
>
> Hi...
>
> One simple question.
> Can -CURRENT work with 3Com HomeConnect ADSL Modem Dual Link?
If you configure you 3Com HomeConnect as router, you can run any
system.
> /john
> Live Free OR Die
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
On Tue, Sep 18, 2001 at 09:50:19PM -0700, Julian Elischer wrote:
>> Can -CURRENT work with 3Com HomeConnect ADSL Modem Dual Link?
>depends how it connects to the system.
I wanna connect it to an NIC, then use it as a media to connect to the
Internet.
I see in the handbook that there is a sysctl
You should contact the maintainer, not me, [EMAIL PROTECTED]
- Original Message -
From: "attila!" <[EMAIL PROTECTED]>
To: "David W.Chapman Jr." <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, September 18, 2001 8:46 AM
Subject: [PORT] mozilla-0.9.3.1 compile error in xpidl.c
Chris Costello wrote:
> On Saturday, September 08, 2001, Maxim Sobolev wrote:
> > I don't like idea to hardcode the same string ("procfs"), with the
> > same meaning in several places across kernel. As for your proposition
> > to use f_fstypename to set v_tag, it is even more bogus because
> > va
On Tuesday, September 18, 2001, Maxim Sobolev wrote:
> Oh, yes, you are correct obviously (don't know what I was thinking about). In this
> case, it looks like v_tag is redundant, because f_fstypename could be used instead
> in a few places where v_tag is abused (the same applies to the statfs.f_t
In message <[EMAIL PROTECTED]>, Maxim Sobolev writes:
>>How do you figure? The contents if `f_fstypename' must match
>> a configured file system exactly, so it could _not_ be anything.
>> To quote sys/kern/vfs_syscalls.c:mount():
>
>Oh, yes, you are correct obviously (don't know what I was t
tp://ftp.uec.ac.jp/pub/firewire/beta/firewire-freebsd-5.0-20010918
Can't build fresh -CURRENT kernel with this patch:
vbook#/usr/src.local/sys/i386/compile/VBOOK 168_> make kernel
cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-
port: Mozilla
operating system built from 5.0 CURRENT cvsup: 28 Aug 01 1600 GMT
===> Extracting for mozilla-0.9.3,1
>> Checksum OK for mozilla-source-0.9.3.tar.bz2.
...
gmake[3]: Entering directory \
`/us0r/ports/www/mozilla/work/mozilla/xpcom/typelib/xpidl'
port: Mozilla
operating system built from 5.0 CURRENT cvsup: 28 Aug 01 1600 GMT
===> Extracting for mozilla-0.9.3,1
>> Checksum OK for mozilla-source-0.9.3.tar.bz2.
...
gmake[3]: Entering directory \
`/us0r/ports/www/mozilla/work/mozilla/xpcom/typelib/xpidl'
Maxim Sobolev wrote:
> sobomax 2001/09/18 07:52:36 PDT
>
> Modified files:
> sys/boot/i386/loader Makefile conf.c
> Log:
> Add support for loading bzip2-compressed kernels and modules. This support
> is turned off by default and could be enabled by defining LOADER_BZIP2_SUPPORT
>
At 9:22 AM +0200 9/18/01, Mark Santcroos wrote:
>Hi Peter,
>
>What is the state of this (for i386)?
>
>Mark
>
>On Sun, Sep 16, 2001 at 11:24:54AM -0700, Julian Elischer wrote:
>> Marcel Moolenaar wrote:
>> >
>> > Gang,
>> >
>> > I don't know exactly what the gdb(1) problems on Alpha are, but
On 18-Sep-01 Vincent Poy wrote:
> With the latest -current sources today, the kernel fails to build
> after a buildworld.
Doh. Something is including sys/mutex.h or sys/sx.h w/o including sys/lock.h.
I'll fix in a bit.
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb
On Mon, 17 Sep 2001, Julian Elischer wrote:
>
> If you find a module that worked in a kernel from before September 11
> but does not work on -current, please let [EMAIL PROTECTED] know.
>
NTFS was working correctly in a kernel from sometime in August, it now fails
with an easily reproducable p
effort
to A/V functions of the firewire. So,I release the SBP-2 code for the
start point of somebody who would loves storage on the firewire.
The URL of the latest code is:
ftp://ftp.uec.ac.jp/pub/firewire/beta/firewire-freebsd-5.0-20010918
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
If you can try a kernel from JUST before the KSE integration..
that migh talso be a good test..
On Tue, 18 Sep 2001, David Taylor wrote:
> On Mon, 17 Sep 2001, Julian Elischer wrote:
> >
> > If you find a module that worked in a kernel from before September 11
> > but does not work on -current
hiya,
While attaching USB Flash card reader to FreeBSD box I am getting message:
_
uhub0: device problem, disabling port 1
-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-curre
My floppy fails to probe for about last 2 weeks. It worked early
with my current-box, and it works on windoze.
dmesg of my mashine:
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University
"Andrey A. Chernov" wrote:
> On Mon, Sep 17, 2001 at 16:26:20 +0300, Maxim Sobolev wrote:
> > Hi,
> >
> > Finally decided to upgrade my current box to the post-ACPI/KSE and found
> > that I'm having problem with resource allocation for floppy disk controller.
> > I'm sure somebody already reporte
On Tue, 18 Sep 2001, Julian Elischer wrote:
> If you can try a kernel from JUST before the KSE integration..
>
> that migh talso be a good test..
>
A kernel from cvs up -D2001-09-10 works perfectly,
A kernel from after the KSE milestone 2 produces various panics
like the following:
Just a question, does /stand still exist in -current? If so, how
does on update it? I remember the old method was make all install in
/usr/src/release/sysinstall but this no longer works.
Cheers,
Vince - [EMAIL PROTECTED] - Vice President __
Unix Networking
On Tue, 18 Sep 2001, John Baldwin wrote:
> On 18-Sep-01 Vincent Poy wrote:
> > With the latest -current sources today, the kernel fails to build
> > after a buildworld.
>
> Doh. Something is including sys/mutex.h or sys/sx.h w/o including sys/lock.h.
> I'll fix in a bit.
Just want
On 18-Sep-01 Garrett Wollman wrote:
> lock order reversal
> 1st 0xd3a5c11c process lock @ ../../../vm/vm_glue.c:469
> 2nd 0xc0e3fe30 lockmgr interlock @ ../../../kern/kern_lock.c:239
>
> This is on relatively old (~ three months) sources. The first lock is
> from swapout_procs(); I assume the
Perhaps this was something that accidentally snuck into the KSE commit?
Index: sys/i386/isa/vesa.c
===
RCS file: /home/ncvs/src/sys/i386/isa/vesa.c,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- sys/i38
yes.. exactly..
should I delete it or will you :-)
(it was to allow a hacked X server to use strange resolution.)
(not needed any more anyhow)
On Tue, 18 Sep 2001, John Baldwin wrote:
> Perhaps this was something that accidentally snuck into the KSE commit?
>
> Index: sys/i386/isa/vesa.c
> ===
On 18-Sep-01 Julian Elischer wrote:
> yes.. exactly..
> should I delete it or will you :-)
> (it was to allow a hacked X server to use strange resolution.)
> (not needed any more anyhow)
You can. :) Just curious what it was doing there is all.
--
John Baldwin <[EMAIL PROTECTED]> -- http://ww
Please take care. I've committed my functional work-in-progress that
splits the nfs code into seperate client and server components. There was
only a very very small amount of sharing between them. This is partly to
enable a cleaner locking attempt. There were some really nasty domain
crossove
On Tue, Sep 18, 2001 at 03:09:33PM +0300, Maxim Sobolev wrote:
The patch looks ok. There's a slight functional change that an ext2fs
filesystem is now correctly returned as such. I don't expect Linux
binaries to break, but it may be remotely possible that certain tools,
now that they detect ext2f
31 matches
Mail list logo