Re: /usr/src/sys/dev/aic7xxx errors when compiling
On Wed, 11 Feb 2004, Didier Wiroth wrote: > Hi, thanks for answering > I'm using this in make.conf > COPTFLAGS= -O2 -pipe -funroll-loops > CFLAGS= -O3 -pipe -funroll-loops Don't: - optimize the base system above -O, it's not officially supported. - top post, it makes things harder to read. - cross-post, it's almost always not necessary. Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 40% slowdown with dynamic /bin/sh
On Mon, 24 Nov 2003, Leo Bicknell wrote: > Process accounting can tell the story: > > % lastcomm | wc -l >47806 > % lastcomm | sed -e 's/ .*.//' | sort | uniq -c | sort -nr | head > 25281 sendmail > 4094 sh > 2987 perl > 2846 inetd > 1704 procmail > 1640 httpd > 1221 cron > 814 date > 732 postgres > 648 rateup > > Looks like sh is the 2nd most frequently executed command on my > system. It is 8.5% of all executed programs on this particular > system. I think slowing down 8.5% of all the programs the system > runs is important. For what it's worth, here's the data that I've taken from the daily process accounting files of one of our somewhat busy shellboxes: # lastcomm -f acct.0 | sed -e 's/ .*.//' | sort | uniq -c | sort -nr | head 4829 qpopper 3426 bash 3191 sendmail 1915 sh 1687 httpd 1281 sed 1030 sshd2 952 rm 792 procmail 739 cron # lastcomm -f acct.1 | sed -e 's/ .*.//' | sort | uniq -c | sort -nr | head 5383 qpopper 3282 bash 2743 sendmail 1617 httpd 1187 sh 1071 sed 772 rm 739 cron 694 procmail 478 cat # lastcomm -f acct.2 | sed -e 's/ .*.//' | sort | uniq -c | sort -nr | head 5376 qpopper 2823 bash 2118 sendmail 1674 httpd 1510 sh 745 procmail 740 cron 292 python 288 atrun 211 inetd Though /bin/sh isn't 2nd on the list, it does feature prominently in the top 10. I would assume that anyone with a fairly busy machine acting as a shellbox and webserver would see something along these lines... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nextboot.conf on sparc64
Hi, It appears that nexboot.conf isn't cleared on boot on sparc64. I tested this with on: FreeBSD ultra.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Nov 7 23:59:19 GMT 2003 root@:/usr/src/sys/sparc64/compile/GENERIC sparc64 The nextboot command was invoked with: nextboot -o "-s" -k kernel I have reason to believe that the problem is due to / being read-only on single-user boot (which is a good thing for fsck purposes) so the file cannot be unlinked. When the system boots multi-user though, all appropriate filesystems are mounted rw, and nexboot.conf still doesn't get cleared. Then again, I could be wrong... :) Any ideas? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Typos in -CURRENT?
Hi, The Online Merriam-Webster dictionary (m-w.com) doesn't have an entry for the word 'recognised', yet it features throughout our source tree (Including manpages). The following was run on CURRENT as of a few hours ago: bling# grep -R recognised /usr/src/ | wc -l 155 bling# grep -R recognized /usr/src/ | wc -l 1898 This isn't a color/colour type of thing... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB (mouse) problem
On Sun, 2 Nov 2003, sebastian ssmoller wrote: > On Sun, 2003-11-02 at 15:18, Andre Guibert de Bruet wrote: > > On Sun, 2 Nov 2003, sebastian ssmoller wrote: > > > > > recently i installed freebsd 5 current on an asus m2400n notebook. most > > > things work fine so far, but one ugly problem left: every time i plug in > > > my usb mouse the system freezes. the system is really dead then (needs > > > to be rebooted) - even the light on the optical mouse is swiched off. > > > > Please read the handbook on the proper form for problem reports. In the > > sorry for not providing enough information. i did not want to submit a > problem report. i just wanted to see whether somebody has similar > problems and whether it really is a problem - or i am just not clever > enough to configure my system ... :) > > so here are further info: > -i tried both: x11 and vt (console). plugging in the mouse always causes > system freeze > -uname -a: > FreeBSD hadriel.linnet 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Nov 2 > 16:37:45 CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SND i386 > -a could not found any further info about this crash (trace, log file) > -i attached my kernel config file > -unfort. i do not have a proper cable to set up a serial > connection/console :( > -what kind of info should the "boot -s" command provide (i could not > find this command on my system) ? I typoed. I really meant to say "boot -v". You enter that at the loader(8) prompt so for it to perform a verbose boot. It gives detailed information about the boot process, including hardware probing and what it eventually finds attached to the system. Here's a couple of things that might put us on the right track: - Does starting the system with the mouse already plugged in cause the system to lock up as well? - Does the machine respond to ping requests when it's "frozen"? - Have you tried another USB mouse? - Does this laptop support USB 2.0? If so, you might want to remove ohci or uhci (they are mutually exclusive on the same ports) and add "ehci". A boot -v with the mouse plugged in at startup time will provide valuable insight into your problem. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB (mouse) problem
On Sun, 2 Nov 2003, sebastian ssmoller wrote: > hi, > recently i installed freebsd 5 current on an asus m2400n notebook. most > things work fine so far, but one ugly problem left: every time i plug in > my usb mouse the system freezes. the system is really dead then (needs > to be rebooted) - even the light on the optical mouse is swiched off. Please read the handbook on the proper form for problem reports. In the future, you might want to include the following: - uname -a - boot -s output - a trace, if available on the first vt or serial console. - your kernel config file of the running system. When you say that your machine locks solid, are you in X11 when you're plugging in the mouse? If so, it might really be panicking, it's just that you don't get to see the message printed to the screen. The best way to catch this class of problem is to hook up a serial console and perform the voodoo that makes the machine "lock up". Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [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, 21 Oct 2003, Vallo Kallaste wrote: > I went back to last known good kernel/world combination, which is > from September 16. The next and problematic kernel/world pair is > from September 30. So the problem was introduced between these > dates. Well, I have a system from the 25th that works just fine, we're looking between the dates of 9/25 - 9/30. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386_set_ldt warnings
On Wed, 22 Oct 2003, Dan Nelson wrote:
> In the last episode (Oct 22), Steve Kargl said:
> > On Wed, Oct 22, 2003 at 12:09:43PM -0400, Daniel Eischen wrote:
> > > On Wed, 22 Oct 2003, C. Kukulies wrote:
> > > > Some (kde) applications now have a warning appear in xconsole:
> > > >
> > > > Warning: pid 595 used static ldt allocation.
> > > > See the i386_set_ldt man page for more info
> > >
> > > Let me guess. You are using Nividia-supplied drivers/libraries?
> >
> > I see similar messages on the console and I do not have a nvidia
> > card. By the time I find the message the process has terminated, so
> > I have no way of translating the PID into an actual executable name.
>
> That's cause whoever coded the warning forgot to print the executable
> name in the error message. Try this patch:
>
> Index: sys_machdep.c
> ===
> RCS file: /home/ncvs/src/sys/i386/i386/sys_machdep.c,v
> retrieving revision 1.91
> diff -u -r1.91 sys_machdep.c
> --- sys_machdep.c 7 Sep 2003 05:23:28 - 1.91
> +++ sys_machdep.c 22 Oct 2003 16:52:49 -
> @@ -464,8 +464,8 @@
> if (!(uap->start == LDT_AUTO_ALLOC && uap->num == 1)) {
> /* complain a for a while if using old methods */
> if (ldt_warnings++ < NUM_LDT_WARNINGS) {
> - printf("Warning: pid %d used static ldt allocation.\n",
> - td->td_proc->p_pid);
> + printf("Warning: pid %d (%s) used static ldt allocation.\n",
> + td->td_proc->p_pid, td->td_proc->p_comm);
> printf("See the i386_set_ldt man page for more info\n");
> }
> /* verify range of descriptors to modify */
This could also be accomplished by enabling process accounting and
grepping the output of lastcomm. But yes, this patch is most welcome
nonetheless. :)
Regards,
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB Keyboard questions
On Tue, 21 Oct 2003, Peter wrote: > Was to quick there, the problem with the letters still exist. But when > I run it with the convertet it works. Under Windows or with the USB2 card (or both)? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB Keyboard questions
On Mon, 20 Oct 2003, Peter wrote: > I have been reading that page and I have the keyboard working, but I > fail to see how this will help a user that only has a USB Keyboard > that wants to use FreeBSD5.1 and is unable to install it due to the > lack of USB support from the start. Some BIOSes offer a "USB legacy support" option which allows the use of a usb keyboard as if it were a PS2 keyboard during system startup. > And I still would like to know if its my keyboard that is out of sync > with the USB spec since it will add letters when I write like . > "This should read like this" but can end up like "Thisi should reaed > likek this" Does this keyboard exhibit the same behavior when it's plugged into a Windows machine? It's a little early to speculate what the issue could be, as there are a number of links in this chain but it's very possible that you simply have a wonky keyboard on your hands. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Anyone working on a port of OpenBSD's CARP?
Hi, I was just wondering if anyone was currently having a look at the possibility of porting OpenBSD's CARP. I have a bit of free time on my hands but wouldn't want to duplicate anyone's work... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slow Boot
What does pciconf -vl show on the affected machine(s)? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Sun, 17 Aug 2003, Bill Moran wrote: > Mike Atamas wrote: > > When my system boots it seems to stall when it gets here: > > > > xa807,0xa400-0xa403,0xa000-0xa007 mem 0xe100-0xe10001ff irq 11 at device 11. > > 0 on pci1 > > ata2: at 0xe100 on atapci0 > > ata3: at 0xe100 on atapci0 > > > > It stalls for about 20-30 seconds and then continues booting. I can not figure out > > what the problem is or how to solve it. Has anyone had similar issues. > > I've seen this on various hardware. I actually have a 200mhz machine sitting here > that has always done this. I've never seen it cause any problems, and I've never > had any suggestions on how to stop it either. > > My best guess is that the chipset responds slowly to probes, thus it takes a while > to get the list of devices from it. However, I've never looked into it any more > than that. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -march athlon breaks my networking was: ip stack broken?
On Sun, 19 Oct 2003, slave-mike wrote: > I realized that my /etc/make.conf was set to use -O0 -march athlon > for kernel builds. > > After removing the COPTS and CPU stuff form /etc/make.conf my kernel's > networking now works fine. > > Any clue as to why -march athlon breaks my networking? Could you change only one variable at a time? Start off by using -march=athlon and -O to eliminate the -march argument. As Kris pointed out, kernels are usually not built with -O0. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 5.1-CURRENT rebooting (multile systems) -- How to troubleshoot?
On Sat, 18 Oct 2003, Tom Parquette wrote: > My question is, if the system fails (I'm assuming these are panics) how > do I get the machine to NOT automatically reboot so I can copy down the > failure information? (Unless these are logged somewhere I have not > found yet.) Try hooking up a serial console and logging a system run with "boot -v", overnight. Make sure that you have all of the kernel debug options in GENERIC in your kernel as they will provide insight that can help trace the problem. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB Keyboard questions
On Sat, 18 Oct 2003, Peter wrote: > I have been trying to install FreeBSD 5.1 with a Logitech USB > keyboard. But I have been unable to do that since it looks like > FreeBSD 5.1 doesnt recognize the keyboard when it hasnt loaded the > kernel. I then tried to install FreeBSD 4.8 and it worked like a charm > with the USB keyboard. > > My first question is; Why isnt there support for a USB Keyboard during > the installation of FreeBSD 5.1 and during the boot up process as > well? I am unable to use it in the boot screen of FreeBSD 5.1. > > My second question is; I have been able to get the usb keyboard > working in FreeBSD after help in the question mailing list, but when I > use it I tend to every now and then get the same character again, this > happens most often when im typing fast. I gues this is common knowledg > but since Im new in current and new to using USB Keyboard in FreeBSD > and I havent found much searching in Google. Is there a way to stop it > or is it a bug in the USB source for FreeBSD, or just me. Mostly > intrested in the status of this. > > Im running FreeBSD 5.1 release #0 with Generic kernel. > Motherboard: Abit KD7 > CPU: AMD Baraton > Keyboard: Logitech cordless comfort All the information you need to set it up is in the ukbd(4) manpage. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fwd: gcc compiler issues with gcc version 3.3.1...,,, onfreebsd 5-current
On Sat, 18 Oct 2003, KroNiC~BSD wrote: > On Sat, 18 Oct 2003 12:29:05 -0600, "KroNiC~BSD" <[EMAIL PROTECTED]> > said: > > I am trying to compile firebird on freebsd 5-current. Something appears > > to be wrong with the compiler on the 5.x series as i am getting the > > following errors: > > others are getting these errors while compiling various other apps. > > > > http://gcc.gnu.org/ml/gcc-bugs/2003-08/msg00370.html > > > > I can find others having these issues but have not found why or how to > > fix it, so i would appreciate some help on this. What upgrade path did you use to get to 5.x/CURRENT? Did you remember to clear out /usr/include/g++ and perform an installworld as stated in current if you've come from 4.x (or a mid-2002 CURRENT)? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What's up with the IP stack?
On Sun, 12 Oct 2003, Josef Karthauser wrote: > On Sun, Oct 12, 2003 at 02:48:01PM +0200, Soren Schmidt wrote: > > It seems Josef Karthauser wrote: > > > I've just built and installed a new kernel, the first since Aug 6th. > > > There appears to be a problem with the IP stack. What happens is that > > > everything is fine for a few hours, and then the IP stack stops working. > > > I can no longer ping anything on the local network, my default route > > > drops out (which is probably dhclient's doing). Perhaps it is ARP that > > > is broken, it's hard to tell. All I know is that I need to reboot to > > > make it work again. > > > > > > Is anyone else experiencing this kind of problem? > > > > Do you have dummynet included in the kernel ? > > That has been broken for me since sam's latest commit as a backout > > of ip_dummynet.c fixes the problem for me... > > > > No, I've not got dummynet in there. My current kernel config is: I experienced this a week ago. I found that ifconfig'ing the interface down and back up again "fixed" the problem. I've since reverted to a kernel compiled on September 25th. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Nvidia driver
On Wed, 8 Oct 2003, Justin Smith wrote: > > > Ahh! > > Here is a fragment of my loader.conf.. > > nvidia_load="YES" > > machdep.disable_mtrrs="1" > > hw.nvidia.registry.ReqAGPRate="1" > > Although this fix alloes me to start up the nvidia driver, the machine > still reboots when I run certain apps (openuniverse, for instance) and > at random times otherwise. Since I need this, I'll have to retreat to > stable for a while... If you hook up a serial console, are there any messages that get printed out? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Fixing -pthreads (Re: ports and -current)
On Wed, 24 Sep 2003, Garrett Wollman wrote: > I think it was John Baldwin who wrote: > > >> I think having a magic option to gcc that translates to 'link with the > >> foo library' is rediculous. What's next, a gcc -math to get the math > >> functions in libm? > > As far as POSIX is concerned, that's precisely how it works. `c99 > foo.c -l m' means `link in the math functions, wherever they may > happen to live'. Likewise `-l rt' for realtime -- and (relevant to > this discussion) `-l pthread' for threads. There is no requirement > that any of these libraries exist as such. That may be true, but these libraries don't have gcc options like '-pthread' does to have them linked against. Why should a threaded library be any different than libz, libpng or lib? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: X10 Wireless Technology Inc USB Receiver
On Sun, 21 Sep 2003, Lars Eggert wrote: > I'm trying to get the USB RF remote control that comes with some ATI > Wonder cards to do something meaningful under -current. Can I recommend the use of libusb for the abstracting of the USB layer? It would allow your driver/interface to work on all FreeBSD, Linux and Solaris. I've found the graphics/s10sh port to be really useful as an example of libusb's usage... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bus error
On Sat, 15 Nov 2003, Philipp Westphal wrote: > Hi today, cvsup'ed my source and build world ... > and now get an so called > > Bus error > > while i want to su, anyone know about it (or fixed it) 1) Adjust your system clock so that it's set to something reasonable. 2) What CFLAGS do you have in /etc/make.conf? 3) Is your kernel in sync with your userland? 4) Have you run mergemaster since the last round of PAM changes? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB CF reader not working in Current.
On Fri, 12 Sep 2003, Gunnar Flygt wrote: > I have a Lexar Media USB Card Reader for CompactFlash. On the box it > says that it is compatible without driver for computers running Windows > 2000/Me/XP and Mac Os 9/X > > I didn't expect them to tell me it was working with FreeBSD but since it > should work with Mac OSX, I assumed that it would be working with > Current. But to my disappointment it doesn't work. Does this device work with 5.1-R or 4.8-R, by any chance? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sylogd not logging
On Sun, 7 Sep 2003, itchibahn wrote: > I used to run 4.6 where syslogd worked fine with cisco 7507, as5300, and > max4048. Eversince I've installed 5.0-RELEASE, I used exact same config as > old, but can't get it working. Please help. The following is configs: I'm currently using current's syslogd for remote logging on a series of Cisco 2650s and 1720s. The rc.conf entries that'll make this work are: syslogd_enable="YES" syslogd_flags="-a 192.168.128.0/24:*" Though I've never done it by domain name, the manpage suggests that you're looking for something like this: syslogd_flags="-a *.isot.com:*" As usual, check for firewalling between the endpoints. Hope this helps... > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Radeon DRM issues under -current (As of 9/10)
On Wed, 10 Sep 2003, Andre Guibert de Bruet wrote: > I'm trying to enable DRM on an ATI Radeon AIW 8500DV (Which gets detected > as a Radeon R200 BB-class board). I've added both "device radeondrm" and > "device agp" to my kernel config file and made sure that XFree86 has both > a "load dri" and a "load glx" directive. > > I'm seeing the following in my all.log: > Sep 10 00:22:36 bling kernel: error: [drm:radeon_cp_init] *ERROR* radeon_cp_init > called without lock held > Sep 10 00:22:36 bling kernel: error: [drm:radeon_unlock] *ERROR* Process 1945 using > kernel context 0 > > I've put a number of configs and logs up: > Kernel config is at: http://bling.properkernel.com/BLING > XF86Config is at:http://bling.properkernel.com/XF86Config > boot -v is at: http://bling.properkernel.com/boot-v > XFree86.0.log is at: http://bling.properkernel.com/XFree86.0.log > glxinfo -v is at:http://bling.properkernel.com/glxinfo Okay, so I missed a couple of messages in the archive. ForcePCIMode true causes DRM to work, but I can't help but think that it's by luck rather than design... I'll update the boot -v with a version from a kernel with DRM_DEBUG in just a little bit. Sep 10 13:13:05 bling kernel: info: [drm] Loading R200 Microcode Sep 10 13:13:05 bling kernel: drm0: [MPSAFE] Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Radeon DRM issues under -current (As of 9/10)
Hi, I'm trying to enable DRM on an ATI Radeon AIW 8500DV (Which gets detected as a Radeon R200 BB-class board). I've added both "device radeondrm" and "device agp" to my kernel config file and made sure that XFree86 has both a "load dri" and a "load glx" directive. I'm seeing the following in my all.log: Sep 10 00:22:36 bling kernel: error: [drm:radeon_cp_init] *ERROR* radeon_cp_init called without lock held Sep 10 00:22:36 bling kernel: error: [drm:radeon_unlock] *ERROR* Process 1945 using kernel context 0 I've put a number of configs and logs up: Kernel config is at: http://bling.properkernel.com/BLING XF86Config is at:http://bling.properkernel.com/XF86Config boot -v is at: http://bling.properkernel.com/boot-v XFree86.0.log is at: http://bling.properkernel.com/XFree86.0.log glxinfo -v is at:http://bling.properkernel.com/glxinfo FreeBSD bling.home 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed Sep 10 01:18:53 EDT 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BLING i386 I've read the radeon(4) manpage and searched the archives but it didn't turn up anything which resolved this. Any ideas? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Multi BOOT
On Thu, 4 Sep 2003, Abdul Hakeem wrote: > > > Hello, > Does anyone know a way of simultaneously booting FreeBSD with Linux or > Win2K with a dual-processor and dual NIC server ? > I can set the processor affinity on the Win2k, but I am having trouble > configuring the FreeBSD to use a particular processor and a particular > NIC. To do server partitioning, you'll have to acquire a Unisys ES7000, IBM zSeries or comparable system. Standard x86 multi-proc systems (As you would buy from Dell, for example) do not support this. You can however run Win2k inside VMware on a FreeBSD machine. This option is even more flexible than partitioning as it lets you turn the "VM" off and reacquire the resources that were tied up by it. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ATAng atacontrol issue
As reported to sos@, with a little extra debugging at the bottom...
---
I was playing with atacontrol reinit'ing all of the channels that are
installed on my machine, when I accidentally tried to reinit channel '4',
which clearly doesn't exist. Here's what showed up at the serial console:
ata0: resetting devices ..
done
ata1: resetting devices ..
done
ata2: resetting devices ..
done
ata3: resetting devices ..
done
panic: lock (sleep mutex) Giant not locked @ kern/sys_generic.c:678
cpuid = 1; lapic.id = 0100
Debugger("panic")
Stopped at Debugger+0x4e: xchgl %ebx,in_Debugger.0
db> tr
Debugger(c04088ac,100,c040bc40,f0e0abe4,100) at Debugger+0x4e
panic(c040bc40,c041c423,c04080be,c040bfe4,2a6) at panic+0x151
witness_unlock(c0494c40,8,c040bfe4,2a6,6) at witness_unlock+0x213
_mtx_unlock_flags(c0494c40,0,c040bfdb,2a6,ca8f9130) at
_mtx_unlock_flags+0x80
ioctl(ca8f9130,f0e0ad14,c042237d,3eb,3) at ioctl+0x4f8
syscall(2f,2f,2f,805e92f,bfbffd36) at syscall+0x253
Xint0x80_syscall() at Xint0x80_syscall+0x1d
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x804995b, esp = 0xbfbff76c, ebp =
0xbfbffc24 ---
My ata setup has the following devicesL
acd0: DVDROM at ata0-master PIO4
ad2: 238475MB [484521/16/63] at ata1-master UDMA100
ad4: 194481MB [395136/16/63] at ata2-master UDMA133
ad6: 194481MB [395136/16/63] at ata3-master UDMA133
These devices are located on the following controllers:
atapci0: port 0xb800-0xb80f at device 7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
atapci1: port
0x9000-0x900f,0x9400-0x9403,0x9800-0x9807,0xa000-0xa003,0xa400-0xa407 mem
0xe600-0xe6003fff irq 11 at device 5.0 on pci2
ata2: at 0xa400 on atapci1
ata3: at 0x9800 on atapci1
A little bit of GDB'ing gives the following:
(kgdb) l *(ioctl+0x4f8)
0xc0270fa8 is in ioctl (../../../kern/sys_generic.c:679).
674 if (memp)
675 free(memp, M_IOCTLOPS);
676 fdrop(fp, td);
677 done:
678 mtx_unlock(&Giant);
679 return (error);
680 }
681
682 /*
683 * sellock and selwait are initialized in selectinit() via SYSINIT.
(kgdb) l *(syscall+0x253)
0xc03c6103 is in syscall (../../../i386/i386/trap.c:1005).
1000td->td_retval[0] = 0;
1001td->td_retval[1] = frame.tf_edx;
1002
1003STOPEVENT(p, S_SCE, narg);
1004
1005error = (*callp->sy_call)(td, args);
1006}
1007
1008switch (error) {
1009case 0:
(kgdb)
We're not locking Giant in this case because of the following check:
/*
* Try to run the syscall without Giant if the syscall
* is MP safe.
*/
if ((callp->sy_narg & SYF_MPSAFE) == 0)
mtx_lock(&Giant);
It appears that the syscall is marked as MPSAFE but ends up calling code
in ioctl that expects Giant to be locked. Any ideas?
Regards,
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup failing with "ASSERT failed"
On Fri, 29 Aug 2003, David Rhodus wrote: > > On Wednesday, August 27, 2003, at 12:48 PM, Peter Wemm wrote: > > Oh, that *is* interesting. I get this 100% of the time when trying to > > run the i386 binary on my amd64 boxes. Hmm. Maybe I dont have an > > emulation > > bug then? > > > > [EMAIL PROTECTED]:46am]~-99> ./cvsup -gL2 cvs-supfile > > Parsing supfile "cvs-supfile" > > Connecting to malaise > > Wow, now I don't get my /compat dir populated during my > installworld/installkernel > on my amd64 machines. How do I go about installing those bits so that I > can run i386 > binary's ? One way of installing all of the stuff that should be in /compat would be to run /stand/sysinstall, Post-Install Config then install the appropriate distributions. Make sure that you *only* select the distributions that you want to install (don't overwrite [s]bin and everything if you've upgraded to HEAD). Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: sony vaio pcg-gr390
On Fri, 29 Aug 2003, Putinas wrote: > I tried to check might be my problem with choppy sound is fixed on my notebook ( > definitly has problems with interupts and acpi , because sound becomes more or less > acceptable if I make ping -f something outside - sound card and network uses same > interupt ). > I upgraded to latest src, compile GENERIC, reboot... and whops: > hanging where initializing pcmcia ( or the something what goes after this ? ) this > is if I boot with ACPI enabled. > If I boot with acpi disabled - panic and debuging screen ... > > So just to pay developers attention to this problem .. because I saw already to > mails about notebooks and acpi ... Could you boot -v with acpi enabled and post the log somewhere? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: recent 5.1-CURRENT kernel panics on acd0 probe/attach, IBM T30laptop
On Wed, 27 Aug 2003, Lee Damon wrote: > : || tylendel.castle.org [10] ; uname -a > FreeBSD tylendel.castle.org 5.1-CURRENT FreeBSD 5.1-CURRENT #38: Wed Aug 27 09:05:21 > PDT 2003 [EMAIL > PROTECTED]:/users/FreeBSD-5.0/obj/users/FreeBSD-5.0/src/sys/TYLENDEL i386 > > The kernel I compiled on 20 AUG recognizes acd0 and loggs the following: > > Aug 27 08:24:10 tylendel kernel: acd0: CD-RW at ata1-master U > DMA33 > Aug 27 08:24:10 tylendel kernel: cd0 at ata1 bus 0 target 0 lun 0 > Aug 27 08:24:10 tylendel kernel: cd0: Removable > CD-ROM SCSI-0 device > Aug 27 08:24:10 tylendel kernel: cd0: 33.000MB/s transfers > Aug 27 08:24:10 tylendel kernel: cd0: Attempt to query device size failed: NOT R > EADY, Medium not present - tray closed > > However, kernels compiled since Monday's SUP get as far as the initial > discovery of the acd0 device and then panic with: > > fatal trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor write, page not present > instruction pointer = 0x8 :0xc015ca8e > stack pointer = 0x10 :0xdd79aaac > frame pointer = 0x10 :0xdd79aab8 > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def 32 1, gran 1 > processor eflags= interrupt enabled, resume, IOPL=0 > current process = 19 (swi 3: cambio) > kernel: type 12 trap, code=0 > Stopped at free_hcb+0x2e: mov1%eax,0(xedx) > > When I remove the DVD/CDRW from the system it boots. Try booting with an ISO 9660 image in the drive. Does it make any difference? I've spotted this behavior with a brand-new SONY DRU-510A (Version "BA"). Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ion startup error in 5.1-current
On Sun, 24 Aug 2003, Michael Goffin wrote: > Every time I start up ion-devel I get an xmessage stating: > > >> Drawing Engine /usr/X11R6/lib/ion-devel/de.la not registered! > >> Stack trace: > 0 [C]: in 'gr_select_engine' > 1 /usr/X11R6/etc/ion-devel/draw.lua:6 > [Skipping unnamed C function.] > > I can click "okay" and everything seems fine, but when I set draw.lua as a > link to another theme, the theme doesn't work. I am not sure if these two > problems are connected, but I've done everything I can to fix this error and > I can't get it to stop. Any suggestions? This belongs on [EMAIL PROTECTED] CC'ing... > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: recover superblock
On Sun, 24 Aug 2003, Jeremy Messenger wrote: > On Sun, 24 Aug 2003 21:26:11 +0200, Thomas Gutzler <[EMAIL PROTECTED]> > wrote: > > I have lost over 1,000 to 2,000 emails like three times when the Nvidia > driver crashed and had to do the power off and on to get it boot to let the > fsck background do the job. Yesterday, I CVSup'ed and did the buildworld to > update my -CURRENT. I got panic and reboot; first time I see the same > message above, 'softupdate inconsistency' and I had to ran fsck by manual. > After that, I discovered that my /var/, /compat/linux/ and very little > stuff in my home directory have been destroyed. I can't produce the panic > anymore so can't really give any help that much now; it was only panic at > once for unknown reason. > > Just want to add in here that you aren't only person in here. I don't have a solution for you, but I have some sound advice: Don't run critical systems on -current. I consider email to fall in that category... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is rl broken?
On Tue, 19 Aug 2003, John Reynolds~ wrote: > > This thread originally taken from the -stable mailing list, but I'm seeing > weird things in -current now, so I thought I'd ask > > > I cvsup'd and rebuilt a FreeBSD 4.8 system last Friday after receiving the > > realpath security advisory. The machine is remote and the NIC uses the rl > > driver. After booting the machine I had no network connectivity. The > > person at the remote site says the boot was normal and he could see that the > > NIC was properly configured but he could not ping it and I could not login. > > We booted off kernel.old and everything came up fine. > > > > I have a machine with an Intel nic using the fxp driver that is exhibiting the > same sort of weirdness. I just installed 5.1-RELEASE on it after it was built > and things were rock solid. I got my NIC configured to use DHCP in my LAN here > at home, everything's fine. then I cvsup and buildworld/kernel (the same > kernel config that an *identical* system on my LAN is using) and test out the > new kernel before installkernel and dhclient seems to finish properly and the > interface seems configured correctly with the correct IP. netstat -r shows the > right stuff, but I can't even ping the NIC itself. It says > > sendto: permission denied > > when I try to ping the NIC itself and *also* 127.0.0.1. If I revert back to the > 5.1-RELEASE kernel with the same hardware and zero config changes, everything > is hunky dory again. Sorry, I'm light on details--I need to do some more > experiments and will cut-n-paste what I see, but I wanted to see if anybody > else is experiencing anything oddball like this. Sounds like you've put IPFIREWALL in your kernel without IPFIREWALL_DEFAULT_TO_ACCEPT. Either add this to your kernel or add an ipfw rule as allows: ipfw add allow ip from any to any Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: CPUTYPE considered harmful? (was: Lot's of SIGILL, SIGSEGV)
On Tue, 19 Aug 2003, Stefan Bethke wrote: > On Montag, 18. August 2003 23:15 Uhr +0200 Pawel Jakub Dawidek > <[EMAIL PROTECTED]> wrote: > > > On Sun, Aug 17, 2003 at 08:00:54PM -0700, David O'Brien wrote: > > +> > This is a FAQ. In the future, please search the archives before > > posting. +> > > > +> > At this moment in time, 'p4' isn't a safe CPUTYPE (It produces broken > > +> > code). 'p3' or 'i686' are what's recommended for Pentium 4s. > > +> > > +> Andre, I think you are out of date -- CPUTYPE=p4 is now safe with GCC > > +> 3.3.1. > > > > I think he is right, because when upgrading host where was gcc3.2 to > > current -CURRENT (with gcc3.3) 'make world' builds make(1) in first > > place and it is builded by gcc3.2 with CPUTYPE=p4, so it will be broken. > > > > So gcc have to be upgraded in first place (with CPUTYPE=p3). > > Hhm, sounds reasonable. > > However, I had the exact same problem updating from a 5.1-RC to a recent > current on a P III 900, and there, I had CPUTYPE=p3 in make.conf. > > Removing CPUTYPE eventually gave me back working systems (I did restore > 5.1-R bits prior to make world). Unfortunatly, I don't have the resources > to investigate this further, but for the time being, I will not use CPUTYPE > until others can confirm it's safe :-) I've been running my laptop with a world that was built with CPUTYPE=p3 (GCC 3.3.1) for close to a month. I haven't noticed anything odd yet. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
fwcontrol -r missing a close() call
# truss fwcontrol -r
mmap(0x0,3440,0x3,0x1000,-1,0x0) = 671535104 (0x2806d000)
munmap(0x2806d000,0xd70) = 0 (0x0)
__sysctl(0xbfbffa28,0x2,0x2806adac,0xbfbffa24,0x0,0x0) = 0 (0x0)
mmap(0x0,32768,0x3,0x1002,-1,0x0)= 671535104 (0x2806d000)
issetugid() = 0 (0x0)
open("/var/run/ld-elf.so.hints",0x0,00) = 3 (0x3)
read(0x3,0xbfbffac0,0x80)= 128 (0x80)
lseek(3,0x80,0) = 128 (0x80)
read(0x3,0x28071000,0x7a)= 122 (0x7a)
close(3) = 0 (0x0)
access("/usr/lib/libc.so.5",0) = 0 (0x0)
open("/usr/lib/libc.so.5",0x0,027757775430) = 3 (0x3)
fstat(3,0xbfbffb00) = 0 (0x0)
read(0x3,0x28069d00,0x1000) = 4096 (0x1000)
mmap(0x0,880640,0x5,0x20002,3,0x0) = 671567872 (0x28075000)
mprotect(0x28134000,0x1000,0x7) = 0 (0x0)
mprotect(0x28134000,0x1000,0x5) = 0 (0x0)
mmap(0x28135000,20480,0x3,0x12,3,0xbf000)= 672354304 (0x28135000)
mmap(0x2813a000,73728,0x3,0x1012,-1,0x0) = 672374784 (0x2813a000)
close(3) = 0 (0x0)
mmap(0x0,360,0x3,0x1000,-1,0x0) = 672448512 (0x2814c000)
munmap(0x2814c000,0x168) = 0 (0x0)
mprotect(0x28075000,0xc,0x7) = 0 (0x0)
mmap(0x0,21240,0x3,0x1000,-1,0x0)= 672448512 (0x2814c000)
munmap(0x2814c000,0x52f8)= 0 (0x0)
mprotect(0x28075000,0xc,0x5) = 0 (0x0)
sigaction(SIGILL,0xbfbffb40,0xbfbffb20) = 0 (0x0)
sigprocmask(0x1,0x0,0x28069c5c) = 0 (0x0)
sigaction(SIGILL,0xbfbffb20,0x0) = 0 (0x0)
sigprocmask(0x1,0x28069c00,0xbfbffb50) = 0 (0x0)
sigprocmask(0x3,0x28069c10,0x0) = 0 (0x0)
open("/dev/fw0.0",0x2,01001132500) = 3 (0x3)
ioctl(3,FW_IBUSRST,0xbfbff400) = 0 (0x0)
exit(0x0)
process exit, rval = 0
We're not closing fd #3 before exiting the process. This is also the case
with 4.8-STABLE.
Digging into the code it appears that it would be trivial to add two lines
to catch all instances of this (copy and pasted):
--- fwcontrol.c.origMon Aug 4 23:26:14 2003
+++ fwcontrol.c Tue Aug 19 11:15:13 2003
@@ -527,5 +527,9 @@
default:
usage();
}
+
+ if(fd != -1)
+ close(fd);
+
return 0;
}
Semantics? Nit-picking? Both? :)
Regards,
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mergemaster b0rked?
On Tue, 19 Aug 2003, John Hay wrote: > > > Stop in /usr/src/etc. > > > > > > *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to > > > the temproot environment > > > > > > # > > > > I'm seeing this too. I've cvsup'ed and rebuilt world (making sure that > > mergemaster was rebuilt) and it still occurs. > > Make sure to get a more clever src/etc/isdn/Makefile. I think 1.11 should > do. > > PS. It broke my nightly release build too. I'm now trying again with the > latest Makefile. O'Brien's version 1.11 of src/etc/isdn/Makefile fixes the problem. Thanks! Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mergemaster b0rked?
On Mon, 18 Aug 2003, Wilko Bulte wrote: > for i in answer isdntel.sh record > tell tell-record unknown_incoming ; do > install -o -g -m 700 $i /var/tmp/temproot/etc/isdn ; done ; for i in > holidays.Disdnd.rates.Aisdnd.rates.D isdnd.rates.F > isdnd.rates.L isdnd.rates.UK.BT isdnd.rc.sample >isdntel.alias.sample ; do install -o -g -m 600 $i > /var/tmp/temproot/etc/isdn ; done > install: -g: Invalid argument > *** Error code 67 > > Stop in /usr/src/etc/isdn. > *** Error code 1 > > Stop in /usr/src/etc. > > *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to > the temproot environment > > # I'm seeing this too. I've cvsup'ed and rebuilt world (making sure that mergemaster was rebuilt) and it still occurs. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slow Boot
On Mon, 18 Aug 2003, Kevin Oberman wrote: > > Date: Mon, 18 Aug 2003 11:09:05 -0400 (EDT) > > From: Andre Guibert de Bruet <[EMAIL PROTECTED]> > > > > On Mon, 18 Aug 2003, Kevin Oberman wrote: > > > > > > From: Bill Moran <[EMAIL PROTECTED]> > > > > > > > > Matthew D. Fuller wrote: > > > > > On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of > > > > > Bill Moran, and lo! it spake thus: > > > > > > > > > >>My best guess is that the chipset responds slowly to probes, thus it > > > > >>takes a while to get the list of devices from it. However, I've never > > > > >>looked into it any more than that. > > > > > > > > > > I've always presumed it to be a question of timing out probes to the > > > > > drives; it only ever happens on IDE controllers with no devices attached > > > > > to 'em. I habitually just disable the controller channels that are empty > > > > > (or, in the case of my SCSI systems, just yank ATA support altogether). > > > > > > > > Could be. This machine is pretty bare-bones. Single ATA HDD and nothing > > > > on the secondary controller. I never really considered that, but it makes > > > > sense that probes on the secondary controller would take the full timeout > > > > value if there was nothing to respond. > > > > > > Nope. My system has disks on both ATA controllers with hard drives as > > > the master for each channel. One channel also has the CD drive as > > > the slave. > > > > Does the hard drive that's on it's own have a "Single" jumper > > configuration option available? > > I'm not sure what a "Single" jumper is, but the drive is jumpered as > "master". The only options are "master", "slave", and "Cable Select". It's a jumper configuration that's commonly found on Western Digital IDE drives. It might also be labelled "Master w/o slave". Weirdness occurs (I've seen write errors and timeouts) when these drives sit on an otherwise empty IDE channel while they are set as 'master'. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Slow Boot
[CC list trimed] On Mon, 18 Aug 2003, Kevin Oberman wrote: > > From: Bill Moran <[EMAIL PROTECTED]> > > > > Matthew D. Fuller wrote: > > > On Sun, Aug 17, 2003 at 02:55:46PM -0400 I heard the voice of > > > Bill Moran, and lo! it spake thus: > > > > > >>My best guess is that the chipset responds slowly to probes, thus it > > >>takes a while to get the list of devices from it. However, I've never > > >>looked into it any more than that. > > > > > > I've always presumed it to be a question of timing out probes to the > > > drives; it only ever happens on IDE controllers with no devices attached > > > to 'em. I habitually just disable the controller channels that are empty > > > (or, in the case of my SCSI systems, just yank ATA support altogether). > > > > Could be. This machine is pretty bare-bones. Single ATA HDD and nothing > > on the secondary controller. I never really considered that, but it makes > > sense that probes on the secondary controller would take the full timeout > > value if there was nothing to respond. > > Nope. My system has disks on both ATA controllers with hard drives as > the master for each channel. One channel also has the CD drive as > the slave. Does the hard drive that's on it's own have a "Single" jumper configuration option available? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bsd.prog.mk duplicate script for target "loader"
I'm seeing the following on today's current (Just cvsup'ed): ... ===> sys/boot/i386/btx/lib ===> sys/boot/i386/boot2 ===> sys/boot/i386/cdboot ===> sys/boot/i386/kgzldr ===> sys/boot/i386/libi386 ===> sys/boot/i386/loader "/usr/src/share/mk/bsd.prog.mk", line 38: warning: duplicate script for target "loader" ignored ===> sys/boot/i386/pxeldr ... This occurs with: # $FreeBSD: src/share/mk/bsd.prog.mk,v 1.131 2003/06/29 18:16:26 gordon Exp $ Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lot's of SIGILL, SIGSEGV
Stefan, This is a FAQ. In the future, please search the archives before posting. At this moment in time, 'p4' isn't a safe CPUTYPE (It produces broken code). 'p3' or 'i686' are what's recommended for Pentium 4s. You'll also want to make sure that your CFLAGS don't use optimization higher than -O, as -O2 and -O3 have been the cause of odd behavior in the past with GCC3 (This might not apply to GCC 3.3.1 as I haven't had the time to do extensive regression testing, yet). Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Sun, 17 Aug 2003, Stefan Bethke wrote: > I've got three machines having trouble doing a installworld, let alone a > buildworld. > > One is a Dell Inspiron 8100 with a GeForce which used to run just fine on a > 5.1-RC, which I updated yesterday. > > Two are brand-new Shuttle SS51G with a SIS chipset and 2 GHz Celeron, which > I installed on Friday, initially with 5.1-R, then cvsupped to -current. > > I did make world with CPUTYPE=p4, as I believed this would be innocent. > However, I can't make world right now without CPUTYPE; I'll get to the > office to reinstall 5.1-R and make world without CPUTYPE on one of them to > later today, to see if that helps. > > Any other suggestions as to what could be the trouble? At this point I > doubt it's hardware, as all three seemed to run just fine on 5.1. > > > Thanks, > > Stefan > > > Here's the dmesg from one of the Shuttle's: > > Copyright (c) 1992-2003 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 5.1-CURRENT #0: Sat Aug 16 12:53:10 CEST 2003 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/EISENBOOT > Preloaded elf kernel "/boot/kernel/kernel" at 0xc0532000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05321cc. > Timecounter "i8254" frequency 1193182 Hz > CPU: Intel(R) Celeron(R) CPU 2.00GHz (2004.56-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 > Features=0xbfebfbff A,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > real memory = 503250944 (479 MB) > avail memory = 483217408 (460 MB) > Pentium Pro MTRR support enabled > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > pcibios: BIOS version 2.10 > Using $PIR table, 6 entries at 0xc00fde70 > acpi0: power button is handled as a fixed feature programming model. > Timecounter "ACPI-fast" frequency 3579545 Hz > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_cpu0: on acpi0 > acpi_cpu1: on acpi0 > acpi_tz0: on acpi0 > acpi_button0: on acpi0 > acpi_button1: on acpi0 > pcib0: port > 0x10c0-0x10ff,0x1000-0x10bf,0x480-0x48f,0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib0: slot 2 INTC is routed to irq 11 > pcib0: slot 3 INTA is routed to irq 10 > pcib0: slot 3 INTB is routed to irq 11 > pcib0: slot 3 INTC is routed to irq 9 > pcib0: slot 3 INTD is routed to irq 5 > pcib0: slot 15 INTA is routed to irq 11 > pcib0: slot 16 INTA is routed to irq 12 > agp0: mem 0xe800-0xebff at device > 0.0 on pci0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pcib0: slot 1 INTA is routed to irq 10 > pcib1: slot 0 INTA is routed to irq 10 > pci1: at device 0.0 (no driver attached) > isab0: at device 2.0 on pci0 > isa0: on isab0 > atapci0: port > 0x4000-0x400f,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 2.5 > on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at device 2.7 (no driver attached) > ohci0: mem 0xec10-0xec100fff irq 10 at device > 3.0 on pci0 > usb0: OHCI version 1.0, legacy support > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > ohci1: mem 0xec101000-0xec101fff irq 11 at device > 3.1 on pci0 > usb1: OHCI version 1.0, legacy support > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > ohci2: mem 0xec102000-0xec102fff irq 9 at device > 3.2 on pci0 > usb2: OHCI version 1.0, legacy support > usb2: on ohci2 > usb2: USB revision 1.0 > uhub2: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > pci0: at device 3.3 (no driver attached) > rl0: port 0xe800-0xe8ff > mem 0xec104000-0xec1040ff irq 11 at device 15.0 on pci
Re: mergemaster chokes on etc/sendmail
I'm seeing this my laptop too. CVSUP'ed 10 minutes ago. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Wed, 13 Aug 2003, Poul-Henning Kamp wrote: > > cd /freebsd/src/etc/sendmail; make distribution > install -o root -g wheel -m 644 /freebsd/src/etc/sendmail/freebsd.mc freebsd.cf > /var/tmp/temproot/etc/mail > install: freebsd.cf: No such file or directory > *** Error code 71 > > Stop in /freebsd/src/etc/sendmail. > *** Error code 1 > > Stop in /freebsd/src/etc. > > *** FATAL ERROR: Cannot 'cd' to /usr/src/etc and install files to > the temproot environment > > critter# > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: smp in 5.1
I guess I'll chime in as well... I have a Dual Athlon 2000+ MP here and it's running like a charm with SCHED_4BSD. Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Mon, 11 Aug 2003, derwood wrote: > I've been running 5.1-Current since its release on a Dell Precision 410 with > dual P-III 500's > No SMP problems here at all.. Its been extremely stable for me thus far. > > Darin - > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Steve Kargl > Sent: Monday, August 11, 2003 7:10 PM > To: Andy Farkas > Cc: [EMAIL PROTECTED]; Eriq Lamar > Subject: Re: smp in 5.1 > > > On Tue, Aug 12, 2003 at 08:25:38AM +1000, Andy Farkas wrote: > > On Mon, 11 Aug 2003, Eriq Lamar wrote: > > > > > Is there any advantage in 5.1 over 4.8 for two amd mp's. and if so > > > could someone tell what they are. I am interested in building dual > > > system using mp's but not sure which version would be better. > > > > Scheduling in 5.1 is broken (sched_ule doesn't even work*). > > > > Stick with 4.8. > > > > * for me, sched_ule completely locks up my box, no ping, no keybd. > > Exact same kernel with sched_4bsd works fine. > > > > Strange. ULE has worked fine on my UP system for > several months and the SMP system I recently obtained > from a co-worker hasn't panicked while running ULE. > Can you drop into ddb and trace the problem with > ULE on your system? > > -- > Steve > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bootstrapping network (bcm) on Dell D800
On Tue, 5 Aug 2003, Dr. Richard E. Hawkins wrote: > If I'm reading the recent messages correctly, the bcm driver won't work > unless updated to approximately July 17. > > I burned 5.1 iso's, and installed most of it successfully. How do I > bootstrap the network. I saw Bill Paul's references to testing a patch > prior to committing it. Is this something I can apply singly to the > source that comes on the ISO (and if so, just where do I grab it?), and > then build a kernel, reboot, and update the rest of the source? > > thanks > > hawk, anxious to play with his new toy Does this new toy have a 32-bit pci slot available? If so, pop in a nic (temporarily), cvsup and/or grab the needed patches and rebuild away! Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bootstrapping network (bcm) on Dell D800
On Wed, 6 Aug 2003, Dr. Richard E. Hawkins wrote: > On Wed, Aug 06, 2003 at 08:48:20AM -0400, David Gilbert wrote: > > I finally figureed out that the removable floppy (which works both as an > external usb and internall) is treated as a scsi device, not /dev/fd0. > So I tried moving the drivers from the up to date machine. No dice; > they depend on another changed function. > > So I borrowed a usb zip drive, and found that a bzip2'd source tree is > only 83M. I've moved that, and have a new kernel compiling from a > source tree updated this morning. Am I going to have to do anything > else to get the bge device detected, or will it just kernel installation > and reboot take care of this? If you've compiled the driver into the kernel, all you'll have to do is configure the IP settings for the device. If you intend on using the kernel loadable module, you'll have to kldload it before you configure the network settings. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: PCM freezes the box
On Thu, 7 Aug 2003 [EMAIL PROTECTED] wrote: > I have problems with my 5.1-Release and 5.1-STABLE boxes: > they freeze if I play anything different from audio CDs. > The cards are ESS 1938, options pcm is in the kernel. > If I try to run xmms/mpg123/KDE or any other application related > with artsd/esound/audiofile, the machines freeze, leaving not > a single chance to escape to shell and kill the process. Is anything printed on the console (or the first vty)? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bootstrapping network (bcm) on Dell D800
On Wed, 6 Aug 2003, David Gilbert wrote: > >>>>> "Andre" == Andre Guibert de Bruet <[EMAIL PROTECTED]> writes: > > Andre> On Tue, 5 Aug 2003, Dr. Richard E. Hawkins wrote: > > >> If I'm reading the recent messages correctly, the bcm driver won't > >> work unless updated to approximately July 17. > >> > >> I burned 5.1 iso's, and installed most of it successfully. How do > >> I bootstrap the network. I saw Bill Paul's references to testing a > >> patch prior to committing it. Is this something I can apply singly > >> to the source that comes on the ISO (and if so, just where do I > >> grab it?), and then build a kernel, reboot, and update the rest of > >> the source? > > Andre> Does this new toy have a 32-bit pci slot available? If so, pop > Andre> in a nic (temporarily), cvsup and/or grab the needed patches > Andre> and rebuild away! > > It has a mini-pci slot. You'd have a hard time getting an ethernet > card in there. Having just had a look at the patch, it's a little > large to be typing in by hand. Actually, you can get mini-pci wireless and wired nics. When I first posted, I didn't realize that the machine in question was a Latitude D800. Popping in a nic would require dismantling the unit, which you probably don't want to do... :-) > Here's the options I see for you: > > 1) the D800 has a serial port (rare on today's laptops). Hook up a > modem or a null serial cable and network thusly to cvsup. I'm under the impression that pretty much all of the 8xx-series Latitudes have DB9 ports (Including C800, C820 and friends). > 2) the D800 has a pccard slot. Find someone with a wireless or > ethernet card. > > 3) the D800 has usb2 and firewire... both of which can have ethernet > > 4) if you remove your hard drive, you can cheaply get a dodad that > will convert the mini ide connector to a regular one. > > 5) burn a CD or a DVD on another machine with the new src tree. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: INET6 in world
On Mon, 4 Aug 2003, Terry Lambert wrote: > Bernd Walter wrote: > > On Mon, Aug 04, 2003 at 03:32:47PM +0200, Harti Brandt wrote: > > > What's the sense of enabling and using IPv6, if your infrastucture > > > in the company doesn't support it (because of the overhead with routing > > > (hardware vs. software routing)) and you don't have an IPv6 connection to > > > the outside world. Well, you could ping localhost per IPv6... > > > > That's chicken/egg - IPv6 never will be widely used if everyone thinks > > that way. > > The sense is to break this dependency loop by ecouraging everyone to > > use it and not to make it easier to completely disable the support. > > As I said: you -always- have an IPv6 connection to the outside world > > as long as you have a single official IPv4 address. > > Not using it because it doesn't fit in your current network is one > > point, but disabling it in a way to make a future step to IPv6 > > harder is another. > > The number of IPv4 only systems is already big enough - we don't need > > to build new ones. This has been so over-argued, I don't think there's anything else to say on the matter except: Use the right tool for the right job. If you don't see yourself keeping your installation for a few years, then go ahead with your IPv4-only installation. More environments are starting to become "mixed" and this is a trend that will only accelerate as more sites embrace IPv6. > The problem, as I see it, is that it doesn't come enabled by > default on Windows systems. Until it does, it's never going > to get any traction. This is really OT, but Windows XP Professional does ship with an IPv6 stack. At the cmd prompt, type 'ipv6 install' and it'll load the "Microsoft IPv6 Developer Edition" protocol suite. Enjoy. > I wouldn't be surprised if the government has asked Microsoft > to not deploy it, or to deploy it without encryption support, > given world events. Well, given that they've included IPSEC in their latest operating system releases, I can't really say that I agree with that statement. To get back to the original question, NO_IPV4 and NO_IPV6 world knobs would be nice and would keep everyone happy for years to come! :-) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP: USB da(4) quirks deprecated
Hi, "camcontrol inquiry" requires the pass driver, so if it's not already in your kernel config you might want to add it when/if you add DA_OLD_QUIRKS. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Mon, 28 Jul 2003, Nate Lawson wrote: > I have committed code to disable the USB and Firewire quirks in da(4). > Since we now have code that should handle the common case of a failure > after receiving 6 byte commands, most of them should no longer be > necessary. However, the only way to tell if a quirk is really needed is > to test the new code with the quirks disabled. You may have a device (USB > camera, pen drive, hard drive, ...) that begins to get errors like "BBB > bulk-in clear stall failed" or "Synchronize cache failed, status 0x35". > If you get these, you can enable previous behavior by adding: > > options DA_OLD_QUIRKS > > to your kernel config and recompiling. Once you do this, please send me > the output of "camcontrol inquiry da0" so I can re-enable your quirk for > good. I'm doing this as soon as possible so the unnecessary quirks can be > removed for 5.2. A similar process will take place in 4-stable after 5.2 > has been released. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: still data corruption with 5.1-R on Intel Pentium 4
On Wed, 24 Jul 2003, Georg-W. Koltermann wrote: > There have been threads about data corruption in RAM on P4 and other > i386 machines on this list. I also observed the problem, on my laptop > with 5.0-R. It seemed to go away with 5.1-R, on the laptop. > > Recently I upgraded my home PC which is a P4 2.0A from 4.8-R to 5.1-R. > No problems at first. > > Until I ran "portsdb -Uu". I got a couple mysterious SIG4 and SIG11. > Just to be sure I rebooted and tried again, same result. I rebooted > another time, this time with ACPI disabled, and tried again, still the > same. > > Then I rebuilt my kernel with options DISABLE_PSE and DISABLE_PG_G, as > suggested by Terry in the old threads: Bingo, everything is fine now, no > more SIG4 or SIG11 during portsdb -Uu. > > It seems the workarounds that we have in 5.1-R are not effective enough. > What do you think? DISABLE_PSE and DISABLE_PG_G fixes all of the machines that I've seen with random segvs (And for the record, they've all been Pentium 4s). I find it ridiculous that chip vendors require NDAs to find out about _faults_ in the chips they've sold you. It's bad enough that these faults made it through QA and they're not offering replacement chips, but not allowing information about the problem to circulate so that appropriate workarounds can be made is immoral. My thoughts, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: where is kern.ca.da.no_6_byte?
On Sun, 20 Jul 2003, Harald Schmalzbauer wrote: > Andre Guibert de Bruet wrote: > > On Sun, 20 Jul 2003, Harald Schmalzbauer wrote: > > > > > Kenneth D. Merry wrote: > > > > > seems that this sysctl doesn't exist any more! > > > > > Is there anything similar? > > > > > > > > It has been renamed: > > > > kern.cam.da.%d.minimum_cmd_size > > > > > > > > Where %d is the unit number for the da(4) device. > > > > > > Thaks a lot! Where can I find such info? I looked via cvsweb > > for scsi_da.c > > > but couldn't find anything. Is it possible to list all kernel tunables? > > > > sysctl -a. You'll probably want to pipe it's output to your favorite > > pager. "sysctl kern" will list just the entries in the kern MIB. > > OIC. It's not available until the device is pluged in, which makes it > absolutely useless. > When I plug it in the machine behaves abnormal, so I need to set it BEFORE > connecting USB devices. > Why has this tunable by default a value which makes the machine unstable by > every umass I plug in which has no "qirk" entry? And if I look how many > quirks there are I assume that almost every device needs no_6byte set. > Why not make it default? Perhaps this would prevent criminal people from > intentionally crashing servers when intruding my serverroom armed with > dozends of USB devices;) I don't mean to defend the current state of the USB stack not recovering from errors and bad behavior, but ask yourself: "Do I really want USB enabled on my servers?" For most people, the answer is a resounding "No". Food for thought. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: where is kern.ca.da.no_6_byte?
On Sun, 20 Jul 2003, Harald Schmalzbauer wrote: > Kenneth D. Merry wrote: > > > seems that this sysctl doesn't exist any more! > > > Is there anything similar? > > > > It has been renamed: > > kern.cam.da.%d.minimum_cmd_size > > > > Where %d is the unit number for the da(4) device. > > Thaks a lot! Where can I find such info? I looked via cvsweb for scsi_da.c > but couldn't find anything. Is it possible to list all kernel tunables? sysctl -a. You'll probably want to pipe it's output to your favorite pager. "sysctl kern" will list just the entries in the kern MIB. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: msdof and fstab
On Wed, 16 Jul 2003 [EMAIL PROTECTED] wrote: > I am having trouble mounting my windows partition from the fstab file. I have an > entry in fstab that looks like this "/dev/ad6s5 /mnt/disk2 msdosfs rw 0 0". > When I try to mount the disk I get the following error "mount: disk2: unknown > special file or file system". What makes things even more strange is that I can > mount the slice just fine when I issue mount_msdosfs from the command prompt. Does > anyone have any ideas? I believe that fstab wants 'msdos' and not 'msdosfs'. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[SMALL PATCH] usbdevs
Hi, I've attached a patch for usbdevs that adds a manufacturer id for "X10 Wireless Technology" and the RF Receiver that they bundle as part of ATI's Radeon 8500DV video card package. Regards, Andy > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/>--- usbdevs Mon Jul 14 15:30:01 2003 +++ usbdevs.new Fri Jul 18 11:07:35 2003 @@ -339,6 +339,7 @@ vendor NEC20x0b62 NEC vendor ATI20x0b6f ATI vendor ASIX0x0b95 ASIX Electronics +vendor X10 0x0bc7 X10 Wireless Technology vendor REALTEK 0x0bda RealTek vendor AGATE 0x0c08 Agate Technologies vendor DMI 0x0c0b DMI @@ -1188,6 +1189,9 @@ product WACOM GRAPHIRE 0x0010 Graphire product WACOM INTUOSA5 0x0021 Intuos A5 product WACOM GD0912U 0x0022 Intuos 9x12 Graphics Tablet + +/* X10 Wireless Technology */ +product X10 USBRFRCVR 0x0004 USB RF Receiver (Sometimes Branded ATI) /* Xirlink products */ product XIRLINK PCCAM 0x8080 IBM PC Camera ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: debugging a lockup
On Fri, 18 Jul 2003, David Hill wrote: > cu -l /dev/cuaa0 completely locks up my machine... > How can I debug this? David, As usual, update your sources, enable all of the debugging options in your kernel config file, including DDB. Compile a kernel and ensure that you have an up-to-date world (Just to make sure that the issue hasn't already been fixed). To find out exactly where it's hanging, truss and strace are your friends. What's the last line that's printed out? Can you break to the debugger when the machine locks up (CTRL+ALT+ESC)? If so, can you get a backtrace by means of a 'tr'? Regards > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FW: escalation stage 2 [was:RE: Big and ugly bug in 5.1-release]
Harald, When in doubt, install freebsd 5.x on a different drive running off of a different controller, mount the slices from one of the disks in the RAID array and copy your data to a safe and trusted location. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tunning 5.1
On Thu, 3 Jul 2003, Danny Braniss wrote: > i run a small program that writes to file, these are the numbers > > Fbsdlocal disk nfs > -- > 4.8 44.86 42.54 > 5.1 34.37 16.42 > > are these values (MB/s) acceptable? comments? > while disk io is less that 30% slower, network is over 60% slower! Do have any kernel debugging options enabled on the 5.1 install? If so, the additional sanity checking is what's causing the discrepency. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VMWare not working anymore
VMWare. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Mon, 30 Jun 2003, Eirik Oeverby wrote: > Reinstalling what? VMWare or FreeBSD? > > On Mon, 30 Jun 2003, Lutz Bichler wrote: > > > I got the same problem/message and "solved" it by reinstalling ;-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[PATCH] Missing case statement in sys/boot/pc98/boot2/io.c
Hi,
There's a case statement missing in the implementation of printf located
in sys/boot/pc98/boot2/io.c to handle double % signs in the format
argument.
I realize that this would probably never be used under normal conditions
but for correctness, shouldn't the attached patch be committed?
Regards,
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>--- io.c.orig Sun Jun 29 11:05:36 2003
+++ io.cSun Jun 29 11:06:48 2003
@@ -96,6 +96,10 @@
putchar(c);
break;
}
+ case '%': {
+ putchar(c);
+ break;
+ }
}
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: libkse now running quite well on smp
On Sun, 22 Jun 2003, Kris Kennaway wrote: > On Sun, Jun 22, 2003 at 11:39:21PM +0800, Khairil Yusof wrote: > > > Great work by the KSE team! Looks like we might get libpthreads as > > default on 5.2. > > It still needs to be ported to sparc64. What about alpha? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: NFS weirdness...
On Thu, 19 Jun 2003, jle wrote: > You are correct, I misread the prev post. mount /home fails. > > # mount /home > mount: /dev/ad0s1h: Device busy > > There are two mount points for /home. One on the local disk (ad0s1h) and > the NFS mount that I mount over /home for shell users, so that HTTTD can > find the public_html dirs. > > The complete fstab on HTTPD: > # DeviceMountpoint FStype Options Dump > Pass# > /dev/ad0s1b noneswapsw 0 0 > /dev/ad0s1a / ufs rw 1 1 > /dev/ad0s1h /home ufs rw 2 2 > /dev/ad0s1d /tmpufs rw 2 2 > /dev/ad0s1g /usrufs rw 2 2 > /dev/ad0s1e /varufs rw 2 2 > /dev/ad0s1f /var/tmpufs rw 2 2 > /dev/acd0 /cdrom cd9660 ro,noauto 0 0 > NFSD:/home2 /home nfs rw,bg 0 0 > > > This worked before I upgraded my webserver (HTTPD) but now it fails to > mount on reboot yet succeeds manually. > > Any Ideas? Multiple mounts for a mountpoint is considered foot-shooting. Either: a) Mount /home off of NFSD:/home2. b) Mount NFSD:/home2 somewhere else. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[PATCH] usbdevs
Current, I've gone through the USB hardware that I had laying around and added a series of entries in usbdevs. I submitted a couple of entries a while ago, but I guess the email got lost in the noise. Who should I contact about getting this committed? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/>--- usbdevs Sat Jun 14 21:30:10 2003 +++ usbdevs.updated Sun Jun 22 15:17:42 2003 @@ -267,6 +267,7 @@ vendor COREGA 0x07aa Corega vendor FREECOM 0x07ab Freecom vendor MICROTECH 0x07af Microtech +vendor GENERALINSTMNTS 0x07b2 General Instruments (Motorola) vendor OLYMPUS 0x07b4 Olympus vendor ABOCOM 0x07b8 AboCom Systems vendor KEISOKUGIKEN0x07c1 Keisokugiken @@ -494,9 +495,11 @@ product BTC BTC79320x6782 Keyboard with mouse port /* Canon, Inc. products */ -product CANON N656U0x2206 CANOSCAN N656U +product CANON N656U0x2206 CanoScan N656U +product CANON N1240U 0x220e CanoScan N1240U product CANON S10 0x3041 PowerShot S10 product CANON S100 0x3045 PowerShot S100 +product CANON S200 0x3065 PowerShot S200 /* CATC products */ product CATC NETMATE 0x000a Netmate ethernet adapter @@ -607,8 +610,8 @@ product EPSON 1600 0x0107 Expression 1600 scanner product EPSON 1640 0x010a Perfection 1640SU scanner product EPSON 1240 0x010b Perfection 1240U / 1240Photo scanner -product EPSON 1250 0x010f Perfection 1250U / 1250Photo scanner product EPSON 640U 0x010c Perfection 640U scanner +product EPSON 1250 0x010f Perfection 1250U / 1250Photo scanner product EPSON 1650 0x0110 Perfection 1650 scanner product EPSON GT9700F 0x0112 GT-9700F scanner product EPSON 1260 0x011d Perfection 1260 scanner @@ -645,6 +648,9 @@ /* Fujitsu protducts */ productFUJITSU AH_F401U0x105b AH-F401U Air H device +/* General Instruments (Motorola) products */ +product GENERALINSTMNTS SB5100 0x5100 SURFboard SB5100 Cable modem + /* Genesys Logic products */ productGENESYS GL650 0x0604 GL650 Hub productGENESYS GL641USB0x0700 GL641USB CompactFlash Card Reader @@ -815,6 +821,7 @@ product LOGITECH WMJOY 0xc281 WingMan Force joystick product LOGITECH RK53 0xc501 Cordless mouse product LOGITECH RB6 0xc503 Cordless keyboard +product LOGITECH MX700 0xc506 Cordless optical mouse product LOGITECH QUICKCAMPRO2 0xd001 QuickCam Pro /* Lucent products */ @@ -848,8 +855,9 @@ product MICROSOFT NATURALKBD 0x000b Natural Keyboard Elite product MICROSOFT DDS800x0014 Digital Sound System 80 product MICROSOFT SIDEWINDER 0x001a Sidewinder Precision Racing Wheel +product MICROSOFT INETPRO 0x001c Internet Keyboard Pro product MICROSOFT INTELLIEYE 0x0025 IntelliEye mouse -product MICROSOFT INETPRO 0x002b Internet Keyboard Pro +product MICROSOFT INETPRO2 0x002b Internet Keyboard Pro /* Microtech products */ product MICROTECH SCSIDB25 0x0004 USB-SCSI-DB25 @@ -1039,6 +1047,7 @@ product SHUTTLE EUSCSI_B 0x000b eUSCSI Bridge product SHUTTLE EUSCSI_C 0x000c eUSCSI Bridge product SHUTTLE CDRW 0x0101 CD-RW Device +product SHUTTLE EUSBORCA 0x0325 eUSB ORCA Quad Reader /* Siemens products */ product SIEMENS SPEEDSTREAM0x1001 SpeedStream USB @@ -1156,6 +1165,7 @@ product WACOM CT0405U 0x CT-0405-U Tablet product WACOM GRAPHIRE 0x0010 Graphire product WACOM INTUOSA5 0x0021 Intuos A5 +product WACOM GD0912U 0x0022 Intuos 9x12 Graphics Tablet /* Xirlink products */ product XIRLINK PCCAM 0x8080 IBM PC Camera ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: rc.firewall not executed?
On Sun, 15 Jun 2003, Kris Kennaway wrote: > On Sun, Jun 15, 2003 at 09:36:23AM -0400, Andre Guibert de Bruet wrote: > > > > On Sat, 14 Jun 2003, Kris Kennaway wrote: > > > > > I just noticed that my ipfw rules were not loaded the last time I > > > rebooted. My rc.conf is included below - has something changed > > > recently so that these settings are not enough? I didn't see anything > > > relevant in UPDATING. My /etc/firewall.conf exists and is readable > > > (and unchanged since 2002). > > > > > > Kris > > > > > > > > > # $FreeBSD: src/etc/defaults/rc.conf,v 1.156 2002/08/30 13:01:42 hm Exp $ > > > hostname="citusc17.usc.edu" # Set this! > > > nisdomainname="cituscdomain"# Set to NIS domain if using NIS (or NO). > > > firewall_enable="YES" # Set to YES to enable firewall functionality > > > firewall_type="/etc/firewall.conf" # Firewall type (see /etc/rc.firewall) > > ^^ > > This is wrong. Set it to "UNKNOWN". There's firewall_script for that. > > Nope..read rc.firewall(5) :-) Well, I'm assuming that you're refering to the rc.firewall that's in section 8 of the manual; And yes, I stand corrected. But I still think that firewall_script is more intuitive... ;) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB locks on laptops.
On Sat, 14 Jun 2003, David Gilbert wrote: > While I thought it might be an isolated example, I have several > laptops ... all of which lock up their ports when usb devices are > connected. Typical messages include: > > usb3: unrecoverable error, controller halted > > and > > usb3: device problem, disabling port 3 > > ... which is an example from a new laptop with usb2.0, but an older > laptop with usb1.0 gives similar messages. > > Jun 14 00:09:48 canoe /kernel: uhub0: device problem, disabling port 2 > > Now... on non-portable hardware, usb ports all seem to work. All of > my desktop machine's USB ports work just fine with the same hardware. > > Any ideas? Disabling ACPI fixed this type of issue on a couple of HP notebooks I have access to. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: rc.firewall not executed?
On Sat, 14 Jun 2003, Kris Kennaway wrote: > I just noticed that my ipfw rules were not loaded the last time I > rebooted. My rc.conf is included below - has something changed > recently so that these settings are not enough? I didn't see anything > relevant in UPDATING. My /etc/firewall.conf exists and is readable > (and unchanged since 2002). > > Kris > > > # $FreeBSD: src/etc/defaults/rc.conf,v 1.156 2002/08/30 13:01:42 hm Exp $ > hostname="citusc17.usc.edu" # Set this! > nisdomainname="cituscdomain"# Set to NIS domain if using NIS (or NO). > firewall_enable="YES" # Set to YES to enable firewall functionality > firewall_type="/etc/firewall.conf" # Firewall type (see /etc/rc.firewall) ^^^^^^ This is wrong. Set it to "UNKNOWN". There's firewall_script for that. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ipfw's "me" keyword
On Tue, 10 Jun 2003, Dan Nelson wrote: > In the last episode (Jun 11), Andre Guibert de Bruet said: > > > > Now I realize that the broadcast address doesn't match the network > > card's IP address, which is why the packet isn't getting matched. But > > do we really want this behavior? Don't broadcasts affect all machines > > on the subnet and therefore qualify for "me" matching? > > "me" was more designed for allow rules when you have a dynamic IP. It > lets you set up rules that are guaranteed to work no matter what your > current IP is. Does this do what you want: > > deny udp from 192.168.1.0/24 to any dst-port 137,138 in via dc0 I ended up using that exact rule when I realized what was going on; And yes it does drop the packets as intended. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ipfw's "me" keyword
Hi, I've been fooling around a bit with IPFW2 and I came across interesting behavior with regards to the "me" keyword. It appears as if smb broadcasts (UDP 137,138) do not get matched when denying packets with a rule similar to the following: deny udp from 192.168.1.0/24 to me dst-port 137,138 I have a rule right after the one above which logs and I'm getting the following in my syslog: Jun 11 00:16:04 bling kernel: ipfw: 65530 Reject UDP 192.168.1.40:138 192.168.1.255:138 in via dc0 Now I realize that the broadcast address doesn't match the network card's IP address, which is why the packet isn't getting matched. But do we really want this behavior? Don't broadcasts affect all machines on the subnet and therefore qualify for "me" matching? Thanks for any insight. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New Kernel Breaks IPFW
On Tue, 10 Jun 2003, Ian Freislich wrote: > Andre Guibert de Bruet wrote: > > > > The new ipfw binary will work with an up-to-date kernel. What you need to > > do is boot this new kernel and only then try out the new ipfw binary. > > That doesn't really explain why the new ipfw binary core dumped > with the new kernel, but worked fine with old kernels. > > Now that I've removed BDECFLAGS, it seems that my buildworld will > succeed and whatever it was that was broken that ipfw linked in > (statically) will hopefully be fixed and all will be good in my > land of -CURRENT, for the moment that is. With CFLAGS of -O -pipe and a conservative value of CPUTYPE (ie not p4), everything should be okay: It works here(tm)! ;-) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New Kernel Breaks IPFW
Ian, The new ipfw binary will work with an up-to-date kernel. What you need to do is boot this new kernel and only then try out the new ipfw binary. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Tue, 10 Jun 2003, Ian Freislich wrote: > Terry Lambert wrote: > > Apparently, someone hosed the compiler flags. Looking at your > > cribbed link: > > > > > Someone posted a link to the failure that I get, so I'll crib: > > > http://www.0xfce3.net/error.txt > > > > We see: > > > > cc -O -pipe -std=iso9899:1999 -I/usr/obj/usr/src/i386/legacy/usr/include > > -static -L/usr/obj/usr/src/i386/legacy/usr/lib -o xinstall xinstall.o -legacy > > > > Works. > > > > cc -O -pipe -I. -I/usr/src/usr.sbin/config -W -Wall -ansi -pedantic > > -Wbad-function-cast -Wcast-align -Wcast-qual -Wchar-subscripts -Winline > > -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wredundant-decls > > -Wshadow -Wstrict-prototypes -Wwrite-strings -std=iso9899:1999 > > -I/usr/obj/usr/src/i386/legacy/usr/include -c config.c > > Hmmm, BDEFLAGS. config.c appears to compile without them. > > > > > Short term, cd /usr/src/sbin/ipfw; make depend && make all install ought > > > > to fix it. > > > > > > I tried that as well, but the new binary also dumps core, but works > > > well with previous versions of the firewall. Even back as far as > > > my kernel.working from May 7 2003. > > > > Bogus header files; specifically, . Because you > > can't build world, you are compiling the ipfw program with the old > > system include files instead of the new ones. You may also be > > missing a cvs update on the ipfw sources themselves (specifically, > > ipfw2.c). > > No, it did compile ipfw2.c (r1.24). I also installed all new > includes before I compiled ipfw and re-worlding to no avail. I > figured an old kernel with a working firewall was better than a new > kernel with no firewall. > > Ian > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP(2): CCD GEOMified.
Poul, Not to be nitpicking here, but the date that you have in UPDATING is a month off. Other than that, great work! :-) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Mon, 9 Jun 2003, Poul-Henning Kamp wrote: > > I've done the deed, remember to update your ccdconfig(8) with your > kernel. > > Poul-Henning > > phk 2003/06/09 12:25:07 PDT > > FreeBSD src repository > > Modified files: > .UPDATING > sys/conf files > sbin/ccdconfig ccdconfig.c > Removed files: > sys/sys ccdvar.h > sys/dev/ccd ccd.c > Log: > GEOMification of CCD. > > You need your kernel and ccdconfig(8) to be in sync, particularly if your > source tree is on a ccd device. > > Revision ChangesPath > 1.252 +8 -0 src/UPDATING > 1.32 +69 -165 src/sbin/ccdconfig/ccdconfig.c > 1.791 +2 -1 src/sys/conf/files > 1.138 +0 -1322 src/sys/dev/ccd/ccd.c (dead) > 1.20 +0 -120src/sys/sys/ccdvar.h (dead) > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 5.1-RELEASE TODO
Larry, Did you ever get back to Intel's Robert Moore WRT to his May 21st message (Msg-ID [EMAIL PROTECTED]) ? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Thu, 5 Jun 2003, Larry Rosenman wrote: > > > --On Thursday, June 05, 2003 18:59:49 +0200 Erik Paulsen Skaalerud > <[EMAIL PROTECTED]> wrote: > > >> > FYI, I still see the ACPI messages described in the "Re: ACPI-0293 > >> > (and > >> > 0166) errors"-thread on -current ca. 5/9/2003 on > >> yesterday's -current. > >> > > >> > Lars > >> > >> Yeah, ACPI is causing many problems these days, much of which > >> can be traced back to non-compliant system BIOS's. The new > >> bootloader menu in FreeBSD 5.1 allows one to disable ACPI for > >> the time being. > >> > >> Scott > >> > > > > Will this lead to an extension of the release schedule for 5.1 until most > > of the problems are fixed? > > To me it looks like there are more and more reports about panics every day > > :( > > > > Erik > For the record, yesterday's sources STILL produce the panic at 0x7 for me > on > transition to battery. > > I can get more crashdumps/kernels if someone asks. > > I've mentioned this for the last ~1.5 months. > > LER > > > > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] > US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749 > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nge in GENERIC
Hi, I noticed that nge doesn't figure in GENERIC. Is this done on purpose? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: i386-undermydesk-freebsd?
On Thu, 5 Jun 2003, Mike Barcroft wrote: > [EMAIL PROTECTED] <[EMAIL PROTECTED]> writes: > > What does "i386-undermydesk-freebsd" refer to? What is it used for? Is there > > an "i386-inthedrawer-freebsd", or "i386-intheXbox-freebsd"? > > As a general rule of thumb, FreeBSD boxes should be kept under desks. > If your system isn't under a desk, consider moving it. I must voice my difference of opinion because I have carpeted floors. At this point in time my Hoover isn't powered by FreeBSD... ;-) > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADSUP: ccd migration issue for some.
Could we get an UPDATING entry for this when it gets committed? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Wed, 4 Jun 2003, Poul-Henning Kamp wrote: > > In a few days time I will flip the switch so that we run on the new > GEOMified CCD. > > In all my tests, the new CCD is compatible with the old CCD, but > it does require an updated ccdconfig(8) program. > > This is nothing out of the ordinary, unless you happen to have > your /usr/src or /usr/obj stored on a ccd volume, in which case > you would do well in squirilling away a copy of the old ccdconfig(8) > binary along with your fall back kernel. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > [EMAIL PROTECTED] | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Additions to sys/dev/usb/usbdevs
Hi, I've added definitions for a few of the devices that I have connected up to my system at the moment. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/>--- usbdevs.origWed Jun 4 18:10:45 2003 +++ usbdevs Wed Jun 4 18:40:29 2003 @@ -497,6 +497,7 @@ product CANON N656U0x2206 CANOSCAN N656U product CANON S10 0x3041 PowerShot S10 product CANON S100 0x3045 PowerShot S100 +product CANON S200 0x3065 PowerShot S200 /* CATC products */ product CATC NETMATE 0x000a Netmate ethernet adapter @@ -814,6 +815,7 @@ product LOGITECH WMJOY 0xc281 WingMan Force joystick product LOGITECH RK53 0xc501 Cordless mouse product LOGITECH RB6 0xc503 Cordless keyboard +product LOGITECH MX700 0xc506 Cordless optical mouse product LOGITECH QUICKCAMPRO2 0xd001 QuickCam Pro /* Lucent products */ @@ -1038,6 +1040,7 @@ product SHUTTLE EUSCSI_B 0x000b eUSCSI Bridge product SHUTTLE EUSCSI_C 0x000c eUSCSI Bridge product SHUTTLE CDRW 0x0101 CD-RW Device +product SHUTTLE EUSBORCA 0x0325 eUSB ORCA Quad Reader /* Siemens products */ product SIEMENS SPEEDSTREAM0x1001 SpeedStream USB @@ -1155,6 +1158,7 @@ product WACOM CT0405U 0x CT-0405-U Tablet product WACOM GRAPHIRE 0x0010 Graphire product WACOM INTUOSA5 0x0021 Intuos A5 +product WACOM GD0912U 0x0022 Intuos 9x12 Graphics Tablet /* Xirlink products */ product XIRLINK PCCAM 0x8080 IBM PC Camera ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
systat -v on -CURRENT
Hi, I've noticed that 'systat -v' sometimes reports a negative disk activity percentile. Has anyone else noticed this behavior? Before I look into the problem, is someone already working on a fix? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OSS SBLive driver causes kernel panic with 5.0 current
On Fri, 7 Mar 2003, Jody Franklin wrote: > I'd been keeping up with current (world/kernel) every other week or so, > and until this week I had no real problems. But after the build I did on > March 3rd my soundcard driver (4Front's SBLive/Audigy driver) causes a > kernel panic on load. If I don't load the driver the system boots fine, > and runs with no other problems. > > This is the message I get from the debugger when I load the driver: > > panic: Invalid major (-1030904368) in make_dev > > I've posted this info to their support forums also, their last responce > was to "see what they broke". Please don't cross-post -current and -questions. Major numbers are now being allocated dynamically. Sounds like the emu10k1 driver doesn't like this. My guess is, it's probably in the process of being converted over... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: UDF: bad file descriptor
On Sun, 16 Mar 2003, FUJITA Kazutoshi wrote: > I could mount DVD-RAM successfully. > But, some files can't be read. > How can I solve this? > > # /bin/ls > . .. VR_MANGR.BUPVR_MANGR.IFOVR_MOVIE.VRO > > # /bin/ls -l > ls: VR_MOVIE.VRO: Bad file descriptor > total 111 > drw-rw-rw- 1 root wheel 2048 Mar 12 13:33 . > drw-rw-rw- 4 root wheel 2048 Mar 16 18:00 .. > -rw-rw-rw- 1 root wheel 56980 Mar 16 18:01 VR_MANGR.BUP > -rw-rw-rw- 1 root wheel 56980 Mar 16 18:01 VR_MANGR.IFO Sounds like the lstat on VR_MOVIE.VRO is failing. Does 'truss ls -l' display anything relevant? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Top weirdness.
Craig, It's not a system process, but it's GCC (step 2) running as root. You were building software (ports, kernel or other) when the screenshot was taken. top -S displays non-system processes as well as system processes. The 168% in the weighed CPU field is a little odd, but it's an approximated average and as such, is not always perfectly accurate. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Sat, 15 Feb 2003, Craig Reyenga wrote: > 'cc1' is _not_ a system process. How is this normal? > > -Craig > > > - Original Message - > From: "Andre Guibert de Bruet" <[EMAIL PROTECTED]> > To: "Craig Reyenga" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Saturday, March 15, 2003 19:52 > Subject: Re: Top weirdness. > > Craig, > > > > That's the normal output of 'top -S'. > > > > Regards, > > > > > Andre Guibert de Bruet | Enterprise Software Consultant > > > > Silicon Landmark, LLC. | http://siliconlandmark.com/> > > > > On Sat, 15 Mar 2003, Craig Reyenga wrote: > > > > > Check these out: > > > > > > http://chat.carleton.ca/~creyenga/1sttime.JPG > > > > > > http://chat.carleton.ca/~creyenga/again.JPG > > > > > > Pretty strange, my normally-aspirated computer is somehow using 168% > of cpu. > > > > > > boss# uname -a > > > FreeBSD boss.sewer.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Mar > 7 > > > 01:49:18 EST 2003 > > > [EMAIL PROTECTED]:/usr/obj/usr/s/run/src/sys/BOSSKERN i386 > > > > > > Using SCHED_4BSD. > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > > with "unsubscribe freebsd-current" in the body of the message > > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Top weirdness.
Craig, That's the normal output of 'top -S'. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Sat, 15 Mar 2003, Craig Reyenga wrote: > Check these out: > > http://chat.carleton.ca/~creyenga/1sttime.JPG > > http://chat.carleton.ca/~creyenga/again.JPG > > Pretty strange, my normally-aspirated computer is somehow using 168% of cpu. > > boss# uname -a > FreeBSD boss.sewer.org 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Mar 7 > 01:49:18 EST 2003 > [EMAIL PROTECTED]:/usr/obj/usr/s/run/src/sys/BOSSKERN i386 > > Using SCHED_4BSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bad malloc flags: 4
On Tue, 11 Mar 2003, Kris Kennaway wrote: > Got this when booting a fresh kernel: > > Bad malloc flags: 4 > Stack backtrace: > backtrace(c03953d4,4,1,c035e443,c1b6e500) at backtrace+0x17 > malloc(3c,c03dfe80,4,c1b85d00,dcd7bc78) at malloc+0x5b What does the output of ls -l /etc/malloc.conf look like? Regards > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: hw.acpi.battery.units not accurate
On Fri, 7 Mar 2003, George Patterson wrote: > I have a Toshiba Satellite 1800 laptop (Mostly Acer subsystems). While > the battery.time is incorrect (negative number), the > hw.acpi.battery.units sysctl doesn't change when I swap out the battery. > > Batter Installed > > sysctl hw.acpi.battery > hw.acpi.battery.life: 99 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 2 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > Battery Removed > > sysctl hw.acpi.battery > hw.acpi.battery.life: -1 > hw.acpi.battery.time: -1 > hw.acpi.battery.state: 7 > hw.acpi.battery.units: 1 > hw.acpi.battery.info_expire: 5 > > The battery time was being reported correct by apm under FreeBSD 4.7 -1 is the value that you get if you get the sysctl sample when the unit is plugged in. Make sure that you disconnect the AC line when you sample... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
387 FPU code (Was: Re: -O2 broke ppp NAT)
On Thu, 6 Mar 2003, Bruce Cran wrote: > 387 (FPU) code generation seems to be broken in gcc 3.2.1 when -O2 is used. Would you happen to know if this is still broken in 3.2.2? > I can compile applications with no problems when -mfpmath=sse is added so > that the 387 unit won't be used, but without it, applications crash. Note > that since SSE support is enabled by the kernel, it probably wouldn't be > a good idea to compile the kernel with -mfpmath=sse. I use -O2 -pipe -mmmx -msse -mfpmath=sse to compile world and kernel. So far so good, no quirks to date! :) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
hw.acpi.battery.units not accurate
Hi, The hw.acpi.battery.units sysctl doesn't seem to be displaying the correct number of batteries. I'm trying this out on a Dell Latitude C800 with two batteries. The sysctl correctly returns '2', but this is also the value that it displays once either battery is swapped out. hw.acpi.battery.time correctly (and immediately) reflects the addition / removal of either battery. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Witness problem with sound
I'm getting the "could sleep with" messages repeated over and over on my Dell Lattitude C800 which uses the maestro3 chip. The sound isn't overly choppy. It only stutters under disk/compute activity. > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Tue, 4 Mar 2003, Pete Carah wrote: > I don't know how system-specific this problem is, but: > > Sony VAIO R505ES > Sound is Intel ICH3 + Yamaha. > > This or something closely related has been happening for weeks. > Several times earlier this week and last week sound panic'd, and > also sometimes there was a panic (several different kinds) on boot. > Late last week X wouldn't start due to not being able to see the > VESA modes. > All those except the sound problems currently appear fixed... > > This may or may not be related to the fact that acpi puts nearly all > device interrupts on irq 9 (which causes other problems). > > Problem: > .. > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:748 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:27 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:696 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:673 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:673 > Mar 4 14:56:28 port2 kernel: /usr/src/sys/vm/uma_core.c:1330: could sleep with > "pcm0:play:0" locked from /usr/src/sys/dev/sound/pcm/dsp.c:673 > . > (repeated by the thousands, at various lines, the above plus > sound.c:191 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Removal of netns
On Tue, 4 Mar 2003, Vincent Jardin wrote: > Why does it need to be removed ? According to me, it would be the same mistake > as the removal of netiso and netccitt. I did not know FreeBSD at this time, > but nowadays, in order to get an OS that supports many stacks, we have to use > NetBSD. If netns has so many users and our implementation has been broken for so long, why is it there hasn't been hordes of complaints? It appears as if users of netns are a rarity... > BSD4.4 was designed in order to support many stacks, FreeBSD 6, 7 ou 9 will > support only IPv4 and IPv6, won't they ? Today, widely-used networking applications use IPv4 and/or IPv6. It's understandable that as such, our IP stacks have gotten more testing and tuning than any other. If there's another networking protocol out there that has enough users interested and enough developer, vendor or device support, I don't see why it wouldn't be incorporated into the FreeBSD tree. A good example of a stack that was recently imported (comparatively speaking) would be Bluetooth. > I do not think that it needs to be removed. One should try to keep this > feature. As always, patches are welcome. If you happen to need netns for anything, scratch the itch... :-) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems compiling KDE after mega-commit
Hi, You need to upgrade your ports skeleton. There's a couple of fixes that were committed within the last 24 hours which fix these issues. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> On Tue, 4 Mar 2003, Rossam Souza Silva wrote: > > I upgraded my machine while compiling KDE, some sys header files > are problematic now: > > In file included from ksimcpu.cpp:45: > /usr/include/sys/dkstat.h:45:2: warning: #warning " is > deprecated and should not be #include'd" > ksimcpu.cpp:244:2: warning: #warning is a GCC extension > ksimcpu.cpp:244:2: warning: #warning "add support for SMP on FreeBSD" > ksimcpu.cpp: In member function `void > CpuView::updateCpu(CpuView::CpuData&, >int)': > ksimcpu.cpp:248: `CPUSTATES' undeclared (first use this function) > ksimcpu.cpp:248: (Each undeclared identifier is reported only once for > each >function it appears in.) > ksimcpu.cpp:249: `cpuTime' undeclared (first use this function) > ksimcpu.cpp:250: warning: deprecated conversion from string constant to > `char*' > ksimcpu.cpp:266: `CP_USER' undeclared (first use this function) > ksimcpu.cpp:267: `CP_NICE' undeclared (first use this function) > ksimcpu.cpp:268: `CP_SYS' undeclared (first use this function) > ksimcpu.cpp:269: `CP_IDLE' undeclared (first use this function) > ksimcpu.cpp:209: warning: unused parameter `int cpuNumber' > gmake[4]: *** [ksimcpu.lo] Error 1 > gmake[4]: Leaving directory > `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors/cpu' > gmake[3]: *** [all-recursive] Error 1 > gmake[3]: Leaving directory > `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors' > gmake[2]: *** [all-recursive] Error 1 > gmake[2]: Leaving directory > `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.1' > gmake: *** [all] Error 2 > *** Error code 2 > > Stop in /usr/ports/misc/kdeutils3. > *** Error code 1 > > Stop in /usr/ports/x11/kde3. > > > CPUSTATES & cia. are defined in sys/resource.h, including this header in > ksimcpu.cpp, I have this: > > > In file included from ksimcpu.cpp:45: > /usr/include/sys/dkstat.h:45:2: warning: #warning " is > deprecated and should not be #include'd" > In file included from ksimcpu.cpp:46: > /usr/include/sys/resource.h:61: field `ru_utime' has incomplete type > /usr/include/sys/resource.h:62: field `ru_stime' has incomplete type > /usr/include/sys/resource.h:122: 'int32_t' is used as a type, but is not >defined as a type. > /usr/include/sys/resource.h:123: 'int32_t' is used as a type, but is not >defined as a type. > /usr/include/sys/resource.h:127: 'rlim_t' is used as a type, but is not > defined >as a type. > /usr/include/sys/resource.h:128: 'rlim_t' is used as a type, but is not > defined >as a type. > /usr/include/sys/resource.h:133: syntax error before `[' token > ksimcpu.cpp:245:2: warning: #warning is a GCC extension > ksimcpu.cpp:245:2: warning: #warning "add support for SMP on FreeBSD" > ksimcpu.cpp: In member function `void > CpuView::updateCpu(CpuView::CpuData&, >int)': > ksimcpu.cpp:251: warning: deprecated conversion from string constant to > `char*' > ksimcpu.cpp:210: warning: unused parameter `int cpuNumber' > gmake[4]: *** [ksimcpu.lo] Error 1 > gmake[4]: Leaving directory > `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors/cpu' > gmake[3]: *** [all-recursive] Error 1 > gmake[3]: Leaving directory > `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim/monitors' > gmake[2]: *** [all-recursive] Error 1 > gmake[2]: Leaving directory > `/usr/ports/misc/kdeutils3/work/kdeutils-3.1/ksim' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/usr/ports/misc/kdeutils3/work/kdeutils-3.1' > gmake: *** [all] Error 2 > *** Error code 2 > > Stop in /usr/ports/misc/kdeutils3. > *** Error code 1 > > Stop in /usr/ports/x11/kde3. > > -- > (_ ) "Contrary to popular belief, UNIX is user friendly. It just happens > \\\'',) ^ to be very selective about who it decides to make friends with." >\/ \( >.\._/_) Rossam Souza Silva ([EMAIL PROTECTED]) > - > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: nvidia module panics today's kernel [03-03-03]
On Mon, 3 Mar 2003, walt wrote: > My mini 'disaster' of earlier today was caused by the nvidia kernel > module being autoloaded at boot, which causes an immediate kernel panic. > > The newest kernel seems fine until I try to load the module manually, > at which time I still get the kernel panic even after re-compiling > the module. > > Maxime, it looks like the nvidia module will need to be sculpted one > more time. :-( If you really need to use your workstation, you can try the open source nv XFree86 driver. It's not as fast as the nVidia detonator driver and it's not accelerated, but you can at least use X11 at a reasonable resolution and color depth. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Double fault with IBM microdrives and CompactFlash (LONG)
Latest update: pccard0: Allocation failed for cfe 0 ata2 at port 0x140-0x14f irq 10 function 0 config 1 on pccard0 ad4: 342MB [695/16/63] at ata2-master PIO1 # atacontrol cap 2 0 # Microdrive ATA/ATAPI revision4 device model IBM-DMDM-10340 serial number XHAF1669 firmware revision MD2IC501 # atacontrol cap 2 0 # Compactflash ATA/ATAPI revision0 device model TOSHIBA THNCF128MBA serial number STCB21M82005E93599A5 firmware revision 2.00 It works! :-) Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Disaster strikes...
On Mon, 3 Mar 2003, walt wrote: > After cvsup'ing just now I cannot reboot -CURRENT either with the new > kernel or the old kernel. > > The new kernel panics instantly on boot, and the old kernel halts > with multiple messages about ACPI, so I'm stuck with an unbootable > machine. > > What is the command to disable acpi at the boot prompt? I tried > 'toggle-module acpi' with no luck. unset acpi_load If you're still having problems, Make sure that you do set module_path=/boot/kernel.old at the loader prompt. This will ensure that you're not loading the new modules with your old kernel. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't sshd into box
On Sun, 2 Mar 2003, Terry Lambert wrote: > Andre Guibert de Bruet wrote: > > On Mon, 3 Mar 2003, Wayne Barnes wrote: > > > Immediately after rebooting, I get this: > > > > > > [EMAIL PROTECTED]:/home/wayne>telnetd -debug ^^^ > > > telnetd: bind: Address already in use > > > > > > This doesn't happen on my other (working) system. > > > Could this be a clue to my problem? > > > > Telnetd is telling you that something else is listening on port 23. This > > is most probably inetd. Do a 'killall inetd' then try that command. > > That's not only going to stop inetd from sitting on the port, > it will probably also make telnet into the box start working, > if it's related to the TCP wrappers (if he had modified his > hosts.allow with the advice from a previous poster, he would > not be having this problem, if that happens, so rather than > posting his problem over and over again, maybe he should read > the responses, and at least tell us if they worked?). > > Otherwise, another common culprit is ipfw; if he has the > firewall enabled, the default is to block everything. > > Given that he got a connection, and that it was subsequently > closed, though, rather than not getting a connection at all, > it's a safe bet that it's the TCP wrappers, not the ipfw, that > is causing the trouble. > > In which case, he should take the advice on the hosts.allow > file contents that he was given earlier, and it will fix his > problem... Terry, Part of the original message said the following: I have installed 5.0 into a new Dell. I have not set up anything special yet (no firewall, no natd, etc.). <...> Is there a new default connecton protection that I must turn off, or something? [/etc/hosts.allow is the default setting, I see no answer there.] If I recall correctly, we don't ship GENERIC with any firewalling options enabled, so like you said, this is not likely to be a firewalling issue. 5.0R's /etc/hosts.allow shipped with something like the following at the top of the file: # Start by allowing everything (this prevents the rest of the file # from working, so remove it when you need protection). # The rules here work on a "First match wins" basis. ALL : ALL : allow If Wayne was trying to run 'telnetd -debug', would it not make sense for him to kill inetd first (or at least reconfigure inetd.conf then hup it) before running the daemon in debug mode at the command line? Wayne: Can you successfully login using telnet over the loopback interface? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't sshd into box
On Mon, 3 Mar 2003, Wayne Barnes wrote: > Immediately after rebooting, I get this: > > [EMAIL PROTECTED]:/home/wayne>telnetd -debug > telnetd: bind: Address already in use > > This doesn't happen on my other (working) system. > Could this be a clue to my problem? Wayne, Telnetd is telling you that something else is listening on port 23. This is most probably inetd. Do a 'killall inetd' then try that command. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Double fault with IBM microdrives and CompactFlash (LONG)
On Sat, 1 Mar 2003, Andre Guibert de Bruet wrote:
> I just tried using my FreeBSD laptop to unload pictures off of a 340MB IBM
> microdrive (Model: DMDM-10340, P/N: 22L0046) using the IBM PC Card adapter
> (P/N: 31L9315). The laptop in question is a stock Dell Latitude C800 with
> a 1Ghz P3, 512MB of RAM and a 20GB ATA66 drive.
>
> I got a double "page fault in kernel mode" message shortly after inserting
> the drive. I rebooted then tried using the same adapter with a 128MB
> Viking CompactFlash card, and I got the same problem. Now, I've used this
> adapter under Windows XP, and it works, so it's not defective. I use the
> same cardbus slots for my wi0 interface (PRISM II-based), so I know both
> slots work. I recvsup'ed to make sure that I have all the latest committed
> fixes. Here's what uname says:
> pccard1: Allocation failed for cfe 0
> ata2 at port 0x100-0x10f irq 10 function 0 config 1 on pccard1
I've since cvsup'ed, and upgraded this machine's kernel.
omikron# uname -a
FreeBSD omikron.properkernel.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Mar 2
09:29:14 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/OMIKRON i386
I also enabled dumps and managed to get a clean dump:
(kgdb) bt
#0 doadump () at ../../../kern/kern_shutdown.c:239
#1 0xc013bb55 in db_fncall (dummy1=0, dummy2=0, dummy3=3999,dummy4=0xd68d0964
"@\003EÀ\f") at ../../../ddb/db_command.c:546
#2 0xc013b8d2 in db_command (last_cmdp=0xc04037c0, cmd_table=0x0,
aux_cmd_tablep=0xc03fdf94, aux_cmd_tablep_end=0xc03fdf98)at
../../../ddb/db_command.c:346
#3 0xc013b9e6 in db_command_loop () at ../../../ddb/db_command.c:470
#4 0xc013e76a in db_trap (type=12, code=0) at ../../../ddb/db_trap.c:72
#5 0xc0388ad1 in kdb_trap (type=12, code=0, regs=0xd68d0b34)at
../../../i386/i386/db_interface.c:166
#6 0xc039a2f2 in trap_fatal (frame=0xd68d0b34, eva=0)at
../../../i386/i386/trap.c:838
#7 0xc039a002 in trap_pfault (frame=0xd68d0b34, usermode=0, eva=0)at
../../../i386/i386/trap.c:757
#8 0xc0399b7d in trap (frame= {tf_fs = -695402472, tf_es = -1072431088, tf_ds =
-1051262960, tf_edi = -1051687936, tf_esi = 128, tf_ebp = -695399504, tf_isp =
-695399584, tf_ebx = 16, tf_edx = -1051231700, tf_ecx = -1068976384, tf_eax =
-1051231700, tf_trapno = 12, tf_err = 0, tf_eip = 0, tf_cs = 8, tf_eflags = 66118,
tf_esp = -1072345719, tf_ss = -1051231700}) at ../../../i386/i386/trap.c:444
#9 0xc038a428 in calltrap () at {standard input}:96
#10 0xc01463d3 in ata_attach (dev=0x80) at ../../../dev/ata/ata-all.c:210
#11 0xc017b24a in pccard_compat_do_attach (bus=0xc40f8500, dev=0x80)at
card_if.h:129
#12 0xc014a5bd in pccard_compat_attach (dev=0x10) at card_if.h:147
#13 0xc0254010 in device_probe_and_attach (dev=0x10) at device_if.h:39
#14 0xc0179f1f in pccard_attach_card (dev=0xc40f8500)at
../../../dev/pccard/pccard.c:243
#15 0xc0181f08 in cbb_insert (sc=0xc15a2c00) at card_if.h:66
#16 0xc0181d2b in cbb_event_thread (arg=0xc15a2c00)at
../../../dev/pccbb/pccbb.c:914
#17 0xc022b634 in fork_exit (callout=0xc0181cb0 , arg=0x0,
frame=0x0) at ../../../kern/kern_fork.c:871
(kgdb) list ../../../dev/ata/ata-all.c:210
205 if (ch->devices & ATA_ATAPI_MASTER)
206 if (ata_getparam(&ch->device[MASTER], ATA_C_ATAPI_IDENTIFY))
207 ch->devices &= ~ATA_ATAPI_MASTER;
208 #ifdef DEV_ATADISK
209 if (ch->devices & ATA_ATA_MASTER)
210 ad_attach(&ch->device[MASTER]);
211 if (ch->devices & ATA_ATA_SLAVE)
212 ad_attach(&ch->device[SLAVE]);
213 #endif
214 #if DEV_ATAPIALL
File versions:
src/sys/dev/ata/ata-all.c 1.167
src/sys/dev/ata/ata-all.h 1.59
src/sys/dev/pccard/card_if.m 1.21
src/sys/dev/pccbb/pccbb.c 1.65
src/sys/kern/device_if.m 1.8
src/sys/kern/kern_fork.c 1.186
src/sys/pccard/pccard.c 1.156
The kernel config file that I'm using can be found at:
http://siliconlandmark.com/staff/andre/files/OMIKRON
If there's anything else that could be helpful, please don't hesitate to
ask! :-)
Thanks again,
> Andre Guibert de Bruet | Enterprise Software Consultant >
> Silicon Landmark, LLC. | http://siliconlandmark.com/>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Double fault with IBM microdrives and CompactFlash (LONG)
Hi, I just tried using my FreeBSD laptop to unload pictures off of a 340MB IBM microdrive (Model: DMDM-10340, P/N: 22L0046) using the IBM PC Card adapter (P/N: 31L9315). The laptop in question is a stock Dell Latitude C800 with a 1Ghz P3, 512MB of RAM and a 20GB ATA66 drive. I got a double "page fault in kernel mode" message shortly after inserting the drive. I rebooted then tried using the same adapter with a 128MB Viking CompactFlash card, and I got the same problem. Now, I've used this adapter under Windows XP, and it works, so it's not defective. I use the same cardbus slots for my wi0 interface (PRISM II-based), so I know both slots work. I recvsup'ed to make sure that I have all the latest committed fixes. Here's what uname says: FreeBSD 5.0-CURRENT #0: Sat Mar 1 11:04:18 EST 2003 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/OMIKRON The following messages print out when the double faults occur. I didn't have a serial console hooked up at the time, so I copied what was on the screen as best I could... :-) pccard1: Allocation failed for cfe 0 ata2 at port 0x100-0x10f irq 10 function 0 config 1 on pccard1 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0x0 stack pointer = 0x10:0xd68d0b74 frame pointer = 0x10:0xd68d0bb0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 9 (cbb1) kernel: type 12 trap, code=0 Stopped at 0: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0388d20 stack pointer = 0x10:0xd68d0978 frame pointer = 0x10:0xd68d097c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 9 (cbb1) kernel: type 12 trap, code=0 db> tr Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0388d20 stack pointer = 0x10:0xd68d0860 frame pointer = 0x10:0xd68d0864 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 9 (cbb1) kernel: type12 trap, code=0 db> show registers cs 0x8 ds 0xc1560010 es 0xc0140010 an_attach+0x450 fs 0xd68d0018 ss 0x10 eax0xc156332c ecx0xc048b8b8 edx0xc156332c ebx 0x10 esp0xd68d0b74 ebp0xd68d0bb0 esi 0x80 edi0xc1508200 eip 0 efl 0x10246 dr0 0 dr1 0 dr2 0 dr3 0 dr40x0ff0 dr5 0x400 dr60x0ff0 dr7 0x400 0: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:c0388d20 stack pointer = 0x10:0xd68d0878 frame pointer = 0x10:0xd68d087c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1 def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 9 (cbb1) kernel: type 12 trap code=0 db>call sync 0 db> If I do not remove the card, doing a "call sync" never finishes. It appears as if this problem is 100% reproducible. Any ideas? Thanks, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
On Thu, 27 Feb 2003, Nuno Teixeira wrote: > On Wed, Feb 26, 2003 at 06:51:55PM -0800, Rhett Monteg Hollander wrote: > > I understand it. Anyway, there is known problems by using -mmmx or > -m3dnow on builworld/buildkernel? Well, I used allways march=pentiumpro > on stable and now pentium2 on current without any problem. I've been using -march=athlon-xp -O2 -mmmx -m3dnow and -msse on my desktop for close to a month without any noticeable quirks. I rebuild world twice daily and kernel every other day... > I use some applications like grip, lame, mplayer, etc. Maybe I get some > extra performance running this apps. With -mmmx, -m3dnow or -msse, you're going to get a noticeable improvement, especially with lame and mplayer. I recommend compiling programs that use sound or graphics with high optimization cflags and keeping moderately conservative options for the base system and kernel. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -O2 considered harmful
On Wed, 26 Feb 2003, Nuno Teixeira wrote: > Does -march=k6-2 implies -m3dnow? Or -march=pentiumpro implies -mmmx? > > I always thought that when I use -march it will enable other > porcessor specific optimizations like mmx and 3dnow (if available). IIRC, 166 and 180 Mhz PPros don't support MMX. I'm seeing differences in compiled code between simple -march=athlon-xp and -march=athlon-xp -mmmx -m3dnow -msse. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X server stops working after recent 5.0-RELEASE -> 5.0-CURRENTupgrade
On Wed, 26 Feb 2003, Daniel Eischen wrote: > On Wed, 26 Feb 2003, Paul Mather wrote: > > Yesterday evening I upgraded a Gateway 450 laptop from 5.0-RELEASE-p3 > > to 5.0-CURRENT. Unfortunately, as a byproduct of that upgrade, > > I can no longer start X. Instead, it now aborts with Signal 10. :-( > > [...] > > > Has anyone else experienced problems with X ceasing to work after a > > 5.0-RELEASE -> 5.0-CURRENT upgrade?? I did not change X at all during > > the upgrade. All I did was rebuilt world and kernel, as per > > /usr/src/UPDATING. After discovering X no longer worked, I rebuilt my > > X server and X libraries ports via portupgrade -f, but still have the > > same problem. > > I posted the same exact problem on this list last week (see "What > broke X between 5.0R and recent current?" as subject line). > > I got two suggestions. One was to upgrade to the latest > version of XFree86, and the other was to add an explicit > mode line for the screen size to your XF86Config file. > Unfortunately, I didn't get the latter suggestion until > I had went through the pain and effort of getting the > latest version of XFree86 (right from the CVS repo, the > last 4.3 release candidate did _not_ work) and rebuilding > it and KDE. > > The good news is that it works with XFree86 from their CVS > repo. I didn't use a port to build it, I just cvsup'd > their tree and did a 'make World' and it just worked. First off, I have no idea what might have caused X to break on your systems. I guess I'm lucky to have not run into such problems... Would you mind doing a binary search (using date tags) to determine which commit caused the breakage between 5.0-R and the date when you first started having problems? Once it has been identified, a fix can be cooked up. Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SSH (TCP?) lag
On Sun, 23 Feb 2003, Giorgos Keramidas wrote: > On 2003-02-22 20:05, Andre Guibert de Bruet <[EMAIL PROTECTED]> wrote: > > > I noticed the same thing... then > > > > > > try sysctl net.inet.tcp.delayed_ack=0 > > > > > > fixed the issue > > > > That worked. Shouldn't this sysctl be turned off by default? > > Nah. Not really. Delaying acks can save quite a lot of of bandwidth > for bulk data transfers. Having read up on the issue, I can understand the reasoning for wanting delayed_ack on by default. >From tuning(7): With delayed acks turned off, the acknowledgement may be sent in its own packet, before the remote service has a chance to echo the data it just received. This same concept also applies to any interactive protocol (e.g. SMTP, WWW, POP3), and can cut the number of tiny packets flowing across the network in half. The FreeBSD delayed ACK implementation also follows the TCP protocol rule that at least every other packet be acknowledged even if the standard 100ms timeout has not yet passed. Normally the worst a delayed ACK can do is slightly delay the teardown of a connection, or slightly delay the ramp-up of a slow- start TCP connection. I find myself waiting up to two seconds for data to flush to the terminal on a 28 line 'ls -l'. net.inet.tcp.delayed_ack doesn't appear to cause this behavior on 4.7-stable. Did we inadvertently break the 100ms clause with the latest TCP patches? Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SSH (TCP?) lag
On Sat, 22 Feb 2003, Erik Greenwald wrote: > On Sat, Feb 22, 2003 at 10:28:02AM -0500, Andre Guibert de Bruet wrote: > > > > I'm experiencing some rather severe lag during ssh sessions, while running > > GENERIC on -current (cvsupped as of 5 minutes ago). This symptom first > > started occuring a couple of days ago with the merging of some TCP > > patches. > > > > I noticed the same thing... then > > try sysctl net.inet.tcp.delayed_ack=0 > > fixed the issue That worked. Shouldn't this sysctl be turned off by default? > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SSH (TCP?) lag
On Sat, 22 Feb 2003, Andre Guibert de Bruet wrote: > I'm experiencing some rather severe lag during ssh sessions, while running > GENERIC on -current (cvsupped as of 5 minutes ago). This symptom first > started occuring a couple of days ago with the merging of some TCP > patches. > > I've checked all of the obvious causes. I've even gone as far as > rebuilding the client system with 5.0-R and upgrading from there. > > Doing an ls -l in a directory with lots of files over ssh lists files in > chunks. I noticed that pressing a key on the keyboard makes more text > appear. > > Hardware is: > Server: Dual Athlon 2000+ MP w/1GB DDR, gigabit nge nic. FreeBSD 4.7. > Client: Athlon 1900+ XP w/1GB DDR, 100mbit dc0 nic. FreeBSD -current. > Network is switched 100mbit fastether. > > I've tried this (reproduceably) with the following software configuration: > 1. Server and client running sshd2/ssh2 from ports/security/ssh2. > 2. Server running sshd2 from ports. Client running openssh. > > This setup has been working great for well over a year; Has anyone else > recently started having problems? Hello again, I just noticed something else that could relate to this issue. I just tried to install apache2 from ports and the machine locked up while running configure at the following line: checking if TCP_NODELAY setting is inherited from listening sockets... Regards, > Andre Guibert de Bruet | Enterprise Software Consultant > > Silicon Landmark, LLC. | http://siliconlandmark.com/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
