subscribe freebsd-current
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
f file for further details. For commonly done items, please see the
COMMON ITEMS: section later in the file.
+20010924:
+ The bug in the buildworld process has been fixed.
+
20010919:
There's a bug in the world build process. The cross-tools
are build with the NEW h
> "Kazu" == Kazutaka YOKOTA <[EMAIL PROTECTED]> writes:
>> which Kazutaka YOKOTA suggested in a different thread might indicate
>> some weirdness. Any suggestions? I tried setting "acpi_load=NO" at
>> boot,but the acpi module gets loaded anyway.
Kazu> Um, you should have typed "unset a
On Mon, Sep 24, 2001 at 01:26:37PM +1000, Peter Jeremy wrote:
> On 2001-Sep-21 10:45:42 +0300, Ruslan Ermilov <[EMAIL PROTECTED]> wrote:
> >Also, this error may only be caused if:
> >
> >1. The previous ``buildworld'' installed new headers in
> >${WORLDTMP}/usr/include.
> >
> >2. The next ``
On Mon, Sep 24, 2001 at 04:53:16PM +0900, Takahashi Yoshihiro wrote:
>
> It uses the boot programs in /boot. So, even if we change boot0 and/or
> mbr, the new sysinstall includes old one. And, it breaks cross
> building, too.
>
> I have made the patch to fix this problem. It adds a new target "b
>Read UPDATING.
Having an old libc.so.4 in /usr/lib is not in UPDATING. (Perhaps it
should be...)
>You have an old libc.so.4. You can have it updated
>automatically by adding "COMPAT4X=yes" into /etc/make.conf. For now:
>
># echo "COMPAT4X=yes" >> /etc/make.conf
># cd /usr/src/lib/compat
>#
On Mon, Sep 24, 2001 at 12:28:42PM -0700, Bill Fenner wrote:
>
> >Read UPDATING.
>
> Having an old libc.so.4 in /usr/lib is not in UPDATING. (Perhaps it
> should be...)
>
I also think updating is a little misleading. It says if you are
upgrading from 4.x, whereas actually the problem exists
On 23-Sep-01 Wilko Bulte wrote:
> On Thu, Sep 20, 2001 at 07:40:52PM +0200, Wilko Bulte wrote:
>> On Wed, Sep 19, 2001 at 01:32:28PM -0700, John Baldwin wrote:
>> >
>> > On 19-Sep-01 Wilko Bulte wrote:
>> > > On Tue, Sep 18, 2001 at 03:01:25PM -0700, John Baldwin wrote:
>>
>> ...
>>
>> > >> p_
On 23-Sep-01 Munehiro Matsuda wrote:
> Hi all,
>
> Here's another one from src-cur.4972.gz. It's repeatable.
> ---
># ps -ae
> lock order reversal
> 1st 0xc7fe4d08 process lock @ ../../../kern/kern_proc.c:215
> 2nd 0xc03e6620 Gian
It appears that nfs_msg function in nfsclient/nfs_socket.c file
is not prepared to deal with NULL thread pointer passed to it
and bogusly tries to reference td->td_proc.
I had to add this simple patch to avoid panics:
Index: nfs_socket.c
=
thanks
I'll fix it..
On Mon, 24 Sep 2001, Alexander N. Kabaev wrote:
> It appears that nfs_msg function in nfsclient/nfs_socket.c file
> is not prepared to deal with NULL thread pointer passed to it
> and bogusly tries to reference td->td_proc.
>
> I had to add this simple patch to avoid pani
I also started getting this error with recent kernels (in the last
day or so).
Mounting root from ufs:/dev/ad0s1a
panic: lock (sleep mutex) vnode interlock not locked @
/usr/src/sys/kern/vfs_default.c:460
Debugger("panic")
Stopped at Debugger+0x44: pushl %ebx
db> t
Debugger(c03c5bbb) at
You could probably set teh device using DDB, but I just use a serial debug
link
On Mon, 24 Sep 2001, Bill Fenner wrote:
>
> I also started getting this error with recent kernels (in the last
> day or so).
>
> Mounting root from ufs:/dev/ad0s1a
> panic: lock (sleep mutex) vnode interlock not l
Julian Elischer wrote:
> You could probably set teh device using DDB, but I just use a serial debug
> link
Not a good strategy. dev_t is a pointer in -current.
We probably need a 'dumpon 13,0x00020001' ddb command that does something
like what sysctl_kern_dumpdev() does..
> On Mon, 24 Sep 2001
I got new notebook and installed -current (20010922) from scratch.
And my kernel detects two psm* at booting.
...
atkbdc0: at port 0x60,0x64 on isa0
atkbd0: flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0: direction bit not s
On Mon, Sep 24, 2001 at 01:26:37PM +1000, I wrote:
> I have an old -CURRENT system[1] that can't do a buildworld any more,
> even with the latest bsd.{prog,lib}.mk changes (1.101 and 1.98). I
> delete /usr/obj before the buildworld, which writes off the above
> scenarios. Is anyone else seeing p
I tried a make release today and when (I think) it's making the kernel
floppy it craps out - the DIOCWLABEL may or may not be a problem, but
it would appear that the kernel floppy has overflowed.
This is probably rather simple to fix (and potentially politically
charged), but more importantly, I'
Gregor,
I can't get the 4.x output, but the 5.0-C output is attached below. I've
cc'd the info to a few other lists in case it helps.
Sorry for the cross-posting...
**
Chris Dempsey
-- Forwarded message --
Date: Mon, 24 Sep 2001 21:59:11 -0700 (PDT)
From:
MFC of mknodes.c,v 1.13 is needed to pass this.
On Fri, Sep 21, 2001 at 02:24:46PM +0700, Nickolay Dudorov wrote:
> When I try to "make release ... RELEASETAG=RELENG_4_4_0_RELEASE"
> on the freshly buildworld-ed -CURRENT it stops on the
>
> >>> stage 2: build tools
>
> with the following
On Mon, Sep 24, 2001 at 08:14:45AM -0400, Viren R. Shah wrote:
> > "Kazu" == Kazutaka YOKOTA <[EMAIL PROTECTED]> writes:
>
>
> >> which Kazutaka YOKOTA suggested in a different thread might indicate
> >> some weirdness. Any suggestions? I tried setting "acpi_load=NO" at
> >> boot,but the
Hi,
-current as of yesterday (updated from pre KSE).
A non verbose boot shows this:
---snip---
ppc0: at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
lpt0: on ppbus0
lpt0: Interrupt-driven port
pcfclock0:
Hi Alexander,
Yes, a bit of debug printfs' snug in there. I'll remove them
Real Soon Now. Don't worry, they're harmless.
Poul-Henning
In message <[EMAIL PROTECTED]>, Alexander Leiding
er writes:
>Hi,
>
>-current as of yesterday (updated from pre KSE).
>
>A non verbose boot shows this:
>---sn
> "DC" == David W Chapman, writes:
DC> Basically delete your /boot/kernel/acpi.ko until this has been
DC> fixed. That's what I am having to do.
Yeah, I've done that as a temporary measure. However, I'd like to help
people figure out what's wrong.
DC> David W. Chapman Jr.
Viren
--
> DC> Basically delete your /boot/kernel/acpi.ko until this has been
> DC> fixed. That's what I am having to do.
>
> Yeah, I've done that as a temporary measure. However, I'd like to help
> people figure out what's wrong.
As would I, the best thing you can do is send the dumps, acpidump to the
current sysinstall building has a problem.
It uses the boot programs in /boot. So, even if we change boot0 and/or
mbr, the new sysinstall includes old one. And, it breaks cross
building, too.
I have made the patch to fix this problem. It adds a new target "boot"
into Makefile.inc1. Because, the
My NIS client FreeBSD-CURRENT 1.2 GHz Athlon seems to be badly
affected by network loads in terms of its NIS client activities.
This is not a new problem and has been present ever since I've
been a NIS client (~ 2 years) and I update monthly or so
(with the last update being 5 days ago).
Does Fr
Peter Wemm wrote:
> > a new made world and kernel from last night (09/22) cvsup,
> > and is unable to cvsup again tonight (09/23).
> > [donny@sys]/usr/src> cvsup
> > /usr/libexec/ld-elf.so.1: /usr/lib/libutil.so.3: Undefined symbol
> > "__stdoutp"
> Read UPDATING. You have an old libc.so.4. You
On 24-Sep-01 Marcel Moolenaar wrote:
> On Mon, Sep 24, 2001 at 04:53:16PM +0900, Takahashi Yoshihiro wrote:
>>
>> It uses the boot programs in /boot. So, even if we change boot0 and/or
>> mbr, the new sysinstall includes old one. And, it breaks cross
>> building, too.
>>
>> I have made the patc
On Mon, Sep 24, 2001 at 12:33:32PM -0700, John Baldwin wrote:
>
> On 23-Sep-01 Wilko Bulte wrote:
> > On Thu, Sep 20, 2001 at 07:40:52PM +0200, Wilko Bulte wrote:
> >> On Wed, Sep 19, 2001 at 01:32:28PM -0700, John Baldwin wrote:
> >> >
> >> > On 19-Sep-01 Wilko Bulte wrote:
> >> > > On Tue, Sep
On Mon, Sep 24, 2001 at 12:33:32PM -0700, John Baldwin wrote:
>
> On 23-Sep-01 Wilko Bulte wrote:
> > On Thu, Sep 20, 2001 at 07:40:52PM +0200, Wilko Bulte wrote:
> >> On Wed, Sep 19, 2001 at 01:32:28PM -0700, John Baldwin wrote:
> >> >
> >> > On 19-Sep-01 Wilko Bulte wrote:
> >> > > On Tue, Sep
OOPS. That's what I get for just looking individual bits of the tree.
Of course, ru not only removed the code from the
compat/compat4x.i386/Makefile but also added some to compat/Makefile
to work [better] for everything.
Sorry for any confusion I introduced.
Bill
To Unsubscribe: send mail t
MFC to 4.4-RELEASE ?
Does this means that there is NO correct way to make
4.4-RELEASE on the latest -CURRENT ?
In article <[EMAIL PROTECTED]> you wrote:
> MFC of mknodes.c,v 1.13 is needed to pass this.
>
> On Fri, Sep 21, 2001 at 02:24:46PM +0700, Nickolay Dudorov wrote:
>> When
In article <[EMAIL PROTECTED]>
Marcel Moolenaar <[EMAIL PROTECTED]> writes:
> On Mon, Sep 24, 2001 at 04:53:16PM +0900, Takahashi Yoshihiro wrote:
> >
> > It uses the boot programs in /boot. So, even if we change boot0 and/or
> > mbr, the new sysinstall includes old one. And, it breaks cross
> >
On Tue, Sep 25, 2001 at 11:27:58AM +0900, Takahashi Yoshihiro wrote:
> > >
> > > It uses the boot programs in /boot. So, even if we change boot0 and/or
> > > mbr, the new sysinstall includes old one. And, it breaks cross
> > > building, too.
> > >
> >
> > I'm not sure this is the right way to d
Why can I "rcp" to my FreeBSD-CURRENT box (built Sept 19th) with
no password when I dont even have a .rhosts file (I dont have an
/etc/hosts.equiv either).
I can also "rsh freebie command" with no prompt for password.
I assume this is due to the upgrade of PAM.
Looking on a RedHat 7.1 system I
Can someone please share with us the magic to disable acpi and add
it to src/UPDATING, my sound fell victim to acpi and i think I just
lost my mouse to it. Now I have a lapbrick that consumes less
power...
"yay"
--
-Alfred Perlstein [[EMAIL PROTECTED]]
'Instead of asking why a piece of softwar
36 matches
Mail list logo
