Re: A question about max_uid
On Fri, 27 Apr 2001 00:15:55 +0900, Yoshihiro Koya wrote: Currently, I have nobody (uid = 65534) account as a default account on my box. It might be easy to guess that the maximum is greater than 65533. My question is why such a restricion still remains. From what I remember from my communication with Bruce Evans, the restrictions (mostly unenforced in our tree are there to protect old software compiled to use 16-bit UID values. By allowing unsigned 32-bit UID values in the system, you open the door for problems with software that uses smaller UID values. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Experiences with new dir allocation on FFS?
Bruce Evans wrote (2001/04/28): This is probably caused by write caching now being off by default in the ata driver, possibly amplified by not using soft updates. Without the new dir allocation, -current would be even slower :(. Yes, thanks. I really forgot on this change. My rough results are now: Old s./wc enabled New s./wc enabled New s./wc disabled tar xvfz8 minutes 4 minutes 14 minutes rm -r 5 minutes 1 minute2 minutes There is another reason for tar slowness: Current version of tar seems to be faster than our old system tar: 3m23 against 3m44 for tar xvfz with wc enabled. I think there are even bigger differences with tar cvfz and tar xvfz with wc disabled. -- Rudolf Cejka ([EMAIL PROTECTED]; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
sio overflows
Hi! So, I've recompiled my Kernel, and if I connect to the internet, my console is flooded by lots of sio overflows(on sio1), and my connection is very slow. My Modem(Elsa Microlink 56k internet) is on com2. Who can help me ? Thx in advance, Georg Funk To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Linux JDK 1.3 and hotspot (native threads)
On Fri, Apr 27, 2001 at 09:32:58PM -0400, Andrew Gallatin wrote: Georg-W. Koltermann writes: ... In order to get real performance I would like to run either the SUN JDK with -hotspot, or the IBM 1.3 JVM. Both of these use native linux threads. With a recent -current I can successfully execute small JAVA test programs, but when I start a real application (e.g. Together from togethersoft.com), it fails with a core dump. ... Can you try the kernel patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=26705 It sounds like this is going to get committed soon, but I'd like to know if it has any affect on your problem. Hi Drew, I tried the patch and found it makes no difference. The current SUN JVM (1.3.0_02) gives the SIG11 as I indicated before. The latest IBM JVM (IBM build cx130-20010329) hangs around and eats up CPU time. It mostly eats system time (usage is about 8% user, 91% system). A normal kill is ineffective, I have to send it a -9 in order to terminate. Also, are there any non commercial apps that demonstrate the problem? Or at least things that I don't have to sign my life away to get access to? Hmm, I don't use any. We are developing a large-scale JAVA servlet application, and that one provokes the SIG11, too. Moneydance, a shareware finance manager that I once evaluated (http://www.seanreilly.com), seems to run ok. If you really want to invest the time, you might go to togethersoft.com and download their product. They will send you an evaluation license as soon as you download the product, without any further request. But it's a big application, and you won't have any use for it unless you develop a large-scale JAVA application. -- Regards, Georg. -- Who in the world needs 2000 Windows? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: {id,rt}prio broken (at syscall level?)
On 29 Apr, Jake Burkholder wrote: Thanks, this should be fixed now. A break; was forgotten in some recent proc locking changes. I will test it after softdep_update_inodeblock: bwrite: got error 22 while accessing filesystem is fixed (I made a backup of / after reading the bugreport and before trying it myself). Bye, Alexander. -- I believe the technical term is Oops! http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Can't boot installer: integer divide fault
[Please CC me as I am a stable user and not on the -current list] I'm running stable on a box at home and wanted to check if the -current kernel fixed a problem with my CD-RW drive. So I downloaded the boot floppies from current.freebsd.org, the 20010419 snap (which John B. tells me installs OK on his system). I disabled nearly everything from the visual config, then quit from that. It got as far as PnP detection then failed with an integer divide fault. The following was on the screen (copied by hand!): sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: PNP0303 can't assign resources unknown: PNP0f13 can't assign resources fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc03085f5 stack pointer = 0x10:0xc080671c frame pointer = 0x10:0xc0806768 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor flags = Interrupts enabled, IOPL = 0 current process = 0 (swapper) trap number = 18 panic: integer divide fault I've attached a dmesg from a verbose boot of 4.3 on the same hardware. If there is any other info I can provide, please yell. Greg. Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-BETA2 #0: Tue Mar 13 23:31:29 GMT 2001 jkh@narf:/usr/src/sys/compile/GENERIC Calibrating clock(s) ... TSC clock: 398261307 Hz, i8254 clock: 1193160 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Pentium II Xeon/Celeron (398.27-MHz 686-class CPU) Origin = GenuineIntel Id = 0x652 Stepping = 2 Features=0x183f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00472000 - 0x040fcfff, 63483904 bytes (15499 pages) 0x0410 - 0x07ff7fff, 66027520 bytes (16120 pages) avail memory = 126283776 (123324K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f6a90 bios32: Entry = 0xfd7b0 (c00fd7b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x203 pnpbios: Found PnP BIOS data at 0xc00f6ae0 pnpbios: Entry = f:9fea Rev = 1.0 Other BIOS signatures found: ACPI: 000f6ac0 Preloaded elf kernel kernel at 0xc044c000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1):mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) npx0: math processor on motherboard npx0: INT 16 interface pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71908086) pcib0: Intel 82443BX (440 BX) host to PCI bridge on motherboard found- vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[10]: type 1, range 32, base f800, size 26 found- vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found- vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[20]: type 1, range 32, base 1000, size 4 found- vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base 1020, size 5 found- vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[90]: type 1, range 32, base 7000, size 4 found- vendor=0x1013, dev=0x6001, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 pci0: PCI bus on pcib0 pcib1: Intel 82443BX (440 BX) PCI-PCI (AGP) bridge at device 1.0 on pci0 found- vendor=0x12d2, dev=0x0018, revid=0x10 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f500, size 24 map[14]: type 1, range 32, base fc00, size 24 pci1: PCI bus on pcib1 pci1: NVidia/SGS-Thomson
ACPI: table load failed
Is this a bug? It's on an ASUS CUSL-2. ACPI debug layer 0x0 debug level 0x0 tbutils-0299: *** Warning: Invalid table signature found tbxface-0170: *** Error: AcpiLoadTables: Could not load RSDT: AE_BAD_SIGNATURE tbxface-0202: *** Error: AcpiLoadTables: Could not load tables: AE_BAD_SIGNATUR E ACPI: table load failed: AE_BAD_SIGNATURE Using $PIR table, 10 entries at 0xc00f1310 -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa There are four kinds of homicide: felonious, excusable, justifiable and praiseworthy... -- Ambrose Bierce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
WinModem Support/Learning the kernel Internals
Hi All, Is anyone looking into converting the Linux winmodem driver ( Lucent Technologies binary object file compiled together with the linux kernel serial driver) into a freebsd device? And another question, is there some documentation (other than the code) on how to use things like timers for devices, the kernel debugger, other useful kernel device development things :) Cheers, -- * Benjamin Close * [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WinModem Support/Learning the kernel Internals
On Tue, 1 May 2001 00:53:33 +0930 (CST) Benjamin Close [EMAIL PROTECTED] wrote: BC Hi All, BC Is anyone looking into converting the Linux winmodem driver ( I'm pretty certain not, although there was a post on USENET recently by someone claiming to have their LT Winmodem running - I have asked for details. -- Optimal hardware acceleration for Windows PC (Mac). 9.81 m/s/s applied for (at least) 2s followed by impact with solid object. Optimal software upgrade FreeBSD (OS-X). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sio overflows
Georg Funk wrote: I've recompiled my Kernel, and if I connect to the internet, my console is flooded by lots of sio overflows (on sio1), and my connection is very slow. They're probably silo overflows; silo (a word which refers to a tall, cylinder-shaped building for storing grain on a farm) is one name for the input buffer of a serial I/O chip (another name is FIFO, an acronym for First In, First Out). Anyway . . . a few questions about your setup: Are you using a serial cable that is set up to use hardware (CTS/RTS) flow control? Is your modem configured to use hardware flow control? If the answer to either of these questions is no, then you aren't using hardware flow control (even if you thought you were), and you are =very= likely to lose data. Fix the cable and/or modem settings. Is your serial port (sio1) identified as a 16550A (the A suffix is very important here) when FreeBSD starts up? If not, then you're at risk of losing data at high communication rates (especially if your computer is not extremely fast). Get a new serial card with 16550A support. Are you running the X Window System (XFree86) on the same computer while you are connected to the Internet? If so, which version? Does the serial I/O problem go away if you get out of X and work directly with the plain-text console? There is a known problem with serial I/O and version 4 of XFree86 -- though this problem doesn't seem to exist with the XFree86 version (3.3.6) that is included by default in FreeBSD. If you are using XFree86-4 and aren't willing to go back to version 3.3.6, there may be a workaround for the serial I/O problem; go to http://www.FreeBSD.org/cgi/query-pr.cgi and look up PR #26261 for more details. Rich Wales [EMAIL PROTECTED] http://www.webcom.com/richw/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: camcontrol stop / restart broken
On Sun, Apr 29, 2001 at 14:47:47 +0300, Tomi Vainio - Sun Finland - wrote: Kenneth D. Merry writes: Can you do the following: camcontrol stop da1 camcontrol tur da1 -v [ then you can start it back up with camcontrol start ] What I want to see here is the sense information coming back from the drive when it is spun down. The new error recovery code should be doing the same thing as the old error recovery code -- sending a start unit. For some reason it isn't doing the right thing, though. cat:~(10)# camcontrol stop da1 Unit stopped successfully cat:~(11)# camcontrol tur da1 -v Unit is not ready (pass1:ahc0:0:2:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass1:ahc0:0:2:0): CAM Status: SCSI Status Error (pass1:ahc0:0:2:0): SCSI Status: Check Condition (pass1:ahc0:0:2:0): NOT READY asc:4,2 (pass1:ahc0:0:2:0): Logical unit not ready, initializing cmd. required field replaceable unit: 2 This should be fixed as of rev 1.22 of scsi_all.c. There was an errant search and replace that caused the 'start' bit in the start/stop unit to always be set to 0 (stop). So automatic spinups wouldn't work, and 'camcontrol start' wouldn't work. Also messages file is full of these: Apr 29 00:55:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Apr 29 00:55:43 cat last message repeated 26 times Apr 29 00:57:43 cat last message repeated 359 times Apr 29 01:07:43 cat last message repeated 1793 times Apr 29 01:17:43 cat last message repeated 1794 times Apr 29 01:27:43 cat last message repeated 1793 times Apr 29 01:34:13 cat last message repeated 1122 times Apr 29 01:34:13 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Apr 29 01:34:13 cat last message repeated 43 times Apr 29 01:36:02 cat last message repeated 322 times I'd still like to know when these messages are cropping up. Ken -- Kenneth Merry [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cp -u patch
On Mon, Apr 30, 2001 at 09:56:09AM +0200, Sheldon Hearn wrote: Question is, do we want to add this to our cp? Bleh. :-) Blah. for i in `find /path/to/src`; do if [ $i -nt /path/to/dst/$i ]; then cp $i /path/to/dst/ fi done Do you also suggest we get rid of `more' as its functionality can be implimented using cat and sed? I personally find this option useful enough that I have to keep `gcp' around. I guess I got used to using a simular utility under M$-DOS and thus it makes sense to me. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cp -u patch
On Mon, 30 Apr 2001 09:30:27 MST, David O'Brien wrote: Do you also suggest we get rid of `more' as its functionality can be implimented using cat and sed? I personally find this option useful enough that I have to keep `gcp' around. That's part of my concern. A lot of our feature creep seems to come from folks who have one particular thing they do a lot, but that lots of other folks don't. Personally, I've _never_ needed such a feature in cp(1) _once_ in the 3 or 4 years that I've been using BSD UNIX. That doesn't make me right. It just makes me skeptical. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: camcontrol stop / restart broken
Kenneth D. Merry writes: This should be fixed as of rev 1.22 of scsi_all.c. There was an errant search and replace that caused the 'start' bit in the start/stop unit to always be set to 0 (stop). So automatic spinups wouldn't work, and 'camcontrol start' wouldn't work. Thanks, I'll test this soon. I'd still like to know when these messages are cropping up. I scanned messages files and it seems to start ~2 hours after I have tried to spin up the disk first time. Apr 28 23:01:40 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 28 23:08:10 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 00:49:42 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate CCB, can't continue Apr 29 14:40:00 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 14:44:31 cat /boot/kernel/kernel: (da1:ahc0:0:2:0): Invalidating pack Apr 29 16:34:04 cat /boot/kernel/kernel: (noperiph:ahc0:0:2:0): xpt_scan_lun: can't allocate path, can't continue Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ipfw: several equal rules under same number bug
Andrey == Andrey A Chernov [EMAIL PROTECTED] writes: Andrey I think it is very contr-intuitive way, better action will Andrey be replace if number is the same. Nonsense. This is what 'add' and 'delete' are for. Andrey For example ipfw delete takes number as an argument, Andrey what rule it suppose to delete, if the number is the same? Andrey I.e. how can I delete specific rule if all have the same Andrey number? Etc, etc. You can't, in which case you shouldn't use that facility. However, for those cases where you *do* want to act on a grouped set of rules, sharing rulesnumbers provides that ability. For example, I have a set of rules that count all in- and out-bound traffic to each IP address on an internal network. All of these are under a single rule number. This makes it trivial to do things like take periodic snapshots of the counters: ipfw show 2000 $somefile; ipfw reset 2000 This takes care of 512 individual rule entries in one simple operation. Now if you want to make some useful changes to ipfw, find someone to commit the fix in bin/18550. And get rid of the needlessly verbose usage message ipfw spits out when it fails to parse a command. It would be a lot more useful if ipfw printed (only) the failed command. At least I might have a chance of seeing what the error is, instead of having the usage message cause any useful information to scroll off the console while the machine boots. --lyndon To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: A question about max_uid
On Tue, 01 May 2001 06:56:56 +0900, Yoshihiro Koya wrote: Hello, chpass: updating the database... pwd_mkdb: 2147483647 recommended max uid value (65535) Gee, that message looks familiar. ;-) The warning was a concession that I implemented after discussions with BDE. The way we want to go for now is to have the entire system uid_t-clean (currently unsigned 32-bit) but to issue warnings from appropriate utilities when values that can't be represented by an unsigned short. Added to this, the above pwd_mkdb commands tells me that the recommended max uid value is 65535, which is a 16-bit UID, and this value 65535 differs from the restricted value of pw command. It might be better to unify such a recommended UID value on the system. Absolutely. If you have the time, that'd be great! Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
WinModem Support/Learning the kernel Internals
Benjamin Close writes: Is anyone looking into converting the Linux winmodem driver ( Lucent Technologies binary object file compiled together with the linux kernel serial driver) into a freebsd device? Please check http://www.geocities.com/wtnbkysh/ . It should work under 4.2R. There is also some 5.0C patches but still some problems probably with interrupts. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: Lucent Win Modem port 0x1c00-0x1cff,0x2f8-0x2ff mem 0xffefff00-0xffef irq 11 at device 2.0 on pci0 Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: using SHARED IRQ. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: unable to activate interrupt in fast mode - using normal modeltmdm0: type Virtual 16550A Tomppa -- SUN Microsystems Oy PL 112, Lars Sonckin kaari 12, 02601 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: [EMAIL PROTECTED]+358 9 52556252 fax To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WinModem Support/Learning the kernel Internals
On Tue, 1 May 2001 02:13:05 +0300 Tomi Vainio - Sun Finland - [EMAIL PROTECTED] wrote: TF Please check http://www.geocities.com/wtnbkysh/ . It should work I stand corrected - and impressed. -- Optimal hardware acceleration for Windows PC (Mac). 9.81 m/s/s applied for (at least) 2s followed by impact with solid object. Optimal software upgrade FreeBSD (OS-X). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WinModem Support/Learning the kernel Internals
On Tue, May 01, 2001 at 02:13:05AM +0300, Tomi Vainio - Sun Finland - wrote: Benjamin Close writes: Is anyone looking into converting the Linux winmodem driver ( Lucent Technologies binary object file compiled together with the linux kernel serial driver) into a freebsd device? Please check http://www.geocities.com/wtnbkysh/ . It should work under 4.2R. There is also some 5.0C patches but still some problems probably with interrupts. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: Lucent Win Modem port 0x1c00-0x1cff,0x2f8-0x2ff mem 0xffefff00-0xffef irq 11 at device 2.0 on pci0 Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: using SHARED IRQ. Apr 25 22:23:04 phb /boot/kernel/kernel: ltmdm0: unable to activate interrupt in fast mode - using normal modeltmdm0: type Virtual 16550A Also I've used PPP with the following on a ThinkPad X20 running 4.3-RELEASE + wtnbkysh patches: ltmdm0: Xircom Win Modem port 0x1810-0x1817 mem 0xf4011000-0xf4011fff irq 9 at device 10.1 on pci 0 ltmdm0: using SHARED IRQ. ltmdm0: type Virtual 16550A This is on the EtherJet Mini-PCI card (combo: fxp + ltmdm). Cheers, -- Jacques Vidrine / [EMAIL PROTECTED] / [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
