Re: strange ping response times...
CPU cache? Cx states? powerd? On Tue, Apr 10, 2012 at 03:40:27PM -0700, Julian Elischer wrote: > On 4/10/12 3:52 PM, Luigi Rizzo wrote: > > I noticed this first on a 10G interface, but now there seems > > to be a similar issue on the loopback. > > > > Apparently a ping -f has a much lower RTT than one with non-zero > > delay between transmissions. Part of the story could be that > > the flood version invokes a non-blocking select. > > On the other hand, pinging on the loopback should make > > the response available right away, so what could be the reason > > for the additional 3..10us in the ping response time ? > > > > The following are numbers on an i7-2600k at 3400 MHz + turboboost, > > running stable/9 amd64. Note how the min ping time significantly > > increases moving from flood to 10ms to 1s. > > On an Intel 10G interface i am seeing a min of 14-16us with > > a ping flood, and up to 33-35us with the standard 1s interval > > (using -q probably trims another 2..5us) > > I'd suggest some ktr points around the loopback path.. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 4 -> 5 Problem
On Tue, Dec 02, 2003 at 05:27:12PM -, Lawrence Farr wrote: > I get this error when trying to install the kernel, > the same kernel installs fine on the box that made it. > > [EMAIL PROTECTED]:/usr/src# make installkernel > > > -Original Message- > > From: M. Warner Losh [mailto:[EMAIL PROTECTED] > > Sent: 02 December 2003 17:16 > > : > > : > install -p -m 555 -o root -g wheel kernel /boot/kernel > > : > *** Signal 12 > > : > > : This usually means you've tried to update something out of > > the correct > > : order. > > > > Signal 12 means thaqt you didn't upgrade your kernel first. I've observed this when installing on a different system than the build system. I got it after building/installing several times on the build system before trying to installkernel on another system with /usr/src and /usr/obj nfs-mounted. The problem appeared to be that the stuff in the legacy directory under /usr/obj is built assuming that what's on the build system will work under the prior kernel - which is true on the build system but not necessarily on the target system. My solution was to edit (temporarily) /usr/src/Makefile.inc1 to put /usr/bin first in the PATH set up for the reinstallkernel target. That allowed make installkernel to succeed on the target system. Then I rebooted the target and backed out the change to /usr/src/Makefile.inc1, and after that make installworld and mergemaster went fine as usual. I didn't delve deeply enough to figure out what a cleaner fix would be, but this should probably be a PR as otherwise the 5.2 upgrade may be "difficult" for people who build and install on separate boxes. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB 1.0 IDE to ATAPI drive enclosure failure
On Mon, Nov 24, 2003 at 03:35:42PM -0700, M. Warner Losh wrote: > : Why hasn't anything been committed? > > Code freeze? I understand the concept, but I haven't seen any reports of people claiming that OHCI works for other than mice/keyboards without the following patch (from "Brian F. Feldman" <[EMAIL PROTECTED]>): --- ohci.c 12 Nov 2003 01:40:11 - 1.138 +++ ohci.c 22 Nov 2003 03:28:42 - @@ -569,7 +569,7 @@ cur->td.td_cbp = htole32(dataphys); cur->nexttd = next; cur->td.td_nexttd = htole32(next->physaddr); - cur->td.td_be = htole32(DMAADDR(dma, curlen - 1)); + cur->td.td_be = htole32(DMAADDR(dma, offset + curlen - 1)); cur->len = curlen; cur->flags = OHCI_ADD_LEN; cur->xfer = xfer; It cured my problems with a Sony DSC F707. Maybe most people with OHCI controllers haven't had problems, but if so they've been quietly satisfied. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB 1.0 IDE to ATAPI drive enclosure failure
On Mon, Nov 24, 2003 at 04:44:02PM -0500, Jesse Guardiani wrote: > > I'm running FreeBSD 5.1-RELEASE. I just bought a generic > USB 1.1/2.0/firewire external drive enclosure for my 32gb > Travelstar 2.0" 12.5mm hard drive. > > The device shows up like this: > > Nov 18 14:06:16 trevarthan kernel: umass0: Acer Labs USB 2.0 Storage Device, rev > 2.00/1.03, addr 3 > Nov 18 14:06:16 trevarthan kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Nov 18 14:06:17 trevarthan kernel: da0: Fixed Direct > Access SCSI-0 device > Nov 18 14:06:17 trevarthan kernel: da0: 1.000MB/s transfers > Nov 18 14:06:17 trevarthan kernel: da0: 30520MB (62506080 512 byte sectors: 255H > 63S/T 3890C) > > But `ls -al /dev/da*` reveals no slices: If you're using an ohci usb controller, perhaps you need a patch. Browse the -current archives for the last week or so. Why hasn't anything been committed? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: atheros (ath) - duplicate packets with long distance link
Off-the-wall suggestion: run tcpdump -e and check whether both responses are coming from the same host. Unless you're running WEP, you many have an unexpected guest. (WEP is no guarantee, but it's better than nothing.) On Mon, Nov 24, 2003 at 03:55:13PM +0200, Johann Hugo wrote: > Hi > > I am getting a lot of duplicate packets on my long distance wireless link, but > on my identical link in the Lab everything works fine. (DWL-AG520 adapter). > > The one adapter is configured in hostap mode, and the other one as a > client, both in 11b mode. ( current 5.2-BETA - 24 Nov ) > > I know there are a lot of CRC errors on the long distance wireless link, but > if I swap the hostap device with a 802.11b Lucent AP (over the same distance) > then I don't get any duplicate packets. > > atheros# ./athstats > 1 beacon miss interrupts > 52 tx management frames > 106 tx frames discarded prior to association > 4 tx failed 'cuz too many retries > 88 long on-chip tx retries > 45 tx frames with no ack marked > 62 tx frames with short preamble > 58979 rx failed 'cuz of bad CRC > 11 rx failed 'cuz decryption > 1511778 rx failed 'cuz of PHY err > 1495162 OFDM timing > 16614 CCK timing > 2 CCK restart > 8 periodic calibrations > 40 rate control checks > 1 rate control dropped xmit rate > > AP = DWL-AG520 - HostAP > atheros# ping -s 1450 192.168.10.10 > PING 192.168.10.10 (192.168.10.10): 1450 data bytes > 1458 bytes from 192.168.10.10: icmp_seq=0 ttl=64 time=27.432 ms > 1458 bytes from 192.168.10.10: icmp_seq=0 ttl=64 time=101.903 ms (DUP!) > 1458 bytes from 192.168.10.10: icmp_seq=0 ttl=64 time=178.306 ms (DUP!) > 1458 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=15.965 ms > 1458 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=96.968 ms (DUP!) > 1458 bytes from 192.168.10.10: icmp_seq=1 ttl=64 time=216.500 ms (DUP!) > 1458 bytes from 192.168.10.10: icmp_seq=2 ttl=64 time=27.865 ms > 1458 bytes from 192.168.10.10: icmp_seq=2 ttl=64 time=107.189 ms (DUP!) > 1458 bytes from 192.168.10.10: icmp_seq=3 ttl=64 time=19.401 ms > 1458 bytes from 192.168.10.10: icmp_seq=3 ttl=64 time=138.412 ms (DUP!) > 1458 bytes from 192.168.10.10: icmp_seq=3 ttl=64 time=213.613 ms (DUP!) > 1458 bytes from 192.168.10.10: icmp_seq=4 ttl=64 time=57.855 ms > 1458 bytes from 192.168.10.10: icmp_seq=4 ttl=64 time=134.540 ms (DUP!) > > AP = Lucent AP-1000 > PING 146.64.86.3 (146.64.86.3): 56 data bytes > 64 bytes from 146.64.86.3: icmp_seq=0 ttl=64 time=81.586 ms > 64 bytes from 146.64.86.3: icmp_seq=1 ttl=64 time=4.358 ms > 64 bytes from 146.64.86.3: icmp_seq=2 ttl=64 time=2.837 ms > 64 bytes from 146.64.86.3: icmp_seq=3 ttl=64 time=3.878 ms > 64 bytes from 146.64.86.3: icmp_seq=4 ttl=64 time=3.889 ms > 64 bytes from 146.64.86.3: icmp_seq=5 ttl=64 time=5.677 ms > 64 bytes from 146.64.86.3: icmp_seq=6 ttl=64 time=3.915 ms > 64 bytes from 146.64.86.3: icmp_seq=7 ttl=64 time=3.945 ms > 64 bytes from 146.64.86.3: icmp_seq=8 ttl=64 time=5.720 ms > > Regards > Johann > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dumb question 'Bad system call' after make world
On Sat, Nov 22, 2003 at 11:42:04PM +1100, Bruce Evans wrote: > On Fri, 21 Nov 2003, Barney Wolff wrote: > > > Will somebody please tell me when "make world" is ever correct in the > > environment of the last several years? I've been unable to understand > > its continued existence as a target. > > >From my normal world-building script: > > DESTDIR=/c/z/root \ > MAKEOBJDIRPREFIX=/c/z/obj \ > time -l make -s world > /tmp/world.out 2>&1 Oh, so it's only correct when you're not really installing world on the system you're building on? Would replacing this with ( make buildworld && make installworld ) really be a hardship? Must we continue to invite innocents to clobber their systems? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: dumb question 'Bad system call' after make world
On Fri, Nov 21, 2003 at 05:35:59PM -0800, Doug White wrote: > On Fri, 21 Nov 2003, Don Bowman wrote: > > > > > So i have a machine freshly installed from 5.1 mini iso. > > I did a cvs co of latest current sources, and accidentally > > did a 'make world' instead of 'make buildworld'. > > Now i just get 'Bad system call' when i try to do anything. > > i need to get the correct kernel on there, does anyone have a > > suggestion for how to fix this? > > If you have it, boot off of the mini iso, pull down and burn CD 2, then > use the fixit facility to start a fixit shell with teh CD. From there > manually install the new kernel (it'll be in > /usr/obj/usr/src/sys/KERNELNAME/kernel) and boot from it. From there you > should be able to finish the installworld. Does make world build a kernel? I didn't think so, and OP's message indicates that make world is all he did. I suspect re-install is the best answer now. Will somebody please tell me when "make world" is ever correct in the environment of the last several years? I've been unable to understand its continued existence as a target. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ppp RADIUS accounting bug
On Wed, Nov 19, 2003 at 09:00:01AM +0500, Boris Kovalenko wrote: > >I found a serious bug in RADIUS accounting code. The problem is that > OctetsIn and OctetsOut are defined as unsingned long long, but the > RADIUS supports only INT32 values, so, when > we're doing rad_put_int(r->cx.rad, RAD_ACCT_OUTPUT_OCTETS, > stats->OctetsOut) in radius.c for OctetsOut (and OctetsIn also) we > loosing information if OctetsOut is greater then INT32_MAX. This should > be fixed. Note that RADIUS integers are unsigned, so the limit is 2^32-1. Also, RFC2869 defines attributes to hold the high-order parts. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Recovery? recent "make world" rendered system unusable (64 bit change)
On Tue, Nov 18, 2003 at 11:50:22AM -0500, Chris Shenton wrote: > I've been running 5.1-CURRENT for a while and a couple nights ago did > a "make world". After a couple hours building, my system was > unusable. Critical binaries like "rm", "ls", "mtree", "sh" failed, > reporting "Exec format error". I can't login, not even single user. > I can no longer even boot single user. Re-install/upgrade from a cd. Upgrade should leave your files alone. I've argued before that "world" should be removed as a target, as I don't believe it's ever correct to do it. Why leave this gun pointed at people's feet? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: undelete for FreeBSD current?
On Thu, Nov 13, 2003 at 11:30:51AM +1030, Thyer, Matthew wrote: > I've done a bad thing and need to recover a single file in /usr/local/etc/rc.d/ > after a rm -rf of /usr/local > > I've kept the file system relatively quiet since then. TCT may help. http://www.porcupine.org/forensics/tct.html but I don't think it's been tested with current/ufs2. Also, don't expect to build it on the system and then find a deleted file. But if you have a clue of what you're looking for, just grepping /dev/da or /dev/ad might work. (grep -a -A100 -B100) -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: hard lockup with new interrupt code, possible cause irq14: ata0
Try adding options NO_MIXED_MODE to your conf. That fixed boot-time hangs on my Asus A7M266-D. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New interrupt stuff breaks ASUS 2 CPU system
Another data point: I can't get my Asus A7M266-D to boot with the new interrupt code at all, perhaps because I have an Adaptec 39160. Whether acpi is on or off, whether it's in the kernel config or not, booting always hangs right after "waiting 10 sec for scsi to settle" and "0 scb's aborted". I've also tried it with 0,1 or 2 of the ide controllers enabled, with no change in result. Sometimes I get a "spurious interrupt" from ata1 message, sometimes not. Kernel from 10/27 works fine. Kernels from last couple of days fail. dmesg, config available on request, if wanted. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jumbograms (& em) & nfs a no go
On Sat, Nov 01, 2003 at 01:09:07PM -0800, Terry Lambert wrote: > Barney Wolff wrote: > > > Implies the sending host is not honoring the MTU restriction when > > > deciding whether or not to frag packets. > > > > 67582 looks awfully bogus even as a pre-frag length. How could that come > > over the wire? > > The sending host is not honoring the MTU restriction? > > 8-) 8-). > > Most likely, a direct call to ether_output, or a code path that > results in fragmentation not being implemented; see my other post: > it could be that he's using NFS over UDP, and that's doing it. Er, how is it possible to send a UDP packet > 65535? Last time I looked it was a 16-bit field. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jumbograms (& em) & nfs a no go
On Fri, Oct 31, 2003 at 12:56:11AM -0800, Terry Lambert wrote: > Michal Mertl wrote: > > I then left one computer at 4.9 and upgraded the other to 5.0. When I > > mount a partition from 5.0 machine I found out, that copying reliably > > works only from 5.0 to 4.9. The other way around I see messages 'em0: > > discard oversize frame (ether type 800 flags 3 len 67582 > max 6014)' on > > 5.0 and the copying stalls. On 4.9 machine I later see 'nfs server > > 10.0.0.2:/usr: not responding'. The interface is stuck for some time - can > > be revived by changing mtu back to 1500 and down/up sequence. > > Implies the sending host is not honoring the MTU restriction when > deciding whether or not to frag packets. 67582 looks awfully bogus even as a pre-frag length. How could that come over the wire? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jumbograms (& em) & nfs a no go
On Thu, Oct 30, 2003 at 08:04:58AM -0800, Sam Leffler wrote: > > I've ran many jumbogram tests of machines connected with a cross-over cable > and em devices at each end. If you've got a swtch in the middle make sure it > does the right thing. Just a minor note: GigE should not require a crossover cable. It's supposed to work to connect two GigE adapters with a straight-thru cable. I verified this with two Intel em NICs, quite a while ago. As I recall, when I used a crossover cable, I could not get the adapters to go to 1000, only 100. That might have been the cable, or not. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random signals in {build,install}world recently?
On Tue, Oct 28, 2003 at 09:01:35AM +0200, Vallo Kallaste wrote: > > > > Well, I have a system from the 25th that works just fine, we're looking > > between the dates of 9/25 - 9/30. > > It is fixed, grab newer sources. It seems mostly but not completely fixed. I got one sig11 (on touch :) building ports. Retrying the port (Mozilla 1.5, pretty big) succeeded, and I got no further sigs doing portupgrade -ap. As always, I can't completely rule out h/w, but the system has never produced any sigs doing builds on RELENG_5_1 or -current before 9/24. However the behavior is very much improved, as -currents after 9/24 until the pmap.c fix would get sigs every few minutes. (Reminder, this is a dual-athlon.) -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GL slowdown with latest kernel
On Tue, Oct 28, 2003 at 09:39:28AM +0100, Yuri Khotyaintsev wrote: > I see a ~3x reduced GL performance as measured by glxgears. This is on a dual > Athlon sysmem with Radeon 9000 Pro. I don't see a slowdown with a dual Athlon and Radeon 7500. Also, mouse is much smoother with glxgears in full-screen window - used to be jerky on that test. (This is with sched_bsd; haven't run _ule.) -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random signals in {build,install}world recently?
On Mon, Oct 20, 2003 at 11:57:48PM -0700, Terry Lambert wrote: > Barney Wolff wrote: > > I don't think so. I tried that on my A7M266D with no effect. I believe > > something in recent pmap code doesn't like this mobo, or maybe dual > > athlons in general. I can run RELENG_5_1 rock solid, and -current from > > 9/24/03 rock solid, but -current from 10/3 or later gets random sigs > > and eventually panics. I have scsi disks so it's not ata. > > I think you need to define "random"; do you mean "rare in frequency > over time at unpredicatable intervals" or "you never know what > program is going to get shot in the head, every 5 seconds, like > clockwork"? The latter, with the interval being more like a very few minutes rather than seconds. The system would sit fine when idle, but never make it all the way through buildworld, or buildkernel, or building a port. In one notorious instance, the -current kernel didn't even make it through installworld without a sig. grep, sed, awk, sh have all gotten sigs, not just cc. > My impression so far in this therad is that it's the former. If > it's the latter, then I need to think about the problem differently. > > > Note that you can identify the patch that caused the problem, if > there's an 8 day difference, in no more than 4 kernel recompiles > (log2(8)+1), if you have a local CVS mirror. The frequency of patches to pmap was quite high, and that was not the only file patched. But yes, I can do a binary search. I haven't, because the changes to pmap were architectural; we're not talking about a typo here. Of course it's just my assumption that it's pmap because the eventual panic is there. btw, I use sched_bsd so _ule is not a suspect. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Random signals in {build,install}world recently?
On Mon, Oct 20, 2003 at 03:20:56PM +0200, Mark Santcroos wrote: > On Mon, Oct 20, 2003 at 10:27:38AM +0200, Harti Brandt wrote: > > On Mon, 20 Oct 2003, Vallo Kallaste wrote: > > > > VK>Hi > > VK> > > VK>It seems to be a recent problem. The hardware is OK, both Windows XP > > VK>(which I use very seldom) and Gentoo Linux do not exhibit any > > VK>problems. > > VK>Basically one will get random signals as I have got in build- and > > VK>installworld. It's impossible to complete make -j2 buildworld on my > > VK>machine, but sometimes non-parallel buildworld will do, only to die > > VK>later in installworld. > > VK>This is on two-processor AMD 2400+ MP system, ASUS A7M-266D mobo and > > VK>1GB ECC memory, ATA disks and CD/RW-DVD only. 4BSD scheduler if it > > VK>matters. > > > > I have the same MB just with 1800+ processors. I had to reduce the CPU > > frequency by about 10% in the BIOS setup to get the machine stable. I > > assume the problem is actually the memory. > > Couldn't the following be of help here? > > options DISABLE_PSE > options DISABLE_PG_G I don't think so. I tried that on my A7M266D with no effect. I believe something in recent pmap code doesn't like this mobo, or maybe dual athlons in general. I can run RELENG_5_1 rock solid, and -current from 9/24/03 rock solid, but -current from 10/3 or later gets random sigs and eventually panics. I have scsi disks so it's not ata. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: panic: pmap_enter: attempted pmap_enter on 4MB page
On Fri, Oct 17, 2003 at 09:51:57AM -0700, Peter Wemm wrote: > > AHA! origpte being 0xd0d0d0d0 means that something really came unstuck > because that is the fill pattern that userland malloc(3) uses. The > 4MB page thing is a red herring, it just happens that PG_PS (0x80) is > a set bit in the fill pattern. > > Now to find the source. :-( Are you getting this repeatably? If somebody > is able to (relatively) easily provoke this, there are a few things I'd > like to try (shotgun diagnostics, but its better than nothing). I also have a dual-athlon system that gets this panic on current. The problem shows up first as sig 10 & 11 on builds (world/kernel/ports) and eventual panic on pmap_enter on 4mb page. I KNOW it's not hardware, because a -current kernel from 9/24/03 is rock-solid (hours of port builds, make -j16 buildworld) and so is RELENG_5_1. The current kernel from yesterday did not even get through installworld without a sig11. I'm pretty sure it's not ata, because my system has scsi disks, and only an idle ata cdrom. I have pentiumpro as my cputype, because I also use this system to build for my laptop - is that a conceivable clue? But for experiments we can set it to anything. It's not in production, so if you want to try stuff, I'm willing to give you a login or take direction. Right now it's running RELENG_5_1 but I also have yesterday's -head on there and a local cvs on another system updated twice a day. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
"pmap_enter: attempted pmap_enter on 4MB page
I've been getting subject panics lately. A sure way to provoke them is to portupgrade -ap. Sooner or later, panic. With the latest build: FreeBSD lab.databus.com 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Tue Oct 14 01:41:23 EDT 2003 it seemed to last longer (almost 30 min!) before failing. HW is Asus A7M266-D with 2xAthlon 2200+, 1GB, Adaptec 39160, 2x10k disks, em0, fxp0. I have (with a slightly older build) tried DISABLE_PSE and DISABLE_PG_G with no visible effect. I believe this started about 10/4/03, but the first few panics were "PTE vanished". With builds in the last couple of days, the panic changed to the "4MB page" one. I cannot rule out hardware, since this system has also lately been getting sig11's on buildworld - but mbmon shows no excessive temp and sensible rpms & volts. Before 10/4, this system was rock solid. One oddity is that I can't get a UP kernel to boot - possibly because the bios is set to apic interrupts. If needed, I can make it happen again and get a traceback, or build an older kernel. I've been hoping for a magical fix, without success so far. Thanks for any advice, Barney ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [security-advisories@freebsd.org: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-03:17.procfs]
On Fri, Oct 03, 2003 at 07:17:50PM -0700, Will Andrews wrote: > > ... The rule is that changes are always committed to > -CURRENT first, unless they do not apply. This rule is rarely > broken in FreeBSD, and certainly never broken for security issues. That's of course expected and appreciated. But consider the different actions required of a reasonably paranoid FreeBSD SA on receipt of a security advisory: If following anything but -current, cvsup and check the versions of the listed files. If following -current, either trust that the updates made it to the mirror of choice, or look up on www.freebsd.org what the latest versions of the listed files are and check that you have them. Since the SO is presumably taking the changes from -current, I hope it would not be too much of an imposition to list those versions in the advisory as well. Thanks, Barney -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [security-advisories@freebsd.org: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-03:17.procfs]
On Fri, Oct 03, 2003 at 06:54:04PM -0700, Will Andrews wrote: > On Fri, Oct 03, 2003 at 09:45:27PM -0400, Barney Wolff wrote: > > I'm finally motivated to ask, why don't security advisories contain > > the equivalent revs for -head? Surely I can't be the only person > > following -current who doesn't build every day. > > Simply because the SO does not support -CURRENT. Does this mean that the situation can ever arise where a security bug is corrected in the advisory's announced releases but not in -current? Or, can we assume that as of the time of the security announcement the vulnerability has *always* been corrected in -current? Thanks, Barney -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[security-advisories@freebsd.org: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-03:17.procfs]
I'm finally motivated to ask, why don't security advisories contain the equivalent revs for -head? Surely I can't be the only person following -current who doesn't build every day. This notable omission has been true of every security advisory I can remember, and I've never understood it. If I'm missing some logic that makes it the right thing to do, can somebody please enlighten me? Thanks, Barney - Forwarded message from FreeBSD Security Advisories <[EMAIL PROTECTED]> - VI. Correction details The following list contains the revision numbers of each file that was corrected in FreeBSD. Branch Revision Path - - RELENG_4 src/sys/i386/linux/linprocfs/linprocfs_misc.c 1.3.2.9 src/sys/kern/kern_subr.c 1.31.2.3 src/sys/miscfs/procfs/procfs_dbregs.c 1.4.2.4 src/sys/miscfs/procfs/procfs_fpregs.c 1.11.2.4 src/sys/miscfs/procfs/procfs_regs.c1.10.2.4 src/sys/miscfs/procfs/procfs_rlimit.c 1.5.2.1 src/sys/miscfs/procfs/procfs_status.c 1.20.2.5 src/sys/sys/uio.h 1.11.2.2 RELENG_5_1 src/UPDATING 1.251.2.11 src/sys/conf/newvers.sh 1.50.2.11 src/sys/fs/procfs/procfs_dbregs.c 1.22.2.1 src/sys/fs/procfs/procfs_fpregs.c 1.28.2.1 src/sys/fs/procfs/procfs_regs.c1.27.2.1 src/sys/fs/pseudofs/pseudofs_vnops.c 1.35.2.1 src/sys/kern/kern_subr.c 1.74.2.1 src/sys/sys/uio.h 1.27.2.1 etc. ----- End forwarded message - -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb flashkey disk copy error
Patch below had some problems. Needed #ifdef USB_DEBUG around the
ref to ohcidebug to compile, and either BROKEN_OHCI added to the
list of valid options or (as I did) kludged to 1. Worse, trying
to mount_msdosfs my camera caused an instant panic: "Length went
negative: -4096". If that's not enough info, I imagine I can
recreate the panic.
Just to restate my particular problem, I get the wrong data on read
of an existing file from the memory stick on the camera. I have
not dared to try writing to it since reads don't work.
Thanks,
Barney
On Sun, Sep 07, 2003 at 01:39:08PM -0700, John-Mark Gurney wrote:
> Barney Wolff wrote this message on Sun, Sep 07, 2003 at 15:48 -0400:
> > I can't do more detailed diagnosis right now, but could in a few days.
>
> When you get a chance (or anyone else who has this problem), try the
> attached patch, and add options BROKEN_OHCI to your kernel config file.
> Please set hw.usb.ohci.debug=1, and send me the dmesg output of the
> writes. (When you copy the data to the media.)
>
> Hmmm. I just thought of something. Now is the data corrupt still correupt
> on another system? What I mean is did the data get written properly, but
> just isn't being read back from the media correctly. Unless you are
> coping a file larger than memory size, the cmp just pulls it from memory,
> not from the media. The umount/mount forces a flush of the cache, and so
> attempts to read from the media.
>
> Thanks.
>
> --
> John-Mark GurneyVoice: +1 415 225 5579
>
> "All that I will do, has been done, All that I have, has not."
> Index: ohci.c
> ===
> RCS file: /home/ncvs/src/sys/dev/usb/ohci.c,v
> retrieving revision 1.132
> diff -u -r1.132 ohci.c
> --- ohci.c2003/08/24 17:55:54 1.132
> +++ ohci.c2003/09/07 20:28:13
> @@ -513,6 +513,14 @@
>
> DPRINTFN(alen < 4096,("ohci_alloc_std_chain: start len=%d\n", alen));
>
> + if (ohcidebug && alen > 4096) {
> + printf("len: %d, pages: ", alen);
> + for (len = 0; len < alen; len += OHCI_PAGE_SIZE) {
> + printf("%s0x%x", len == 0 ? "" : ", ", DMAADDR(dma,
> + len));
> + }
> + }
> +
> len = alen;
> cur = sp;
>
> @@ -546,9 +554,14 @@
>* We can describe the above using maxsegsz = 4k and nsegs = 2
>* in the future.
>*/
> +#if BROKEN_OHCI
> + if (len < OHCI_PAGE_SIZE - OHCI_PAGE_OFFSET(dataphys))
> +#else
> if (OHCI_PAGE(dataphys) == OHCI_PAGE(DMAADDR(dma, offset +
> len - 1)) || len - (OHCI_PAGE_SIZE -
> - OHCI_PAGE_OFFSET(dataphys)) <= OHCI_PAGE_SIZE) {
> + OHCI_PAGE_OFFSET(dataphys)) <= OHCI_PAGE_SIZE)
> +#endif
> + {
> /* we can handle it in this TD */
> curlen = len;
> } else {
--
Barney Wolff http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb flashkey disk copy error
On Sun, Sep 07, 2003 at 10:55:24AM -0700, John-Mark Gurney wrote: > > > > Make me the third. I have a Sony F707 camera, which I can use on > > 4-stable and with 5-current on a Dell I5000 laptop, but not on 5-current > > on an Asus A7M266-D with world/kernel built 9/4/03. The bad data starts > > at byte 4096, always. The problem has existed for at least a month, > > Ahh, this is useful information. What are the controller types > of the two machines? ohci? uhci? I think it might be ohci, and > it maybe a page miscalculation when dispatching the request. Indeed, failing system has ohci, working has uhci. > Have you looked at the corrupted data? does it apear to be from > some other location, like the kernel? Can't tell offhand, but doesn't look like code - not enough zeroes. As I recall, multiple tries produced the same bad data each time (after umount and re-mount). I can't do more detailed diagnosis right now, but could in a few days. > > perhaps longer; I can't remember if it ever worked on the Asus. But > > the same system runs fine with usb keyboard and mouse - which proves > > nothing as the data rate and amount are so small. So I can't rule > > out hardware as the problem. In a few days I can try booting from > > a 4.8 live cd and see if the hardware works ok. Old-quirks had no > > effect on the problem. > > It's been about two months since I updated USB to use bus_dma. So > you could try checking out the usb code from July 4th or so and see > if it goes away (it probably will). Will try that, again in a few days. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: usb flashkey disk copy error
On Sun, Sep 07, 2003 at 12:32:46AM -0700, John-Mark Gurney wrote: > > You're the second person that has reported corruption with USB umass > devices. I am interested in tracking down this problem, but it's a > bit difficult since I haven't seen it myself. Make me the third. I have a Sony F707 camera, which I can use on 4-stable and with 5-current on a Dell I5000 laptop, but not on 5-current on an Asus A7M266-D with world/kernel built 9/4/03. The bad data starts at byte 4096, always. The problem has existed for at least a month, perhaps longer; I can't remember if it ever worked on the Asus. But the same system runs fine with usb keyboard and mouse - which proves nothing as the data rate and amount are so small. So I can't rule out hardware as the problem. In a few days I can try booting from a 4.8 live cd and see if the hardware works ok. Old-quirks had no effect on the problem. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI battery state and resume not working on Inspiron 5150
On Wed, Aug 06, 2003 at 03:31:01PM -0400, Joe Marcus Clarke wrote: > ACPI-1287: *** Error: Method execution failed > [\\_SB_.PCI0.LPCB.BAT1._STA] (Node 0xc6137640), AE_NOT_EXIST I would not expect BAT1 to exist unless you have 2 batteries installed. As to resume, on my I5000 it takes almost a minute to come back from S3, but does eventually come back on a -current from 7/30. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gcc related -current upgrade problems
On Fri, Jul 25, 2003 at 06:46:50PM -0400, John wrote: > > rm -rf src obj > cd /usr > cvs -Rqd /home/ncvs co -P src > cd src > make buildkernel You can't buildkernel before buildworld. Do read UPDATING and the handbook. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Compaq Evo N610c
On Wed, Jul 23, 2003 at 03:45:48PM +0200, Robert Blacquière wrote: > > pcmcia cards work only (at least one) if you put more than one card in > the pcmcia slots. > So inserting a Lucent orinoco wireless fails but the second ASUS > wireless card gets working ... > And also the reverse can be done.. > It's strange but it gives a working wireless connection. I'd look for port address conflicts. On my Dell I5000, the ltmdm uses ports that the card drivers don't seem to notice (or vice versa). The result is that I have to wait to load if_dc until after the ltmdm is loaded. One way to see if this is happening to you is to boot without the card and see if it then works when you plug it in. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Stop in /usr/src/sys/modules/harp
On Mon, Jul 21, 2003 at 11:14:24PM -0400, Xaos wrote: > I keep getting this error when compiling a freshly cvsup'd source. 5.1-Current > > /usr/src/sys/dev/harp/if_harp.c:128: `VENDAPI_FORE_2' undeclared here (not in Me too. I decided to wait a few hours and see if it's been fixed. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ``Resource temporarily unavailable'' in vi
On Mon, Jul 14, 2003 at 06:08:32PM -0400, Mikhail Teterin wrote: > Every once in a while, a vi-session dies on me with: > > input: Resource temporarily unavailable > > What does it mean, why does it happen, and how can I prevent it? I suspect vi's not handling an EAGAIN error return. I get this on -stable when ripping a cd with grip/cdda2wav. Are you doing something that runs at very high priority when it happens? Judging from the comments in /usr/src/sys/errno.h, it could also be that there is a resource deadlock and vi is not translating the errno correctly. Anyway, pending a fix in vi to handle retryable errors, the workaround is not to do whatever it is that you're doing at the same time. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ACPI Bad Param on Dell 5000
With a recent -current (6/18/03) I now see the infamous ACPI-0340 error (Could not release ACPI Global Lock, AE_BAD_PARAMETER) spewing out. This did not happen with a kernel from 6/5/03. I tried to apply the patch that's been referenced here, but apparently the Inspiron 5000 DSDT is completely different than the later ones. (Yes, I've upgraded to the A08 bios.) I have the disassembled dsdt, if anybody wants to look at it or suggest fixes: http://www.databus.com/i5000.dsl What has not changed from previous -current kernels is getting the following acpi error: ACPI-0432: *** Error: Handler for [Embedded Control] returned AE_ERROR ACPI-1287: *** Error: Method execution failed [\_SB_.BAT0._STA] (Node 0xc0eb9be0), AE_ERROR (Also on BAT1, which is not present.) Despite this, sysctl seems to know the charge % of the battery, just not how long it will last. Suspend to S3 works by closing the lid (I set S3 on lid close in sysctl). Resume is odd in that it powers up right away but the screen takes 30-60 seconds to come back. Also, network stuff needs help on resume. The Cisco 340 needs to have its parameters re-set with ancontrol. The 3C575 needs to be ejected and re-inserted. In both cases dhclient fails to re-apply the IP address, but it can be set by ifconfig. Sound stops, but can be recovered by unloading and reloading snd_maestro. Touchpad needs the flags set in hints to recover from suspend. DRI/DRM doesn't seem to work. No errors in XFree86.0.log, but glxinfo shows direct as no and glxgears confirms. xmbmon can't find the power controller, despite recognizing the PIIX. The 3C575 causes frequent lockups under load. No panic, the machine just freezes. Often it will cause shutdown to fail if not ejected first. I can live with all of these issues, but I'll be glad to cooperate with any attempts to fix them. Thanks, Barney -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI testing/debugging guide?
On Tue, Jun 17, 2003 at 03:54:34PM -0700, Kevin Oberman wrote: > > I am also seeing the same thing on my T30 when I run ACPI. It's the > temperature, not any of the others. It was reading 3186 and that seems > about right for centi-degrees C. (31.86C) Kelvin simply does not > compute. According to the spec, it does. Google for acpi - the official spec is at the first entry. Anyway, 318.6 - 273.2 = 45.4C, which is perfectly reasonable. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI testing/debugging guide?
On Tue, Jun 17, 2003 at 04:29:59PM -0600, M. Warner Losh wrote: > : > : ACPI records temperature in tenths of a Kelvin, if you can believe it :) > > I don't believe that. 369.2K is 96.2C, which is over 200F. That seems > to hot to me. My laptop says 2982, which is either about 30C or > 15.2C. Given how warm it is on my leg at the moment, I'd guess it is > centi-Celcius. Maybe converted internally? Reading the source, it really is tenths Kelvin. Is the 3692 the actual temp, or the CRT, which I assume is the critical temp? In the output of sysctl hw.acpi.thermal.tz0 there are a bunch of values, only one of which is the current temp. The rest are thresholds - AC appears to mean active cooling (aka fan), PSV seems to mean passive. How come xmbmon can't interpret acpi temps? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI testing/debugging guide?
On Tue, Jun 17, 2003 at 01:16:49PM -0500, Dan Nelson wrote: > > > My resume from suspend doesn't work and I don't know how to tell where > > that is going wrong. I have no serial interface so I can't use a serial > > console when the LCD doesn't come on. I can live without suspend/resume > > functionality. You can't miss something you have never had. :-) > > My Dell laptop doesn't bring the display back on, but I can manually > re-enable it with the Fn-CRT/LCD key. Have you tried waiting? I thought the same on my I5000, but discovered that if I waited 30-60 seconds, the display did come back by itself. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Need acpi-event-d?
On Mon, Jun 16, 2003 at 07:07:36AM -0400, David Gilbert wrote: > > Anyways, after a resume, it would appear I need to kill and restart > moused. Under 4.x, apmd was used for this purpose ... but this new > laptop doesn't support apm at all. /dev/apm seemed to be emulated by > acpi for the benifit of battery monitors, but apmd won't run. > > Is there a facility to run things on resume, or is this reset > something better done inside the kernel? man psm Set the HOOKRESUME and INITAFTERSUSPEND flags in /boot/device.hints. Works for me on a Dell I5000. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
CPUTYPE?
I need to buildworld (current) and ports to run on both p3 and athlon-mp. What's a good value for CPUTYPE, or should I just leave it out? Thanks. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Plea for base system trim
I have both apache-modssl and net-snmp running, but do NOT have the openssl port installed. Everything builds and runs fine, with no mods to anything. I conjecture that the problem others experience is that they have installed the openssl port, which I have never done. This is on both current and stable. On Wed, Mar 05, 2003 at 06:00:13PM +0100, Adrian Steinmann wrote: > > I use this command in my build script to force apache13+modssl to use > the openssl in base. > > # Use base openssl (OpenSSL 0.9.7a as of Feb 19 2003) > cd /usr/ports/www/apache13-modssl > cp Makefile Makefile- > sed -ie 's/^\.include.*Makefile\.ssl.*$/OPENSSLBASE=\/usr/' Makefile- >Makefile > > You wrote: >On Wed, Mar 05, 2003 at 09:54:13AM -, Subscriber wrote: >> Having just done two rebuilds for recent OpenSSL and sendmail >> vulnerabilities, I was surprised to discover that building the port >> of apache13-modssl required the build of a port version of >> OpenSSL when I had the most updated (4.7) base system with >> OpenSSL in it!. I hate having two versions installed; it makes me >> fear that there will be problems caused by the wrong version being >> used. > >You are right to hate having two versions installed --- it is >pointless in most cases. Please complain to the apache+mod_ssl and >openssl port maintainers. It sounds to me like they are doing >something very wrong. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [tlambert2@mindspring.com: Re: can't sshd into box]
On Mon, Mar 03, 2003 at 10:22:21AM -0600, Wayne Barnes wrote: > Looking back at the waiting telnet job, it has no message or > anything. > > Trying it with 'telnetd -debug -D report' > Use tcpdump to make sure your machine is actually receiving the telnet connection. It sounds as though something else is getting it. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: type errors in src-tree
On Sun, Mar 02, 2003 at 02:33:55AM +0100, Jens Rehsack wrote: ... > >>+ n = write ( ilmi_fd[intf], resp+1, resp[0] ); > > > >Here's a case where it matters whether something is u_char or char. > >write(2) takes a size_t as its third arg, and extension of a char to > >that may not be the same as for u_char, for example on Sparc. If the > >response is ever >127 bytes, this will fail. You're going to have to > >look carefully at how things are used to see when char is appropriate > >and when u_char is necessary. > > That is really right, but for those check I have to know more 'bout ATM, > right? I just have detected some compiler errors using > -finline-functions (yes, I'm playing with optimization options :-)). If > you know a real good online-reference, one fine day I'll check it and > check the entire ilmid.c code for valid signment. This has nothing to do with ATM. It has to do with how the code that's in the file uses 8-bit bytes, and how it calls standard functions. If you make changes blindly just to get rid of compiler warnings, you will introduce bugs in operation that may be difficult to find, years later. The fact that Resp_Buf needs to remain a u_char[] is just one example. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: type errors in src-tree
This is an example of what I was pointing out:
On Sun, Mar 02, 2003 at 01:53:33AM +0100, Jens Rehsack wrote:
...
> @@ -1444,22 +1420,19 @@
> * none- response sent
> *
> */
> -void
> -send_resp ( intf, Hdr, resp )
> - int intf;
> - Snmp_Header *Hdr;
> - u_char *resp;
> +static void
> +send_resp ( const int intf, Snmp_Header *Hdr, char *resp )
> {
> int n;
>
> - if ( ilmi_fd[intf] > 0 ) {
> - n = write ( ilmi_fd[intf], (caddr_t)&resp[1], resp[0] );
> + if ( ilmi_fd[intf] > 0 ) { /* FIXME: does ilmi_fd[intf] exists? out of range?
> */
> + n = write ( ilmi_fd[intf], resp+1, resp[0] );
...
Here's a case where it matters whether something is u_char or char.
write(2) takes a size_t as its third arg, and extension of a char to
that may not be the same as for u_char, for example on Sparc. If the
response is ever >127 bytes, this will fail. You're going to have to
look carefully at how things are used to see when char is appropriate
and when u_char is necessary.
--
Barney Wolff http://www.databus.com/bwresume.pdf
I'm available by contract or FT, in the NYC metro area or via the 'Net.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: PATCH: type errors in src-tree
On Sat, Mar 01, 2003 at 11:09:03PM +0100, Jens Rehsack wrote: > ... > >>- u_char **bufp; > >>+ caddr_t *bufp; > ... > Of course. Very often in ilmid.c the type caddr_t was used, and nearly > the same count of 'const char *'s was used. I've searched the include > files for caddr_t (core address) and found it defined as 'char *', so I > decided to used commonly caddr_t - maybe later I check which of them > could be changed into 'c_caddr_t' for being const. But You can of couse > replace all 'caddr_t' which 'char *'. Shouldn't we care about u_char vs char? On some machines it matters, and on all machines compilers tend to notice and generate warnings. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
