Re: singed short to unsigned long conversion problem in isa.c
: The assumption that an I/O port address is lower than 0x8000 is OK for : IBM-PC's ISA-bus, but PC98 can use hiher addresses for ISA-bus like : bus. : :I understand. I think the best thing is to store the port address as an :int. I don't think there is a need to fork the file into a pc98 version. : :-- :Doug RabsonMail: d...@nlsystems.com :Nonlinear Systems Ltd. Phone: +44 181 442 9037 I would recommend making it an unsigned short, and representing the -1 case with a '#define BAD_PORT ((unsigned short)-1)'. All representations and tests for this special case would be required to use the #define rather then a constant. -Matt Matthew Dillon dil...@backplane.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
quotas are broken?
Is anyone using quotas on -current or -stable on SMP machines and has it working? Several of my friends are experiancing weird stuff with them enabled, either total lockups, or slowdowns so bad that the machine becomes unsuable quite quickly. The problems are supposedly quite easy to trigger, especially on SMP boxes. This is preventing deployment of FreeBSD in several critical areas for a number of my friends in the ISP business. any help would be appreciated, and i apologize for not having more information available about what triggers it, but again it's supposedly very easy to trigger. http://www.freebsd.org/cgi/query-pr.cgi?pr=11004 thanks, -Alfred To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
night make buildworld failed...
Hello! Night make buildworld failed: === sys/modules/fxp @ - /usr/src/sys machine - /usr/src/sys/i386/include echo #define NFXP 1 fxp.h echo #define NBPFILTER 0 bpfilter.h touch opt_bdg.h perl /usr/src/sys/modules/fxp/../../kern/makedevops.pl -h /usr/src/sys/modules/fxp/../../kern/device_if.m perl: not found *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Rgdz, Osokin Sergey aka oZZ, o...@etrust.ru To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
procfs-rlimit patch
Sorry for the delay on this one. http://www.freebsd.org/~adrian/procfs-rlimit/ Thats a patch against -current as of a few days ago, and a README. Any suggestions / improvements are welcome. Adrian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: procfs-rlimit patch
In message 19990425094122.22629.qm...@ewok.creative.net.au, adr...@freebsd.or G writes: Sorry for the delay on this one. http://www.freebsd.org/~adrian/procfs-rlimit/ Thats a patch against -current as of a few days ago, and a README. Any suggestions / improvements are welcome. I think we need the names in there, something like: cputime -1 -1 filesize -1 -1 ... Mode 0444 is fine with me. -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: night make buildworld failed...
Night make buildworld failed: === sys/modules/fxp @ - /usr/src/sys machine - /usr/src/sys/i386/include echo #define NFXP 1 fxp.h echo #define NBPFILTER 0 bpfilter.h touch opt_bdg.h perl /usr/src/sys/modules/fxp/../../kern/makedevops.pl -h /usr/src/sys/modules/fxp/../../kern/device_if.m perl: not found *** Error code 1 This is probably caused by using the NOPERL option. Don't use it. It shouldn't exist, since perl is not optional. It is used by `make world' for at least building fxp and updating the man page indexes. The latter uses the wrong version of perl (/usr/bin/perl) so it fails when DESTDIR is set and perl is not already installed. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
VESA screenmodes
Hello -CURRENTers, I CVSup every night, and a couple of days ago my 'vidcontrol VESA_132x60' line in my /etc/rc.local stopped working. The VESA-related lines in my config file are: VIDEO CONTROLLER device vga0 at isa? port? conflicts optionsVGA_ALT_SEQACCESS # optionsVESA# VESA BIOS support optionsVM86# Required by the vga0 driver What's going on? -- [gjvc] To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: procfs-rlimit patch
Poul-Henning Kamp writes: In message 19990425094122.22629.qm...@ewok.creative.net.au, adr...@freebsd.or G writes: Sorry for the delay on this one. http://www.freebsd.org/~adrian/procfs-rlimit/ Thats a patch against -current as of a few days ago, and a README. Any suggestions / improvements are welcome. I think we need the names in there, something like: cputime -1 -1 filesize -1 -1 ... Mode 0444 is fine with me. Which means that we need an array in sys/resource.h containing the names - something I wanted to double check before I did it. Adrian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: procfs-rlimit patch
In message 19990425164902.23274.qm...@ewok.creative.net.au, adr...@freebsd.or G writes: Poul-Henning Kamp writes: In message 19990425094122.22629.qm...@ewok.creative.net.au, adr...@freebsd.or G writes: Sorry for the delay on this one. http://www.freebsd.org/~adrian/procfs-rlimit/ Thats a patch against -current as of a few days ago, and a README. Any suggestions / improvements are welcome. I think we need the names in there, something like: cputime -1 -1 filesize -1 -1 ... Mode 0444 is fine with me. Which means that we need an array in sys/resource.h containing the names - something I wanted to double check before I did it. And we should change all other users to use it too :-) -- Poul-Henning Kamp FreeBSD coreteam member p...@freebsd.org Real hackers run -current on their laptop. FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
config nit
Hi, I just noticed that after all the dequote stuff went into config (great work!) options NO_F00F_HACK still needs quotes. Its interpreted as NO_F0F_HACK without them; to be expected I guess. This should probably be reflected in LINT. Thanks, Jake -- we are but packets in the internet of life To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: config nit
Hi, I just noticed that after all the dequote stuff went into config (great work!) options NO_F00F_HACK still needs quotes. Its interpreted as NO_F0F_HACK without them; to be expected I guess. It also translates unsigned hex to signed decimal, so N0xF00F_HACK becomes N61455_HACK, and it prints the translated version in the warning message about unknown options. Bruce To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
config NO_F00F_HACK
Hi, # ident LINT LINT: $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ with: option NO_F00F_HACK # config WORK WORK:15: unknown option NO_F0F_HACK with: option NO_F00F_HACK # config WORK Don't forget to do a ``make depend'' Bye, Alexander. -- http://netchild.home.pages.de A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Network problem with Laptop/Current.
When I try to configure my D-Link de-660 pcmcia card with a kernel from sources from the last 5 days or so, I get the following: PC-Card VLSI 82C146 (5 mem 2 I/O windows) pcic: controller irq 5 Card inserted, slot 2 Card inserted, slot 3 ed0: address 00:80:c8:8c:03:8d, type NE2000 (16 bit) Fatal trap 12: page fault while in kernel mode fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01ac150 stack pointer = 0x10:0xc60f0d58 frame pointer = 0x10:0xc60f0d60 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 424 (ifconfig) interrupt mask = net tty trap number = 12 panic: page fault syncing disks... 8 4 done Automatic reboot in 15 seconds - press a key on the console to abort With a kernel from April 20 everything works except my pcmcia Viking Modem which hasn't worked since last weekend. Is anyone else else having this problem? Could I be doing something wrong? Thanks, ed (This is a generic AMS K6-300 .) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network problem with Laptop/Current.
It seems Edwin Culp wrote: When I try to configure my D-Link de-660 pcmcia card with a kernel from sources from the last 5 days or so, I get the following: PC-Card VLSI 82C146 (5 mem 2 I/O windows) pcic: controller irq 5 Card inserted, slot 2 Card inserted, slot 3 ed0: address 00:80:c8:8c:03:8d, type NE2000 (16 bit) Try the patch I posted a couble of days ago, that does it for me... -Søren To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: suspend mode broken since one week ago
WL == Warner Losh i...@harmony.village.org writes: WL In message 87so9r3x44@muon.xs4all.nl Peter Mutsaers writes: WL : Is this a bug that I should report through send-pr, is it already WL : known as a bug or is this an intentional change in behaviour? WL This is a known bug. I thought I kludged around it in apm.c in the WL timeframe that you mentioned. Do you have WL $Id: apm.c,v 1.80 1999/04/21 07:57:55 imp Exp $ WL or newer? Today I did a cvsup which upgraded apm.c from 1.79 to 1.80. Now after a reboot when X starts, the screen gets garbled and crashes after a while. When I press the suspend button and resume from suspend, the system reboots. I don't know if apm.c is causing this (probably the screen corruption and crash has another cause). -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know p...@xs4all.nl | the Netherlands| what I'm doing. ---+-+-- Running FreeBSD-current UNIX. See http://www.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new-bus, pcm, and matcd (was Re: new-bus breaks both sound drivers)
On Sat, 24 Apr 1999, Chris Csanady wrote: Ugh. This also has the same effect on captured audio using fxtv. It seems that everything audio related is messed up now. (Or perhaps real time?) I will try to find the exact day where things broke I guses. I don't have much time right now though.. FWIW, I can still play audio CDs... perhaps its time to shake the dust off some CDs? ;) - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: config NO_F00F_HACK
On Sun, Apr 25, 1999, a.leidin...@wurzelausix.cs.uni-sb.de wrote: Hi, # ident LINT LINT: $Id: LINT,v 1.589 1999/04/24 21:45:44 peter Exp $ with: option NO_F00F_HACK # config WORK WORK:15: unknown option NO_F0F_HACK ^ You made a typo. -- Chris Costelloch...@calldei.com Make sure all variables are initialized before use. pgpyX4tJId8X8.pgp Description: PGP signature
Encanto Networks chooses FreeBSD over Linux
Just came across an interesting article in Investor's Business Daily (April 26th issue) in the Computers and Technology section. The title is Windows Foes Pose A Threat: Ex-Novell CEO. In it Bob Frankenberg cites the reason why his company chose FreeBSD over Linux: they did a very careful evaluation and found that there was a 2-1 or 3-1 improvement over Linux. ... A lot of work had been done to maximize transaction-processing performance. But Linux, on the other hand, performs better for individual use because of better network performance. Hmm, are we finally getting good press coverage? I am sure this did not happen by accident. There must be an effort going on to get this kind of press coverage. Good job, guys. Carlos C. Tapang http://www.genericwindows.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
-current compile failure (cvsup'ed today)
I just cvsup'ed today at around 4:00pm and I got this when building world. bison -y -d -o bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y conflicts: 1 shift/reduce cc -L/opt/gnome/lib -I/opt/gnome/include -L/usr/local/lib -I/usr/local/include -I. -I/usr/src/gnu/usr.bin/bc -I/usr/src/gnu/usr.bin/bc/../../../contrib/bc/h -DHAVE_CONFIG_H -I/usr/obj/usr/src/tmp/usr/include -c bc.c /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y: In function `yyparse': /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `interactive' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: (Each undeclared identifier is reported only once /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: for each function it appears in.) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:108: `quiet' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:170: `break_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:174: `genstr' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:181: `continue_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:200: `next_label' undeclared (first use in this function) /usr/src/gnu/usr.bin/bc/../../../contrib/bc/bc/bc.y:244: `if_label' undeclared (first use in this function) *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Shawn === America Held Hostage === Day 2286 for the poor and the middle class. Day 2305 for the rich and the dead. 636 days remaining in the Raw Deal. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Network problem with Laptop/Current.
PC-Card VLSI 82C146 (5 mem 2 I/O windows) It is probably TI CardBus controller, -current code not support it correctly. You should be use PAO. -- NAKAGAWA, Yoshihisa y-nak...@nwsl.mesh.ad.jp nakag...@jp.freebsd.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Fatal Trap 12
I updated my source tree, successfully did a make buildworld and installworld. Rebuilt the kernel. Upon reboot I encountered the following trap. Fatal Trap 12: page fault while in kernel mode mp_lock = 0002; cpuid = 0; lapic.id = fault virtual address = 0xbfc0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01dc935 stack pointer = 0x10:0xc0295ed8 frame pointer = 0x10:0xc0295ed8 code segment= base 0x0 limit 0xf type 0x1b = DPL 0, page 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL=0 current process = 0 () interrupt mask = net tty bio cam - SMP:XXX trap number = 12 mp_lock = 0002; cpuid = 0; lapic.id = When it dropped into ddb I got the following: stopped at kvtop+0x2d: movl PTmap(,%eax,4),%edx At trace in ddb provides the following: kvtop(0) at kvtop+0x2d isa_compat_probe(...) at isa_compat_probe+0x297 DEVICE_PROBE(...) at DEVICE_PROBE+0x25 device_probe_child(...) at device_probe_child+0x4a device_probe_and_attach(...) at device_probe_and_attach+0x25 bus_generic_attach(...) at bus_generic_attach+0x16 configure(0) at configure+0x46 main at main+0x83 begin at begin+0x55 This is an dual 233MMX system with hardware I have been using for several years without any problems. The last kernel I built was on 4 April. Everything worked fine. Also, the GENERIC kernel does works. I have looked through my config file and compared it against GENERIC and nothing seems to be out of wack. The fault occured right after probing the ppbus. I thought that might be the problem, but commenting out the ppbus stuff does not prevent it from faulting. Any suggenstions would be appriciated. Thanks Greg Shaffer To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
