kana> I have same experience.My current-box was hung up when "make release".
kana> then, log is below:
Ya, exactly the same point of current.jp.FreeBSD.org. The same story
should be applied to current.FreeBSD.org. We cannot make a -current
distribution now. Changes from Oct/10/2000 to now cause
:484: (Each undeclared identifier is reported only once
> ../../dev/bktr/bktr_os.c:484: for each function it appears in.)
>
> More logfile:
>http://current.jp.FreeBSD.org/build/i386/LINT/5.0-CURRENT-20001020-JPSNAP.bad>
>
> -- -
> Makoto `MAR' MATSUSHITA
>
>
> $ I'm very interested if current.jp.freebsd.org was hung up when "make
> $ release" procedure was running. current.jp.freebsd.org was hung up in
> $ these two days, when making a boot floppy (the hungup was occured
> $ *exactly* the same point).
>
> I have same experience.My current-box was hun
On Fri, 20 Oct 2000, Udo Schweigert wrote:
> On Fri, Oct 20, 2000 at 08:48:46 +0400, Andrej Cernov wrote:
> > In very recent -current, my entropy file writted and readed sucessfully,
> > but I got the same fortune quote again and again right after reboot!
> >
> > It means that anything writted t
jhay> For now I just went back to an older kernel that works for me.
Would you please explain "an older kernel" ? I'm using a kernel as of
Sep/30/2000 and it panics.
***
Note that this (Sep/30/2000) kernel doesn't panic until Oct/13/2000.
Between Oct/14/2000 and Oct/17/2000, "make release" was
From: John Hay <[EMAIL PROTECTED]>
Subject: Re: current.freebsd.org problems?
Date: Fri, 20 Oct 2000 10:07:14 +0200 (SAT)
$ For now I just went back to an older kernel that works for me.
How older is your kernel?
My kernel build 2000-09-21 JST. It panic when "make release".
---
Masanori Kanaok
>
> $ For now I just went back to an older kernel that works for me.
>
> How older is your kernel?
> My kernel build 2000-09-21 JST. It panic when "make release".
Not that old. 2000-10-05. The machine is a dual 266MHz PII. I have
no problem building releases using "NODOC=YES WORLD_FLAGS=-j4" wh
Does anybody know PCI devices IDs database on-line (at least for Intel
chips...)?
I have lots of unknown IDs for ASUS CUSL2 card...
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, Oct 20, 2000 at 05:48:03PM +0400, Andrej Cernov wrote:
> Does anybody know PCI devices IDs database on-line (at least for Intel
> chips...)?
> I have lots of unknown IDs for ASUS CUSL2 card...
http://www.yourvote.com/pci/
--
Wilko Bulte
[EMAIL PROTECTED] Arnh
On Fri, Oct 20, 2000 at 08:48:46AM +0400, áÎÄÒÅÊ þÅÒÎÏ× wrote:
> In very recent -current, my entropy file writted and readed sucessfully,
> but I got the same fortune quote again and again right after reboot!
>
> It means that anything writted to /dev/random not reseed it but _reset_ it
> to the
On Fri, Oct 20, 2000 at 08:27:53PM +0400, áÎÄÒÅÊ þÅÒÎÏ× wrote:
> On Fri, Oct 20, 2000 at 08:48:46AM +0400, áÎÄÒÅÊ þÅÒÎÏ× wrote:
> > In very recent -current, my entropy file writted and readed sucessfully,
> > but I got the same fortune quote again and again right after reboot!
> >
> > It means th
Does anyone have X server settings for an ATI Rage pro 128 graphics card &
Eizo lcd monitor L661 ?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> It seems I find the problem area. 4096 bytes written in rc.shutdown are
> not enough for reseeding. When I change them to 16384 bytes, it works!
> I'll commit working rc.shutdown variant.
This is bogus.
_Any_ randomness written to /dev/random is good enough to perturb the
sequence.
Please do
On Thu, Oct 19, 2000 at 02:26:39PM -0500, Michael C . Wu wrote:
> http://www.ece.utexas.edu/~mwu/{presentation.ps,i18n.*}
> This is our paper presented at BSDCon.
Thanks ... Please don't send the wrong version next time. :-)
Oh, could you put pictures about Taiwan Beer on web as well ?
(I think t
snapshots are still broken, but you can at least get the previous
ones via ftp now.
- jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Thu, Oct 19, 2000 at 08:38:47PM +0200, Johan Granlund scribbled:
| On Thu, 19 Oct 2000, Michael C . Wu wrote:
| > At the BSDCon I18N BOF, we discussed several things that could/should
| > happen with the future of I18N(internationalization) in FreeBSD.
| > We would like some inputs and comments
In article <[EMAIL PROTECTED]>, Archie
Cobbs <[EMAIL PROTECTED]> wrote:
> Absent violent rejection, I'd like to add the ISC utility library
> to the FreeBSD build. If you're not familiar, check out the man
> pages /usr/src/contrib/bind/lib/isc/*.mdoc. There are several useful
> utilities in there
On Thu, Oct 19, 2000 at 01:16:12PM -0700, Jordan Hubbard scribbled:
| > The advantages are :
| > A. Easy bug reporting by users. (e.g. "I have error 2398423")
| > B. I18N error messages
|
| Let me just say, as someone who's done "escalation tech support" for
| major ISVs (the people who
I have introduced the M_ZERO flag to the kernel malloc, which provides
the service to bzero() the memory allocted.
In the kernel sources, the archetypical change to use this facility
looks like this:
Old code:
databuf = malloc(length, M_DEVBUF, M_WAITOK);
bzero(dat
I found that if I remove #ifndef SMP /#endif in:
sys/i386/i386/machdep.c:
void
cpu_idle(void)
{
#ifndef SMP
if (cpu_idle_hlt) {
disable_intr();
if (procrunnable())
enable_intr();
else {
enabl
On Fri, Oct 20, 2000 at 10:06:37AM -0700, Mark Murray wrote:
> > It seems I find the problem area. 4096 bytes written in rc.shutdown are
> > not enough for reseeding. When I change them to 16384 bytes, it works!
> > I'll commit working rc.shutdown variant.
>
> This is bogus.
>
> _Any_ randomness
On 20-Oct-00 Valentin Chopov wrote:
> I found that if I remove #ifndef SMP /#endif in:
Errr, this doesn't really make sense, and if anything is probably
hiding the problem. Also, this change will potentially increase
interrupt latency even further on SMP machines.
--
John Baldwin <[EMAIL P
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Hi,
I've run into an interesting problem:
ad0: 19473MB [39566/16/63] at ata0-master UDMA33
ad1: 19541MB [39703/16/63] at ata0-slave UDMA33
I have swap and two large partitions on ad1:
#size offsetfstype [fsize bsize bps/cpg]
b: 104857600 swap
In <17100.972069144@critter>, Poul-Henning Kamp wrote:
> If anybody is looking for a simple task to perform in the FreeBSD
> kernel: this is it.
Is it necessary to announce it somewhere, when I want to do that?
>Submit changes to the maintainer of the file (if any) or
>with send-
At 01:21 PM 10/20/2000 -0700, John Baldwin wrote:
>On 20-Oct-00 Valentin Chopov wrote:
>> I found that if I remove #ifndef SMP /#endif in:
>
>Errr, this doesn't really make sense, and if anything is probably
>hiding the problem. Also, this change will potentially increase
>interrupt latency ev
jhay> Not that old. 2000-10-05.
Hmm. I'll try it later, thank you.
***
I've tried with a kernel as of Oct/07/2000, kernel also panics.
However, panic point is different:
mfsroot: 71.5% <<-- THE POINT OF LAST HUNGUP
disklabel: ioctl DIOCWLABEL: Operation not su
On Sat, 21 Oct 2000, Makoto MATSUSHITA wrote:
> Yes, during a newfs. Console shows following messages:
>
> /mnt: bad dir ino 2 at offset 0: mangled entry
> panic: ufs_dirbad: bad dir
>
> syncing disks...
Hmm, I've seen the same panic with pre-SMPng kernel when booting
>From
>http://current.jp.FreeBSD.org/build/i386/LINT/5.0-CURRENT-20001021-JPSNAP.bad>:
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include -DGP
29 matches
Mail list logo
