Re: EV1 Servers makes me sick
On Wed, 2006-10-04 at 12:58 -0700, Colin Percival wrote: In the 20 months for which layeredtech has been providing free hosting for FreeBSD Update, one of the two Portsnap mirrors, and my personal website, I haven't had any complaints. Yes, GREAT service! I've had the possibility to test it from different carrier here from Italy and it has always worked great. -- Massimo.run(); ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fetchmail - sendmail problem
Julian Stacey wrote: PS I guess you'r using fetchmail built into/ called from sendmail: that's why a timeout can occur. I do it a different way: fetchmail called from crontab, localy delivers to me on gate host, gate invokes another mail via ~/.forward to my internal network; More processing, but no DNS hang. Slightly OT, but any reason you don't run fetchmail as a daemon (just currious)? -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgpt1rfLpbANX.pgp Description: PGP signature
Re: fetchmail - sendmail problem
Slightly OT, but any reason you don't run fetchmail as a daemon (just currious)? Reason was smaller building blocks to rearrange/ debug during construction/ breakage. Now merely a case of it works others things to do. `When I get round to it (TM ie ages ;-) I'll go D-DNS SMTP whole way omit fetchmail (except when travelling). -- Julian Stacey. BSD Unix C Net Consultancy, Munich/Muenchen http://berklix.com Mail Ascii, not HTML. Ihr Rauch = mein allergischer Kopfschmerz. Don't buy it ! Get it free ! http://berklix.org/free-software ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ffs snapshot lockup
On Wed, Oct 04, 2006 at 05:16:53PM -0400, Vivek Khera wrote: On Oct 3, 2006, at 4:43 AM, Kostik Belousov wrote: Details are posted at http://vivek.khera.org/scratch/crashlogs/ I have the crashdumps available to a kernel hacker upon request (i'd rather not make them generally available to the public...) It seems that you have snapshotted fs exported by nfsd ? At least, 18a is definitely the case. I have the patch (for current) that shall fix the issue. In fact, you need two patches: As per advice of Kris Kenneway, I turned off the software watchdog to rule out that as my problem. Then I ran a level 3 dump. Dump of root fs went fine, then it proceeded to do /usr. After a few minutes it locked up. Typescript 20 at the above URL shows the debugging info from the break into debugger of the locked up system. Since /usr was locked, nobody could log in at all. The network load was minimal at the time. I had everyone log out and close mail etc. What were the symptoms of locked system ? Could you log in on console, or do something at the shell prompt on console ? Also, did the system respond to the pings ? Fs-related deadlocks (as well as stalled disk io) usually do not prevent lowest levels of the isr/network stack from working. Again, I do not see the fs deadlock per se in the supplied script. Dump does disk io, it seems that nfsd tries to serve some request. Sshd looks to be ready to accept connections. If console is available, but ping responses not arrive, this is definitely network card problem. pgpzVHIESJM7W.pgp Description: PGP signature
FreeBSD 6.1 and maildrop compiling error
Please verify do u have installed Perl? Regards Umar Iftikhar Network Administrator Virtual University of Pakistan, Lahore. Phone # 042-9203114-7 Ext. 251 UAN # 042-111-880-880 http://www.vu.edu.pk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
On Thu, 5 Oct 2006, Eugene Grosbein wrote: On Wed, Oct 04, 2006 at 12:36:22PM -0400, Kris Kennaway wrote: When this kind of thing happens you just need to periodically make a bit of noise to make sure it doesn't get forgotten. In particular you should mention the problem to re@ so they can investigate and track it. Do I need to bother re@ with non-working fdc(4) in 6.2-PRERELEASE? http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/103841 In short: dual boot computer, floppy drive works in Windows, does not work at all in 6.2-PRE. Could you try booting a 6.1 or 6.0 CD and see if this is a regression from previous FreeBSD versions? Often, floppy disk problems are a symptom of an ACPI/BIOS problem, FYI, so you might want to check if there's a BIOS update from your system/motherboard vendor. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 945GM graphics and mplayer
On Wed, 2006-10-04 at 09:41 +0800, Ganbold wrote: Marcus Alves Grando wrote: Eric Anholt wrote: On Mon, 2006-10-02 at 13:25 +0800, Ganbold wrote: Hi, I have strange problem with my Dell Latitude D620 laptop which has 945GM chipset and onboard graphic card. I'm using September 30th RELENG_6. If I use acpi_video only, mplayer can only use sdl video output for full screen playing. If I use [EMAIL PROTECTED]'s i945 graphics support patch without using acpi_video, mplayer can use other video outputs for full screen playing but my mouse works in strange way, mouse pointer doesn't move, or moves very very slowly. I can see mouse goes over gnome applets (highlights) but I don't see pointer itself is moving. If I use mnag's patch and acpi_video together mplayer can use only sdl for full screen playing. OK, I think in reading your email, I'll substitute having acpi_video with not having AGP loaded. If you have acpi_video on RELENG_6, that prevents your AGP from loading afaik. So, if you have AGP loaded, you get a broken cursor, but playing XV works fine? Could you try the patch at http://people.freebsd.org/~anholt/agp-i945-4.diff instead? There were RELENG_6: http://marcus.grupos.com.br:8080/patch/agp_i810.c.patch I thought I was posting the link to the RELENG_6 patch, but I posted the -current one. Oops. Use mnag@'s patch. -- Eric Anholt [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
FreeBSD 6.2-BETA2 Available
The second of the BETAs for the FreeBSD 6.2 release cycle is now available. There have been quite a few things fixed since BETA1 but a few of the bigger problems are still being worked on so there will definitely be a BETA3. We appreciate your continued testing and reports of problems. MD5s/SHA256s: MD5 (6.2-BETA2-alpha-bootonly.iso) = fbf94e72f3486738f7f1d4f014d0e37e MD5 (6.2-BETA2-alpha-disc1.iso) = 02cc818bdcea9f0997e013c7c2e9a7d6 MD5 (6.2-BETA2-amd64-bootonly.iso) = 5111a255383d8e758848371192c8a23f MD5 (6.2-BETA2-amd64-disc1.iso) = 9e1c0a0164ffd4dd67a8cf53604e17f7 MD5 (6.2-BETA2-amd64-disc2.iso) = b98f1a57797006bd95eeeba4c3e5488f MD5 (6.2-BETA2-i386-bootonly.iso) = 680ce5f25ae800067ba779c78a232191 MD5 (6.2-BETA2-i386-disc1.iso) = 74d629fc0d9230903b3d0688f530f203 MD5 (6.2-BETA2-i386-disc2.iso) = 1aefcc677a4d5b41d050c72d3e2436ac MD5 (6.2-BETA2-ia64-bootonly.iso) = 02d426b52f51a343ea4c24d6b8dc6626 MD5 (6.2-BETA2-ia64-disc1.iso) = db57c4b01d64d658540bb920f822aaad MD5 (6.2-BETA2-ia64-livefs.iso) = 51b284e9bbdeac0019e96e2c76a2a3e8 MD5 (6.2-BETA2-pc98-bootonly.iso) = 030337716f413a2e940a3d109c1ba878 MD5 (6.2-BETA2-pc98-disc1.iso) = 10bd9fd5e6361aa017c89f0f64ae07c9 MD5 (6.2-BETA2-sparc64-bootonly.iso) = dc80bc5ac4531a6653e40904362d64ff MD5 (6.2-BETA2-sparc64-disc1.iso) = b48ebb5c107f7cb76309cdc61ecceeb0 MD5 (6.2-BETA2-sparc64-disc2.iso) = cdc071bd0d192255a03aa866618d1eeb SHA256 (6.2-BETA2-amd64-bootonly.iso) = efdd4c55e09d655305c4d8e03acbb2e2c0f9bf40ed749d85c82a97c44ec571d5 SHA256 (6.2-BETA2-amd64-disc1.iso) = 0f1fa925a683bd4aeec01246acbe884164c4c418a3e21fd040962d4477e955a6 SHA256 (6.2-BETA2-amd64-disc2.iso) = 36bd86f6a65617b8ad98cee3329412fc4a3e84fb8cae6117cc7ce28b6ece5f71 SHA256 (6.2-BETA2-i386-bootonly.iso) = a5cd8ea997c65d5b0ab70599a3226bdf53e48a764bf69953d2b321517a6062a3 SHA256 (6.2-BETA2-i386-disc1.iso) = 8301c747fa9a3cac9d162d8175932df55d9563349c33e9cb972e70017dcb3608 SHA256 (6.2-BETA2-i386-disc2.iso) = 58897f6f784eb45be8bccee0e94f71d4cfcffd30dc60c8bced082181073b4397 SHA256 (6.2-BETA2-ia64-bootonly.iso) = a36049addd30c97c9580dd10eab8d9751821b4bcb613af2c4fb226f617ce2989 SHA256 (6.2-BETA2-ia64-disc1.iso) = 1e87276c6ea23a8e9b794c1e40c208ab68e6c482c9a8e02ffa6417c8adfd25c5 SHA256 (6.2-BETA2-ia64-livefs.iso) = ccaa623a8ae4291d4c321bafe60a348adcc44a29ae58ca14a5f917cec4a0434b SHA256 (6.2-BETA2-pc98-bootonly.iso) = c9ba1b662a7861d24d54460fddc39962c97334a3cfa75de3a54bf49cf54cc569 SHA256 (6.2-BETA2-pc98-disc1.iso) = 3d732d4f2ee69450f4661cdaf3f42e5fecd064d9e6d75619e4e2a3285369ff45 SHA256 (6.2-BETA2-sparc64-bootonly.iso) = bfc22d9e200bb1838de1248b7b234592eee3baa689827e96db2e97b664335955 SHA256 (6.2-BETA2-sparc64-disc1.iso) = bccc7f4c5e4426d2f9bd78414e6f13138d2d60ae807e20bce2e2e95fb49490b0 SHA256 (6.2-BETA2-sparc64-disc2.iso) = eff5fd6e76e5070e7f3287fe9d5bd5c6b7bfaa4c877deb7667b355eeef020037 -- Ken Smith - From there to here, from here to | [EMAIL PROTECTED] there, funny things are everywhere. | - Theodore Geisel | signature.asc Description: This is a digitally signed message part
Is jemalloc going to make its way into RELENG_6?
Judging from my tests (allocating numerous small objects, then freeing the memory) it looks like the bottleneck is in free(). I've built a different libc library with the malloc.c and tree.h taken from HEAD and it now behaves nicely. I haven't seen any bad side effects on this machine (it's the lappie I do most of my work on, I run KDE, seamonkey, mplayer, openoffice, the like) since I switched to the new libc. Another nice solution would be to ship the modified libc in base so the people who really need jemalloc can relink to it via libmap.conf. -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
On Thu, Oct 05, 2006 at 10:30:09AM +0100, Robert Watson wrote: When this kind of thing happens you just need to periodically make a bit of noise to make sure it doesn't get forgotten. In particular you should mention the problem to re@ so they can investigate and track it. Do I need to bother re@ with non-working fdc(4) in 6.2-PRERELEASE? http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/103841 In short: dual boot computer, floppy drive works in Windows, does not work at all in 6.2-PRE. Could you try booting a 6.1 or 6.0 CD and see if this is a regression from previous FreeBSD versions? Often, floppy disk problems are a symptom of an ACPI/BIOS problem, FYI, so you might want to check if there's a BIOS update from your system/motherboard vendor. I run latest BIOS afaik. It's definetely a regression from 4.11-STABLE that runs fine on this system with ACPI fully enabled (see also followup to the PR that I made today for more details). I have up-to-date mirror of FreeBSD Repo here so can build 6.1 or 6.0 kernel to test, and I will. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Start system with 'downed' carp interfaces
Hello, I'm looking for a generic way to create and configure carp interfaces upon boot (so daemons can bind against the IP address), but keep the carp interfaces 'down'. This is to allow the administrator to first check every service after the failure, and if deemed ready, put the system back into production by simply issuing: ifconfig carp0 up But there are several problems: ifconfig_carp0=foo bar will always up the interface first via /etc/rc.d/netif ifconfig carp0 foo bar down will ignore the 'down' and up the interface. This is especially announing. I wish ifconfig would honour the down statement, even though the manpage says the interface will always be brought up when assigned its first address. Using a start_if.carp0 with the following contents ifconfig carp0 vhid 1 1.2.3.4/24 ifconfig carp0 down and ifconfig_carp0=down in rc.conf will result in an 'up' interface. I also disabled devd, as it seems to be running pccard_ether carp0 start as a result of the interface creation. Although it is started sometime after the interface has been created. How are other people handling the startup of carp interfaces? Uli ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
On Thu, 5 Oct 2006, Eugene Grosbein wrote: On Thu, Oct 05, 2006 at 10:30:09AM +0100, Robert Watson wrote: When this kind of thing happens you just need to periodically make a bit of noise to make sure it doesn't get forgotten. In particular you should mention the problem to re@ so they can investigate and track it. Do I need to bother re@ with non-working fdc(4) in 6.2-PRERELEASE? http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/103841 In short: dual boot computer, floppy drive works in Windows, does not work at all in 6.2-PRE. Could you try booting a 6.1 or 6.0 CD and see if this is a regression from previous FreeBSD versions? Often, floppy disk problems are a symptom of an ACPI/BIOS problem, FYI, so you might want to check if there's a BIOS update from your system/motherboard vendor. I run latest BIOS afaik. It's definetely a regression from 4.11-STABLE that runs fine on this system with ACPI fully enabled (see also followup to the PR that I made today for more details). I have up-to-date mirror of FreeBSD Repo here so can build 6.1 or 6.0 kernel to test, and I will. 4.x doesn't use ACPI for device resource allocation (etc), I believe, so while ACPI may be enabled in the BIOS, it's not being used by FreeBSD. The limited ACPI support in FreeBSD 4.x is for power management. It would be interesting to know how 4.x probes the hardware vs. how it apperas in the 6.x dmesg. Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CALL FOR TESTERS! [Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2]
Scott Long ([EMAIL PROTECTED]) on 04/10/2006 at 14:49 wrote: #*default release=cvs tag=RELENG_6 date=2006.08.08.09.12.56 # OK # #*default release=cvs tag=RELENG_6 date=2006.08.08.09.21.00 # BROKEN ... #*default release=cvs tag=RELENG_6 # BROKEN From sys commitlogs the culprit commits are: glebius 2006-08-08 09:19:25 utc glebius 2006-08-08 09:20:26 utc So you tested before these two changes and after these two changes, yes? Yes that's it. What about with just the first change and not the second? Anyways, I'm Because building a kernel that only has the first change (2006-08-08 09:19:25) fails. Can you try a quick test? Reboot and press '6' at the FreeBSD loader menu. That will drop you to a prompt. Then enter the following line: set hint.apic.0.disabled=1 Done: synced to STABLE-6 of this morning (9:00 UTC)i, made world and kernel and boot with APIC disabled. Still same freeze after starting X and loading a few tabs in Firefox. Thanks for the suggestion Scott. -- bug ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: western digital mybook (external usb drive, 250gb) takes 15 minutes to be recognized
hi roland, i formatted the disk and created a single bsd slice, but no luck. it's interesting to hear that the mybook 500gb version works fine, as well as freebsd releng6 from sep.19. i'm going to hook mine up someplace else on the network, so i'm not going to compile a new kernel with the CAMDEBUG option. thanks again for you suggestions and help! brian On 10/1/06, Roland Smith [EMAIL PROTECTED] wrote: On Sun, Oct 01, 2006 at 12:32:06AM +0200, Brian King wrote: I've got an external harddrive with a WD disk. It works without problems; snip interesting. perhaps it's something specific to the MyBook. i'm guessing that you don't have a MyBook? Correct. no other messages related to the drive are displayed on the console during these 15 minutes. once the da0 device is recognized, i can mount the partitions (i've got it split into two roughly equal-sized primary partitions, one ext2fs and one msdos), e.g.: mount -t ext2fs /dev/da0s1/mnt/backup Maybe the driver is looking for FreeBSD slices? Do you see any disk activity during this 15 minute period? no, i haven't noticed any. in fact, after about 10 minutes the disk spins down because there's been no activity. Then I guess it's time for some kernel debugging. ;-) snip ... and then the long pause before it attaches to da0 (nothing more is displayed at time of attachment) camcontrol devlist gives this right after plugging in the drive: WD 2500JB External 0107 at scbus0 target 0 lun 0 (probe0) and after it finally attaches to da0 camcontrol devlist gives: WD 2500JB External 0107 at scbus0 target 0 lun 0 (pass0,da0) so it seems that the probe phase is what is taking so long. Could be. But it could also be the creation of the appropriate devices. So it might be CAM, devfs or a combination of the two. is there any way to specify what action to take when this specific drive is attached, instead of having the system probe it? Sorry, I don't know. i also tried running devd verbosely in the foreground (/sbin/devd -d -D). here is the output when the drive is attached: snip ... and then the long pause before it attaches to da0 (nothing more is displayed at time of attachment) That more or less rules out devd, I'd say. this MyBook doesn't have any delay when connecting on linux (ubuntu 6.06) or on windows xp on this computer. any ideas? i'm stumped at this point... Could you test if it makes a difference if there are BSD slices on it? Otherwisw check the partition table with fdisk to see if the partition table is OK. According to §7.3 of The design and implementation of the FreeBSD operating system attach operations for da devices are handled in the CAM peripheral layer, one ot the three layers in the CAM subsystem. It might be usefull to build a kernel with the CAM driver built-in complete with the CAMDEBUG option, see cam(4). You can then use camcontrol(8) to enable debugging options, e.g. CAM_DEBUG_CDB. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ffs snapshot lockup
On Oct 5, 2006, at 4:30 AM, Kostik Belousov wrote: The network load was minimal at the time. I had everyone log out and close mail etc. What were the symptoms of locked system ? Could you log in on console, or do something at the shell prompt on console ? Console was non-responsive. This time dump locked doing /usr so pretty much anything you try to run will block. When the lockup happens when dump is running on my home dir (/u/yertle1) partition, as long as you don't need that partition you can log in and run any programs you like. I have a service account whose home dir is in / var and was able to login that time to that account. No such luck this time since any activity pretty much uses /usr. Ping was responding (our monitoring didn't complain it was down). The only thing I could do was break to debugger on the console.
Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
On Thu, Oct 05, 2006 at 01:09:27PM +0100, Robert Watson wrote: It's definetely a regression from 4.11-STABLE that runs fine on this system with ACPI fully enabled Hmm, I was wrong about 4.11 using ACPI - it does not use it here really, it uses good old APM. It would be interesting to know how 4.x probes the hardware vs. how it apperas in the 6.x dmesg. 4.11-STABLE: fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 6.2-PRERELEASE: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Start system with 'downed' carp interfaces
On Thursday 05 October 2006 13:58, Ulrich Spoerlein wrote: Hello, I'm looking for a generic way to create and configure carp interfaces upon boot (so daemons can bind against the IP address), but keep the carp interfaces 'down'. This is to allow the administrator to first check every service after the failure, and if deemed ready, put the system back into production by simply issuing: ifconfig carp0 up Can't you just use a high value for advskew so it won't become MASTER unless all other hosts are dead as well. But there are several problems: ifconfig_carp0=foo bar will always up the interface first via /etc/rc.d/netif ifconfig carp0 foo bar down will ignore the 'down' and up the interface. This is especially announing. I wish ifconfig would honour the down statement, even though the manpage says the interface will always be brought up when assigned its first address. Using a start_if.carp0 with the following contents ifconfig carp0 vhid 1 1.2.3.4/24 ifconfig carp0 down and ifconfig_carp0=down in rc.conf will result in an 'up' interface. I also disabled devd, as it seems to be running pccard_ether carp0 start as a result of the interface creation. Although it is started sometime after the interface has been created. How are other people handling the startup of carp interfaces? -- /\ Best regards, | [EMAIL PROTECTED] \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | [EMAIL PROTECTED] / \ ASCII Ribbon Campaign | Against HTML Mail and News pgp7J1juukBMM.pgp Description: PGP signature
Re: NFS client slow on amd64 6.2-PRERELEASE #2
Heinrich Rebehn wrote: Hi list, despite recent improvements with the nfs code, client performance still seems to be a problem. I am getting 2 MB/sec where i would expect at least 10 MB/sec. My Setup: Machine | ANTSRV1| ANTSRV2 == Board| Tyan 2882-D| ASUS A7V8X-X CPU | Opteron 246| Athlon XP1800+ Mem | 2G | 1G NIC | Broadcom BCM5704C | Intel PRO/1000MT OS:6.2-PRERELEASE #2 as of 01-OCT-2006 64Bit OS on ANTSRV1, 32Bit on ANTSRV2 The 2 machines are connected via a 1GB switch Trying UDP first [EMAIL PROTECTED] [/tmp] # mount_nfs -U -L antsrv2:/export/disk2 /mnt [EMAIL PROTECTED] [/tmp] # rm /mnt/x/* [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 4.967248 secs (2110980 bytes/sec) real0m5.253s user0m0.005s sys 0m0.022s [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 69.020366 secs (1519227 bytes/sec) real1m9.276s user0m0.028s sys 0m0.211s == Now TCP == [EMAIL PROTECTED] [/tmp] # umount /mnt [EMAIL PROTECTED] [/tmp] # mount_nfs -T -L antsrv2:/export/disk2 /mnt [EMAIL PROTECTED] [/tmp] # rm /mnt/x/* [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 5.289492 secs (1982376 bytes/sec) real0m5.312s user0m0.001s sys 0m0.023s [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 58.715595 secs (1785856 bytes/sec) real0m58.740s user0m0.000s sys 0m0.204s === SCP === [EMAIL PROTECTED] [/tmp] # scp 100MB.dat antsrv2:/tmp/x Password: 100MB.dat100% 100MB 11.1MB/s 00:09 === Iperf === [EMAIL PROTECTED] [~] # iperf -c antsrv2 Client connecting to antsrv2, TCP port 5001 TCP window size: 32.5 KByte (default) [ 3] local 134.102.176.16 port 59123 connected with 134.102.176.17 port 5001 [ 3] 0.0-10.0 sec743 MBytes623 Mbits/sec NFS from a Linux machine (Kernel 2.6.17.8) (connected via 10Mb LAN) yields a constant value of ~10MB/sec (TCP and UDP), so the FreeBSD NFS server seems to be ok. = Reversing the setup = [EMAIL PROTECTED] [~] # mount_nfs -L -U antsrv1:/export/huge/x /mnt [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 0.533470 secs (19655758 bytes/sec) real0m0.547s user0m0.001s sys 0m0.085s [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 7.647475 secs (13711401 bytes/sec) real0m7.673s user0m0.000s sys 0m0.920s [EMAIL PROTECTED] [~] # umount /mnt [EMAIL PROTECTED] [~] # mount_nfs -L -T antsrv1:/export/huge/x /mnt [EMAIL PROTECTED] [~] # rm /mnt/* [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 0.524917 secs (19976030 bytes/sec) real0m0.557s user0m0.000s sys 0m0.085s [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 5.723110 secs (18321787 bytes/sec) real0m5.756s user0m0.000s sys 0m0.704s This yields much better results. Could this be a 64bit-specific problem? Both machines have statd and lockd running. Any ideas where i could tune? Hmm, no one? Is 2MB/s on a Gbit link all i can expect on FreeBSD? --Heinrich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Recommendations for a serial port card you can actually BUY?
Hi folks; Ok, one of my pet peeves is coming around to bite me again. I filed [kern/103137: Rocketport driver is broken in 6.x] a few weeks ago after fruitlessly trying to get the Comtrol Rocketport driver to actually behave under 6.x. Its fine under 5.x, but under 6.x it fails badly, either radically delaying input characters or in some cases sending multiple copies upstream to the application (!) The misbehavior is grossly increased by doing such horiffic things as using select(2) and poll(2) on an I/O stream associated with a port. My original posting here drew an unofficial patch that did not improve things at all. Barf. Ok, so that card is no longer supported (even though it is listed as supported! I've heard nothing about the listing of it being supported being removed from the hardware list, and according to the web version, it still there! Supported it ain't when it doesn't work at all!) So what do I buy to replace this thing? Well, looking at the serial hardware claimed supported, I seem to have a problem finding anything I can actually purchase! I don't need real high performance - a 16550 based multiport card is fine. I also don't want a $1500 solution - this isn't a $1500 problem. $500 seems reasonable. The Rocketport 550 looked promising, as its just a bunch of 16550s on the PCI bus, and so should work. Guess what? Comtrol EOL'd the entire 550 line several months ago. They are now unobtanium, and their replacements are all smart cards - which gets me right back where I started! I can't find any evidence that any of the other 4 or 8-port versions claimed to work under the puc() driver are actually in production either - I've been unable to find any of THOSE for sale online or otherwise. I have several Digiboards, and the Digi driver worked last time I looked at it (back in the 5.x days), but they're ISA. Useless in today's machines which are increasingly ISA-slot devoid (including all of my present line of servers!) So. I have an application that requires six serial ports, and would like ten. 5.x FreeBSD versions are being EOL'd per the announcement, forcing me to move to 6.x. The Comtrol driver for the Smart Rocketport boards is broken in 6.x, and the PR appears to be one that will sit and rot. What options do I have in the FreeBSD universe here guys? This is a real no-BS production application that has hundreds of deployed instances, and it is in no way obsolete or something I intend to stop supporting. I know serial I/O is passe for many, but some of us have applications that actually require it, and can't rationally be moved to anything else due to external hardware considerations. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS client slow on amd64 6.2-PRERELEASE #2
Heinrich Rebehn wrote: Hi list, despite recent improvements with the nfs code, client performance still seems to be a problem. I am getting 2 MB/sec where i would expect at least 10 MB/sec. My Setup: Machine | ANTSRV1| ANTSRV2 == Board| Tyan 2882-D| ASUS A7V8X-X CPU | Opteron 246| Athlon XP1800+ Mem | 2G | 1G NIC | Broadcom BCM5704C | Intel PRO/1000MT OS:6.2-PRERELEASE #2 as of 01-OCT-2006 64Bit OS on ANTSRV1, 32Bit on ANTSRV2 The 2 machines are connected via a 1GB switch Trying UDP first [EMAIL PROTECTED] [/tmp] # mount_nfs -U -L antsrv2:/export/disk2 /mnt [EMAIL PROTECTED] [/tmp] # rm /mnt/x/* [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 4.967248 secs (2110980 bytes/sec) real0m5.253s user0m0.005s sys 0m0.022s [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 69.020366 secs (1519227 bytes/sec) real1m9.276s user0m0.028s sys 0m0.211s == Now TCP == [EMAIL PROTECTED] [/tmp] # umount /mnt [EMAIL PROTECTED] [/tmp] # mount_nfs -T -L antsrv2:/export/disk2 /mnt [EMAIL PROTECTED] [/tmp] # rm /mnt/x/* [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 5.289492 secs (1982376 bytes/sec) real0m5.312s user0m0.001s sys 0m0.023s [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 58.715595 secs (1785856 bytes/sec) real0m58.740s user0m0.000s sys 0m0.204s === SCP === [EMAIL PROTECTED] [/tmp] # scp 100MB.dat antsrv2:/tmp/x Password: 100MB.dat100% 100MB 11.1MB/s 00:09 === Iperf === [EMAIL PROTECTED] [~] # iperf -c antsrv2 Client connecting to antsrv2, TCP port 5001 TCP window size: 32.5 KByte (default) [ 3] local 134.102.176.16 port 59123 connected with 134.102.176.17 port 5001 [ 3] 0.0-10.0 sec743 MBytes623 Mbits/sec NFS from a Linux machine (Kernel 2.6.17.8) (connected via 10Mb LAN) yields a constant value of ~10MB/sec (TCP and UDP), so the FreeBSD NFS server seems to be ok. = Reversing the setup = [EMAIL PROTECTED] [~] # mount_nfs -L -U antsrv1:/export/huge/x /mnt [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 0.533470 secs (19655758 bytes/sec) real0m0.547s user0m0.001s sys 0m0.085s [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 7.647475 secs (13711401 bytes/sec) real0m7.673s user0m0.000s sys 0m0.920s [EMAIL PROTECTED] [~] # umount /mnt [EMAIL PROTECTED] [~] # mount_nfs -L -T antsrv1:/export/huge/x /mnt [EMAIL PROTECTED] [~] # rm /mnt/* [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/10MB.dat bs=1M count=10 10+0 records in 10+0 records out 10485760 bytes transferred in 0.524917 secs (19976030 bytes/sec) real0m0.557s user0m0.000s sys 0m0.085s [EMAIL PROTECTED] [~] # time dd if=/dev/zero of=/mnt/100MB.dat bs=1M count=100 100+0 records in 100+0 records out 104857600 bytes transferred in 5.723110 secs (18321787 bytes/sec) real0m5.756s user0m0.000s sys 0m0.704s This yields much better results. Could this be a 64bit-specific problem? Both machines have statd and lockd running. Any ideas where i could tune? Hmm, no one? Is 2MB/s on a Gbit link all i can expect on FreeBSD? --Heinrich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS client slow on amd64 6.2-PRERELEASE #2
On Thu, Oct 05, 2006 at 05:28:03PM +0200, Heinrich Rebehn wrote: [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/10MB.dat bs=1M count=10 10485760 bytes transferred in 4.967248 secs (2110980 bytes/sec) [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/100MB.dat bs=1M count=100 104857600 bytes transferred in 69.020366 secs (1519227 bytes/sec) [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/10MB.dat bs=1M count=10 10485760 bytes transferred in 5.289492 secs (1982376 bytes/sec) [EMAIL PROTECTED] [/tmp] # time dd if=/dev/zero of=/mnt/x/100MB.dat bs=1M count=100 104857600 bytes transferred in 58.715595 secs (1785856 bytes/sec) This isn't a valid test of performance, in my opinion. bs=1M is a bad idea. You shouldn't be using dd for this kind-of test at all. I should also note that bs=1M is not the same thing as obs=1M ibs=1M. dd's weird like that (someone can explain it, I'm sure -- I've seen it discussed in the pasT). scp is an acceptable real-life test (not the best, but it's legitimate), and you only did it from antsrv1 -- antsrv2, not the other direction. It's really too bad the OpenBSD guys refuse to incorporate the HP (high-performance) patches into OpenSSH, and being able to say -c none would *really* help when it comes to benchmarking network I/O via scp (in our case, we do dump over ssh across a segregated private LAN -- the encryption overhead slows our backups down to a crawl, and is worthless in our environment since as I said, segregated private LAN...) That said: I have seen cases where network peformance on BSD works fantastic uni-directionally -- for example, using FTP to get a file from a FreeBSD box on a 100mbit LAN results in a speed of about 300-400kbit/sec, while doing a put to the same box results in 90mbit/sec. The problem in that case turned out to be duplex-related. Both boxes were auto-negotiating with the Cisco switch correctly, and indeed the Cisco labelled them as auto-100/full, but as anyone who is familiar with Ciscos knows, auto-negotiation on Catalysts is far from reliable. Both boxes reported auto-neg and being at 100/full as well. I ended up hard-setting the boxes to use 100/full, and set the switch ports to 100/full, then rebooted both boxes (yes, this is sometimes required, as driver auto-neg code is a bit tweaky); voila, problem fixed. If you can connect these two boxes directly via a crossover cable, and you still see the problems, then yes, there's something definitely amiss that needs investigating. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 945GM graphics and mplayer
On Wed, 2006-10-04 at 10:05 +0800, Ganbold wrote: Eric Anholt wrote: On Mon, 2006-10-02 at 13:25 +0800, Ganbold wrote: Hi, I have strange problem with my Dell Latitude D620 laptop which has 945GM chipset and onboard graphic card. I'm using September 30th RELENG_6. If I use acpi_video only, mplayer can only use sdl video output for full screen playing. If I use [EMAIL PROTECTED]'s i945 graphics support patch without using acpi_video, mplayer can use other video outputs for full screen playing but my mouse works in strange way, mouse pointer doesn't move, or moves very very slowly. I can see mouse goes over gnome applets (highlights) but I don't see pointer itself is moving. If I use mnag's patch and acpi_video together mplayer can use only sdl for full screen playing. OK, I think in reading your email, I'll substitute having acpi_video with not having AGP loaded. If you have acpi_video on RELENG_6, that prevents your AGP from loading afaik. Oh, ok, I thought so. Some questions: Do I really need acpi_video? It gets you brightness controls for some panels. Can I use both AGP and acpi_video at the same time? Not on RELENG_6. Do I need to load i915 kernel module? No, X does that for you. It is strange though I see mouse pointer in center of the screen, but it doesn't move. As I recall it was working without moused when I first installed FreeBSD-6.1-RELEASE. I'm not quite sure, I did several updates to RELENG_6 and somewhere July it didn't work without moused loaded beforehand. Maybe it is ACPI related problem, but it is only my opinion. sysmouse always sits there, and if you have no mouse events fed from a moused (either automatically started by devd for USB mice, or started for others from rc.conf), you won't see any events on that simulated mouse. -- Eric Anholt [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Re: Is jemalloc going to make its way into RELENG_6?
In the last episode (Oct 05), Vlad GALU said: Judging from my tests (allocating numerous small objects, then freeing the memory) it looks like the bottleneck is in free(). I've built a different libc library with the malloc.c and tree.h taken from HEAD and it now behaves nicely. I haven't seen any bad side effects on this machine (it's the lappie I do most of my work on, I run KDE, seamonkey, mplayer, openoffice, the like) since I switched to the new libc. Another nice solution would be to ship the modified libc in base so the people who really need jemalloc can relink to it via libmap.conf. You can compile just the -current version of malloc.c as a shared object, then inject it into specific binaries: $ gcc -O -Wall -I/usr/src/lib/libc/include -shared -o /lib/jemalloc.so jemalloc.c $ MALLOC_OPTIONS=P date date in malloc(): warning: unknown char in MALLOC_OPTIONS Thu Oct 5 11:44:36 CDT 2006 $ LD_PRELOAD=/lib/jemalloc.so MALLOC_OPTIONS=P date | head Thu Oct 5 11:44:49 CDT 2006 ___ Begin malloc statistics ___ Number of CPUs: 2 Number of arenas: 11 Chunk size: 524288 (2^19) Quantum size: 16 (2^4) Max small size: 512 Pointer size: 4 Assertions enabled Allocated: 4096, space used: 1048576 I've tried this with seamonkey and mysqld, so this method seems to work fine on complex apps. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kern/103841: [fdc] fdc(4) does not work (regression)
On Thu, Oct 05, 2006 at 10:48:52PM +0800, Eugene Grosbein wrote: It's definetely a regression from 4.11-STABLE that runs fine on this system with ACPI fully enabled Hmm, I was wrong about 4.11 using ACPI - it does not use it here really, it uses good old APM. It would be interesting to know how 4.x probes the hardware vs. how it apperas in the 6.x dmesg. 4.11-STABLE: fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 6.2-PRERELEASE: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 I managed to know that fdc_initial_reset() in sys/dev/fdc/fdc.c probes my fdc controller as Enhanced floppy controller (ic_type==0x90) vs. 4.x's NEC close. BTW, does in possible to obtain fdc's probe result vs. fdc_acpi's result without addition of call to fdc_print_child(device_get_parent(dev), dev); to fdc_initial_reset()? I've forced sys/dev/fdc/fdc.c to probe my controller as NEC clone by moving case 0x90: upwards to case 0x80 in this function but that does not help, no change in behavour was observed. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
On Thu, Oct 05, 2006 at 10:48:52PM +0800 I heard the voice of Eugene Grosbein, and lo! it spake thus: 4.11-STABLE: fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ^^^ 6.2-PRERELEASE: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 ^^^ That's suspicious right there (doubly for the overlap)... -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
I would recommend staying with FreeBSD-5. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kern/103841: [fdc] fdc(4) does not work (regression)
I've tried 5.4-RELEASE and 6.0-RELEASE. 5.4-RELEASE works OK. 6.0-RELEASE does not work the same way as 6.2-PRE. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On Thu, Oct 05, 2006 at 10:19:25AM -0500, Karl Denninger wrote:
Hi folks;
Ok, one of my pet peeves is coming around to bite me again.
{snip}
I know serial I/O is passe for many, but some of us have applications that
actually require it, and can't rationally be moved to anything else due
to external hardware considerations.
This is in no way flame-bait, nor does it have any negative
implications -- as a fellow SA I'm just curious.
What exactly are you using serial cards for in this day and age?
A serial console server (a la Cyclades TS)? Or is there something
that's more mission-critical (for lack-of better term).
I guess my question is: what are you using these cards for, and
can whatever the goal is be accomplished by some alternate hardware
(serial-via-USB adaptors/hubs, serial-over-IP, etc.)?
BTW -- I completely agree with you about the cost of these cards,
especially so in 2006. There is absolutely no justified explanation
for such a card costing US$1500, or even US$500. These are ICs and
basic PCBs that at most cost US$20 per device -- the profit mark-up
is appalling.
--
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networkinghttp://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em, bge, network problems survey.
On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote: All, I'm seeing some patterns here with all of the network driver problem reports, but I need more information to help narrow it down further. I ask all of you who are having problems to take a minute to fill out this survey and return it to Kris Kennaway (on cc:) and myself. Thanks. 1. Are you experiencing network hangs and/or timeout messages on the console? If yes, please provide a _brief_ description of the problem. OK, next question, to all em users: If your em device is using a shared interrupt, and you are NOT experiencing timeout problems when using this device, please let me know: dalki# vmstat -i interrupt total rate irq4: sio0 2071 0 irq6: fdc010 0 irq14: ata0 47 0 irq20: ahd021755 4 irq23: em0124751 23 -- not a shared interrupt irq24: ahd1 15 0 cpu0: timer 10453509 1999 Total 10602158 2027 tyan# vmstat -i interrupt total rate irq14: ata0 58 0 irq16: em0 fxp1 332832851 -- shared interrupt irq18: fxp0 973 2 irq19: atapci1132883339 cpu0: timer 774308 1980 cpu1: timer 777136 1987 Total2018190 5161 So far all of the em problems I have seen involve shared interrupts, and conversely all em systems I have seen that do not have timeout problems are not shared. Kris pgprR0xTjBQxE.pgp Description: PGP signature
Re: kern/103841: [fdc] fdc(4) does not work (regression)
I've backported fdc(4) from CURRENT to RELENG_6 and it now works all right, it reads, it formats, it writes. Please perform MFC and then close this PR :-) Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On Thu, Oct 05, 2006 at 12:08:22PM -0700, Jeremy Chadwick wrote:
On Thu, Oct 05, 2006 at 10:19:25AM -0500, Karl Denninger wrote:
Hi folks;
Ok, one of my pet peeves is coming around to bite me again.
{snip}
I know serial I/O is passe for many, but some of us have applications that
actually require it, and can't rationally be moved to anything else due
to external hardware considerations.
This is in no way flame-bait, nor does it have any negative
implications -- as a fellow SA I'm just curious.
Fair enough.
What exactly are you using serial cards for in this day and age?
A serial console server (a la Cyclades TS)? Or is there something
that's more mission-critical (for lack-of better term).
I guess my question is: what are you using these cards for, and
can whatever the goal is be accomplished by some alternate hardware
(serial-via-USB adaptors/hubs, serial-over-IP, etc.)?
Two things:
1. Fax servers running traditional fax modems. There's a HUGE installed
base of fax modems that run on POTS lines and there's simply no
justification for moving to something like a channelized T1 system
for people who need a half-dozen ports (but not 20+!)
2. Embedded control systems. There is some hardware either is RS232 or,
for floor automation type stuff, is RS-422/485. The latter is easily
converted to using a little dongle, but it requires a 232 port on the
computer end and that port must actually work correctly.
Both of these applications are timing critical or they don't work at all.
Much of the latter hardware is still only available in a serial interface,
no matter the cost. It is not high-data-rate by any means (typically 4800
or 9600 bps) but it is what it is.
Serial over IP will not work for either. Serial-via-USB might, and I will
look into that, but I suspect I'm going to get in trouble with that one,
especially if I have to toggle control signals (e.g. DTR, etc) or support
hardware flow control (and for the fax servers, you DO need it if you expect
things to work correctly.)
FreeBSD's USB support has always been somewhat deficient. For example,
apcupsd can't talk to their UPSs over the USB bus, even though the software
itself knows how, because FreeBSD doesn't know what a UPS is and throws up
its hands when you plug it in. I wasn't aware that the USB to Serial
converters would work - I can try them, but there are a lot of those out
there that don't work right even under Windows - expecting them to under
FreeBSD might be asking too much.
The problem that is nailing me particularly hard right now is the second one
- I have embedded control systems that I speak to over a RS-232 interface
(the devices are actually '485 on a common bus but talked to via a 232/485
converter) and it simply does not work on 6.x using the Comtrol driver
at all. 100ms delays and the like are one thing - we're talking about
delays in characters reaching the application of one second or more, and in
some cases either characters or entire frames (e.g. a burst of characters)
are being repeated! When you're trying to manage a synchronous polling
protocol this sort of error makes the software on the other end throw up in
a really ugly way, since it looks like there's a fault in the equipment on
the other end or the wire has been compromised.
With FreeBSD 5.x being EOL'd this is now turning into a critical problem.
I can't in good conscience put packages out there that have been EOL'd nor
offer meaningful support on them. While 5.4 has been reasonably stable for
some time, that is now declared a dead release. 5.5 is similarly on that
road. The only right path forward is into the 6.x world, but I can't get
there from where I am now unless this problem can be resolved.
BTW -- I completely agree with you about the cost of these cards,
especially so in 2006. There is absolutely no justified explanation
for such a card costing US$1500, or even US$500. These are ICs and
basic PCBs that at most cost US$20 per device -- the profit mark-up
is appalling.
I don't mind the $500 cards (the $1500 ones are another matter!) I very much
mind that it appears I can't find a board on the market today that works!
For FreeBSD to not differentiate between hardware in their lists that is
actually deliverable today and that which is historical is problematic
when one tries to go shopping. If you look at the current serial hardware
list you will see a LOT of stuff that simply isn't made any more - and very
little that is.
I gave up on Specialix a number of years ago after similar problems showed
up in some of their drivers for a different OS and they were unwilling to
fix them. Digi has always been pretty solid, but they are passe' now and
while I have a nice stock of ISA interface cards, finding motherboards
with ISA slots is rapidly becoming impossible.
Among the PCI cards only Comtrol appears to be really in the market with
anything current, and driver support in
Re: Recommendations for a serial port card you can actually BUY?
At 11:19 AM 10/5/2006, Karl Denninger wrote: So what do I buy to replace this thing? Well, looking at the serial hardware claimed supported, I seem to have a problem finding anything I can actually purchase! I don't need real high performance - a 16550 based multiport card is fine. I also don't want a $1500 solution - this isn't a $1500 problem. $500 seems reasonable. I use a lot of 4 port Lava cards on RELENG_6. They are about $80 CDN. I have also used the PCI cards and USB FTDI based adaptors in the past at http://www.byterunner.com/ puc1: Lava Computers Quattro-PCI serial port port 0xbc00-0xbc07,0xb800-0xb807 irq 17 at device 2.0 on pci1 sio5: Lava Computers Quattro-PCI serial port on puc1 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode sio6: Lava Computers Quattro-PCI serial port on puc1 sio6: type 16550A sio6: unable to activate interrupt in fast mode - using normal mode puc2: Lava Computers Quattro-PCI serial port port 0xc400-0xc407,0xc000-0xc007 irq 17 at device 2.1 on pci1 sio7: Lava Computers Quattro-PCI serial port on puc2 sio7: type 16550A sio7: unable to activate interrupt in fast mode - using normal mode sio8: Lava Computers Quattro-PCI serial port on puc2 sio8: type 16550A sio8: unable to activate interrupt in fast mode - using normal mode I have one box where 2 4 port cards live together (zoo.freebsd.org) [zoo]% uname -a FreeBSD zoo.freebsd.org 6.1-STABLE FreeBSD 6.1-STABLE #6: Fri Aug 18 06:16:39 EDT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZOO i386 [zoo]% puc0: Lava Computers Quattro-PCI serial port port 0xdf00-0xdf07,0xde00-0xde07 irq 20 at device 0.0 on pci2 sio4: Lava Computers Quattro-PCI serial port on puc0 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode sio5: Lava Computers Quattro-PCI serial port on puc0 sio5: type 16550A sio5: unable to activate interrupt in fast mode - using normal mode puc1: Lava Computers Quattro-PCI serial port port 0xdd00-0xdd07,0xdc00-0xdc07 irq 20 at device 0.1 on pci2 sio6: Lava Computers Quattro-PCI serial port on puc1 sio6: type 16550A sio6: unable to activate interrupt in fast mode - using normal mode sio7: Lava Computers Quattro-PCI serial port on puc1 sio7: type 16550A sio7: unable to activate interrupt in fast mode - using normal mode puc2: Lava Computers Quattro-PCI serial port port 0xdb00-0xdb07,0xda00-0xda07 irq 21 at device 1.0 on pci2 sio8: Lava Computers Quattro-PCI serial port on puc2 sio8: type 16550A sio8: unable to activate interrupt in fast mode - using normal mode sio9: Lava Computers Quattro-PCI serial port on puc2 sio9: type 16550A sio9: unable to activate interrupt in fast mode - using normal mode puc3: Lava Computers Quattro-PCI serial port port 0xd900-0xd907,0xd800-0xd807 irq 21 at device 1.1 on pci2 sio10: Lava Computers Quattro-PCI serial port on puc3 sio10: type 16550A sio10: unable to activate interrupt in fast mode - using normal mode sio11: Lava Computers Quattro-PCI serial port on puc3 sio11: type 16550A sio11: unable to activate interrupt in fast mode - using normal mode ---Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kern/103841: [fdc] fdc(4) does not work (regression)
Hello! The problem is clearly an I/O port resource misdetection: On Fri, 6 Oct 2006, Eugene Grosbein wrote: 4.11-STABLE: fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ---^ OK. 6.2-PRERELEASE: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 ^ Bad (no 0x3f7, 0x3f0 gets listed twice). Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On 10/5/06, Karl Denninger [EMAIL PROTECTED] wrote: [...] I know serial I/O is passe for many, but some of us have applications that actually require it, and can't rationally be moved to anything else due to external hardware considerations. [...] Serial over IP will not work for either. Serial-via-USB might, and I will look into that, but I suspect I'm going to get in trouble with that one, especially if I have to toggle control signals (e.g. DTR, etc) or support hardware flow control (and for the fax servers, you DO need it if you expect things to work correctly.) I have used USB-to-serial converters with no problem. All the control signals (at least the ones my applications need) seem to work correctly. I don't remember any brands or models off hand, I bought what was cheap as I needed them and they all worked. Cheap means under $20 delivered (for one port). FreeBSD's USB support has always been somewhat deficient. For example, apcupsd can't talk to their UPSs over the USB bus, even though the software itself knows how, because FreeBSD doesn't know what a UPS is and throws up its hands when you plug it in. I wasn't aware that the USB to Serial converters would work - I can try them, but there are a lot of those out there that don't work right even under Windows - expecting them to under FreeBSD might be asking too much. I've had no problem getting them to work in FreeBSD. I've had some trouble getting them to work in WIndows. YMMV, but they are so dirt cheap that the time it takes to test one will likely be more significant than the cost of the device. man uplcom will give you an idea of what chipsets to look for, although determining the chipset in one of those things is frequently impossible. The uvscom driver seems to support another chipset, but none of my devices use it so I don't know how well it works. At the moment I can't tell you what version of FreeBSD I'm using these under, probably 5.3, maybe 6.0. It isn't reachable to me from where I am. - Bob ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On Thu, Oct 05, 2006 at 03:21:44PM -0500, Karl Denninger wrote: FreeBSD's USB support has always been somewhat deficient. For example, apcupsd can't talk to their UPSs over the USB bus, even though the software itself knows how, because FreeBSD doesn't know what a UPS is and throws up its hands when you plug it in. This is false for at least the APC SmartUPS the machine I'm sending this from is connected to. I wouldn't be suprised if it was true once, but it isn't today. ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 -- Brooks pgp7xaOqphxz8.pgp Description: PGP signature
Re: kern/103841: [fdc] fdc(4) does not work (regression)
On Fri, Oct 06, 2006 at 12:00:15AM +0300, Dmitry Pryanishnikov wrote: The problem is clearly an I/O port resource misdetection: On Fri, 6 Oct 2006, Eugene Grosbein wrote: 4.11-STABLE: fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ---^ OK. 6.2-PRERELEASE: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 ^ Bad (no 0x3f7, 0x3f0 gets listed twice). Recent revisions of fdc(4) do not use control register at port 0x3f7. CURRENT's version works fine and still probes controller this way, without 0x3f7. You can get background info from commint logs for fdc.c Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On Thu, Oct 05, 2006 at 03:21:44PM -0500, Karl Denninger wrote: FreeBSD's USB support has always been somewhat deficient. Yes. For example, apcupsd can't talk to their UPSs over the USB bus, even though the software itself knows how, because FreeBSD doesn't know what a UPS is and throws up its hands when you plug it in. apcupsd works with FreeBSD 4.11-STABLE and later. It uses ugen(4) interface to talk with UPS. It has no problems with my BackUPS CS 500. Do not try it with 4.11-RELEASE, though - it won't work. Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em, bge, network problems survey.
Kris Kennaway wrote: On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote: All, I'm seeing some patterns here with all of the network driver problem reports, but I need more information to help narrow it down further. I ask all of you who are having problems to take a minute to fill out this survey and return it to Kris Kennaway (on cc:) and myself. Thanks. 1. Are you experiencing network hangs and/or timeout messages on the console? If yes, please provide a _brief_ description of the problem. OK, next question, to all em users: If your em device is using a shared interrupt, and you are NOT experiencing timeout problems when using this device, please let me know: dalki# vmstat -i interrupt total rate irq4: sio0 2071 0 irq6: fdc010 0 irq14: ata0 47 0 irq20: ahd021755 4 irq23: em0124751 23 -- not a shared interrupt irq24: ahd1 15 0 cpu0: timer 10453509 1999 Total 10602158 2027 tyan# vmstat -i interrupt total rate irq14: ata0 58 0 irq16: em0 fxp1 332832851 -- shared interrupt irq18: fxp0 973 2 irq19: atapci1132883339 cpu0: timer 774308 1980 cpu1: timer 777136 1987 Total2018190 5161 So far all of the em problems I have seen involve shared interrupts, and conversely all em systems I have seen that do not have timeout problems are not shared. Kris And so looks mine, FreeBSD 6.2-PRE/AMD64, high I/O on disks and I/O on net renders this box unusuable ... thor# vmstat -i interrupt total rate irq1: atkbd0 12437 1 irq6: fdc027 0 irq12: psm0 335285 42 irq14: ata0 215 0 irq17: fwohci0 1 0 irq20: atapci1102616 12 irq21: ohci0+ 2 0 irq22: nve0 ehci07594338956 irq23: pcm041007 5 cpu0: timer 31752206 3999 Total 39838134 5018 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
Hello! On Thu, 5 Oct 2006, Karl Denninger wrote: The problem that is nailing me particularly hard right now is the second one - I have embedded control systems that I speak to over a RS-232 interface (the devices are actually '485 on a common bus but talked to via a 232/485 converter) and it simply does not work on 6.x using the Comtrol driver at all. 100ms delays and the like are one thing - we're talking about delays in characters reaching the application of one second or more, and in What makes me wonder is whether delays you're seeing have the same nature as recent watchdog timeouts on various Gbit NICs observed by many RELENG_6 users (interrupt processing scheduling problem I suspect), or they're strictly rp(4)-specific. With FreeBSD 5.x being EOL'd this is now turning into a critical problem. I can't in good conscience put packages out there that have been EOL'd nor offer meaningful support on them. While 5.4 has been reasonably stable for some time, that is now declared a dead release. 5.5 is similarly on that road. The only right path forward is into the 6.x world, but I can't get there from where I am now unless this problem can be resolved. If I were you, I'd try to prepare easy-repeatable test case so developer (or just curious and clever person) who has Comtrol Serial Port Card could recreate the problem. And no, I don't have either hardware or time available. [ Cost considerations are totally skipped cause they're irrelevant to software regressions like the one you're seeing... ] Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel panic with backtrace.
Hi folks.
I have kernel panic on 5.5-RELEASE-p5 box.
Could some one please help me to find the source of this panic.
If you need more info just let me know.
==
vel-28# uname -a
FreeBSD vel-28.129 5.5-RELEASE-p5 FreeBSD 5.5-RELEASE-p5 #0: Wed Sep 27
06:07:25 GMT 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEBUG i386
==
Unread portion of the kernel message buffer:
panic: vm_fault: fault on nofault entry, addr: ecf1a000
Uptime: 6h34m7s
Dumping 1022 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336
352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656
672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 960 976
992 1008
#0 doadump () at pcpu.h:160
160 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:160
#1 0xc06150ec in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:412
#2 0xc061536a in panic (fmt=0xc08406b1 vm_fault: fault on nofault entry,
addr: %lx) at /usr/src/sys/kern/kern_shutdown.c:568
#3 0xc07629c1 in vm_fault (map=0xc103b000, vaddr=3975258112, fault_type=1
'\001', fault_flags=0) at /usr/src/sys/vm/vm_fault.c:273
#4 0xc07be0a3 in trap_pfault (frame=0xe33c4c08, usermode=0, eva=3975258112) at
/usr/src/sys/i386/i386/trap.c:726
#5 0xc07bdd81 in trap (frame=
{tf_fs = -1064173544, tf_es = 16, tf_ds = -1065222128, tf_edi =
-1032584476, tf_esi = -319709186, tf_ebp = -482587500, tf_isp = -482587596,
tf_ebx = -1032852224, tf_edx = 0, tf_ecx = 327, tf_eax = -712875290, tf_trapno
= 12, tf_err = 0, tf_eip = -1065631578, tf_cs = 8, tf_eflags = 66054, tf_esp =
5291, tf_ss = 2048}) at /usr/src/sys/i386/i386/trap.c:427
#6 0xc07ae29a in calltrap () at /usr/src/sys/i386/i386/exception.s:140
#7 0xc0920018 in nfsheur ()
#8 0x0010 in ?? ()
#9 0xc0820010 in ?? ()
#10 0xc27402e4 in ?? ()
#11 0xecf19ffe in ?? ()
#12 0xe33c4c94 in ?? ()
#13 0xe33c4c34 in ?? ()
#14 0xc26fed00 in ?? ()
#15 0x in ?? ()
#16 0x0147 in ?? ()
#17 0xd58262e6 in ?? ()
#18 0x000c in ?? ()
#19 0x in ?? ()
#20 0xc07bc0a6 in generic_bcopy () at /usr/src/sys/i386/i386/support.s:489
#21 0x14ab in ?? ()
#22 0x0800 in ?? ()
#23 0xc0648eac in m_devget (buf=0xecf19d1a , totlen=-1065631578, off=0,
ifp=0xc2369000, copy=0) at /usr/src/sys/kern/uipc_mbuf.c:943
#24 0xc0714235 in rl_rxeof (sc=0xc2369000) at /usr/src/sys/pci/if_rl.c:1176
#25 0xc07145df in rl_intr (arg=0xc2369000) at /usr/src/sys/pci/if_rl.c:1376
#26 0xc0603740 in ithread_loop (arg=0xc2278400) at
/usr/src/sys/kern/kern_intr.c:547
#27 0xc0602bb4 in fork_exit (callout=0xc060361c ithread_loop, arg=0xc2278400,
frame=0xe33c4d38) at /usr/src/sys/kern/kern_fork.c:791
#28 0xc07ae2fc in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:209
==
vel-28# pciconf -vl
[EMAIL PROTECTED]:0:0:class=0x06 card=0x25601458 chip=0x25608086
rev=0x03 hdr=0x00
vendor = 'Intel Corporation'
device = '82845G/GL/GV/GE/PE DRAM Controller / Host-Hub I/F Bridge'
class= bridge
subclass = HOST-PCI
[EMAIL PROTECTED]:2:0: class=0x03 card=0x25621458 chip=0x25628086 rev=0x03
hdr=0x00
vendor = 'Intel Corporation'
device = '82845G/GL/GV/GE/PE Integrated Graphics Device'
class= display
subclass = VGA
[EMAIL PROTECTED]:29:0:class=0x0c0300 card=0x24c21458 chip=0x24c28086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:29:1:class=0x0c0300 card=0x24c21458 chip=0x24c48086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:29:2:class=0x0c0300 card=0x24c21458 chip=0x24c78086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:29:7:class=0x0c0320 card=0x50061458 chip=0x24cd8086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB 2.0 EHCI Controller'
class= serial bus
subclass = USB
[EMAIL PROTECTED]:30:0:class=0x060400 card=0x chip=0x244e8086
rev=0x82 hdr=0x01
vendor = 'Intel Corporation'
device = '82801BA/CA/DB/DBL/EB/ER/FB (ICH2/3/4/4/5/5/6), 6300ESB Hub
Interface to PCI Bridge'
class= bridge
subclass = PCI-PCI
[EMAIL PROTECTED]:31:0:class=0x060100 card=0x chip=0x24c08086
rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '82801DB/DBL (ICH4/ICH4-L) LPC Interface Bridge'
class=
Re: Recommendations for a serial port card you can actually BUY?
Brooks Davis wrote: On Thu, Oct 05, 2006 at 03:21:44PM -0500, Karl Denninger wrote: FreeBSD's USB support has always been somewhat deficient. For example, apcupsd can't talk to their UPSs over the USB bus, even though the software itself knows how, because FreeBSD doesn't know what a UPS is and throws up its hands when you plug it in. This is false for at least the APC SmartUPS the machine I'm sending this from is connected to. I wouldn't be suprised if it was true once, but it isn't today. ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 The uhid driver used to grab the APC USB device, but I think someone added a quirk in 6.1 to stop it so the ugen driver would get it instead. Guy -- Guy Helmer, Ph.D. Chief System Architect Palisade Systems, Inc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kern/103841: [fdc] fdc(4) does not work (regression)
Hello!
On Fri, 6 Oct 2006, Eugene Grosbein wrote:
fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on
acpi0
^
Bad (no 0x3f7, 0x3f0 gets listed twice).
Recent revisions of fdc(4) do not use control register at port 0x3f7.
Are you sure? I see the following in /sys/dev/fdc/fdc.c (CURRENT version):
#define FDCTL 7 /* Control Register (W) */
static void
fdctl_wr(struct fdc_data *fdc, u_int8_t v)
{
fdregwr(fdc, FDCTL, v);
}
Well, in CURRENT it _may not_ be used if you've got the Enhanced
floppy controller:
if (fdc-fdct == FDC_ENHANCED)
fddsr_wr(fdc, fd-ft-trans);
else
fdctl_wr(fdc, fd-ft-trans);
while in RELENG_6 it's always
fdctl_wr(fdc, fd-ft-trans);
That's why version from CURRENT works for you despite the absence of 0x3f7
resource. But it's incorrect to say that Recent revisions of fdc(4) do not
use control register at port 0x3f7 - actually they do for non-FDC_ENHANCED
case.
Sincerely, Dmitry
--
Atlantis ISP, System Administrator
e-mail: [EMAIL PROTECTED]
nic-hdl: LYNX-RIPE
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em, bge, network problems survey.
On Thu, Oct 05, 2006 at 11:17:33PM +0200, O. Hartmann wrote: Kris Kennaway wrote: On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote: All, I'm seeing some patterns here with all of the network driver problem reports, but I need more information to help narrow it down further. I ask all of you who are having problems to take a minute to fill out this survey and return it to Kris Kennaway (on cc:) and myself. Thanks. 1. Are you experiencing network hangs and/or timeout messages on the console? If yes, please provide a _brief_ description of the problem. OK, next question, to all em users: If your em device is using a shared interrupt, and you are NOT experiencing timeout problems when using this device, please let me know: dalki# vmstat -i interrupt total rate irq4: sio0 2071 0 irq6: fdc010 0 irq14: ata0 47 0 irq20: ahd021755 4 irq23: em0124751 23 -- not a shared interrupt irq24: ahd1 15 0 cpu0: timer 10453509 1999 Total 10602158 2027 tyan# vmstat -i interrupt total rate irq14: ata0 58 0 irq16: em0 fxp1 332832851 -- shared interrupt irq18: fxp0 973 2 irq19: atapci1132883339 cpu0: timer 774308 1980 cpu1: timer 777136 1987 Total2018190 5161 So far all of the em problems I have seen involve shared interrupts, and conversely all em systems I have seen that do not have timeout problems are not shared. Kris And so looks mine, FreeBSD 6.2-PRE/AMD64, high I/O on disks and I/O on net renders this box unusuable ... thor# vmstat -i interrupt total rate irq1: atkbd0 12437 1 irq6: fdc027 0 irq12: psm0 335285 42 irq14: ata0 215 0 irq17: fwohci0 1 0 irq20: atapci1102616 12 irq21: ohci0+ 2 0 irq22: nve0 ehci07594338956 irq23: pcm041007 5 cpu0: timer 31752206 3999 Total 39838134 5018 You don't appear to be using the em driver. Can you confirm? Kris pgp0D4kyJscBm.pgp Description: PGP signature
Re: Kernel panic with backtrace.
On Fri, Oct 06, 2006 at 12:25:42AM +0300, Nikolay Pavlov wrote:
Hi folks.
I have kernel panic on 5.5-RELEASE-p5 box.
Could some one please help me to find the source of this panic.
If you need more info just let me know.
==
vel-28# uname -a
FreeBSD vel-28.129 5.5-RELEASE-p5 FreeBSD 5.5-RELEASE-p5 #0: Wed Sep 27
06:07:25 GMT 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEBUG i386
==
Unread portion of the kernel message buffer:
panic: vm_fault: fault on nofault entry, addr: ecf1a000
Uptime: 6h34m7s
Dumping 1022 MB
16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320
336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624
640 656 672 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928
944 960 976 992 1008
#0 doadump () at pcpu.h:160
160 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:160
#1 0xc06150ec in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:412
#2 0xc061536a in panic (fmt=0xc08406b1 vm_fault: fault on nofault entry,
addr: %lx) at /usr/src/sys/kern/kern_shutdown.c:568
#3 0xc07629c1 in vm_fault (map=0xc103b000, vaddr=3975258112, fault_type=1
'\001', fault_flags=0) at /usr/src/sys/vm/vm_fault.c:273
#4 0xc07be0a3 in trap_pfault (frame=0xe33c4c08, usermode=0, eva=3975258112)
at /usr/src/sys/i386/i386/trap.c:726
#5 0xc07bdd81 in trap (frame=
{tf_fs = -1064173544, tf_es = 16, tf_ds = -1065222128, tf_edi =
-1032584476, tf_esi = -319709186, tf_ebp = -482587500, tf_isp = -482587596,
tf_ebx = -1032852224, tf_edx = 0, tf_ecx = 327, tf_eax = -712875290,
tf_trapno = 12, tf_err = 0, tf_eip = -1065631578, tf_cs = 8, tf_eflags =
66054, tf_esp = 5291, tf_ss = 2048}) at /usr/src/sys/i386/i386/trap.c:427
#6 0xc07ae29a in calltrap () at /usr/src/sys/i386/i386/exception.s:140
#7 0xc0920018 in nfsheur ()
#8 0x0010 in ?? ()
#9 0xc0820010 in ?? ()
This backtrace appears to be mostly corrupt (maybe you're using
CFLAGS=-O2), but I can tell you that few developers are interested in
supporting 5.x any longer, so your best bet would be to upgrade to
6.1 and see if the problem persists, then proceed from there.
kris
pgpatxdUtkZbo.pgp
Description: PGP signature
Re: BCM5754 supported in 6.2 release?
Mike Jakubik wrote: Yi-Hua Edward Yang wrote: I asked the question below a while back but got no answer. Does that mean BCM5754 integrated GbE will not be supported by 6.2 release at all? The HARDWARE.TXT file does not list it, but the source code seems to have the BCM5754 support, or at least so the CVS comments say. Does anyone know when if_bge will support BCM5754 GbE? We really hope to run FreeBSD on our Dell Precision desktops. If the source code mentions support, then it most likely will be supported but has not made it to the docs yet. To be sure, download ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.2/6.2-BETA2-i386-bootonly.iso , boot it up and see for yourself. Hi, thanks for your reply and suggestion. I downloaded FreeBSD 6.2 Beta2 and tried to boot it on Dell Precision 390. It failed with the same sympton as before (upgrade 6.1 release by cvsup and buildkernel/buildworld). The BCM5754 device is recognized (wrongly) as BCM5787, folloed by a kernel trap 19. This problem effectively makes FreeBSD 6.2 Beta2 unusable on any new Dell Precision machines. Please help, anyone? Thanks in advance! Edward ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RELENG_6/amd64 buildworld error
Hi there colleagues am I the only one who got the following error? === sbin/geom/class/mirror (all) cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=opteron -I/usr/src/sbin/geom/class/mirror/../.. -I/usr/src/sbin/geom/class/mirror/../../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/sbin/geom/class/mirror/geom_mirror.c -o geom_mirror.So /usr/src/sbin/geom/class/mirror/geom_mirror.c: In function `mirror_main': /usr/src/sbin/geom/class/mirror/../../../../sys/geom/mirror/g_mirror.h:374: warning: inlining failed in call to 'mirror_metadata_decode': --param max-inline-insns-single limit reached after inlining into the callee /usr/src/sbin/geom/class/mirror/geom_mirror.c:310: warning: called from here /usr/src/sbin/geom/class/mirror/../../../../sys/geom/mirror/g_mirror.h:374: warning: inlining failed in call to 'mirror_metadata_decode': --param max-inline-insns-single limit reached after inlining into the callee /usr/src/sbin/geom/class/mirror/geom_mirror.c:346: warning: called from here Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em, bge, network problems survey.
On 5. okt. 2006, at 22.05, Kris Kennaway wrote: On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote: All, I'm seeing some patterns here with all of the network driver problem reports, but I need more information to help narrow it down further. I ask all of you who are having problems to take a minute to fill out this survey and return it to Kris Kennaway (on cc:) and myself. Thanks. 1. Are you experiencing network hangs and/or timeout messages on the console? If yes, please provide a _brief_ description of the problem. OK, next question, to all em users: If your em device is using a shared interrupt, and you are NOT experiencing timeout problems when using this device, please let me know: [ snip ] So far all of the em problems I have seen involve shared interrupts, and conversely all em systems I have seen that do not have timeout problems are not shared. I am sorry to say that I have trouble with a system that does not have shared interrupt on the em. It does share PCI bus with the two onboard ahc's though, but that hardly has anything to do with it. # vmstat -i interrupt total rate irq4: sio0 398 0 irq6: fdc010 0 irq16: ahc0 16 0 irq17: ahc1 16 0 irq20: amr0 1439521 1 irq21: em0 5110499 3 irq31: acpi0 134252 0 cpu0: timer 2689289991 1999 Total 2695974703 2004 # pciconf -l |grep pci1 [EMAIL PROTECTED]:4:0: class=0x01 card=0x00cf8086 chip=0x00cf9005 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:4:1: class=0x01 card=0x00cf8086 chip=0x00cf9005 rev=0x01 hdr=0x00 [EMAIL PROTECTED]:10:0:class=0x060400 card=0x00dc chip=0x00261011 rev=0x05 hdr=0x01 [EMAIL PROTECTED]:11:0: class=0x02 card=0x10048086 chip=0x10048086 rev=0x02 hdr=0x00 -- Frode Nordahl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Linux Stable
Hi All Yesterday I'm make a make buildworld/make buildkernel after cvsup (because security fix in openssh, but i update all). I'm running RELENG_6 After that I've one big linux software don't work (maple 9.5), before this update everything work fine. Now my question what can I do ? Are there any kind of technics to ?downgrad? a STABLE ? It's very important software for me, if I can make this software work, i must re-install all my server:-( Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. 7 i?me ?tage, plateau D, bureau 10 Heure local/Local time: Fri Oct 6 00:37:29 CEST 2006 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
/dev/null
Hi All From someday I've some very strange thing sometime my /dev/null just vanish. Anyone have this problem ? I'm running FreeBSD RELENG_6 Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. 7 i?me ?tage, plateau D, bureau 10 Heure local/Local time: Fri Oct 6 00:40:33 CEST 2006 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
If memory serves me right, Philippe Pegon wrote: In June 2006, I opened a PR (kern/98622) about a regression on CARP with IPv6 addresses: CARP is not usable with IPv6. Since I tracked down the culprit commit (see appropriate info in the PR), I can affirm that this regression appeared before the 6.1-RELEASE. bz@ has just recently (a couple of hours ago) updated kern/98622 with a possible fix. It'd be really useful if you (or anyone else experiencing this problem) could try this out and give him some feedback. (I know that you, Philippe, know all this already, but I wanted to get the information out to a wider audience.) Cheers, Bruce. signature.asc Description: OpenPGP digital signature
Re: Recommendations for a serial port card you can actually BUY?
On Thu, Oct 05, 2006 at 05:04:41PM -0400, Bob Johnson wrote: On 10/5/06, Karl Denninger [EMAIL PROTECTED] wrote: [...] I know serial I/O is passe for many, but some of us have applications that actually require it, and can't rationally be moved to anything else due to external hardware considerations. I have used USB-to-serial converters with no problem. All the control signals (at least the ones my applications need) seem to work correctly. I don't remember any brands or models off hand, I bought what was cheap as I needed them and they all worked. Cheap means under $20 delivered (for one port). Interesting. Now, what happens when you reboot? Do they come back in random order? That won't work! I need to know that port 2 will BE Port 2 the next time the machine comes up -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On Thu, Oct 05, 2006 at 04:04:47PM -0500, Brooks Davis wrote: On Thu, Oct 05, 2006 at 03:21:44PM -0500, Karl Denninger wrote: FreeBSD's USB support has always been somewhat deficient. For example, apcupsd can't talk to their UPSs over the USB bus, even though the software itself knows how, because FreeBSD doesn't know what a UPS is and throws up its hands when you plug it in. This is false for at least the APC SmartUPS the machine I'm sending this from is connected to. I wouldn't be suprised if it was true once, but it isn't today. ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 Does apcupsd connect to it? I tried this back on 5.x and it failed miserably. It identified the unit, but wouldn't talk to it. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On Fri, Oct 06, 2006 at 12:22:09AM +0300, Dmitry Pryanishnikov wrote: Hello! On Thu, 5 Oct 2006, Karl Denninger wrote: The problem that is nailing me particularly hard right now is the second one - I have embedded control systems that I speak to over a RS-232 interface (the devices are actually '485 on a common bus but talked to via a 232/485 converter) and it simply does not work on 6.x using the Comtrol driver at all. 100ms delays and the like are one thing - we're talking about delays in characters reaching the application of one second or more, and in What makes me wonder is whether delays you're seeing have the same nature as recent watchdog timeouts on various Gbit NICs observed by many RELENG_6 users (interrupt processing scheduling problem I suspect), or they're strictly rp(4)-specific. It might be. I am NOT having problems with em0 however, and I DO have it in the box With FreeBSD 5.x being EOL'd this is now turning into a critical problem. I can't in good conscience put packages out there that have been EOL'd nor offer meaningful support on them. While 5.4 has been reasonably stable for some time, that is now declared a dead release. 5.5 is similarly on that road. The only right path forward is into the 6.x world, but I can't get there from where I am now unless this problem can be resolved. If I were you, I'd try to prepare easy-repeatable test case so developer (or just curious and clever person) who has Comtrol Serial Port Card could recreate the problem. And no, I don't have either hardware or time available. Its easy for me to do that, but so far nobody has picked up the PR. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: FreeBSD 5.3, 5.4, 6.0 EoLs coming soon
On Thursday 05 October 2006 10:48 am, Eugene Grosbein wrote: On Thu, Oct 05, 2006 at 01:09:27PM +0100, Robert Watson wrote: It's definetely a regression from 4.11-STABLE that runs fine on this system with ACPI fully enabled Hmm, I was wrong about 4.11 using ACPI - it does not use it here really, it uses good old APM. It would be interesting to know how 4.x probes the hardware vs. how it apperas in the 6.x dmesg. 4.11-STABLE: fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive on fdc0 drive 0 6.2-PRERELEASE: fdc0: floppy drive controller port 0x3f0-0x3f5,0x3f0 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 You have bad ACPI DSDT. Try newer BIOS if there's any. Jung-uk Kim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On Thu, Oct 05, 2006 at 07:09:56PM -0500, Karl Denninger wrote: On Thu, Oct 05, 2006 at 04:04:47PM -0500, Brooks Davis wrote: On Thu, Oct 05, 2006 at 03:21:44PM -0500, Karl Denninger wrote: FreeBSD's USB support has always been somewhat deficient. For example, apcupsd can't talk to their UPSs over the USB bus, even though the software itself knows how, because FreeBSD doesn't know what a UPS is and throws up its hands when you plug it in. This is false for at least the APC SmartUPS the machine I'm sending this from is connected to. I wouldn't be suprised if it was true once, but it isn't today. ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 Does apcupsd connect to it? I tried this back on 5.x and it failed miserably. It identified the unit, but wouldn't talk to it. Yes. I get notifications of power failures and can query status. -- Brooks pgpukGQDBDeJP.pgp Description: PGP signature
Re: Recommendations for a serial port card you can actually BUY?
At 08:09 PM 10/5/2006, Karl Denninger wrote: ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 Does apcupsd connect to it? I tried this back on 5.x and it failed miserably. It identified the unit, but wouldn't talk to it. I literally have 150+ remote FreeBSD boxes with them and they succeed fantastically... They are configured to shut down the box and power to the UPS outlets on power failure with 25% battery left. All the notification hooks work as expected. They have been working for me since the 5.x days. I have a few in the field running on 5.4 boxes (May 2005) without issue. (ugen0: APC Back-UPS ES 725 FW:802.n2.D USB FW:n2, rev 1.10/1.06, addr 2) [ps0006]# apcaccess APC : 001,034,0908 DATE : Thu Oct 05 20:28:56 EDT 2006 HOSTNAME : ps0006.sentex.ca RELEASE : 3.10.18 VERSION : 3.10.18 (21 July 2005) freebsd UPSNAME : RAPIDS CABLE: USB Cable MODEL: Back-UPS ES 500 UPSMODE : Stand Alone STARTTIME: Wed Jun 14 11:00:07 EDT 2006 STATUS : ONLINE LINEV: 120.0 Volts LOADPCT : 12.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 29.9 Minutes MBATTCHG : 25 Percent MINTIMEL : -1 Minutes MAXTIME : 0 Seconds LOTRANS : 088.0 Volts HITRANS : 139.0 Volts ALARMDEL : 30 seconds BATTV: 13.6 Volts NUMXFERS : 19 XONBATT : Mon Sep 25 10:53:00 EDT 2006 TONBATT : 0 seconds CUMONBATT: 173 seconds XOFFBATT : Mon Sep 25 10:53:02 EDT 2006 STATFLAG : 0x0208 Status Flag MANDATE : 2005-10-13 SERIALNO : JB0542018502 BATTDATE : 2000-00-00 NOMBATTV : 12.0 FIRMWARE : 24.B1.D USB FW:B1 APCMODEL : Back-UPS ES 500 END APC : Thu Oct 05 20:28:57 EDT 2006 [ps0006]# usbdevs addr 1: UHCI root hub, VIA addr 2: Back-UPS ES 500 FW:824.B1.D USB FW:B1, APC addr 1: UHCI root hub, VIA addr 1: UHCI root hub, VIA addr 1: UHCI root hub, VIA addr 1: EHCI root hub, VIA [ps0006]# ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
On 2006-10-05, Brooks Davis wrote: On Thu, Oct 05, 2006 at 07:09:56PM -0500, Karl Denninger wrote: On Thu, Oct 05, 2006 at 04:04:47PM -0500, Brooks Davis wrote: On Thu, Oct 05, 2006 at 03:21:44PM -0500, Karl Denninger wrote: FreeBSD's USB support has always been somewhat deficient. For example, apcupsd can't talk to their UPSs over the USB bus, even though the software itself knows how, because FreeBSD doesn't know what a UPS is and throws up its hands when you plug it in. This is false for at least the APC SmartUPS the machine I'm sending this from is connected to. I wouldn't be suprised if it was true once, but it isn't today. ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 Does apcupsd connect to it? I tried this back on 5.x and it failed miserably. It identified the unit, but wouldn't talk to it. Yes. I get notifications of power failures and can query status. I don't know what you guys are doing right, but it doesn't work right for me on $ uname -srm FreeBSD 6.1-RELEASE amd64 I do get some results: this is the console when it's connected: ugen1: American Power Conversion Smart-UPS 750 FW:651.12.I USB FW:7.3, rev 1.10/0.06, addr 6 I find that apcaccess gives much less info from the USB port than it does from the RS232 port (on the same hardware) and apctest (which I want to use to set eprom values) doesn't work at all. This is very irritating, as I'd like to use my only serial port for a remote console. For now, I've gone back to using the serial port. But I'd love the USB to work fully. Greg ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
What's your config like? I hooked the USB back up and it identified, but when I told it to use USB and specified the device, it panics (the software, not the machine) with a complaint about not being able to talk to the UPS. Works perfectly on a serial port... -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind On Thu, Oct 05, 2006 at 08:35:32PM -0400, Mike Tancsa wrote: At 08:09 PM 10/5/2006, Karl Denninger wrote: ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 Does apcupsd connect to it? I tried this back on 5.x and it failed miserably. It identified the unit, but wouldn't talk to it. I literally have 150+ remote FreeBSD boxes with them and they succeed fantastically... They are configured to shut down the box and power to the UPS outlets on power failure with 25% battery left. All the notification hooks work as expected. They have been working for me since the 5.x days. I have a few in the field running on 5.4 boxes (May 2005) without issue. (ugen0: APC Back-UPS ES 725 FW:802.n2.D USB FW:n2, rev 1.10/1.06, addr 2) [ps0006]# apcaccess APC : 001,034,0908 DATE : Thu Oct 05 20:28:56 EDT 2006 HOSTNAME : ps0006.sentex.ca RELEASE : 3.10.18 VERSION : 3.10.18 (21 July 2005) freebsd UPSNAME : RAPIDS CABLE: USB Cable MODEL: Back-UPS ES 500 UPSMODE : Stand Alone STARTTIME: Wed Jun 14 11:00:07 EDT 2006 STATUS : ONLINE LINEV: 120.0 Volts LOADPCT : 12.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 29.9 Minutes MBATTCHG : 25 Percent MINTIMEL : -1 Minutes MAXTIME : 0 Seconds LOTRANS : 088.0 Volts HITRANS : 139.0 Volts ALARMDEL : 30 seconds BATTV: 13.6 Volts NUMXFERS : 19 XONBATT : Mon Sep 25 10:53:00 EDT 2006 TONBATT : 0 seconds CUMONBATT: 173 seconds XOFFBATT : Mon Sep 25 10:53:02 EDT 2006 STATFLAG : 0x0208 Status Flag MANDATE : 2005-10-13 SERIALNO : JB0542018502 BATTDATE : 2000-00-00 NOMBATTV : 12.0 FIRMWARE : 24.B1.D USB FW:B1 APCMODEL : Back-UPS ES 500 END APC : Thu Oct 05 20:28:57 EDT 2006 [ps0006]# usbdevs addr 1: UHCI root hub, VIA addr 2: Back-UPS ES 500 FW:824.B1.D USB FW:B1, APC addr 1: UHCI root hub, VIA addr 1: UHCI root hub, VIA addr 1: UHCI root hub, VIA addr 1: EHCI root hub, VIA [ps0006]# ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] %SPAMBLOCK-SYS: Matched [EMAIL PROTECTED], message ok ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /dev/null
On Fri, 6 Oct 2006, Albert Shih wrote: From someday I've some very strange thing sometime my /dev/null just vanish. Anyone have this problem ? Not with FreeBSD in particular. However, from time to time I've run across a piece of software that makes bad assumptions about deleting various input or output files. If run as root, the program/library might accidentally delete a character special device such as /dev/null. Not that *I* would have ever written such code, mind you. (whistles innocently) Brent ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
At 09:49 PM 10/5/2006, Karl Denninger wrote: What's your config like? I hooked the USB back up and it identified, but when I told it to use USB and specified the device I think it says in the docs not to specify the device. , it panics (the software, not the machine) with a complaint about not being able to talk to the UPS. UPSNAME STATN UPSCABLE usb UPSTYPE usb DEVICE LOCKFILE /var/spool/lock ONBATTERYDELAY 7 BATTERYLEVEL 25 MINUTES -1 TIMEOUT 0 ANNOY 10 ANNOYDELAY 10 NOLOGON disable KILLDELAY 2 NETSERVER on NISIP 127.0.0.1 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 100 UPSCLASS standalone UPSMODE disable STATTIME 600 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 600 FACILITY local2 UPSNAME STN SENSITIVITY H WAKEUP 010 SLEEP 000 RETURNCHARGE 00 BEEPSTATE T SELFTEST 336 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Patch available for shared em interrupts (Re: em, bge, network problems survey.)
On Thu, Oct 05, 2006 at 04:05:52PM -0400, Kris Kennaway wrote:
On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote:
All,
I'm seeing some patterns here with all of the network driver problem
reports, but I need more information to help narrow it down further.
I ask all of you who are having problems to take a minute to fill
out this survey and return it to Kris Kennaway (on cc:) and myself.
Thanks.
1. Are you experiencing network hangs and/or timeout messages on the
console? If yes, please provide a _brief_ description of the problem.
OK, next question, to all em users:
If your em device is using a shared interrupt, and you are NOT
experiencing timeout problems when using this device, please let me
know:
Based on successful testing on a machine with shared em interrupt, the
following patch should work around the problem *in that case*.
Note that this patch will not help you if you are not using the em
driver, or if you are seeing the problem with non-shared em interrupt
(I have investigated on such outlier, which seems to be a problem with
a particular model of em hardware and not a generic problem with the
driver).
Index: if_em.c
===
RCS file: /home/ncvs/src/sys/dev/em/if_em.c,v
retrieving revision 1.65.2.18
diff -u -u -r1.65.2.18 if_em.c
--- if_em.c 25 Aug 2006 12:38:26 - 1.65.2.18
+++ if_em.c 5 Oct 2006 22:05:45 -
@@ -2086,7 +2086,7 @@
taskqueue_start_threads(adapter-tq, 1, PI_NET, %s taskq,
device_get_nameunit(adapter-dev));
if ((error = bus_setup_intr(dev, adapter-res_interrupt,
- INTR_TYPE_NET | INTR_FAST, em_intr_fast, adapter,
+ INTR_TYPE_NET | INTR_MPSAFE, em_intr_fast, adapter,
adapter-int_handler_tag)) != 0) {
device_printf(dev, Failed to register fast interrupt
handler: %d\n, error);
Please let Scott and I know whether or not this patch works for you
(in addition to the information previously requested, if you have not
already sent it). Unfortunately it is only a workaround, but it
points to an underlying problem with fast interrupt handlers on a
shared irq that can be studied separately.
Kris
pgpp54QFa2jMW.pgp
Description: PGP signature
Re: Recommendations for a serial port card you can actually BUY?
At 09:49 PM 10/5/2006, Karl Denninger wrote: What's your config like? I hooked the USB back up and it identified, but when I told it to use USB and specified the device, it panics (the software, not the machine) with a complaint about not being able to talk to the UPS. Works perfectly on a serial port... From the documentation at http://www.apcupsd.org/manual/Configuration_Examples.html#SECTION000131000 If you have a USB UPS, and you have apcupsd version 3.10.7 (3.10.17a for *BSD) or higher, the essential elements of your apcupsd.conf file should look like the following: ## apcupsd.conf v1.1 ## UPSCABLE usb UPSTYPE usb DEVICE LOCKFILE /var/lock UPSCLASS standalone UPSMODE disable Notice that we have not specified a device. In doing so, apcupsd will try all the well known USB ports. We strongly recommend you use this (empty device address) form unless you have a good reason to do otherwise. -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind On Thu, Oct 05, 2006 at 08:35:32PM -0400, Mike Tancsa wrote: At 08:09 PM 10/5/2006, Karl Denninger wrote: ugen0: American Power Conversion Smart-UPS 750 FW:651.12.D USB FW:4.2, rev 1.10/0.06, addr 2 Does apcupsd connect to it? I tried this back on 5.x and it failed miserably. It identified the unit, but wouldn't talk to it. I literally have 150+ remote FreeBSD boxes with them and they succeed fantastically... They are configured to shut down the box and power to the UPS outlets on power failure with 25% battery left. All the notification hooks work as expected. They have been working for me since the 5.x days. I have a few in the field running on 5.4 boxes (May 2005) without issue. (ugen0: APC Back-UPS ES 725 FW:802.n2.D USB FW:n2, rev 1.10/1.06, addr 2) [ps0006]# apcaccess APC : 001,034,0908 DATE : Thu Oct 05 20:28:56 EDT 2006 HOSTNAME : ps0006.sentex.ca RELEASE : 3.10.18 VERSION : 3.10.18 (21 July 2005) freebsd UPSNAME : RAPIDS CABLE: USB Cable MODEL: Back-UPS ES 500 UPSMODE : Stand Alone STARTTIME: Wed Jun 14 11:00:07 EDT 2006 STATUS : ONLINE LINEV: 120.0 Volts LOADPCT : 12.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 29.9 Minutes MBATTCHG : 25 Percent MINTIMEL : -1 Minutes MAXTIME : 0 Seconds LOTRANS : 088.0 Volts HITRANS : 139.0 Volts ALARMDEL : 30 seconds BATTV: 13.6 Volts NUMXFERS : 19 XONBATT : Mon Sep 25 10:53:00 EDT 2006 TONBATT : 0 seconds CUMONBATT: 173 seconds XOFFBATT : Mon Sep 25 10:53:02 EDT 2006 STATFLAG : 0x0208 Status Flag MANDATE : 2005-10-13 SERIALNO : JB0542018502 BATTDATE : 2000-00-00 NOMBATTV : 12.0 FIRMWARE : 24.B1.D USB FW:B1 APCMODEL : Back-UPS ES 500 END APC : Thu Oct 05 20:28:57 EDT 2006 [ps0006]# usbdevs addr 1: UHCI root hub, VIA addr 2: Back-UPS ES 500 FW:824.B1.D USB FW:B1, APC addr 1: UHCI root hub, VIA addr 1: UHCI root hub, VIA addr 1: UHCI root hub, VIA addr 1: EHCI root hub, VIA [ps0006]# ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] %SPAMBLOCK-SYS: Matched [EMAIL PROTECTED], message ok ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
Hi, Karl Denninger wrote: So. I have an application that requires six serial ports, and would like ten. 5.x FreeBSD versions are being EOL'd per the announcement, forcing me to move to 6.x. The Comtrol driver for the Smart Rocketport boards is broken in 6.x, and the PR appears to be one that will sit and rot. What options do I have in the FreeBSD universe here guys? This is a real no-BS production application that has hundreds of deployed instances, and it is in no way obsolete or something I intend to stop supporting. I know serial I/O is passe for many, but some of us have applications that actually require it, and can't rationally be moved to anything else due to external hardware considerations. I do serial I/O a bit. I use USB to RS232 and USB to RS485/RS422 devices. There are a bunch of vendors, they are cheap and seem to work well. I have also seen (but not used) 4 port versions of these things, and I wouldn't be surprised if you could find an eight port version as well. Regards, Jan Mikkelsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Linux Stable
On Fri, 6 Oct 2006 00:40:14 +0200
Albert Shih [EMAIL PROTECTED] wrote:
Now my question what can I do ? Are there any kind of technics to
_downgrad_ a STABLE ?
Hi Albert,
this was discussed in -questions@ on September 27th.
http://monkey.org/freebsd/archive/freebsd-questions/200609/msg02105.html
Best,
B
_
{Beto|Norberto|Numard} Meijome
I've dirtied my hands writing poetry, for the sake of seduction; that is, for
the sake of a useful cause. Dostoevsky
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Recommendations for a serial port card you can actually BUY?
Karl Denninger wrote: So. I have an application that requires six serial ports, and would like ten. 5.x FreeBSD versions are being EOL'd per the announcement, forcing me to move to 6.x. The Comtrol driver for the Smart Rocketport boards is broken in 6.x, and the PR appears to be one that will sit and rot. What options do I have in the FreeBSD universe here guys? This is a real no-BS production application that has hundreds of deployed instances, and it is in no way obsolete or something I intend to stop supporting. Well, you could find (or hire) someone to fix the driver in 6.x, which would save you the cost of re-deploying hardware. (I'm assuming that the PR is a statement of brokenness, and not one that has a patch that fixes the problem.) -- Matt Emmerton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_6/amd64 buildworld error
On Fri, Oct 06, 2006 at 02:02:27AM +0400, Dmitry Morozovsky wrote: Hi there colleagues am I the only one who got the following error? === sbin/geom/class/mirror (all) cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=opteron -I/usr/src/sbin/geom/class/mirror/../.. -I/usr/src/sbin/geom/class/mirror/../../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/sbin/geom/class/mirror/geom_mirror.c -o geom_mirror.So /usr/src/sbin/geom/class/mirror/geom_mirror.c: In function `mirror_main': /usr/src/sbin/geom/class/mirror/../../../../sys/geom/mirror/g_mirror.h:374: warning: inlining failed in call to 'mirror_metadata_decode': --param max-inline-insns-single limit reached after inlining into the callee /usr/src/sbin/geom/class/mirror/geom_mirror.c:310: warning: called from here /usr/src/sbin/geom/class/mirror/../../../../sys/geom/mirror/g_mirror.h:374: warning: inlining failed in call to 'mirror_metadata_decode': --param max-inline-insns-single limit reached after inlining into the callee /usr/src/sbin/geom/class/mirror/geom_mirror.c:346: warning: called from here It I go into sbin/geom/class/mirror and compile it like this: make DEBUG_FLAGS=-I/usr/src/sbin/geom/class/mirror/../../../../sys I also get this error. The question is why you have this -I added. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgpGbMEUwPrjE.pgp Description: PGP signature
Re: RELENG_6/amd64 buildworld error
On Fri, Oct 06, 2006 at 09:24:39AM +0400, Ruslan Ermilov wrote: On Fri, Oct 06, 2006 at 02:02:27AM +0400, Dmitry Morozovsky wrote: Hi there colleagues am I the only one who got the following error? === sbin/geom/class/mirror (all) cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=opteron -I/usr/src/sbin/geom/class/mirror/../.. -I/usr/src/sbin/geom/class/mirror/../../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/sbin/geom/class/mirror/geom_mirror.c -o geom_mirror.So /usr/src/sbin/geom/class/mirror/geom_mirror.c: In function `mirror_main': /usr/src/sbin/geom/class/mirror/../../../../sys/geom/mirror/g_mirror.h:374: warning: inlining failed in call to 'mirror_metadata_decode': --param max-inline-insns-single limit reached after inlining into the callee /usr/src/sbin/geom/class/mirror/geom_mirror.c:310: warning: called from here /usr/src/sbin/geom/class/mirror/../../../../sys/geom/mirror/g_mirror.h:374: warning: inlining failed in call to 'mirror_metadata_decode': --param max-inline-insns-single limit reached after inlining into the callee /usr/src/sbin/geom/class/mirror/geom_mirror.c:346: warning: called from here It I go into sbin/geom/class/mirror and compile it like this: make DEBUG_FLAGS=-I/usr/src/sbin/geom/class/mirror/../../../../sys I also get this error. The question is why you have this -I added. The below explains why the warning is only seen when using non-system headers: :-Winline :Warn if a function can not be inlined and it was declared as :inline. Even with this option, the compiler will not warn about :failures to inline functions declared in system headers. Cheers, -- Ruslan Ermilov [EMAIL PROTECTED] FreeBSD committer pgp3lJnduj5jF.pgp Description: PGP signature
