Re: Interesting NFS hangs under current
Could you print out *p and *uap in frame 18?
frame 18
print *p
print *uap
Also, do:
ps -axl -N /sys/compile/bleep/kernel.debug -M /var/crash/vmcore.2
This is very odd. There is no way it should be looping in supervisor
mode in that call chain.
No sooner received than done
(kgdb) frame 18
#18 0xc01ef2d6 in mmap (p=0xc5e49020, uap=0xc5f45f80) at ../../vm/vm_mmap.c:330
330 error = vm_mmap(p-p_vmspace-vm_map, addr, size, prot, maxprot,
(kgdb) print *p
$2 = {p_procq = {tqe_next = 0xc0290ed0, tqe_prev = 0x0}, p_list = {
le_next = 0xc5e492e0, le_prev = 0xc0290f60}, p_cred = 0xc0a42b20,
p_fd = 0xc0a23c80, p_stats = 0xc5f44230, p_limit = 0xc099a600,
p_upages_obj = 0xc5ea59c4, p_procsig = 0xc0a3eaa0, p_flag = 16388,
p_stat = 2 '\002', p_pad1 = "\000\000", p_pid = 4672, p_hash = {
le_next = 0xc5e4a8e0, le_prev = 0xc05ad780}, p_pglist = {le_next = 0x0,
le_prev = 0xc0a42ae8}, p_pptr = 0xc58c6ec0, p_sibling = {le_next = 0x0,
le_prev = 0xc58c6f10}, p_children = {lh_first = 0x0}, p_ithandle = {
callout = 0xc1b86108}, p_oppid = 0, p_dupfd = 0, p_vmspace = 0xc5e4cec0,
p_estcpu = 1502, p_cpticks = 1247, p_pctcpu = 1791, p_wchan = 0x0,
p_wmesg = 0x0, p_swtime = 20, p_slptime = 0, p_realtimer = {it_interval = {
tv_sec = 0, tv_usec = 0}, it_value = {tv_sec = 0, tv_usec = 0}},
p_runtime = 10333, p_uticks = 0, p_sticks = 2437, p_iticks = 1991,
p_traceflag = 0, p_tracep = 0x0, p_siglist = 0, p_textvp = 0xc5dfbcc0,
p_lock = 0 '\000', p_oncpu = 0 '\000', p_lastcpu = 0 '\000',
p_pad2 = 0 '\000', p_locks = 0, p_simple_locks = 0, p_stops = 0,
p_stype = 0, p_step = 0 '\000', p_pfsflags = 0 '\000', p_pad3 = "\000",
p_retval = {0, 6}, p_sigiolst = {slh_first = 0x0}, p_sigparent = 20,
p_oldsigmask = 0, p_sig = 0, p_code = 0, p_sigmask = 0,
p_priority = 127 '\177', p_usrpri = 127 '\177', p_nice = 0 '\000',
p_comm = "rpc.rstatd\000\000\000\000\000\000", p_pgrp = 0xc0a42ae0,
p_sysent = 0xc025bbc0, p_rtprio = {type = 1, prio = 0}, p_prison = 0x0,
p_addr = 0xc5f44000, p_md = {md_regs = 0xc5f45fa8}, p_xstat = 0,
---Type return to continue, or q return to quit---
p_acflag = 2, p_ru = 0x0, p_nthreads = 0, p_aioinfo = 0x0, p_wakeup = 0,
p_peers = 0x0, p_leader = 0xc5e49020, p_asleep = {as_priority = 0,
as_timo = 0}, p_emuldata = 0x0}
(kgdb) print *uap
$3 = {addr = 0xc07a8180 "", addr_ = 0xc0a41744 "À\206zÀ\001",
len = 3229255360, len_ = 0xc0a41748 "\001", prot = 65537,
prot_ = 0xc0a4174c "\001", flags = 1, flags_ = 0xc0a41750 "\200¢ÀÄ#À\002",
fd = -1063108992, fd_ = 0xc0a41754 "Ä#À\002", pad = -1071242300,
pad_ = 0xc0a41758 "\002", pos = 17592186044418, pos_ = 0xc0a41760 ""}
(kgdb)
# ps -axl -N /sys/compile/bleep/kernel.debug -M /var/crash/vmcore.2
UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND
0 259 1 32 10 0 5080 wait I#C1- 0:00.00 (sh)
88 276 259 0 2 0 111320 - R#C1- 0:00.00 (mysqld)
0 282 1 32 10 0 5120 wait I#C1- 0:00.00 (sh)
65534 289 282 0 2 0 33080 - R#C1- 0:00.00 (squid)
65534 307 289 0 -6 0 7560 piperd I#C1- 0:00.00 (unlinkd)
0 3428 3424 0 10 0 6080 wait Is #C10:00.00 (sh)
0 3454 3428 4 10 0 9280 wait I+ #C10:00.00 (make)
0 3457 3454 4 10 0 5040 wait I+ #C10:00.00 (sh)
0 3458 3457 5 10 0 9200 wait I+ #C10:00.00 (make)
0 3461 3458 5 10 0 5040 wait I+ #C10:00.00 (sh)
0 3462 3461 5 10 0 11760 wait I+ #C10:00.00 (make)
0 3466 3462 5 10 0 5080 wait I+ #C10:00.00 (sh)
0 3467 3466 49 10 0 6280 wait I+ #C10:00.00 (make)
0 3534 3467 49 10 0 5040 wait I+ #C10:00.00 (sh)
0 3535 3534 49 10 0 5640 wait I+ #C10:00.00 (make)
0 3538 3535 51 10 0 5080 wait I+ #C10:00.00 (sh)
0 3671 3538 54 10 0 3920 wait I+ #C10:00.00 (make)
0 3676 3671 29 10 0 5080 wait I+ #C10:00.00 (sh)
0 4659 3676 14 10 0 27120 wait I+ #C10:00.00 (make)
0 4667 4659 14 -2 0 3400 getblk I+ #C10:00.00 (install)
1000 3436 3433 6 10 0 6080 wait Is #C10:00.00 (sh)
1000 3442 3436 0 3 0 12920 - R+ #C10:00.00 (systat)
0 3491 3486 0 3 0 6080 ttyin Is+ #C10:00.00 (sh)
0 325 1 0 3 0 6040 ttyin Is+ #C90:00.00 (sh)
0 327 1 0 3 0 8400 ttyin Is+ #C20:00.00 (getty)
1000 326 1 1 10 0 6040 wait Is #C20:00.00 (sh)
0 338 326 0 2 0 15760 select I+ #C20:00.00 (ssh1)
0 0 0 0 -18 0 00 - RLs ??0:00.00 (swapper)
Assembler capable of supporting 3dnow!
I'm messing around with the latest mesa and have discovered (suprise)that our assembler doesn't support 3dnow instructions. Are there any plans to update to a version of binutils that does? Linux's stuff appears to support it. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: MTRR stuff
What exactly are the ranges? You haven't given me enough info yet. I wrote the K6-* MTRR driver, so I'd like to help. OK, the Linux 3dfx driver attempts to set up a write combining range starting at the card's base address and 0x40 bytes long. After doing this it then sets up a range marked as uncacheable starting at the card's base address of length 0x1000. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Finding out what function an interrupt is tied to..
I'm having some problems since when the newbus code went in, in that my sound card doesn't seem to be interrupting anymore (PAS16, Voxware drivers). So what I'd like to do is look at the kernel and see if an interrupt actually has a function associated with it, and if it's being masked out. Any ideas? Of course, this would have to happen just as I learnt to rip my music CD's into mp3s. Stephen To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: pcm still broken in -current (at least for me)
The same happens with snd0 instead of pcm. It looks like it can't register the interrupt handler - is it now supposed to be registered in a different way (perhaps via nexus)? I'm seeing the exact same problem, only with the Voxware driver and a PAS16. I've held off upgrading the soundcard because all the local vendors only seem to sell cards we don't have drivers for. Sigh. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Hacking objcopy
Would anyone have any objections to me hacking objcopy so that it could do the following - a) Change symbol names from one thing to another b) Add/remove dependencies on other shared objects. If I submit these changes, what chance do I have of getting them made official? Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: MTRR support for AMD K6-2?
Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want to allow mtrr support for my Voodoo Banshee) It's being worked on. The K6 is a problematic device, as it only supports two memory ranges, as opposed to the eight the P6 does. OK - give me a yell once it's ready for testing. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
MTRR support for AMD K6-2?
Do we have MTRR support for the AMD K6-2, and how's it done (e.g., if I want to allow mtrr support for my Voodoo Banshee) Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
SGI to release XFS under Open Source license
Some of you may already know this - I'm wondering about the pain involved in fitting it to our architecture. Journaling. Hmmm. http://www.news.com/News/Item/0,4,36807,00.html?owv -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Some interrupt bogons still around.
An old 486 of mine still cant see its IDE driver with versions of ata-all.c later than 1.8, and my soundcard (PAS16) still doesn't seem to generate interrupts since the nexus stuff went in. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Sound still not quite working (Voxware)
I get DMA / interrupt timeouts on programs such as mpg123 or NAS. Those programs that mmap the DMA buffer and set it cycling through (quake friends) work fine. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: New ATA drivers problem? (Was: New kernels won't boot)
Soren, I did a bit of experimenting with my CVS archive and found that version 1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed out errors about unexpected interrupts whilst probing and eventually hung, and 1.10 gave the unable to mount wd0s2a errors we all love. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
New kernels won't boot
On my machine, a kernel newer than one built on the 22nd will not complete booting, panicing about not being able to mount root. Another machine with a very similar config is fine. The main difference is that the faulty machine has its FreeBSD partition in an odd spot on the disk. Below is the dmesg output, the fdisk output and the config file. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Apr 22 00:37:32 WST 1999 t...@bloop.craftncomp.com:/usr/src/sys/compile/bleep Timecounter i8254 frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = AuthenticAMD Id = 0x484 Stepping=4 Features=0x1FPU real memory = 16777216 (16384K bytes) avail memory = 13750272 (13428K bytes) Preloaded elf kernel kernel.good at 0xc02c4000. Probing for PnP devices: npx0: math processor on motherboard npx0: INT 16 interface pcib0: PCI host bus adapter on motherboard pci0: PCI bus on pcib0 chip0: Host to PCI bridge (vendor=10b9 device=1445) at device 0.0 on pci0 de0: Digital 21140 Fast Ethernet at device 4.0 on pci0 de0: interrupting at irq 11 de0: SMC 9332DST 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:c0:a6:59:dc de0: enabling 10baseT port isa0: ISA bus on motherboard atkbdc0: keyboard controller (i8042) at port 0x60 on isa0 atkbd0: AT Keyboard on atkbdc0 atkbd0: interrupting at irq 1 vga0: Generic ISA VGA on isa0 sc0: System console on isa0 sc0: VGA color 16 virtual consoles, flags=0x0 ata1 at irq 14 on isa0 ata1: interrupting at irq 14 fdc0: interrupting at irq 6 fdc0: NEC 765 or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fd0: 1440-KB 3.5 drive at fdc0 drive 0 mse0 at port 0x23c irq 5 on isa0 mse0: interrupting at irq 5 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 sio1: type 16550A sio1: interrupting at irq 3 ed0 at port 0x280-0x29f iomem 0xd8000-0xdbfff irq 10 on isa0 ed0: address 00:00:c0:d2:b2:72, type SMC8216T (16 bit) ed0: interrupting at irq 10 ppc0 at port 0x378 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppi0: generic parallel i/o on ppbus 0 lppps0: Pulse per second Timing Interface on ppbus 0 ppc0: interrupting at irq 7 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled ds0 XXX: driver didn't set ifq_maxlen ad0: ST34321A/3.11 ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, PIO mode changing root device to wd0s4a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates *** Working on device /dev/rwd0 *** parameters extracted from in-core disklabel are: cylinders=1042 heads=128 sectors/track=63 (8064 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1042 heads=128 sectors/track=63 (8064 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: UNUSED The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 201600, size 7999488 (3906 Meg), flag 80 (active) beg: cyl 25/ sector 1/ head 0; end: cyl 1016/ sector 63/ head 127 machine i386 ident BLEEP maxusers10 options INCLUDE_CONFIG_FILE # Include this file in kernel config kernel root on ad0 dumps on ad0 cpu I486_CPU cpu I586_CPU # aka Pentium(tm) cpu I686_CPU # aka Pentium Pro(tm) options COMPAT_43 options USER_LDT#allow user-level control of i386 ldt options SYSVSHM options SYSVSEM options SYSVMSG options VM86 options DDB options KTRACE #kernel tracing options UCONSOLE options USERCONFIG #boot -c editor options INET#Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop#Network loopback device pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device disc#Discard device pseudo-device tun 2 #Tunnel driver (ppp(8), nos-tun(8)) options TCP_COMPAT_42 #emulate 4.2BSD TCP bugs options MROUTING# Multicast routing
Further on tape CAM problems
When the tape hangs with an unkillable process, its relevant PS flags are physstrat and DL+. It doesn't hang forever, just a very long time, like someone's confused milliseconds with microseconds, or some such. Also, when writing to the 2nd tape in a CPIO archive, it doesn't actually write to the tape. systat -vmstat records lots of stuff going to the tape device (a SCSI QIC-525 in this case) very quickly - way beyond the speed it can actually do but there's no actual activity. Dump on the otherhand seems fine. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: DoS from local users (fwd)
Mikhail Teterin wrote: What about a new login-class capability specifying the maximum percentage of CPU time a class of users can utilize? With standard class having 90% (or 95%)? The machine would appear (to most of the users) as if it had 10% slower CPU, with the remaining usable by the root-class. This way, if the CPU consumption by system is 30%, the most CPU time the standard users can get is 60%. Trusted users can be placed into a different class, of course. Plausible? What you guys are describing is the FAIR SHARE scheduler for Unix, as implemented by Softway in Sydney many years ago. It originated in Sydney University as part of the efforsts of the CS department there to share out an old Vax 11/780 amongst 80 odd users at a time. Students aren't noted for their common sense, so measures like this were necessary. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATTENTION PLEASE: g77 in base system.
Thus spake Brian Handy ha...@lambic.physics.montana.edu On Fri, 9 Apr 1999, The Hermit Hacker wrote: [g77 in the source tree] I have to agree here...I personally know noone that actually uses Fortran...having it as an option to turn off would be nice...one less thing to compile on a buildworld... I know *lots* of people that use FORTRAN. That aside, I think I'd be satisfied with a port. Brian I can see that it would get out of sync very rapidly with our cc - Please put the sources in with egcs and have a know to turn it *on* rather like profiled libs. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
CAM changes causing prob?
After the last lot of CAM changes, I occasionally get processes hanging attempting to access my QIC-525 tape drive. They can't be killed, so doing backups can be a mite troublesome. Sometimes it works, sometimes it doesn't. There seems to be some relation to how recently the last lot of tape activity was (althought this is rather tenuous). Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Patched RealTek driver -- please test
This version survived for a little longer, but hung (on the 486 box) whilst doing a recursive ls of a large directory tree. Again, no messages, except for one which came up as the box was booting, whilst it was starting squid. The box was OK for about 4 minutes after this message, which was rl0: watchdog timeout Hope this helps. Stephen To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Patched RealTek driver -- please test
OK - I've banged on the new version with extra debug messages and it still locks up, but without any messages! I can only conclude that the 486MB BIOS is iffy. I haven't tried any other slots in the MB, but have tried various PCI settings, all to no avail. I have swapped the de0 and the rl0 between machines, and the rl0 is happy in it's new home - hasn't fallen over, although it's netpipe performance sucks with very small packets. I think we can write this one off as a faulty PCI implementation on the 486 motherboard. Thanks for your patience time. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: More on rl0 woes
I can't believe I'm getting so worked up because you cheap bastards insist on buying the absolute worst network adapter in the world. Go buy an ASIX card for crying out loud. They're cheap, and they actually work worth a damn. Weeelll... I'm a cheap bastard I actually expected it to work - not real fast, but work reliably anyway. I'm trying to convert my home network over to 100Mbs and the box this is going into is not a performance monster. Now, as punishment for making me mad, I'm going to address Steven's problem, and the rest of you can just lump it. There are things you should be checking when your problem happens. What does ifconfig rl0 show you? Is the OACTIVE flag set? What does netstat -in say? What does netstat -m say? I'll check that tonight. You say 'traffic continues normally.' This is very confusing: SHOW ME AN EXAMPLE OF WHAT YOU MEAN. OK - the ls of the directory remains hung, but I can still ping the box. It's as if NFS reckons it's sent the reply to the READDIR packet, but it never actually made its way out of the card. When the NFS transfer stops, can you still ping the server host, or do you have to interrupt the transfer and wait for a while before you can communicate with the server again? Can you run tcpdump on the client and observe what happens when the transfer stops? Is the client still sending out read requests? Is the server replying or not? I ran tcpdump on the server and observed READDIR packets being received, but no response being emitted. Are the replies garbled? Is there a lot of other activity on the network at the time? Can you initiate another (smaller) NFS transfer when the first one wedges? I'll try this when I get home. Don't know enough about the contents of NFS packets yet to tell if it's garbled. You have to give me as much information as you can. I need to be able to clearly identify the symptoms of the problem with out all the 'oh my god it doesn't work and I tried this and this and this' crap. Orright.. Just give me a little time. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: egcs
What will become of f77 which is in src/gnu/usr.bin/cc/f77? This seems to be a good time to decide what will happen with Fortran in the base FreeBSD system. VERY good question. I have no opinion in the matter, but will follow the wishes of others (or Core, or committers, or who ever should make this decision and who ever tells me which way to go). My vote is to include the sources for g77 that go with the egcs suite, but to have a knob in /etc/make.conf (BUILD_G77=yes) to control if they get built or not. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Patched RealTek driver -- please test
Well, I nipped home over my lunch break gave it a try - some progress, of a sort. My NFS problems have gone away (at least under light activity), but it now seems rather sensitive to sending lots of stuff. The symptoms observed are a hard hang of the whole machine, no response to pings or keyboard action. I cant even break into DDB. How I reproduced this is as follows - get the netpipe program off ports, then set up a receiver on the non-realtek machine as follows - NPtcp -s -r Then on the RealTek machine do this - NPtcp -s -t -h non-realtek-hostname -P After about 5 or so lines of throughput stats, it dies in the bum. Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
More on rl0 woes
On the offchance that mty problems were chipset related, I swapped the RealTek with the de0 card in my other machine, a 233MHz k6. It being a socket 7 mboard presumably has a later PCI bios. Still the same symptoms - hangs on NFS access. These can be interrupted and other network traffic continues fine. To reproduce, take your RealTek equipped machine and place a copy of /usr/src on it. Export /usr/src so that it can be NFS mounted by other machines. From the other machines, do an ls -CFR of /usr/src. It will hang partway through. Stephen .e w. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RealTek driver woes
I'm running a RealTek ethernet card in a 486dx4-100 machine and am having some problems. Firstly, doing an ls on a nfs mounted directory exported from the RealTek machine hangs. According to tcpdump it is receiving the readdir packets. Secondly, it will hange solidly when acting as the receiver (haven't tried it as the sender) running the netpipe tests (NPtcp -s -r receiving, the sender runs NP -t -h host_rl -s) - no DDB, just a solid hang. An ISA SMC card in the same machine is fine. I've tried it with RL_USEIOSPACE defined and undefined. This is running a very current system, with the id string $Id: if_rl.c,v 1.12 1999/02/23 15:38:25 wpaul Exp$ Here's the dmesg output. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Thu Mar 25 21:37:03 WST 1999 t...@bloop.craftncomp.com:/data/src/sys/compile/bleep Timecounter i8254 frequency 1193182 Hz CPU: AMD Enhanced Am486DX4 Write-Through (486-class CPU) Origin = AuthenticAMD Id = 0x484 Stepping=4 Features=0x1FPU real memory = 16777216 (16384K bytes) avail memory = 13750272 (13428K bytes) Preloaded elf kernel kernel at 0xc02c3000. Preloaded elf module linux.ko at 0xc02c309c. Probing for devices on PCI bus 0: chip0: Host to PCI bridge (vendor=10b9 device=1445) rev 0x00 on pci0.0.0 rl0: RealTek 8139 10/100BaseTX rev 0x10 int a irq 9 on pci0.4.0 rl0: Ethernet address: 00:00:e8:53:a2:3e rl0: autoneg complete, link status good (half-duplex, 10Mbps) Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 ed0 at 0x280-0x29f irq 10 maddr 0xd8000 msize 16384 on isa ed0: address 00:00:c0:d2:b2:72, type SMC8216T (16 bit) atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A pca0 on motherboard pca0: PC speaker audio driver ata0 at 0x1f0-0x1f7 irq 14 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled ad0: ST34321A/3.11 ATA-4 disk at ata0 as master ad0: 4103MB (8404830 sectors), 8894 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue changing root device to ad0s2a Stephen -- The views expressed above are not those of PGS Tensor. People often think of research as a form of development -- that it's about doing exactly what you planned, doing it on time, and doing it with resources that you said you'd use. But if you're going to do that, you have to know what you are doing, and if you know what you are doing, it isn't really research. --Dave Liddle, The New Yorker, Feb. 23/Mar.2, 1998, p 84 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: bmake/contrib framework for egcs
BTW, do you plan to include egcs' g77 as well? Current, the g77 driver is built. But the f771 isn't. From previous talk, I've gotten the impression g77 should be a port vs. in the base system. I'm Ok either way -- I leave the decision to the lists and Core. - -- - -- David(obr...@nuxi.com -or- obr...@freebsd.org) I think the building of the fortran compiler should be controlled through some variable in /etc/make.conf - BUILD_G77 or something like that, the same way you can elect to build profiled libs et cetera. It'd be a pain in the rear artificially ripping out source and including it in another tarball. Stephen -- The views expressed above are not those of PGS Tensor. People often think of research as a form of development -- that it's about doing exactly what you planned, doing it on time, and doing it with resources that you said you'd use. But if you're going to do that, you have to know what you are doing, and if you know what you are doing, it isn't really research. --Dave Liddle, The New Yorker, Feb. 23/Mar.2, 1998, p 84 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Successfully cross-compiling Linux code!
Well, after unpacking various RPMs from my RedHat 5.23 CD, making a number of hardlinks within the library directories under /compat/linux, I've finally got this going. Who do I contact to put together an official Linux development port that'll work? Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Linux devel doesn't work with glibc libs
When trying to link, it complains about libc.os.6 vs libc.so.5. This makes life rather difficult when trying to test glide programs against my version of the /dev/3dfx driver. Can someone commit the RedHat dev system (. egcs )? Stephen -- The views expressed above are not those of PGS Tensor. We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true.Robert Wilensky, University of California To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
