buildkernel breakage on Today's kernel
../../dev/bktr/bktr_os.c: In function `bktr_detach': ../../dev/bktr/bktr_os.c:484: `unit' undeclared (first use in this function) ../../dev/bktr/bktr_os.c:484: (Each undeclared identifier is reported only once ../../dev/bktr/bktr_os.c:484: for each function it appears in.) More logfile: URL:http://current.jp.FreeBSD.org/build/i386/LINT/5.0-CURRENT-20001020-JPSNAP.bad -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
jkh I'll look into this tomorrow morning, thanks. 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). -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
On Fri, Oct 20, 2000 at 07:58:09AM +0200, 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 to /dev/random not reseed it but _reset_ it to the same default state. How do you shutdown your machine: a) reboot or halt b) shutdown -r now If a) the /entropy file is not updated and the existing one will be used at next reboot. Only when using shutdown the /etc/rc.shutdown file will be executed. That was a problem for me, as I often use "halt". I shutdown my machine via Ctrl-Alt-DEL and see "Writting entropy file" message on console, i.e. rc.shutdown is activated. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
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 same default state. BTW, I can't reproduce it on the machine with ethernet card, it happens only on my home dialup machine. It seems random can gather something from ethernet which masks this bug. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
From: Makoto MATSUSHITA [EMAIL PROTECTED] Subject: Re: current.freebsd.org problems? Date: Fri, 20 Oct 2000 15:30:30 +0900 $ 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 hung up when "make release". then, log is below: sh -e /usr/src/release/scripts/doFS.sh -s mfsroot /R/stage /mnt 2880 /R/stage/mfsfd 8000 minimum2 disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 6. Warning: 2432 sector(s) in last cylinder unallocated /dev/rvnn0c:5760 sectors in 2 cylinders of 1 tracks, 4096 sectors 2.8MB in 1 cyl groups (6 c/g, 12.00MB/g, 384 i/g) super-block backups (for fsck -b #) at: 32 3700 blocks Filesystem 1K-blocks UsedAvail Capacity iused ifree %iused Mounted on /dev/vnn0c 2803 1868 71172% 67 31518% /mnt Filesystem is 2880 K, 711 left 8000 bytes/inode, 315 left mfsroot: 71.4% --- Masanori Kanaoka [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
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 to /dev/random not reseed it but _reset_ it to the same default state. How do you shutdown your machine: a) reboot or halt b) shutdown -r now C-A-D usually works too, as does 'init 6'. One of the oft-agreed on topics at the con is that we need a _consistent_ schedule of events for all forms of shutdown that are not explicitly "fast" shutdown paths that for whatever reason we don't want to schedule things like rc.shutdown and sync for. Expect to see conversation about this on -arch sometime soon. Doug -- "The dead cannot be seduced." - Kai, "Lexx" Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
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 failed at buildworld. Oct/18/2000, panic. Oct/19/2000, also panic. -- - Makoto `MAR' MATSUSHITA To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
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 Kanaoka [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org problems?
$ 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" when the source is not broken. :-) I'm trying now again after the bktr fix went in. John -- John Hay -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PCI device IDs sourses?
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
Re: PCI device IDs sourses?
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] Arnhem, the Netherlands To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
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 same default state. 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. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: entropy reseeding is totally broken
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 that anything writted to /dev/random not reseed it but _reset_ it to the same default state. 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! BTW, 16384 is _minimal_ value, all lower values _not_ cause reseeding. I don't know, why. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
X server setting
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
Re: entropy reseeding is totally broken
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 _not_ make that commit. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: I18N Paper URL
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 they're legally imported..
SFO, HKG, and TW airport allowed me taking 12 bottles of beer)
--
CirX - This site doesnt' exist.
9c k9o h9 s1bg s1f, 7v .y xqx a sj m8r ffg1 vg5 a6 asox tmul h38 .
ant sj m8r ob ? 1fj mwby a1 tao vg5. soq df v ' .a. CirX.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
current.freebsd.org back up
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
Re: I18N Progress, Plans, and Proposals
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 regarding the following: | 2. Needing a graphics console to display various character sets. | There should be a kernel or loader option to start | a graphics console by default. | The magic word is option :) | We have to be careful to not loose the ability to boot a bare-bone system | if / when having problems. Right, it will/should be an option. | I _still_ like VAX/VMS ability to be "talked" up thru the boot process. Er, *meep* too young to know what you are talking about -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: new library: libisc
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. The main thing I'm interested in is the event library, but there is other useful stuff in there too. Yes please! This is something I've wanted to have in the system for a long time. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: I18N Progress, Plans, and Proposals
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 get called whenever front-line tech support | is confronted with a "I have error 2398423" question), that this can | also be a tremendous pain in the butt when done wrong. The format I have in mind is more like: kern.pci.cardbus.insert.ed0 kern.net.tcpip.route.not-responding.gateway.123.233.233.100 kern.pci.pcm.yamaha.ptr.mem.0xfedf8000.irq9.device.9.on-pci0 | Done wrong, a message catalog-using program will emit cryptic numeric | errors whenever a message catalog file cannot be found or is | corrupted. Done right, the program is written in such a way as to | contain a default message which can also be overridden from the | message catalog file if some different text is found in the | appropriate language. I believe this is the way that catgets(3) | currently works, but you'd be amazed how many programmers just skip | providing a default message since the appropriate message catalog is | always found on *their* system. | | There's also nothing more unreadable than code which tests a failure | condition and then calls a message catalog routine with some numeric | constant, the actual text of the error message being an aid to the | programmer as well as the user when reading someone else's code and | trying to figure out what varioups parts of it are trying to do. So can we output the message catalogue name along with the plaintext message? -- +--+ | [EMAIL PROTECTED] | [EMAIL PROTECTED] | | http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. | +--+ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Junior Kernel Hacker Task: M_ZERO
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(databuf, length); New code: databuf = malloc(length, M_DEVBUF, M_WAITOK | M_ZERO); Short term the benefit is less clutter in the code and a smaller cache footprint of the kernel. Long term, this will allow us to optimize malloc(9) by allocating from a pool of memory which is zero'ed whenever the cpu is idle. If anybody is looking for a simple task to perform in the FreeBSD kernel: this is it. A quick grep tells me that there are at least 91 files in the src/sys tree which could use this flag to simplify and optimize the code. The ground rules for such a cleanup are: Respect the style of the source file. Don't make unrelated changes: If you spot other issues with the code as you read it, make a separate diff for those issues. Bundle the patches at administrative boundaries: a directory at a time, a driver at a time etc etc. Submit changes to the maintainer of the file (if any) or with send-pr. Junior committers are encouraged to review and commit these PR's as they arrive -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sys/i386/i386/machdep.c:cpu_idle() changes causes this Was: Re:kernel trap 12 with interrupts disabled
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 {
enable_intr();
__asm __volatile("hlt");
}
}
#endif
}
it works again.
I'm running SMP kernel on Dual PIII machine.
Regards,
Val
On Thu, 19 Oct 2000, Valentin Chopov wrote:
I got the same with addition that the machine hangs:(
Val
On Wed, 18 Oct 2000, Manfred Antar wrote:
With current kernel I'm getting alot of :
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
Kernel from yesterday did not do this.
Everything seems to work fine although I think it hung on a "shutdown -r now"
I don't have a monitor hooked up to the machine right now, so I have no further
info.
I'm in process of hooking up a serial console.
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
fsck not rewriting super block?
Hi, I've run into an interesting problem: ad0: 19473MB Maxtor 92049U6 [39566/16/63] at ata0-master UDMA33 ad1: 19541MB Maxtor 52049H4 [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# (Cyl.0 - 10402*) c: 400205610unused0 0 # (Cyl.0 - 39702*) e: 25165824 104857604.2BSD 1024 819216 # (Cyl. 10402*-35368*) f: 4368977 356515844.2BSD 1024 819216 # (Cyl. 35368*-39702*) However, the f partition will not fsck correctly: %/sbin/fsck -y /dev/ad1s1f ** /dev/ad1s1f BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE LOOK FOR ALTERNATE SUPERBLOCKS? yes USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1 files, 1 used, 2116933 free (13 frags, 264615 blocks, 0.0% fragmentation) UPDATE STANDARD SUPERBLOCK? yes * FILE SYSTEM WAS MODIFIED * So, running fsck again produces the same identical output. The superblock is not updated. No failures are reported on the console or in the messages file. System is current: FreeBSD 5.0-CURRENT #0: Thu Oct 19 Any ideas on the best way to track this down are appreciated. Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Junior Kernel Hacker Task: M_ZERO
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-pr. Even relatively large diffs? It is ok to send them directly to [EMAIL PROTECTED]? -- Robert S. F. Drehmel [EMAIL PROTECTED] "Do not ask me; I am the programmer." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: sys/i386/i386/machdep.c:cpu_idle() changes causes this Was:
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 even further on SMP machines. -- John Do you have any idea what's causing this ? Oct 20 21:20:36 pozo last message repeated 17 times Oct 20 21:30:00 pozo last message repeated 4 times Oct 20 21:30:00 pozo last message repeated 4 times Oct 20 21:41:26 pozo last message repeated 9 times Oct 20 21:41:26 pozo last message repeated 9 times Oct 20 21:50:01 pozo last message repeated 13 times Oct 20 21:50:01 pozo last message repeated 13 times #dmesg kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled kernel trap 12 with interrupts disabled this is a very truncated version there are probably 301 messages like this in a SMP machine that has only been up about 4 hours with very little activity , just a few cvsups and mail. If I build a kernel then the messages really increase. If there is any thing I can do Thanks Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
