Hi!
This was tricky. Due to the old bug in release/Makefile (it did
not pass -DRELEASE_CRUNCH when building list of object files for
crunched binary), ${OBJS} list for ppp was computed incorrectly,
and ppp/Makefile had a special glue to build empty object files:
: .if defined(RELEASE_CRUNCH)
:
On 29-Mar-01 Jesper Skriver wrote:
> On Thu, Mar 29, 2001 at 01:13:09PM -0800, John Baldwin wrote:
>> >
>> > Index: src/sys/dev/pccbb/pccbb.c
>> > ===
>> > RCS file: /home/ncvs/src/sys/dev/pccbb/pccbb.c,v
>> > retrieving revision 1.
Hi
I have an SMP kernel with I586 and I686 support. If I boot it
on a 686 it works. On a 586 it craps out with
CPU1 stopping CPUs: 0x0001... Stopped.
Stopped at i586_bzero_oops+0x1:jmp i586_bzero_oops
late into the boot (during network/RPC init stuff).
I thought the 586 FP stu
On Thu, Mar 29, 2001 at 01:13:09PM -0800, John Baldwin wrote:
> >
> > Index: src/sys/dev/pccbb/pccbb.c
> > ===
> > RCS file: /home/ncvs/src/sys/dev/pccbb/pccbb.c,v
> > retrieving revision 1.12
> > diff -u -r1.12 pccbb.c
> > --- src/s
On 28-Mar-01 Jesper Skriver wrote:
> On Wed, Mar 28, 2001 at 10:15:21PM +0200, Niels Chr. Bank-Pedersen wrote:
>> On Wed, Mar 28, 2001 at 10:09:28PM +0200, Jesper Skriver wrote:
>> > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs
>> > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-
* Michael Class <[EMAIL PROTECTED]> [010329 02:36] wrote:
> Hello,
>
> on a FBSD-5.0-current (as of yesterday) system I am having a
> question about the way malloc works. The manpage states
> that malloc cannot be recursed. Does this mean that our
> malloc is not thread safe? I checked the manpag
On a -current from this morning, I can reliably trigger a panic by
"make release" (I believe the problem has existed for some time,
though).
The box can do make worlds without problem, but during make release,
it stumples at the same place every time.
This is a Dual P3 with all involved filesystem
subscribe
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi Ruslan,
>
> Could you please try the attached patch and let me know?
>
> I had to move -DRELEASE_CRUNCH to *_fixit.conf so that
> ${OBJS} are computed correctly for usr.bin/telnet.
I have tried it, but now it breaks in boot_crunch:
##
cc -O -pipe-DCRUNCHED_BINARY -c tunefs_stub
John!
Could you please try the attached patch and let me know?
I had to move -DRELEASE_CRUNCH to *_fixit.conf so that
${OBJS} are computed correctly for usr.bin/telnet.
On Thu, Mar 29, 2001 at 10:08:50AM +0200, John Hay wrote:
> > On Wed, Mar 28, 2001 at 01:00:59PM +0300, Ruslan Ermilov wrote:
Bruce Evans wrote:
>
> On Wed, 28 Mar 2001, John Baldwin wrote:
>
> > On 28-Mar-01 Terry Lambert wrote:
> > > Run the 4.3 mountd on it.
> > >
> > > Boom! Kernel memory allocation way to large; unrecoverable!
>
> Does this really panic -current? It panics old versions of -current, and
> the -c
Hello,
on a FBSD-5.0-current (as of yesterday) system I am having a
question about the way malloc works. The manpage states
that malloc cannot be recursed. Does this mean that our
malloc is not thread safe? I checked the manpage on HPUX
and there it explicitely states that malloc is thread-safe.
On Wed, Mar 28, 2001 at 11:07:02PM -0600, Conrad Sabatier wrote:
>
> On 29-Mar-2001 Kris Kennaway wrote:
> > On Wed, Mar 28, 2001 at 10:20:33PM -0600, Conrad Sabatier wrote:
> >> I've been notified that one of the ports I'm responsible for, xswallow, will
> >> no longer build under -current. Her
On Wed, 28 Mar 2001, Georg-W. Koltermann wrote:
> I am experiencing a strange lockup with -current as of about a week
> ago: It will suspend and resume, but after the resume the console is
> dead and the system hangs after a short while.
>
> When I type on the console after a resume, nothing is
14 matches
Mail list logo
