Re: flowtable usable or not
Em Sex, Março 2, 2012 11:35, Nomen Nescio escreveu: my experiences of slow and nightmarishly error-ridden port updates I have no intention to bash FreeBSD or ports but ports is certainly not without problems. It's annoying but not a reason to use Ubuntu! Get a grip, man! ;-) I know there are users who have operated without such problems I think if you use the i386 architecture and the common ports you are less likely to find something before somebody else finds it and it gets fixed. If you use any other platform you are likely to find problems with ports and this gets amplified if you use nonstandard (read stuff not everybody uses) ports. with some good luck may be ... ports need some kind of disaster management for example, certain ports depending on perl, install or upgrade fine when using portupgrade or portinstall and are satisfied with let's say perl-8.9 then you use pkg_add, or -P[P] switch and the same port looks for perl.12.4 and bumps it into the system careless, not even checking if there is another perl already no way using batch on ports today unless you like to get screwed and never turn your eyes away from screen I do not need to say more, you all know that and I can understand the frustration of whom is gotten caught by this mess I have found several ports broken for many releases in a row. Other ports aren't supported on certain target architectures but the build doesn't tell you that until after it has run for a couple of hours downloading huge source tarballs and compiling them only to give you a nastygram Sorry this port is not available on AMD64 of something like that. I understand not every port maintainer can test on every arch but come on, then the port should not be there for this architecture ... or it is and works or it is not or do we have new standards now as 0|0.5|1 or is it still 0|1 ? come on, for stuff that you know doesn't work can't you check at the beginning and stop rather than put out a message when the build breaks? some fine ports are compiling fine, go through the whole process and screw all up at the install process, they already run pkg_delete, do not find the dependency, do some stuff and bail out, at the end portupgrade confirm success but they do not got installed but de-installed, as present some dependencies are messed up ... :) so as it is, better grab the original sources and compile your stuff on your own and stay far away from ports -- João Martins (JoaoBR) Infomatik Development Team http://wipserver.matik.com.br +55 11 4249. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Short SMART check causes disk op timeouts
On Monday 27 October 2008 20:03:21 Jeremy Chadwick wrote: I had no idea users were blindly uncommenting examples in well seems you're new in support business then :) the issue might be the reason why weapons are not delivered with roles in the chambers ... so developers probably should take care of what kind of example they include smartd.conf.sample without reading what the features do. Then again, I guess many users/admins have no idea what sort of impact offline tests could have on a system. Short/long tests should not have any effect on a running/used disk -- and most do not see any effect -- but under high I/O I would assume there is a chance the suspend/resume aspect of SMART tests could take longer than 5 seconds. Though I am disappointed in the fact that people often schedule maintenance things all at the same time (between 0200 and 0500) but never think about the implications of them all running in parallel. well good idea to start a faq with general orientations :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: constant zfs data corruption
On Friday 17 October 2008 15:49:54 Xin LI wrote: JoaoBR wrote: Hi constantly I find data corruption on ZFS volums, ever from rrdtool, this corrupt data happens on SATA disks, never seem on SCSI scrub is not able to repair, when comes to touch this files machines reboots, deleting and restorin also is not possíble, seems I need to delete the files, umount, scrub and mount again to clear it # zpool status -v os pool: os state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scrub: none requested config: NAMESTATE READ WRITE CKSUM os ONLINE 0 0 0 ad4s1dONLINE 0 0 0 errors: Permanent errors have been detected in the following files: /usr/local/www/data-dist/monitor/wip_diskio.rrd /usr/local/www/data-dist/monitor/200.152.90.12mon.rrd some idea? For ZFS: I think you need to remove these file. ZFS scrub does not recover file if you don't have redundant, e.g. copies=2 or raid-z, etc. ok I see, I discovered this but should the machine crash when scrub reach the damaged file? For the data corruption itself: I think this is highly critical issue if you are sure that the hardware is good. What controller and disk are you using? disks are most seagate or maxtor sata-2 250G new, max 6 month old the Sata controller are mostly Nvidia as MCP51, MCP61, CK804 thank's -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: constant zfs data corruption
On Friday 17 October 2008 15:39:59 Chuck Swiger wrote: On Oct 17, 2008, at 11:30 AM, JoaoBR wrote: constantly I find data corruption on ZFS volums, ever from rrdtool, this corrupt data happens on SATA disks, never seem on SCSI Presumably your SATA drives are correctly being reported by ZFS as corrupting data, and you should do something like replace cables, the drives themselves, perhaps try downgrading to SATA-150 rather than -300 if you are using the later. Also consider running a drive diagnostic utility from the mfgr (or smartmontools) and doing an extended self-test or destructive write surface check. well, hardware seems to be ok and not older than 6 month, also happens not only on one machine ... smartctl do not report any hw failures on disk regarding jumpering the drives to 150 you suspect a driver problem? thank's -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: constant zfs data corruption
On Monday 20 October 2008 11:22:08 you wrote: On Mon, Oct 20, 2008 at 08:37:40AM -0200, JoaoBR wrote: On Friday 17 October 2008 15:39:59 Chuck Swiger wrote: On Oct 17, 2008, at 11:30 AM, JoaoBR wrote: constantly I find data corruption on ZFS volums, ever from rrdtool, this corrupt data happens on SATA disks, never seem on SCSI Presumably your SATA drives are correctly being reported by ZFS as corrupting data, and you should do something like replace cables, the drives themselves, perhaps try downgrading to SATA-150 rather than -300 if you are using the later. Also consider running a drive diagnostic utility from the mfgr (or smartmontools) and doing an extended self-test or destructive write surface check. well, hardware seems to be ok and not older than 6 month, also happens not only on one machine ... smartctl do not report any hw failures on disk regarding jumpering the drives to 150 you suspect a driver problem? It's not because of a driver problem. There are known SATA chipsets which do not properly work with SATA300 (particularly VIA and SiS chipsets); they claim to support it, but data is occasionally corrupted. Capping the drive to SATA150 fixes this problem. http://en.wikipedia.org/wiki/Serial_ATA#SATA_1.5_Gbit.2Fs_and_SATA_3_Gbit.2 Fs There are also known problems with Silicon Image chipsets (on Linux, Windows, and FreeBSD). Because you didn't provide your smartctl output, I can't really tell if the drives are in good shape or not. :-) ok then here it comes smartctl version 5.38 [amd64-portbld-freebsd7.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar T7K500 Device Model: Hitachi HDT725025VLA380 Serial Number:VFL101RK0A9SDP Firmware Version: V5DOA7EA User Capacity:250.058.268.160 bytes Device is:In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: ATA/ATAPI-7 T13 1532D revision 1 Local Time is:Mon Oct 20 15:07:01 2008 BRST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (4949) seconds. Offline data collection capabilities:(0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 1) minutes. Extended self-test routine recommended polling time:( 83) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 099 099 016Pre-fail Always - 3 2 Throughput_Performance 0x0005 100 100 050Pre-fail Offline - 0 3 Spin_Up_Time0x0007 117 117 024Pre-fail Always - 316 (Average 322) 4 Start_Stop_Count0x0012 100 100 000Old_age Always - 36 5 Reallocated_Sector_Ct 0x0033 100 100 005Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 020Pre-fail Offline - 0 9 Power_On_Hours 0x0012 100 100 000
Re: constant zfs data corruption
On Monday 20 October 2008 14:44:50 Chuck Swiger wrote: Hi, all-- On Oct 20, 2008, at 6:22 AM, Jeremy Chadwick wrote: [ ...JoaoBR wrote... ] well, hardware seems to be ok and not older than 6 month, also happens not only on one machine ... smartctl do not report any hw failures on disk regarding jumpering the drives to 150 you suspect a driver problem? It's not because of a driver problem. There are known SATA chipsets which do not properly work with SATA300 (particularly VIA and SiS chipsets); they claim to support it, but data is occasionally corrupted. Capping the drive to SATA150 fixes this problem. http://en.wikipedia.org/wiki/Serial_ATA#SATA_1.5_Gbit.2Fs_and_SATA_3_Gbit .2Fs Exactly so. Just as a general principle, if you've got sporadic data corruption, turning I/O and system busses down a notch and retesting is a useful starting point towards identifying whether the issue is repeatable and whether it leans towards a hardware issue or software. However, ZFS file checksumming supposedly is code that has been carefully reviewed and tested so when it logs problems that is supposed to be a fairly sure sign that the hardware isn't behaving right. ok, I will jumper it on some machines and see if the error comes back, even if my are Nvidia Sata Because you didn't provide your smartctl output, I can't really tell if the drives are in good shape or not. :-) Also, do you not think it's a little odd that the only data corruption occurring for you are related to RRDtool? RRD tends to involve lots of small writes so it's files are going to be changed often compared to other things that might be running; a busy webserver or mailserver would involve more I/O to logfiles and queue/mailspool, or so I would expect, but who knows what the machine in question is being used for? this server are transparent proxies (squid) on the top of small ISP networks with IPFW bandwidth control for the clients, the rrdtools collect the client traffic and some other data at every 5 minutes very ocasional I get the data corruption on a squid_cache file, normally 2 days after the rrdtool error appears first -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: constant zfs data corruption
On Monday 20 October 2008 15:03:14 Chuck Swiger wrote: On Oct 20, 2008, at 9:48 AM, Jeremy Chadwick wrote: Hm... I thought we determined earlier in this thread that the OP is not getting the benefits of ZFS checksums because he's not using raidz (only a single disk with a single pool)? He's not getting working filesystem redundancy with the existing config and is vulnerable to losing data from a single drive failure, agreed. But the ZFS checksum mechanism should still be working to detect data corruption, even though ZFS cannot recover the corrupted data the way it otherwise would if redundancy was available. all right and understood but shouldn't something as fsck should correct the error? Seems kind of problematic to me mounting zfs in single user mode, deleting the file and restarting the OS ? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
constant zfs data corruption
Hi constantly I find data corruption on ZFS volums, ever from rrdtool, this corrupt data happens on SATA disks, never seem on SCSI scrub is not able to repair, when comes to touch this files machines reboots, deleting and restorin also is not possíble, seems I need to delete the files, umount, scrub and mount again to clear it # zpool status -v os pool: os state: ONLINE status: One or more devices has experienced an error resulting in data corruption. Applications may be affected. action: Restore the file in question if possible. Otherwise restore the entire pool from backup. see: http://www.sun.com/msg/ZFS-8000-8A scrub: none requested config: NAMESTATE READ WRITE CKSUM os ONLINE 0 0 0 ad4s1dONLINE 0 0 0 errors: Permanent errors have been detected in the following files: /usr/local/www/data-dist/monitor/wip_diskio.rrd /usr/local/www/data-dist/monitor/200.152.90.12mon.rrd some idea? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: am2 MBs - 4g + SCSI wipes out root partition
On Saturday 11 October 2008 07:13:16 Jeremy Chadwick wrote: On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote: On Fri, 10 Oct 2008 14:29:37 -0300 JoaoBR [EMAIL PROTECTED] wrote: I tried MBs as Asus, Abit and Gigabyte all same result Same hardware with SATA works perfect Same hardware with scsi up to 3.5Gigs installed works perfect what calls my attention that all this MBs do not have the memroy hole remapping feature so the complete 4gigs are available what normally was not the case with amd64 Mbs for the Athlon 64 CPUs some has an opinion if this is a freebsd issue or MB falure or scsi drv problem? It's a driver problem. If you want to use SCSI then you'll have to limit memory to 3.5 GB. What you're saying is that Adaptec and LSI Logic SCSI controllers behave badly (and can cause data loss) on amd64 systems which contain more than 3.5GB of RAM. This is a very big claim. Have you talked to Scott Long about this? Please expand on this, and provide evidence or references. I need to document this in my Wiki if it is indeed true. I have an Asus AM2 Mb which support ECC mem and at least with the Adaptec raid card (aacd) the problem does not happen (when ECC support enabled) I did 10x buildworld, ahc and mpt still same issue, first build cracks the data on da0s1a On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote: It's a driver problem. If you want to use SCSI then you'll have to limit memory to 3.5 GB. well indeed with less then 4G installed it works flawless, so the difference I see is that former athln64 MBs had memory hole remap options or when 4Gig installed they only gave 3.something to the OS even under amd64 - this is NOT the case with the AM2 MBs which should support up to 8/16Mb onboard but wth this amount freebsd amd64 does not even boot when a scsi adaptor is installed -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: am2 MBs - 4g + SCSI wipes out root partition
On Saturday 11 October 2008 13:52:50 Jeremy Chadwick wrote: On Sat, Oct 11, 2008 at 12:26:29PM -0400, Adam McDougall wrote: Jeremy Chadwick wrote: On Sat, Oct 11, 2008 at 04:45:29PM +0200, Gary Jennejohn wrote: On Sat, 11 Oct 2008 03:13:16 -0700 Jeremy Chadwick [EMAIL PROTECTED] wrote: On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote: On Fri, 10 Oct 2008 14:29:37 -0300 JoaoBR [EMAIL PROTECTED] wrote: I tried MBs as Asus, Abit and Gigabyte all same result Same hardware with SATA works perfect Same hardware with scsi up to 3.5Gigs installed works perfect what calls my attention that all this MBs do not have the memroy hole remapping feature so the complete 4gigs are available what normally was not the case with amd64 Mbs for the Athlon 64 CPUs some has an opinion if this is a freebsd issue or MB falure or scsi drv problem? It's a driver problem. If you want to use SCSI then you'll have to limit memory to 3.5 GB. What you're saying is that Adaptec and LSI Logic SCSI controllers behave badly (and can cause data loss) on amd64 systems which contain more than 3.5GB of RAM. This is a very big claim. Have you talked to Scott Long about this? Please expand on this, and provide evidence or references. I need to document this in my Wiki if it is indeed true. See the freebsd-scsi thread with Subject data corruption with ahc driver and 4GB of memory using a FBSD-8 64-bit installation? from Wed, 30 Jan 2008. This was for ahc, but the bit-rot which Scott mentions in his reply might also apply to the LSI Logic controllers. Basically the driver doesn't correctly handle DMA above 4GB. Since the PCI hole gets mapped above 4GB it causes problems. the (S)ATA drivers don't seem to have this problem. Thank you -- this is the exact information I was looking for. I will update my Wiki page to reflect this quite major problem. I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac driver) with a 5th generation RAID card with 8G of ram, both have no such corruption problems. Providing this as a counter-example just to document some evidence of which products seem to work fine. Is your LSI SAS controller driven by mpt(4) or mfi(4)? Let's break down what we know for sure at this point: aac(4) - not affected aha(4) - unknown ahb(4) - unknown ahc(4) - affected ahd(4) - unknown; no one answered the OP's question in the thread asr(4) - unknown ips(4) - unknown mpt(4) - not affected mfi(4) - unknown sym(4) - unknown Could the problem be specific to certain firmware revisions on the cards? no, I tried different card versions AHD has the same problem AHC also AAC also MPT as well this is true for AM2 MBs but not true S939 and S940 MBs -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: am2 MBs - 4g + SCSI wipes out root partition
On Sunday 12 October 2008 06:57:11 Gary Jennejohn wrote: On Sat, 11 Oct 2008 23:51:18 +0200 Fabian Wenk [EMAIL PROTECTED] wrote: Hello Jeremy On 11.10.08 18:52, Jeremy Chadwick wrote: Could the problem be specific to certain firmware revisions on the cards? Some other idea, which versions of FreeBSD/amd64 are affected? Only 8-CURRENT, or also 6.x- and/or 7.x-RELEASE? As far as I have seen from the reports, it does only happen with more then 3.5 GB RAM and with SCSI disks. I do have a system with FreeBSD/amd64 6.3-RELEASE with 4 GB RAM and an Adaptec 29160 Ultra160 SCSI adapter (ahc) with only a tape drive connected. The disks are on an Areca RAID controller. Access to the disks and the tape drive does work just fine without any crashes. This is interesting because the 29160 is exactly the controller with which I had all my problems, but I was running it with disks only. Maybe Scott, or someone, has fixed it in the meantime? I haven't tried to use the full 4 GB in my box since January since I can't afford data corruption. I guess his MB is not an AM2 socket -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: am2 MBs - 4g + SCSI wipes out root partition
On Sunday 12 October 2008 14:10:36 Scott Long wrote: I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac driver) with a 5th generation RAID card with 8G of ram, both have no such corruption problems. Providing this as a counter-example just to document some evidence of which products seem to work fine. Is your LSI SAS controller driven by mpt(4) or mfi(4)? I can personal vouch for MPT and MFI drivers working just fine with 4GB. let narrow this a little bit, are you talking about AM2 sockets? because on AM2 the MPT drv is faulty as AHC, AHD and AACD with = 4Gigs -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: am2 MBs - 4g + SCSI wipes out root partition
On Monday 13 October 2008 10:50:54 Gary Jennejohn wrote: On Mon, 13 Oct 2008 09:35:10 -0200 JoaoBR [EMAIL PROTECTED] wrote: On Saturday 11 October 2008 07:13:16 Jeremy Chadwick wrote: It's a driver problem. If you want to use SCSI then you'll have to limit memory to 3.5 GB. I probably should have written - it seems to be a problem with ahc. In general SCSI seems to work, as Scott has recently documented. But see below. well indeed with less then 4G installed it works flawless, so the difference I see is that former athln64 MBs had memory hole remap options or when 4Gig installed they only gave 3.something to the OS even under amd64 - this is NOT the case with the AM2 MBs which should support up to 8/16Mb onboard but wth this amount freebsd amd64 does not even boot when a scsi adaptor is installed I'm beginning to believe that it's motherboard/BIOS related and not a general problem with ahc or any other SCSI driver. I can say that at least with my Gigabyte GA-M61P-S3 I observed data corruption with 4GB of memory installed and with the BIOS mapping a part of memory above 4GB. Forcing the kernel to use only 3.5GB solved the problem. exactly, I have the same MB and Gigabytes support changed Ideas with me, even released a newer bios version but at the end they insisted that it is an OS issue since this problem does not appear with windows and fedora -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: am2 MBs - 4g + SCSI wipes out root partition
On Saturday 11 October 2008 13:26:29 Adam McDougall wrote: Jeremy Chadwick wrote: On Sat, Oct 11, 2008 at 04:45:29PM +0200, Gary Jennejohn wrote: On Sat, 11 Oct 2008 03:13:16 -0700 Jeremy Chadwick [EMAIL PROTECTED] wrote: On Sat, Oct 11, 2008 at 11:30:57AM +0200, Gary Jennejohn wrote: On Fri, 10 Oct 2008 14:29:37 -0300 JoaoBR [EMAIL PROTECTED] wrote: I tried MBs as Asus, Abit and Gigabyte all same result Same hardware with SATA works perfect Same hardware with scsi up to 3.5Gigs installed works perfect what calls my attention that all this MBs do not have the memroy hole remapping feature so the complete 4gigs are available what normally was not the case with amd64 Mbs for the Athlon 64 CPUs some has an opinion if this is a freebsd issue or MB falure or scsi drv problem? It's a driver problem. If you want to use SCSI then you'll have to limit memory to 3.5 GB. What you're saying is that Adaptec and LSI Logic SCSI controllers behave badly (and can cause data loss) on amd64 systems which contain more than 3.5GB of RAM. This is a very big claim. Have you talked to Scott Long about this? Please expand on this, and provide evidence or references. I need to document this in my Wiki if it is indeed true. See the freebsd-scsi thread with Subject data corruption with ahc driver and 4GB of memory using a FBSD-8 64-bit installation? from Wed, 30 Jan 2008. This was for ahc, but the bit-rot which Scott mentions in his reply might also apply to the LSI Logic controllers. Basically the driver doesn't correctly handle DMA above 4GB. Since the PCI hole gets mapped above 4GB it causes problems. the (S)ATA drivers don't seem to have this problem. Thank you -- this is the exact information I was looking for. I will update my Wiki page to reflect this quite major problem. I am using some LSI (mpt driver) ultra4 (U320 scsi) and LSI SAS controllers in FreeBSD 7.x amd64 with 20G of ram, and Adaptec (aac driver) with a 5th generation RAID card with 8G of ram, both have no such corruption problems. Providing this as a counter-example just to document some evidence of which products seem to work fine. ___ well this for sure is NOT a AM2 MB but any server MB which indeed run fine as Tyans, SMs and others I guess -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
am2 MBs - 4g + SCSI wipes out root partition
I get a problem on several am2 motherboards when an SCSI Adaptor (LSI or Adaptec) is installed and with 4Gigs of Ram the problem is easy to repeat, after some minutes compiling world the machine crashes, sometimes a panic mmap ffs crossrefeerence or something, passes too fast to look an when the machine comes back often the complete root partition is gone or if not it needs manual fsck and mostly /dev references are gone or other important parts so the disk isn't bootable anymore funny is (for me) that the other partitions are ok ever and only root is fucked ever I tried MBs as Asus, Abit and Gigabyte all same result Same hardware with SATA works perfect Same hardware with scsi up to 3.5Gigs installed works perfect what calls my attention that all this MBs do not have the memroy hole remapping feature so the complete 4gigs are available what normally was not the case with amd64 Mbs for the Athlon 64 CPUs some has an opinion if this is a freebsd issue or MB falure or scsi drv problem? Gigabyte support tips a driver problem and no MB issue. Other manufactures don't answer. regarding the SCSI I tried the LSI U320, Adaptec U320 and Adaptec Raid SCSI (aacd) and all of them give me the same problem -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: am2 MBs - 4g + SCSI wipes out root partition
On Friday 10 October 2008 07:43:07 Dieter wrote: I get a problem on several am2 motherboards when an SCSI Adaptor (LSI or=20 Adaptec) is installed and with 4Gigs of Ram the problem is easy to repeat, after some minutes compiling world the machi= ne=20 crashes, sometimes a panic mmap ffs crossrefeerence or something, passes to= o=20 fast to look an when the machine comes back often the complete root partiti= on=20 is gone or if not it needs manual fsck and mostly /dev references are gone = or=20 other important parts so the disk isn't bootable anymore funny is (for me) that the other partitions are ok ever and only root is=20 fucked ever Are you running FreeBSD i386 or amd64? amd64 Is the compiler using /tmp and /tmp is in root partition? Maybe try having a seperate partition for /tmp, might keep root partition from getting trashed? /tmp is linked to /var/tmp Same hardware with SATA works perfect Maybe try root partition on SATA, everything else on SCSI and see what happens. If the system supports a RS-232 console, you could capture panic message that way. Or aim a video camera at the screen. well to be more clear the machine hangs somewhere in buildworld I saw some panics all with mmap and crossreference, the panic does not complete either it hangs before getting to the pointer lines I have still a disk which wasn't completly wiped out so if you have some need for finding some info I try but without camera and dogs envolved please :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
usb data xfer problem with to/from nokia smartphones
I have difficulties transferring data from or to nokia smartphones in mass storage mode, specially nokia N80 and N95. The files are coming with missing parts, accessing a photo which s stored ont the phone is beeing seen cut somewhere in half, mp3 files are transferred but there are missing parts within, same with other binaries from the same computer (dual boot) with windows xp and fedora 8 txferring the exact same file the thing runs fine happens on i386 and amd64 some idea what might be wrong? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
kern.cp_time wrong with phenoms
Hi kern.cp_time seems is reporting wrong values (most time too high) with Phenom and amd64 (i386 Ido not know) but with snmpget I get the correct machine values when consulting ssCpuRawUser.0 ssCpuRawNice.0 ssCpuRawSystem.0 ssCpuRawInterrupt.0 ssCpuRawIdle.0 kern.cp_time on RELENG6 reports correct with same hardware -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: possible zfs bug? lost all pools
On Sunday 18 May 2008 12:39:11 Jeremy Chadwick wrote: ... and if necessary /etc/rc.d/zfs should start hostid or at least set REQUIRE different and warn ... I've been in the same boat you are, and I was told the same thing. I've documented the situation on my Wiki, and the necessary workarounds. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issue so I changed the rcorder as you can see in the attached filesile http://suporte.matik.com.br/jm/zfs.rcfiles.tar.gz i'm coming back on this because I am convicted to zfs each day more and more and like to express my gratitude not only to whom made zfs but also and specially to the people who brought it to FBSD - and: thank you guys making it public, this is really a step forward! my zfs related rc files changes(above) made my problems go away and like to share some other experience here as on Jeremie's page explained I had similare problems with zfs but seems I could get around them with (depending on machine's load) setting either to 500, 1000 or 1500k vm.kmem_size* ... but seems main problem on FBSD is zfs recordsize, on ufs like partitions I set it to 64k and I never got panics any more, even with several zpools (as said as dangerous), cache_dirs for squid or mysql partitions might need lower values to get to there new and impressive peaks. this even seems to solve panics when copying large files from nfs|ufs to or from zfs ... so seems that FBSD do not like recordsize64k ... I have now a mail server running, for almost two month, with N zfs volumes (one per user) in order simulating quotas (-/+ 1000 users) with success and completely stable and performance is outstanding under all loads web server, apache/php/mysql, gave up maior stability problems but distributing depending on workload to zpools with different recordsizes and never 64k solved my problems and I am appearently panic free now I run almost scsi-only, only my test machines are sata, lowest conf is X2/4G, rest is X4 or opterons with 8g or more and I am extremely satisfied and happy with zfs my backups are running twice as fast as on ufs, mirroring in comparims to gmirror is fucking-incredible fast and the zfs snapshot thing deserves an Oscar! ... and the zfs send|receive another so thank you all who had fingers in/on zfs! (sometimes I press reset at my home server only to see how fast it comes up) .. just kidding but true is: thank's again! zfs is thE fs. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with nVidia nForce CK804 SATA300 controller
Hi anybody else experience a problem with this SATA controller? atapci1: nVidia nForce CK804 SATA300 controller port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xdc00-0xdc0f mem 0xfe02d000-0xfe02dfff irq 21 at device 7.0 on pci0 atapci1: [ITHREAD] ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jun 18 01:27:50 BRT 2008 my amd64 crashs under heavy disk i/o as each night at 0300 daily cron, also often after some minutes when compiling world. Also with kde and after some flash videos (youtube) or large file copying I do not see this problem with other sata controllers or same hardware and a scsi adapter and this sata disabled what makes me believe it is related to this specific sata controller this sata controller is part of some ASUS (M2N SLI Deluxe) or Epox AM2 MBs there is no panic at all, some seconds of hard freeze, on desktop machine the mouse still moves some seconds and reset, no log either, no crash dump, nothing I have no irq conflict, latest bios onboard, I also exchanged other hw parts with no success. Any idea? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: zfs start failure when /usr is on zfs (and rcorder change suggestion)
On Sunday 01 June 2008 09:41:09 JoaoBR wrote: Hi when you need /usr/compat on your sistem (linuxfs) and you have /usr on zfs boot fails because mountcritlocal does not find /usr/compat so I changed the rcorder as you can see in the attached files also I changed /etc/rc.d/zfs and added /etc/rc.d/zfs_swap in order to make the actual zfs_swap behaviour and configuration a little bit more [user]understandable and easier and working this needs two more rc vars as zfs_swap_enable=YES|NO zfs_swap_vols=spaced vol_list using this rc files zfs, swap on zfs and other fs mount fine the changed /etc/rc.d/zfs prevents losing zpools (and later import) as long as zfs started by this script seems the attached files were cut, you can get them here: http://suporte.matik.com.br/jm/zfs.rcfiles.tar.gz -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
zfs start failure when /usr is on zfs (and rcorder change suggestion)
Hi when you need /usr/compat on your sistem (linuxfs) and you have /usr on zfs boot fails because mountcritlocal does not find /usr/compat so I changed the rcorder as you can see in the attached files also I changed /etc/rc.d/zfs and added /etc/rc.d/zfs_swap in order to make the actual zfs_swap behaviour and configuration a little bit more [user]understandable and easier and working this needs two more rc vars as zfs_swap_enable=YES|NO zfs_swap_vols=spaced vol_list using this rc files zfs, swap on zfs and other fs mount fine the changed /etc/rc.d/zfs prevents losing zpools (and later import) as long as zfs started by this script -- João ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
possible zfs bug? lost all pools
after trying to mount my zfs pools in single user mode I got the following message for each: May 18 09:09:36 gw kernel: ZFS: WARNING: pool 'cache1' could not be loaded as it was last accessed by another system (host: gw.bb1.matik.com.br hostid: 0xbefb4a0f). See: http://www.sun.com/msg/ZFS-8000-EY any zpool cmd returned nothing else as not existing zfs, seems the zfs info on disks was gone to double-check I recreated them, rebooted in single user mode and repeated the story, same thing, trying to /etc/rc.d/zfs start returnes the above msg and pools are gone ... I guess this is kind of wrong -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: possible zfs bug? lost all pools
On Sunday 18 May 2008 12:39:11 Jeremy Chadwick wrote: On Sun, May 18, 2008 at 12:20:33PM -0300, JoaoBR wrote: On Sunday 18 May 2008 11:11:38 Greg Byshenk wrote: On Sun, May 18, 2008 at 09:56:17AM -0300, JoaoBR wrote: after trying to mount my zfs pools in single user mode I got the following message for each: May 18 09:09:36 gw kernel: ZFS: WARNING: pool 'cache1' could not be loaded as it was last accessed by another system (host: gw.bb1.matik.com.br hostid: 0xbefb4a0f). See: http://www.sun.com/msg/ZFS-8000-EY any zpool cmd returned nothing else as not existing zfs, seems the zfs info on disks was gone to double-check I recreated them, rebooted in single user mode and repeated the story, same thing, trying to /etc/rc.d/zfs start returnes the above msg and pools are gone ... I guess this is kind of wrong I think that the problem is related to the absence of a hostid when in single-user. Try running '/etc/rc.d/hostid start' before mouning. well, obviously that came to my mind after seeing the msg ... anyway the pools should not vanish don't you agree? and if necessary /etc/rc.d/zfs should start hostid or at least set REQUIRE different and warn I've been in the same boat you are, and I was told the same thing. I've documented the situation on my Wiki, and the necessary workarounds. http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues nice work this page, thanks This sort of thing needs to get hammered out before ZFS can be considered usable from a system administration perspective. Expecting people to remember to run an rc.d startup script before they can use any of their filesystems borders on unrealistic. yes but on the other side we know it is new stuff and sometimes the price is what happens to me this morning but then it also helps to make things better anyway, a little fix to rc.d/zfs like if [ ! `sysctl -n kern.hostiid 2/dev/null` ]; then echo zfs needs hostid first; exit 0; fi or something as precmd or first in zfs_start_main should fix this issue talking about there are more things, I experienced still not working swapon|off from rc.d/zfs script does not work either not sure what it is because same part of script run as root works, adding a dash to #!/bin/sh does not help either, from rc.d/zfs the state returns a dash do not see sense in rc.d/zfs `zfs share` since it is the default when sharenfs property is enabled man page tipo tells swap -a ... not swapon -a subcommands volini and volfini not in manual at all man page thar zfs can not be a dump device, not sure if I understand it as meant but I can dump to zfs very well and fast as long as recordsize=128 but at the end, for the short time zfs is there it gives me respectable performance results and it is stable for me as well -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: INET6 -- and why I don't use it
On Sunday 09 March 2008 20:41:51 Kevin Oberman wrote: From: JoaoBR [EMAIL PROTECTED] Date: Thu, 6 Mar 2008 20:19:33 -0300 your computer will or better CAN use ipv6 when it is on a ipv6 network and nothing else, ipv6 WILL NOT come eventually available on your ipv4 network (unless it's address space change ...) I'm unclear on the last sentence. I can assure you that IPv6 WILL come to your IPv4 network. It's not 'if' but 'when'. I am regularly amazed to see the number of people who bury their heads in the sand and claim it won't. Hi I am not saying that ipv6 is not coming but I am saying that as long as your network is ipv4 you do not need to care this has nothing to do with vista or dawn, this is a routing issue and as long as you are NOT on a ipv6 network you do NOT need ipv6 on our machine, still beeing able to access ipv6 networks ... as weel as ipv6 networls can access ipv4 networlks guys, if not so all this ipv[4|6] stuff wouldn't make any sense ... Whether you need to or not, you WILL have it if you run Vista. Read up on Teredo tunnels. You can turn this off on Vista, but it is on by default and every Vista system not configured to turn it off WILL run IPv6 regardless of what network it is connected to. well, fedora and FreeBSD also but you do not need it, windows does install netbeui netbios and simlare things by default which you do not neeed either on the internet and probably will disable or uninstall them Whether you need IPv6 is debatable. If you want to see the Kame dancing turtle, you will need IPv6. There are a very few specialized locations that are IPv6-only, but they are of little or no general interest. None the less, if you have Vista up and running or FreeBSD with the appropriate setup (6to4), your can reach them even if your network connection is IPv4 only. I am not sure if this correct, ipv4 to ipv6 and viceversa is be done by TRT (RFC3142) routers which are supposed to run on the border of such networks or by whom provides both protocols, as enduser you do not need to care about connectivity to each protocol I'm afraid I couldn't parse the latter part of this paragraph. (Still, your English is far better than my Portuguese.) :) then let's stay with it I think it is very easy, you need ipv6 when you are on or connected to an ipv6 network, otherwise not FWIW, I run a full production IPv6 network and have been working with IPv6 since it was still being developed by the IETF. It's far from perfect and, in fact, I am quite disappointed on how it came out, but it is what it is and, as of today, it is the only game in town that can move us to beyond the end of IPv4 address space availability. Live with it or live in the expensive past. (IPv4 addresses will soon get very expensive as the supply runs out.) well, I guess the question is not if it works or not but when and where you need it -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 - slow/unstable Internet access via Linux router
On Monday 03 March 2008 19:07:38 Mark Andrews wrote: On Mon, Mar 03, 2008 at 02:30:01PM +0300, Dmitry Antipov wrote: Is it required to have 'options INET6' even if I'm not using any IPv6 connectivity ? No, not unless you rely on SCTP, which at this time *does* require INET6. If you remove INET6, you must also remove SCTP. Be aware that if you remove INET6, ntpd (if used) will complain about missing transport protocol capability for tcp6 and udp6. It's a harmless warning, and won't impact functionality of ntpd. There is an open PR for this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/78728 Also I have occasional 'mskc0: Uncorrectable PCI Express error' messages, which is a known (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/119613) problem... Can't help you with this, but I bet Pyun YongHyeon can. :-) I really don't understand this wish people have to turn off IPv6. The world is running out of IPv4 addresses. IPv6 will be required within a year or two. Now is the time to easy, you do not need ipv6 when you are on an ipv4 network make sure every piece of software you use that requires IP connectivity supports IPv6. In 2-3 years time it will be too late as you won't have the option to fall back to IPv4. IPv6 connectivity is available to everyone today if they wish it. You don't have to wait for you ISP to supply it. well, that might not be exactly true, what do you want (and why should you) with an ipv6 address/service on your computer when you are on an ipv4 network??? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em very slow, shared irq... on 6.3p8
On Wednesday 27 February 2008 07:49:42 Holger Kipp wrote: Hello, I updated a system with 12 dc-interfaces to a new hardware with 14 em-interfaces. Yes, it is a firewall. New System is 6.2-RELEASE-p8. What I now experience between two internal networks (100MBit/s each) is the following: 1318 packets transmitted, 1317 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.387/246.153/2441.392/324.142 ms tcpdump on the firewall shows similar delays (on the outgoing interface). tcpdump on the system I ping however shows very quick responses for incoming packages (ie usually less than a millisecond). I therefore assume that the problem is between receiving the irq from emx and getting the data from the interface on the firewall itself. My first option would be to activate polling on em-interfaces - but as I did not experience this sort of notieceable slowdown with the old dc-based firewall (without polling), maybe someone can shed some light on this strange behaviour or has other suggestions as well? I had a setup with 4 (dlink 4port + 1 nic nfe onboard) which run extremely stable 6.3 I upgraded the hardware (S939 - AM2) and used two em 2port cards, without polling it was certanly unusable but with polling I got very good performance without polling normally in a day or less the machine hung, no msg, simply freezed with polling it stands some days up to two weeks when it freeze again I upgraded to 7.0 same result check your setup with vmstat -i and if you see two nics on the same interrupt I guess you get the same result as I got actual I am running one em 2port and two single port pci cards what seems to be stable anyway, similare setup on Tyan MBs do not have this problem where I also have 8 nics on one system I also do not have this problems on S939 boards only on AM2, so I am not sure where the problem is exactly but seems in a certain way hardware related You could try changing your PS unit because you might be short on power with lots of em cards and SATA disks -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: synaptics problem
On Sunday 10 February 2008 11:24:41 Matthieu Bollot wrote: Hi all, It seems that the current synaptics driver doesn't work with xorg 1.4, but with the patch it isn't necessary for virtual scrolling and 3 tap clic for middle clic. If somebody else has the problem : - apply this patch http://people.freebsd.org/~dumbbell/synaptics/psm-synaptics-virtualscrollin g-c.patch - compile kernel - xorg.conf : use the default way with moused. Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection hi for me using sysmouse and synaptics never did well, and what is satisfying for my case, is this with virtualscrolling perfectly working on all laptops I tried Identifier whatever Driver mouse Option Device /dev/psm0 Option Protocol auto -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: synaptics problem
On Wednesday 06 February 2008 19:48:56 Matthieu Bollot wrote: Hi, I've recently installed FreeBSD 6.3, and I've got a problem with synaptics. I've installed it, followed the pkg-message : hw.psm.synaptics_support=1 It works, dmesg gives : psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 moused_enable=NO ps shows me that moused doesn't run. hi the synaptic thing is bad explained everywhere if you want to use synaptics driver in xorg.conf you need to run sysmouse first from rc.conf otherwise you use as psm mouse and all synaptics options are availble in Freebsd's desktop then you do not need to set hw.psm.synaptics_support in loader,conf -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upgrading FreeBSD Questions
On Monday 29 October 2007 20:25:18 Jason Slack wrote: I have an HP Media center PC that has the Viiv 920-D processor with 4GB of RAM. I hate Windows, but had to sell my MacBook so my Fiance and I could get into a new apartment together. you really should read manpage of gmirror deactivate or something and then issue the gmirror forget cmd or get yourself a more reliable equipment :) or! ... transfer the apartment to me and I help you getting a new fiance worth the troubles :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [OT] Which one is best MTA for me?
On Tuesday 28 August 2007 23:28:42 LI Xin wrote: We (one of the largest ICP company in China and provides some billions of free e-mail accounts) well ... and the server is hosted in Gotham City -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Thursday 23 August 2007 14:37:57 Ian Smith wrote: so now I did because of your question and it seems the power_profile script has a bug I tries to set hw.acpi.cpu.cx_lowest=C1 but I guess it should be dev.cpu.0.cx_lowest Ah, ok. Updated in HEAD but not STABLE: http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1=te xttr1=1.7r2=texttr2=1.11 well, seems you are mistaken, it is not fixed, the new power_profile I have on my current is wrong as well # $FreeBSD: src/etc/rc.d/power_profile,v 1.11 2007/04/02 22:53:07 it still tries to set hw.acpi.cpu.cx_lowest but should set dev.cpu.0.cx_lowest so it still gives the same erro -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Thursday 23 August 2007 00:17:56 Ian Smith wrote:
Call me curious, but (assuming that you're tuning for performance, not
economy, and so will always run these boxes on AC power, not battery):
a) why you think that line in /etc/rc.d/power_profile is 'funny'?
well, in first place because it gave an error, I haven't looked deeper at that
moment because I was after something else
so now I did because of your question and it seems the power_profile script
has a bug
I tries to set hw.acpi.cpu.cx_lowest=C1
but I guess it should be dev.cpu.0.cx_lowest
b) what value for performance_cx_lowest you would consider more
appropriate to use than C1, and why?
I didn't said that, My comment was not regarding the value but the error per
se
c) whether you have overridden the /etc/defaults/rc.conf values for
{performance,economy}_cx_lowest or {performance,economy}_cpu_freq ?
no
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Thursday 23 August 2007 14:37:57 Ian Smith wrote: On Thu, 23 Aug 2007, JoaoBR wrote: On Thursday 23 August 2007 00:17:56 Ian Smith wrote: Call me curious, but (assuming that you're tuning for performance, not economy, and so will always run these boxes on AC power, not battery): a) why you think that line in /etc/rc.d/power_profile is 'funny'? well, in first place because it gave an error, I haven't looked deeper at that moment because I was after something else so now I did because of your question and it seems the power_profile script has a bug I tries to set hw.acpi.cpu.cx_lowest=C1 but I guess it should be dev.cpu.0.cx_lowest Ah, ok. Updated in HEAD but not STABLE: http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile.diff?r1=te xttr1=1.7r2=texttr2=1.11 But http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/power_profile indicates that hw.acpi.cpu.cx_lowest should still work anyway, to set all cpus the same? What is the error message you're getting? no it not working # sysctl hw.acpi.cpu.cx_lowest=C1 hw.acpi.cpu.cx_lowest: C1 sysctl: hw.acpi.cpu.cx_lowest: Invalid argument -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Monday 06 August 2007 09:28:35 JoaoBR wrote: . I had a chance to test several MBs with the same 6000+, 5000+ and 4600+ cpu At the end seems that the problem is mb/hardware related since some combinations hung even with latest BIOS installed and others not. not sure if somebody still wants to hear about this but it is kind of interesting I guess for my understandings in first place the MB and Bios is most important thing and there are vendor bios out which say they support the higher freq CPUs but certainly they don't or at least not all of them even so I gut freezes on all kind of combinations and seems that xorg and it's video drv are kind of very sensitive to certain settings, also with glx and dri disabled I still got freezings sooner or later I got a new monitor this days and that brought the real stuff up, seems that xorg is not liking when the HorizSync and VertRefresh rates are not 100% correct and what then cause the kill. In order to doublecheck this I took my old monitor back with correct settings and i got no further freezes either with any of the CPU/MB combinations I tested before. I have an LCD which can 1280x1024 at 75hz , the former could 1024x768 at 75hz and with both it works now fine with VertRefresh 50-100 HorizSync 31.5 - 82.0 before I had VertRefresh 50 - 90 HorizSync 30 - 75 one thing more I did which caused a sysctl error on boot. There is a funny line in /etc/rc.s/power_profile as 'highest_value=C1' which I commented out but I guess that has nothing to do since the setting was not accepted anyway xorg seems to have problems when enabling DPMS and returns wrong values. The vesa driver seems to work better or is less sensitive than sis and nv and ati but with the correct monitor rates all are working fine. well, I believe that's it because I have now two different MATX MBs running 24h with Athlon 5000 without any problem, since friday night -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 07:10:21 Michael Nottebrock wrote: but I have better news and seems my first idea was right, the MB is it I found a tech info on the manufactor's support site telling cpu support up to 4600+ and found a bios for newer cpus including my 5000+ so I upgraded the bios and my CPU now works with smp + cpufreq + powerd on both amd64 and i386 Good to hear. Unfortunately my Mobo's BIOS is already up-to-date, the CPU is officially supported and Cool'n'Quiet works dandy in Windows XP I had a chance to test several MBs with the same 6000+, 5000+ and 4600+ cpu At the end seems that the problem is mb/hardware related since some combinations hung even with latest BIOS installed and others not. I tested newer MATX MBs and the only one which seems to run stable for long time is the Gigabyte MCP61 chipset. All others are freezing sooner or later with Athlon 5000 or faster CPUs. The problem is less with the 4600 CPU almost all boards are fine and with 4200 CPU no problem at all. The MBs with sis vga onboard are appearently unusable with the higher freq CPUs. ATI and NVidia are ok. Xorg appearently do not like HPET enabled because it freezes then with all this boards I tested. Anyway, funny is that Fedora 7 which I have on the same HD is not freezing (same xorg+kde version) what makes me guess that eventual there is some problem with freebsd's acpi understanding the acpi tables when using this high freq amd processors. Only to remember the problem only ocurres when loading powerd and seems the freeze happens when cpu freq is upshifting not down. Not sure if it is worth looking deeper into this on 6 and soon I have some time I will check current first -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Monday 06 August 2007 12:54:08 Scot Hetzel wrote: On 8/6/07, JoaoBR [EMAIL PROTECTED] wrote: Only to remember the problem only ocurres when loading powerd and seems the freeze happens when cpu freq is upshifting not down. Try setting: hint.acpi_throttle.0.disabled=1 in /boot/loader.conf, as acpi_throttle may be the cause of the freeze. Scot thank's but I tried this switch and in none of this cases (MBs with problem) it helped -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote: JoaoBR schrieb: On Friday 27 July 2007 12:31:55 Nate Lawson wrote: JoaoBR wrote: Hi when I enable powerd with default flags (and any other also) the computer freezes some seconds after powerd is started. It does not reach login. Nothing in the logs. This is with amd 5000 X2 Am2 When i stick into the same computer a 4600 or 4200 it runs fine and smooth. I thought it is MB related and did the same and again the 5000 cpu freeze, the smaller ones not. Any idea what I should do? I use releng_6 amd and i386 same story and cpufreq and acpi is compiled. Disable powerd again and boot normally. Try changing the frequency with sysctl dev.cpu, etc. and see if any of the levels freeze for you. ok, this is what I get dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1000/25535 no need to say but the fan levels obviously are wrong And now the interesting part I shift to 2400 or any other and immediately freeze, that from kde konsole in single user mode I can shift up and down between all speeds and nothing happens [Jumping in from the thread started on -stable - http://lists.freebsd.org/pipermail/freebsd-stable/2007-July/036395.html - see there for system details] Same here - in single user mode, even powerd works fine - like it does with SMP disabled - but no go in multiuser. I see some similar discussion on stable but I can not match with everything there because I have the problem only with the athlon 5000 cpu The CPU difference is interesting - exactly what model is your X2 4600+? Mine is a stepping F, model 4B, rev BH-F2 (Energy Efficient with 65W TDP). seems to be the same but I have better news and seems my first idea was right, the MB is it I found a tech info on the manufactor's support site telling cpu support up to 4600+ and found a bios for newer cpus including my 5000+ so I upgraded the bios and my CPU now works with smp + cpufreq + powerd on both amd64 and i386 nothing wrong with freebsd and xorg neither :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 07:10:21 Michael Nottebrock wrote: JoaoBR schrieb: On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote: JoaoBR schrieb: On Friday 27 July 2007 12:31:55 Nate Lawson wrote: JoaoBR wrote: Hi when I enable powerd with default flags (and any other also) the computer freezes some seconds after powerd is started. It does not reach login. Nothing in the logs. This is with amd 5000 X2 Am2 When i stick into the same computer a 4600 or 4200 it runs fine and smooth. I thought it is MB related and did the same and again the 5000 cpu freeze, the smaller ones not. Any idea what I should do? I use releng_6 amd and i386 same story and cpufreq and acpi is compiled. Disable powerd again and boot normally. Try changing the frequency with sysctl dev.cpu, etc. and see if any of the levels freeze for you. ok, this is what I get dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1000/25535 no need to say but the fan levels obviously are wrong And now the interesting part I shift to 2400 or any other and immediately freeze, that from kde konsole in single user mode I can shift up and down between all speeds and nothing happens [Jumping in from the thread started on -stable - http://lists.freebsd.org/pipermail/freebsd-stable/2007-July/036395.html - see there for system details] Same here - in single user mode, even powerd works fine - like it does with SMP disabled - but no go in multiuser. I see some similar discussion on stable but I can not match with everything there because I have the problem only with the athlon 5000 cpu The CPU difference is interesting - exactly what model is your X2 4600+? Mine is a stepping F, model 4B, rev BH-F2 (Energy Efficient with 65W TDP). seems to be the same but I have better news and seems my first idea was right, the MB is it I found a tech info on the manufactor's support site telling cpu support up to 4600+ and found a bios for newer cpus including my 5000+ so I upgraded the bios and my CPU now works with smp + cpufreq + powerd on both amd64 and i386 Good to hear. Unfortunately my Mobo's BIOS is already up-to-date, the CPU is officially supported and Cool'n'Quiet works dandy in Windows XP ... =/ my ok msg was too fast, after some time my video starts flickering and stays so and the PC is freezed up, disabling powerd and works stable until it freeze cpu frequency shifting is done well manually I can set all cpu speeds and seems to stay stable on each must be related to X because I have some servers without X but cpufreq+smp+powerd running absolutely stable I found some msgs about the same problem with Gentoo and Debian and people say the problem is with xorg and changing to xfree solved it for them but I myself probably will not risk getting into a nightmare after the /usrX11R6 thing I have no windows but fedora 7 on the same pc and works fine too, kde's 'kpowersave info dialog' shows fine the cpu frequency shifting -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 08:40:33 Oliver Brandmueller wrote: Hi, On Sat, Jul 28, 2007 at 08:33:55AM -0300, JoaoBR wrote: my ok msg was too fast, after some time my video starts flickering and stays so and the PC is freezed up, disabling powerd and works stable until it freeze cpu frequency shifting is done well manually I can set all cpu speeds and seems to stay stable on each must be related to X because I have some servers without X but cpufreq+smp+powerd running absolutely stable Did you ever try to measure the difference in power consumption of the whole PC, so you know all the trouble actually is worth anything? :-) yup I did, probably not exactly the issue if you use a computer from time to time at home but if you have 200 running 24x7 things change Anyway I understand what you try to say but powerconsumption is not the only reason for using powerd there are secondary issues as PS, cooler and fan lifetimes for example, lower air conditioning costs also come in here fan noise is one of the interesting issues for home users or for whom likes it quiet in the office -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 14:47:17 Kris Kennaway wrote: On Sat, Jul 28, 2007 at 03:46:15PM +0200, Michael Nottebrock wrote: Meanwhile I found a workaround for my system: I had SCHED_ULE configured in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should have thought of that sooner, ISTR having problems with powerd and SCHED_ULE even on single cpu P4s. I see you've now learned a reason why no-one should be using SCHED_ULE on FreeBSD 7 so using ULE in 7 is ok ? ? ? you already told once ULE is broken in 6 what is nonsense as probably using ULE in 7 is ... ULE in 6.x is absolutely ok and it runs depending on situation faster than 4BSD with correct kernel and sysctl settings for it and it is perfectly stable, specially with polling + net.isr.enable + net.inet.ip.forwarding + some other tweaks depending on the servers load and several NICs on a router probably up to 4-6MB continuous throughput when then 4BSD gets faster but not so much, small and midsize MySQL seems to be faster with ULE too especially with small r/w packages ULE also seems to be faster on a desktop with SMP and KDE on X2 CPUs and you can feel it -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 10:46:15 Michael Nottebrock wrote: JoaoBR schrieb: On Saturday 28 July 2007 07:10:21 Michael Nottebrock wrote: JoaoBR schrieb: On Saturday 28 July 2007 04:21:39 Michael Nottebrock wrote: JoaoBR schrieb: On Friday 27 July 2007 12:31:55 Nate Lawson wrote: JoaoBR wrote: Hi when I enable powerd with default flags (and any other also) the computer freezes some seconds after powerd is started. It does not reach login. Nothing in the logs. This is with amd 5000 X2 Am2 When i stick into the same computer a 4600 or 4200 it runs fine and smooth. I thought it is MB related and did the same and again the 5000 cpu freeze, the smaller ones not. Any idea what I should do? I use releng_6 amd and i386 same story and cpufreq and acpi is compiled. Disable powerd again and boot normally. Try changing the frequency with sysctl dev.cpu, etc. and see if any of the levels freeze for you. ok, this is what I get dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1000/25535 no need to say but the fan levels obviously are wrong And now the interesting part I shift to 2400 or any other and immediately freeze, that from kde konsole in single user mode I can shift up and down between all speeds and nothing happens [Jumping in from the thread started on -stable - http://lists.freebsd.org/pipermail/freebsd-stable/2007-July/036395.htm l - see there for system details] Same here - in single user mode, even powerd works fine - like it does with SMP disabled - but no go in multiuser. I see some similar discussion on stable but I can not match with everything there because I have the problem only with the athlon 5000 cpu The CPU difference is interesting - exactly what model is your X2 4600+? Mine is a stepping F, model 4B, rev BH-F2 (Energy Efficient with 65W TDP). seems to be the same but I have better news and seems my first idea was right, the MB is it I found a tech info on the manufactor's support site telling cpu support up to 4600+ and found a bios for newer cpus including my 5000+ so I upgraded the bios and my CPU now works with smp + cpufreq + powerd on both amd64 and i386 Good to hear. Unfortunately my Mobo's BIOS is already up-to-date, the CPU is officially supported and Cool'n'Quiet works dandy in Windows XP ... =/ my ok msg was too fast, after some time my video starts flickering and stays so and the PC is freezed up, disabling powerd and works stable Meanwhile I found a workaround for my system: I had SCHED_ULE configured in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should have thought of that sooner, ISTR having problems with powerd and SCHED_ULE even on single cpu P4s. here no change, I was already on 4BSD I tried both schedulers but my problem persist. Since my MB has a sis onboard vga I will try a PCIe on monday and see if it helps because when I disable DPMS in xorg.conf it stands longer here -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 10:46:15 Michael Nottebrock wrote: Good to hear. Unfortunately my Mobo's BIOS is already up-to-date, the CPU is officially supported and Cool'n'Quiet works dandy in Windows XP ... =/ my ok msg was too fast, after some time my video starts flickering and stays so and the PC is freezed up, disabling powerd and works stable Meanwhile I found a workaround for my system: I had SCHED_ULE configured in my kernel - switching to SCHED_4BSD gets rid of the freezes. Should have thought of that sooner, ISTR having problems with powerd and SCHED_ULE even on single cpu P4s. I spend some time here on different MBs with the same 5000+ cpu, comparing i386 and amd64 I cvsuped both sources and compiled world and kernel an hour ago firstable, smp (either 4BSD or ULE) with powerd_enable (cpufreq in kernel) works as long as no xorg is started (GENERIC, no sysctl, no loader.conf options) nevertheless strange, on all MBs, same CPU: i386: dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1575/43957 1350/37677 1125/31398 1000/25535 875/22343 750/19151 625/15959 500/12767 375/9575 250/6383 125/3191 amd64:dev.cpu.0.freq_levels: 2600/10 2400/85596 2200/72544 2000/60778 1800/50237 1000/25535 both, amd64 and i386 with same ports and up to date wether 4BSD or ULE on i386 freeze soon as xorg starts when powerd is enabled ULE freeze on xorg start before coming up and 4BSD comes up and works for a certain time on amd64 (5-30 minutes) all kernels are compiled with make.conf option CPUTYPE?=athlon64 beeing translated appearently to the same athlon-mp option when available somebody knows why I get different frequencies under i386 and amd64 for the same hardware? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerd freeze with amd 5000 X2 but not with lower cpus
On Saturday 28 July 2007 20:21:02 Peter Jeremy wrote: On 2007-Jul-28 19:03:54 -0300, JoaoBR [EMAIL PROTECTED] wrote: so using ULE in 7 is ok ? ? ? Yes. I thought it is SCHED_SMP on 7 ... isn't it? if not forget my joke, I remember a msg from Roberson saying the _SMP will substitute _ULE on 7 but I do not use 7 so may be it changed later back to it's original name ULE in 6.x is absolutely ok and it runs depending on situation faster than 4BSD with correct kernel and sysctl settings for it and it is perfectly stable, This is simply wrong. ULE in 6.x is known to have problems and is unsupported. If the problems do not affect your particular workload then fine. If you have _any_ problems whilst running with ULE in 6.x, your problems will not be invstigated unless you can reproduce the problem with the 4BSD scheduler. interesting, what do you know? Do you have some data to share? I don't know where you got your info but I have 50 X2 SMP amd64 running and 25 or so dual-opteron dualcores with SCHED_ULE absolute rockstable and faster than 4BSD, as I mentioned under the circumstances I described before I also have more 40 or so X2s and 60 or so dual and quad opteron dualcores running 4BSD and before you tell me more blabla copied from newspapers and other cha-cha sources better you come to me with data (DATA=numbers) from *real* world As Kris stated, reporting problems in 6.x when you are running ULE is just wasting developer resources. well I also don't know where you got this because I *never ever* claimed any problem with ULE Please stop implying that people should be using ULE in 6.x unless you are willing to personally provide support for them. I also do not know where you got this because I also *never ever* implied using ULE, I simply say that I do *NOT* have any problem with it the way I use it So you please read the complete msgs and *try* to understand them before answering with distortions and irrelevant conversations -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
tar -x freeze machine
When I tar -xzvf file.tar.gz -C/d the machine freeze completely and instantly after extracting the first file. I tried different option no chance. No error msg nothing. I used then gtar on the same file created with tar -c and it worked. It is amd64 with smp kernel. The tarball is 2.4G . I did this before but times ago and do not remember such a problem. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: BIND Configuration
On Friday 29 June 2007 16:37:34 Tobias Roth wrote: Doug Barton wrote: [EMAIL PROTECTED] wrote: -- snip bind question -- And how exactly is this related to FreeBSD -STABLE? There is a tradition of answering basic SA questions on our lists, whether they are directly relevant to the list topic or not. If things get too far off base, users are generally directed to a more topic-specific list. I don't see any reason to alter that tradition. All right, I'll respect that and will refrain from sending similar messages in the future. My apologies to Minseok. For the record, I was sending a polite message explaining my point, which the above short quote fails to reflect. I just don't want people that didn't read my previous message to think I am a rude grumbler :-) heart-breaking ... guess Doug did in your favor cutting the not so polite stuff ;) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DDoS in FreeBSD 6.2-STABLE And Problen With The Clock
On Monday 11 June 2007 18:05:59 Chuck Swiger wrote: On Jun 11, 2007, at 1:57 PM, Mike Tancsa wrote: At 04:54 PM 6/11/2007, Chuck Swiger wrote: this unfortunate event by reordering instructions if needed, but if you wrote your own assembly, you could in fact do a hardware DDoS if you weren't careful. :-) Hi, I thought DDoS = _Distributed_ Denial of Service where multiple attacking devices gang up to attack a host. Yes, it is. Is your example not just a plain old Denial of Service (DoS) ? Yes, as it stands. But if you ship this code to other machines, perhaps it would then qualify as being _Distributed_? :-) / 2 clever switch but still wrong ... DDoS is ONE target and multi-source but not multi-target and local source :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: calcru: runtime went backwards, RELENG_6, SMP
On Wednesday 06 June 2007 17:17:28 Ivan Voras wrote: Dmitry Morozovsky wrote: Dear colleagues, on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP kernel I got zillions of 'runtime went backwards' errors, both on i386 and amd64 kernels. Upd: on GENERIC/amd64 kernel I got the same errors. Do you perhaps run with TSC timecounter? (that's the only cause I've notice that can generate this message). I got recently some squid panics where the machines freezed accusing calcru went backwards too. This happened on amd64 with sources from first week of may. I got it on 20-30 days uptime untouched smp dual-core amds and two opteron server. On all of them acpi-fast seems to be the counter. Anyway I did a cvsup and haven't seen the problem again so far. I did't get any message before, the first caused a panic and funny all panics happened almost the same hour last friday. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Friday 25 May 2007 23:36:24 Scot Hetzel wrote: On 5/25/07, JoaoBR [EMAIL PROTECTED] wrote: ... it tells to run script xorg-upgrade but this xorg-upgrade does not exist either The UPDATING entry does not tell you to run a script named xorg-upgrade, it tells you to run the script(1) command, which will then save all output to the file xorg-upgrade. oh really? h ... how can you possible defend this? A computer manual is not an approximation algorithm. Computer science is about three possible outcomes, 0, 1 or error. There is nothing else. Guess what you get when the input already is error? And perhaps you have access to computer users, give them this manual and ask to follow the instructions, guess what they will type in ... -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Saturday 26 May 2007 09:14:21 Stefan Lambrev wrote: This is off topic in this mail list. Why do not you please move the thread to freebsd-x11/freebsd-ports Most of us are subscribed to this list because they are interested in FreeBSD-STABLE, and if we want to read discussions about problems with specific ports we will subscribe to freebsd-ports/freebsd-x11 Thanks. ok, right if it was so simple unfortunately this port touch releng issues since /usr/X11R6 paths are part of the OS configuration defaults and are beeing migrated to /usr/local but may be I see this wrong and it's the maintainer's responsibility or am the only one who cares, what do you think, who should look at this? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Saturday 26 May 2007 10:22:23 Stefan Lambrev wrote: JoaoBR wrote: On Saturday 26 May 2007 09:14:21 Stefan Lambrev wrote: This is off topic in this mail list. Why do not you please move the thread to freebsd-x11/freebsd-ports Most of us are subscribed to this list because they are interested in FreeBSD-STABLE, and if we want to read discussions about problems with specific ports we will subscribe to freebsd-ports/freebsd-x11 Thanks. ok, right if it was so simple unfortunately this port touch releng issues since /usr/X11R6 paths are part of the OS configuration defaults and are beeing migrated to /usr/local but may be I see this wrong and it's the maintainer's responsibility or am the only one who cares, what do you think, who should look at this? There is no excuse for ignoring documentation. Better do NOT upgrade, if you do not plan to read manual/docs I'm pretty sure /usr/X11R6 is empty in base install and XFree and Xorg are not part of the FreeBSD. I'm excluding stable mail list because this is is off topic there. Your problem was discussed many times in freebsd-ports and freebsd-x11 And I'm pretty sure that you do not search help how to solve your problems, but you are just trolling. ops, let's see who is doing that first let me say, you respond blind or try to turn my words around because I didn't said anything of what you try to sell here second, I do not have a problem at all third, cut your ego-shit out to get a clear mind then read all again but with attention to find the issue but let me help you to find it, here is the shortcut for you: if you have src on your computer look into /usr/src/etc then look for the X11R6 string within the files then think and reread the shit you wrote here then, if still is something to add then talk again then, perhaps you spend a thought about if you are really preoccupied with your issues, with mine or with freebsd and it's users, because if not with the latter then you do not need to respond this issue at all because you didn't get it at all -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error from freebsd-stable Digest, Vol 207, Issue 6
On Friday 25 May 2007 07:21:24 Oliver Fromme wrote: First, I don't think atapicam is an exotic driver. I'm using it for several years (in fact, since it was an inofficial patch, before it hit the repository). It's working perfectly fine for me, including with today's RELENG_6. Second, if you run a mission-critical mail cluster (or similar things) and update it along RELENG_6 without proper testing, then you deserve to be shot in the foot. thank you for your consideration (or as serious or even as stupid) but it was ment to be kind of sarcastic input (don't shoot me, gotcha ... ) and keep smiling! :) anyway, beside of this confusing dmesg error I can write a cd with cdrecord but my k3b still crashs with this pthread/libpthread advice and don't get it right, I rebuild at night k3b with -R and finished fine but soon I put a cd into the drive k3b still crashes, it also crashes when a cd is in when starting it seems that Andy and Robert can use k3b on amd64 on their systems somebody has an idea what might be wrong here on my computer (beside the latter consideration of course)? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Friday 25 May 2007 13:54:04 Oliver Fromme wrote: JoaoBR wrote: Roland Smith wrote: It didn't. All the drivers were in one huge package, the X server. Now they are in seperate ports. But the xorg or xorgs-drivers meta-ports should install all of them. ok, that is what I ment, the better way would be that portupgrade installs them all as before (when they were in the package) That's exactly what happens when you install the xorg meta port (as explained in the UPDATING instructions). ok but the meta port is what the name says and probably not interesting for everybody like kde3 meta port, same thing, big big big Tools like portupgrade and portmaster and even the ports system are great but they have their limitations. I think they are kept relatively simple for a reason. It's much better to have a simple (maintainable) tool that does 95% of the jobs well than to build an extremely complicated ACME contraption that can cover all the corner cases and oddball situations. It's just not worth the effort. I agree and totally understandable but when there is a big change involved then it would be wise to advise more clearly what is happening from within the upgrade process because almost nobody reads the files I think that's wrong. Almost everybody reads UPDATING. Those who don't start threads on one of the mailing lists. may be or may be not, what I want to say is that when something was ever a certain way then a sudden change need to be better adviced, especially long before the change in fact occurres. Same as a power out, you are used to having power so when interrupted without previous advice you may not agree. Or your street is twoway, suddenly they change it into oneway and exactly the contrary direction you are used to leave your house each morning. So you crash into a car i bet you are not wanting to hear : oh silly you haven't read the sign? and more I guess you sure will sue the city and held them responsible because they did not advice you properly in time. And that is exactly the same thing with xorg, ipfw, /etc or anything which we got used to. And I tell you, each time in my live I typed X11R6 I thought jeee, who might have invented this thing. Anyway, still so, you can not move it away without publishing it over and over anywhere to prevent this shit to happened. And especially not moving before you are sure the migration really works. Xorg is too big and too important and especially too much needed in our daily work. Knowing this all creates responsibility for whom dares to change the port and this guy need to be prepared to hear anything and to help everybody but not calling us stupid shitheads which do not read the book other ports do it for less and a message like local base has changed you need to edit your xorg.conf or something would do good here If someone refused to read UPDATING, then why would he not ignore a message that scrolls through the screen at some point? As others have already stated, there are very detailed instructions in /usr/port/UPDATING. You should not blindly update your ports without looking at that file. well well ... but the xorg advice even following step by step does not work and let you still with fixed not found and X dead ... and no need to ask geeing for script logs because there is no error Also this updating advice is kind of vage and incorrect and the sequence is wrong. Even if Kris gets pissed off again UPDATING is wrong: ...try moving aside your /etc/X11/xorg.conf and allow X to auto-create it because it does not autocreate but use defaults ... it suggest to do portupgrade -Rf libXft which obviously upgrades xorg but does not install the meta port ... it tells to run script xorg-upgrade but this xorg-upgrade does not exist either and at the end it does not really explain anything what happens and it seems to be exactly what it is starting with: welcome to a mystical journey ... or better get fucked ... or get yourself a backup computer because you will be 48 hours without X ... :) so please dont tell me to read something what does not work as it should ... and then what ? everybody calling us silly stupids because we do not read, nice deal, yup, I like that, I really love it so then, imagin how much people do not have any chance to solve this problem: fixed not found and they do not claim, eventually they ask something but get RTFM back, so they step back so, and now? IMO before some sends me reading the manual I ask him to write a good one but not some crap what does not work either well then, what Roland wrote about worth and effort I agree, that is almost exactly like things work - but under normal conditions. A complete path migration of a port old and big as xorg need something better even cvsup must be envolved here, ldconfig, login.conf and a lot of other things which might cause troubles later
Re: atapicam cd error
On Thursday 24 May 2007 15:15:51 you wrote: On Wed, 23 May 2007 17:40:25 -0300 [EMAIL PROTECTED] ~ uname -a FreeBSD asus64.konav201.local 6.2-STABLE FreeBSD 6.2-STABLE #1: Tue Apr 17 17:38:20 HST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~ dmesg | grep acd acd0: DMA limited to UDMA33, device found non-ATA66 cable acd0: DVDR SONY DVD RW DW-Q120A/PYS1 at ata1-master UDMA33 acd1: DVDROM TOSHIBA ODD-DVD SD-M1802/1030 at ata1-slave UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x00 acd1: FAILURE - MODE_SENSE_BIG ILLEGAL REQUEST asc=0x24 ascq=0x0 K3B works fine after build kernel/world on above date. Hi so you are suggesting a rollback? I compiled on may 21st and 23rd and as Joe Altman confirmed too it's not working anymore on amd64 ... on i386 it's ok, may be this is a good moment then to change my backup strategy and use usb mem chips and kick atapicam out of the kernel -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error from freebsd-stable Digest, Vol 207, Issue 6
On Thursday 24 May 2007 12:12:34 Joe Altman wrote: __FBSDID($FreeBSD: src/sys/dev/ata/atapi-cam.c,v 1.42.2.5 2007/05/15 16:19:42 thomas Exp $); I am, and I just wanted to acknowledge your message, unfortunately I won't be able to further look into it immediately, as I'm about to leave for vacation... I'm keeping it on my inbound list, feel free to ping me if I don't get back to you within 2 weeks. All the best, Thomas. I have no clue why someone would insert changes into source, find (assuming he saw the discussion in April, on this list) those changes problematic, change the source somewhat to remedy those problems, put further changes into the source either causing new problems or reintroducing the old one; and when told at least once that Hey, there is a problem here; what can you tell me? replies Sorry, I'm on vacation. same as ipfw some weeks ago :S lucky us that atapicam is an exotic driver and not so widely used and still more lucky us that it is atapicam and not ahd or aac right? Sorry dear clients our mail cluster is out of service and when it does not work in three weeks or so please give me a new call ok ... -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Thursday 24 May 2007 16:10:02 Robert Marella wrote: On Thu, 24 May 2007 15:48:04 -0300 Hi so you are suggesting a rollback? I compiled on may 21st and 23rd and as Joe Altman confirmed too it's not working anymore on amd64 ... on i386 it's ok, may be this is a good moment then to change my backup strategy and use usb mem chips and kick atapicam out of the kernel Well, now I'm scared! I usually update via build kernel/world on Fridays but I missed a week or two. I was planing on doing it tomorrow. I don't think I'll have a need for K3B so for test purposes I will do it today and report back in an hour or so. Wish me luck. my dear ... no luck in site at this moment, don't wast your time, patience is what you need now and a tail -f on cvs-src ;) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Thursday 24 May 2007 17:19:00 Andy Fawcett wrote: ping# uname -a FreeBSD ping.int.athame.co.uk 6.2-STABLE FreeBSD 6.2-STABLE #0: Wed May 23 15:19:22 EEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PING amd64 (compiled from sources updated immediately before the build started, no later than 10.00 UTC on 23.5.2007) k3b is working absolutely fine on this box, I just managed to burn a CD followed by a DVD. so that is funny now so i tried and indeed I can write an iso with cdrecord which is your k3b version? I have k3b 1.0_2 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
atapicam cd error
Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 I can still mount and read bot not write anymore k3b crashes whith CD inserted or when I put one in telling about in pthread_testcancel () from lib/libpthread.so.2 in pthread_mutexattr_init () from lib/libpthread.so.2 in pthread_setconcurrency () from lib/libpthread.so.2 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wednesday 23 May 2007 13:05:40 you wrote: JoaoBR wrote: Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 I can still mount and read bot not write anymore k3b crashes whith CD inserted or when I put one in telling about in pthread_testcancel () from lib/libpthread.so.2 in pthread_mutexattr_init () from lib/libpthread.so.2 in pthread_setconcurrency () from lib/libpthread.so.2 It's fixed in latest 6-STABLE. hum, dont think so, I cvsupped yesterday and portstree also and it is still here -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wednesday 23 May 2007 13:46:55 Jeremy Chadwick wrote: On Wed, May 23, 2007 at 01:28:50PM -0300, JoaoBR wrote: On Wednesday 23 May 2007 13:05:40 you wrote: JoaoBR wrote: Hi, some knows how to solve this problema or what it is? acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 It's fixed in latest 6-STABLE. hum, dont think so, I cvsupped yesterday and portstree also and it is still here Did you buildkernel + installkernel + reboot after cvsup'ing? sure, but as make kernel KERNCONF=blabla after building world may be that I am running amd64 is the problem? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wednesday 23 May 2007 14:03:18 Jeremy Chadwick wrote: On Wed, May 23, 2007 at 01:49:33PM -0300, JoaoBR wrote: sure, but as make kernel KERNCONF=blabla after building world may be that I am running amd64 is the problem? I only run i386, so I can't confirm/deny. Sorry. :-( I am now compiling on my nb which is i386 to confirm this or compare thank's so far! -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wednesday 23 May 2007 16:26:25 Kris Kennaway wrote: On Wed, May 23, 2007 at 11:06:46AM +0300, Iulian M wrote: joke Yep... you have to rebuild everything. Not to fix the error but just because you don't read other threads on the ML /joke On another thread the conclusion was that installing x11-fonts/font-alias solved the fixed font problem. Speaking of not reading other threads, you might also look closer to home ;) Adding font-alias would just be treating the next symptom, and then you'll probably find that something else still doesn't work because it is also missing. As I've said a *number* of times already (and as is mentioned in the UPDATING instructions), install the x11/xorg port to obtain a complete installation. I also haven't read anything and got terrible caught by this 7.2 xorg thing I guess that the most shit comes from the path change and that portupgrade deos not tell anything about the old default /usr/X11R6/lib/X11/fonts change to /usr/local/lib/X11/fonts. Kind of sed operation would have solved this easily without bothering anyone Seems it is necessary to delete manually the old font dirs because portupgrade does not. so then most people may find out that editing the font paths in xorg.conf will solve the problem at the end and not to forget the new X path in kdmrc which also is a good one when saying a msg as cannot execute instead of is not there ... :) font-alias also does wierd things and creates font.alias even for fonts which are not installed, let's say cyrillic for instance, not sure if this is right, anyway, font-alias is not necessary I think and kind of lame that portupgrade xorg does not install the modules, that is a funny strike uninstalling xorg and installing the meta port also does not solve the issue ... but installs some zillions of font crap which I can not believe that somebody still use them but it was a funny day and useful to learn finally something about xorg which before 7.2 was a really too easy going install :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atapicam cd error
On Wednesday 23 May 2007 14:03:18 Jeremy Chadwick wrote: On Wed, May 23, 2007 at 01:49:33PM -0300, JoaoBR wrote: acd0: CDRW HL-DT-ST GCE-8527B/1.02 at ata0-master UDMA33 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 cd0 at ata0 bus 0 target 0 lun 0 cd0: HL-DT-ST CD-RW GCE-8527B 1.02 Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [1 x 2048 byte records] acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 acd0: FAILURE - READ_TOC ILLEGAL REQUEST asc=0x24 ascq=0x00 sure, but as make kernel KERNCONF=blabla after building world may be that I am running amd64 is the problem? I only run i386, so I can't confirm/deny. Sorry. :-( ok I compiled on i386 it's ok, also k3b works fine I recompiled amd64 world and kernel to be sure and the problem persists -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wednesday 23 May 2007 17:51:34 Roland Smith wrote: On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote: I also haven't read anything and got terrible caught by this 7.2 xorg thing Says it all, really. :-) you're not laughing at me aren't you? and kind of lame that portupgrade xorg does not install the modules, And how is portupgrade to know which specific drivers you need? good question deserve good answers: how the heck portupgrade did it before? There will always be big ports changes that exceed the capabilities of the automated ports management tools and need manual intervention. absolutely, but only partial correct because the tools are perfectly capable, the thing is that the process is not really thought through enough when publishing it -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg 7.2 start problem
On Wednesday 23 May 2007 18:46:41 Roland Smith wrote:
On Wed, May 23, 2007 at 06:18:12PM -0300, JoaoBR wrote:
On Wednesday 23 May 2007 17:51:34 Roland Smith wrote:
On Wed, May 23, 2007 at 05:29:54PM -0300, JoaoBR wrote:
I also haven't read anything and got terrible caught by this 7.2 xorg
thing
Says it all, really. :-)
you're not laughing at me aren't you?
A little. Ignoring /usr/{ports|src}/UPDATING usually has predictable
results. Been there, done that. :-)
good to know, so at the end nobody is alone and some beast will bite me again
sooner or later at the same place :)
and kind of lame that portupgrade xorg does not install the modules,
And how is portupgrade to know which specific drivers you need?
good question deserve good answers: how the heck portupgrade did it
before?
It didn't. All the drivers were in one huge package, the X server. Now
they are in seperate ports. But the xorg or xorgs-drivers meta-ports
should install all of them.
ok, that is what I ment, the better way would be that portupgrade installs
them all as before (when they were in the package)
I believe that is unusual that some de-installs xorg and installs the meta
port then and also I am not sure but I believe that xorg needs some drivers
in any case so it should be a necessary step or dependency here
That's funny. :-) If you can't be bothered to read UPDATING, you are not
the person to tell the maintainers that they haven't thought it
through.
yup, that is right but life is hard either way and it is never fair to all of
us, but then, thinking well, we might discover that the critics are ever a
valid input even if appear to one or another as offense they might not been
thought to be so
Tools like portupgrade and portmaster and even the ports system are
great but they have their limitations. I think they are kept relatively
simple for a reason. It's much better to have a simple (maintainable)
tool that does 95% of the jobs well than to build an extremely
complicated ACME contraption that can cover all the corner cases and
oddball situations. It's just not worth the effort.
I agree and totally understandable but when there is a big change involved
then it would be wise to advise more clearly what is happening from within
the upgrade process because almost nobody reads the files especially when he
portupgraded flawless something like xorg for years, even from x86 to xorg
was a no-issue at all but there was a scary name-change.
other ports do it for less and a message like local base has changed you need
to edit your xorg.conf or something would do good here
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fast rate of major FreeBSD releases to STABLE
On Thursday 17 May 2007 15:10:06 Jeremy Chadwick wrote: On Thu, May 17, 2007 at 05:51:07PM +0100, Gavin Atkinson wrote: On Thu, 2007-05-17 at 16:30 +0100, Chris wrote: A more user friendly installer so datacentres stop been put off FreeBSD. Although work on a new installer is ongoing, nobody ever seems to be clear what the problems are with the current installer that they are trying to fix. I believe PC-BSD uses a different installer, which is the current candidate, although I personally prefer the current one. I'm guessing a new installer never make everybody happy. As someone who has had to show many people how to use the FreeBSD installer, I can confirm what Chris is referring to. datacenters probably do not use the installer at all but that is another point further to the points you mentioned already I like to add that the most missing thing is that the installer does not suggest a default disk layout. Jumping directly into fdisk is where a user aborts and also as mentioned, since disk geometry is not necessary to show at all, first because it is mostly wrong and second who cares. This is not for a standard installer and should be an option (if). a user does not know what fdisk is and what to do (and eventually he does not even speak nor read english so the options list is what scares him still more) so he is bailing out here and for my understandings this is the most important point which cause freebsd does not make it to the user's desktop. So a better solution would be to invert the current situation and give a default layout for fdisk AND labels which can be accepted (OK) or cancelled and if then jumps into fdsik for advanced users My personal suggestion is to invert the IP screen and put GW and DNS after IP and mask fields what is kind of more usual and logical -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clock too slow - big time offset with ntpdate
On Tuesday 01 May 2007 18:10:38 Martin Dieringer wrote: not to mention the energy waste power off solve this if it is really your issue ... :S -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
make -D recent problem?
make -DFORCE_PKG_REGISTER [re]install do install a second port (duplicate) is this a bug or do I have some problem on this machine? 6.2-STABLE FreeBSD 6.2-STABLE #0: Fri Apr 27 20:46:32 BRT 2007 portsnap update I did today -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: watchdog network card
On Tuesday 10 April 2007 01:24, Andrew Reilly wrote: Wow. Somehow we've slipped through a one-year timewarp: On Tue, Mar 28, 2006 at 07:47:54AM -0300, JoaoBR wrote: On Tuesday 28 March 2006 07:40, Andrew Reilly wrote: After the last rebuild on my amd64-x2 box, both the nve ethernet on the motherboard and the dc ethernet that I had been using to work around other problems in the nve driver stopped working in this way. DEVICE_POLLING and ifconfig...polling has got me going again. I thoroughly recommend it. nve does not run polling mode but dc does I guess you have an IRQ conflict, nve and dc on the same hw interrupt, and that setting dc in polling mode worked around this problem then you could check vmstat -i with and without polling enabled to see it Thanks for the tip. I haven't been running dc or nve for about a year, now :-) Nfe has been working beautifully for me, without polling. I guess that I should have a look to see if nve has improved in the interim, but it's difficult to make oneself mess with something that isn't broken... nfe appears to work much better (also with polling) and flawless. I tried one and another time nve but nfe is what works, at least on amd64 and newer hardware so probably you don't need to waste your time ;) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Wednesday 04 April 2007 00:05, you wrote: Console is not intended for everyday use! You should login to your FreeBSD box with ssh-client of your choise and from the OS of your choise (preferably from graphic mode). please stay on topic the question is not what one should or not but to hook into your talk, if there is a console it can be used as wanted 1024x768 is more than enough for 120x50 virtual terminals. may be for you, for me and lot of other users it is definitly not p.s. Or you just trolling? RH is rather professional, but definitely not because of graphics in console... :-\ don't try to be smart with me nobody said that RH is professional because of it's graphics in console I said that for example RH looks professional with the graphic boot they offer that is very easy to understand, look: A/ fits much more info on one screen B/ line wraps do not complicate orientation on screen both points are very usefull debugging any kind of problem or tailing logs -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Wednesday 04 April 2007 04:49, Peter Jeremy wrote: On 2007-Apr-03 14:27:00 -0300, JoaoBR [EMAIL PROTECTED] wrote: simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM I don't understand why displaying a silly graphic whilst hiding the boot messages is professional. If you really need eye-candy to make your FreeBSD box look like it's running MS Windows, see splash(4) uuuhf man, my example of RH's graphical boot is *not* about a picture and this wasn't at all a comparism to any graphics in picture form, you should pay more attention to the whole thread instead of junking in here this thread is about displaying *text console* in 1024x768 and so I compared RH 8x8 boot text to fbsd's 16x16 mode and it is not about professional looking even if it was one of the points as example, it is extremely useful to get more information on one screen and still more usefull not having linewraps and I do not even get why this is beeing fight because it is natural having bigger screens and smaller letter to see more at once, unless you have disabilities and need the big letters but that is another point of view -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Wednesday 04 April 2007 19:35, [EMAIL PROTECTED] wrote: On 04/04/07, JoaoBR [EMAIL PROTECTED] wrote: don't try to be smart with me nobody said that RH is professional because of it's graphics in console I said that for example RH looks professional with the graphic boot they offer Don't try to play dumb with us. You implied that it was when you wrote: simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM yeahh but did you read it really, all??? I guess not, at least it seems you didn't understood the sense, only a word and another and glued it together as you wanted in order to make some noise And both premises are patent nonsense, since they are both predicated on some bollocks notion of professionalism which likely started with the first school to sell MBAs via post. talk to the hand :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw add pipe broken?
On Tuesday 03 April 2007 05:53, Oliver Fromme wrote: Well, FreeBSD is mostly a volunteer project, so people work on it when they have time. we all know that, we could discuss the general issue deeply which might be usefull but might be misunderstood by people, anyway I like to answer your points but first I like to make clear that this is NOT a personal issue and I am not angry with Julian or anyone else, it is merely the issue itself so I hope you're all cool with this and nobody starts yelling. Admittedly, you're right that any changes should be tested. But in reality it's not always that easy. Some changes are complex so that not all possible things can be tested. And I do not agree with can not be tested, this was eventually ok in 97's ipfw code ... some changes _seem_ trivial and obviously don't need to be tested (especially if a nearly identical change ran for months in -current), but then that might turn out to be a mistake. Errare humanum est. (Translation: shit happens.) ;) thanks for the latin translation but of course it happens, but is not the point please do it all or don't do it, ipfw is an mature and essential part where we do not espect such sudden surprises in releng6 to happen First, if you absolutely don't want surprises, then you should run RELENG_6_2, not RELENG_6. If you run RELENG_6, you should be prepared and able to deal with breakages. ok, as you say shit happens but we should be aware of where it happens, some exotic driver or hardware, let's say here sk,nve or re - ok, BUT ipfw certainly is not experimental code and do not depend on hardware as long you have any which runs fbsd (Even if it's unusual that RELENG_x breaks, it does happen sometimes. The FreeBSD Handbook chapter staying stable contains appropriate warnings.) like I said before, the playground is CURRENT for this and you talk about the handbook, then let's read all: ... the general assumption that they have first gone into FreeBSD-CURRENT for testing ... (I guess this is meant for new code but law for mature code) this assumption is important because it is kind of rule, common sense like speeding a Ferrari over a bumpy street it might break but a Fiat not, so this would not be a suprise but cooking the motor at 80mph on a highway is not the thing we need to be prepared for and is certainly a bad thing where the car maker should look at before releasing it and so I feel right to say, essential and mature code *needs* to be tested extensively before committing it, exotic or new code not This makes more sense today as FreeBSD has an important position, but not only has it but also has to defend it. This makes it necessary that the common sense of responsibility is there and this is the next assumption, a comitter should have this responsibility. (which certainly does not exclude the risc of errors, but reduce it) Also no secret and common sense is that releng_6 is widely used on production servers. So ipfw is not supposed to be broken. My personal suggestion is that certain code like ipfw needs to be marked for double check, so there should be one other responsible reviewing AND testing it before comitting it, this probably is the only way to prevent or reduce the error rate And second, it's not a big deal to go back to Friday's sources until Julian had time to fix the issue, is it? no it is not but it is not the point thank's -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Tuesday 03 April 2007 12:18, Freddie Cash wrote: I don't understand why people who want high resolution consoles don't run X. that is very easy to understand, look: A/ fits much more info on one screen B/ line wraps do not complicate orientation on screen both points are very usefull debugging any kind of problem or tailing logs also, there are people out who say FreeBSD is very perfect for remotecontrol, the letters are so big you can see them from far away :) simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Tuesday 03 April 2007 15:02, Freddie Cash wrote: On Tuesday 03 April 2007 10:27 am, JoaoBR wrote: On Tuesday 03 April 2007 12:18, Freddie Cash wrote: Just a note that the above should read: On Monday 02 April 2007 05:45 pm, Daniel O'Connor wrote: As I am not the one who wrote the following line, but Daniel is. :) sorry, no bad intention I might have highlighted the right quote in th ewrong msg before hitten the reply button I don't understand why people who want high resolution consoles don't run X. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ipfw add pipe broken?
it seems I can not add pipes with releng6 sources from the last days ipfw add pipe 1 ip from any to any ipfw: getsockopt(IP_FW_ADD): Invalid argument or any similar add pipe command does not work (sure I have options DUMMYNET in kernel) world and kernel from march 29 works still fine anything changed? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
scsi/mpt problem with latest source
with new sources I get an mpt error which is not present with sources from march 28 mpt0: LSILogic 1030 Ultra4 Adapter port 0xdc00-0xdcff mem 0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on pci1 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 ... (xpt0:mpt0:0:-1:-1): reset bus ... da0 at mpt0 bus 0 target 0 lun 0 da1 at mpt0 bus 0 target 1 lun 0 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw add pipe broken?
On Sunday 01 April 2007 12:04, Mike Tancsa wrote: At 10:07 AM 4/1/2007, JoaoBR wrote: it seems I can not add pipes with releng6 sources from the last days ipfw add pipe 1 ip from any to any ipfw: getsockopt(IP_FW_ADD): Invalid argument or any similar add pipe command does not work (sure I have options DUMMYNET in kernel) world and kernel from march 29 works still fine anything changed? There were a bunch of MFCs. When I try from a kernel today, seems the thing happened on saturday by all respect to Julians work but with ipfw broken and sunday fucked up ... kind of scaring when seeing I have no time to check, I do it on tuesday or I need to do the userland ipfw too to add some new features, but, not today.. please do it all or don't do it, ipfw is an mature and essential part where we do not espect such sudden surprises in releng6 to happen -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi/mpt problem with latest source
On Sunday 01 April 2007 14:02, Matthew Jacob wrote: pleasep pooint out what the error is, and are you booting verbose? On 4/1/07, JoaoBR [EMAIL PROTECTED] wrote: with new sources I get an mpt error which is not present with sources from march 28 mpt0: LSILogic 1030 Ultra4 Adapter port 0xdc00-0xdcff mem 0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on pci1 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.2.14.0 ... this reset bus didn't and do not happen with some day older sources: (xpt0:mpt0:0:-1:-1): reset bus no, I do not boot verbose ... da0 at mpt0 bus 0 target 0 lun 0 da1 at mpt0 bus 0 target 1 lun 0 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi/mpt problem with latest source
On Sunday 01 April 2007 14:49, Matthew Jacob wrote: this reset bus didn't and do not happen with some day older sources: (xpt0:mpt0:0:-1:-1): reset bus Well, don't worry about it. It's always been happening. no, I do not boot verbose Thanks. I'll make this message show up under 'bootverbose' only., good to know, so it was hidden before would you mind to tell why it happens and this -1 values ? thank's for your attention ... da0 at mpt0 bus 0 target 0 lun 0 da1 at mpt0 bus 0 target 1 lun 0 -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ipfw add pipe broken?
On Sunday 01 April 2007 15:22, Mike Tancsa wrote: At 11:55 AM 4/1/2007, JoaoBR wrote: by all respect to Julians work but with ipfw broken and sunday fucked up ... kind of scaring when seeing I have no time to check, I do it on tuesday or I need to do the userland ipfw too to add some new features, but, not today.. please do it all or don't do it, ipfw is an mature and essential part where we do not espect such sudden surprises in releng6 to happen I seriously doubt he intentionally meant to break it Accidents man sure not, no one said that happen. Roll your sources back to Friday and you will be OK until yaya but essential and especially mature code should be tested before comitting changes I guess, I believe that ipfw wasn't tested before beeing hacked and comitted this time, and overall btw, there was an alert and reply to the commit msg on cvs which then was politly ignored until tuesday ... luck that it wasn't the bootstrap or something its sorted out. Remember, its a best effort, not perfect effort project. sure, but when became perfect the honor is welcome as it comes for free when it went wrong ;) ---Mike João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
amd64 ahd scsi error/problem with tyan mb
hi some else has seen this? With more then 2 scsi disks on one channel I get the error below. The machine seems to work on all disks after then. With one or two disks the machine boots well. The error does not appear with FC6 and Tyan support argues a freebsd driver problem. some idea what I can do? Waiting 10 seconds for SCSI devices to settle ahd0: Invalid Sequencer interrupt occurred. Dump Card State Begins ahd0: Dumping Card State at program address 0x23c Mode 0x0 Card was paused INTSTAT[0x0] SELOID[0x2] SELID[0x10] HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] DFFSTAT[0x33] SCSISIGI[0x0] SCSIPHASE[0x0] SCSIBUS[0x0] LASTPHASE[0x1] SCSISEQ0[0x0] SCSISEQ1[0x12] SEQCTL0[0x0] SEQINTCTL[0x6] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] QFREEZE_COUNT[0x3] KERNEL_QFREEZE_COUNT[0x3] MK_MESSAGE_SCB[0xff00] MK_MESSAGE_SCSIID[0xff] SSTAT0[0x0] SSTAT1[0x0] SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0x0] SIMODE1[0xa4] LQISTAT0[0x0] LQISTAT1[0x0] LQISTAT2[0x0] LQOSTAT0[0x0] LQOSTAT1[0x0] LQOSTAT2[0x0] SCB Count = 16 CMDS_PENDING = 0 LASTSCB 0x CURRSCB 0xd NEXTSCB 0xff00 qinstart = 36 qinfifonext = 37 QINFIFO: 0xf WAITING_TID_QUEUES: Pending list: 15 FIFO_USE[0x0] SCB_CONTROL[0x48] SCB_SCSIID[0x7] Total 1 Kernel Free SCB list: 14 13 1 2 3 4 5 6 7 8 9 10 11 12 0 Sequencer Complete DMA-inprog list: Sequencer Complete list: Sequencer DMA-Up and Complete list: Sequencer On QFreeze and Complete list: ahd0: FIFO0 Free, LONGJMP == 0x8000, SCB 0xe SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xd SEQIMODE[0x3f] SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89] SG_CACHE_SHADOW[0x2] SG_STATE[0x0] DFFSXFRCTL[0x0] SOFFCNT[0x0] MDFFSTAT[0x5] SHADDR = 0x00, SHCNT = 0x0 HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10] LQIN: 0x8 0x0 0x0 0xe 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 ahd0: LQISTATE = 0x0, LQOSTATE = 0x0, OPTIONMODE = 0x42 ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x1 ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 SIMODE0[0xc] CCSCBCTL[0x0] ahd0: REG0 == 0x7ffd, SINDEX = 0x10e, DINDEX = 0x106 ahd0: SCBPTR == 0xe, SCB_NEXT == 0xff00, SCB_NEXT2 == 0xd CDB 12 20 0 80 8 25 STACK: 0x237 0x2 0x0 0x0 0x0 0x0 0x0 0x0 Dump Card State Ends SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x0 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 Copied 18 bytes of sense data offset 12: 0x70 0x0 0x6 0x0 0x0 0x0 0x0 0xa 0x0 0x0 0x0 0x0 0x29 0x2 0x2 0x0 0x0 0x0 da0 at ahd0 bus 0 target 0 lun 0 da0: MAXTOR ATLAS15K2_36WLS JNZH Fixed Direct Access SCSI-3 device da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 35074MB (71833096 512 byte sectors: 255H 63S/T 4471C) da1 at ahd0 bus 0 target 1 lun 0 da1: SEAGATE ST373207LW 0005 Fixed Direct Access SCSI-3 device da1: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) da2 at ahd0 bus 0 target 2 lun 0 da2: SEAGATE ST373207LW 0005 Fixed Direct Access SCSI-3 device da2: 320.000MB/s transfers (160.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 70007MB (143374744 512 byte sectors: 255H 63S/T 8924C) Trying to mount root from ufs:/dev/da0s1a -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
scsi error with latest sources
hi, somebody knows to interprete this scsi error I get after upgrading amd64 with sources from 26/03/ or is this a hardware problem? Mar 27 17:48:45 msrv kernel: (da0:ahc0:0:3:0): WRITE(10). CDB: 2a 0 0 60 1 1f 0 0 20 0 Mar 27 17:48:45 msrv kernel: (da0:ahc0:0:3:0): CAM Status: SCSI Status Error Mar 27 17:48:45 msrv kernel: (da0:ahc0:0:3:0): SCSI Status: Check Condition Mar 27 17:48:45 msrv kernel: (da0:ahc0:0:3:0): UNIT ATTENTION asc:29,1 Mar 27 17:48:45 msrv kernel: (da0:ahc0:0:3:0): Power on occurred field replaceable unit: 1 Mar 27 17:48:45 msrv kernel: (da0:ahc0:0:3:0): Retrying Command (per Sense Data) Mar 27 17:49:23 msrv kernel: (da0:ahc0:0:3:0): READ(10). CDB: 28 0 0 ef 93 3f 0 0 20 0 Mar 27 17:49:23 msrv kernel: (da0:ahc0:0:3:0): CAM Status: SCSI Status Error Mar 27 17:49:23 msrv kernel: (da0:ahc0:0:3:0): SCSI Status: Check Condition Mar 27 17:49:23 msrv kernel: (da0:ahc0:0:3:0): UNIT ATTENTION asc:29,1 Mar 27 17:49:23 msrv kernel: (da0:ahc0:0:3:0): Power on occurred field replaceable unit: 1 Mar 27 17:49:23 msrv kernel: (da0:ahc0:0:3:0): Retrying Command (per Sense Data) Mar 27 17:50:01 msrv kernel: (da0:ahc0:0:3:0): Unexpected busfree in Data-in phase Mar 27 17:50:01 msrv kernel: SEQADDR == 0x96 Mar 27 17:50:09 msrv kernel: (da0:ahc0:0:3:0): READ(10). CDB: 28 0 3 19 a0 1f 0 0 4 0 Mar 27 17:50:09 msrv kernel: (da0:ahc0:0:3:0): CAM Status: SCSI Status Error Mar 27 17:50:09 msrv kernel: (da0:ahc0:0:3:0): SCSI Status: Check Condition Mar 27 17:50:09 msrv kernel: (da0:ahc0:0:3:0): UNIT ATTENTION asc:29,1 Mar 27 17:50:09 msrv kernel: (da0:ahc0:0:3:0): Power on occurred field replaceable unit: 1 Mar 27 17:50:09 msrv kernel: (da0:ahc0:0:3:0): Retrying Command (per Sense Data) Mar 27 17:54:02 msrv kernel: (da0:ahc0:0:3:0): Unexpected busfree in Message-in phase Mar 27 17:54:02 msrv kernel: SEQADDR == 0x106 Mar 27 17:54:10 msrv kernel: (da0:ahc0:0:3:0): WRITE(10). CDB: 2a 0 5 d3 85 7f 0 0 80 0 Mar 27 17:54:10 msrv kernel: (da0:ahc0:0:3:0): CAM Status: SCSI Status Error Mar 27 17:54:10 msrv kernel: (da0:ahc0:0:3:0): SCSI Status: Check Condition Mar 27 17:54:10 msrv kernel: (da0:ahc0:0:3:0): UNIT ATTENTION asc:29,1 Mar 27 17:54:10 msrv kernel: (da0:ahc0:0:3:0): Power on occurred field replaceable unit: 1 Mar 27 17:54:10 msrv kernel: (da0:ahc0:0:3:0): Retrying Command (per Sense Data) Mar 27 17:54:13 msrv kernel: (da0:ahc0:0:3:0): WRITE(10). CDB: 2a 0 5 72 6b 5f 0 0 20 0 Mar 27 17:54:13 msrv kernel: (da0:ahc0:0:3:0): CAM Status: SCSI Status Error Mar 27 17:54:13 msrv kernel: (da0:ahc0:0:3:0): SCSI Status: Check Condition Mar 27 17:54:13 msrv kernel: (da0:ahc0:0:3:0): UNIT ATTENTION asc:29,1 Mar 27 17:54:13 msrv kernel: (da0:ahc0:0:3:0): Power on occurred field replaceable unit: 1 Mar 27 17:54:13 msrv kernel: (da0:ahc0:0:3:0): Retrying Command (per Sense Data) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: scsi error with latest sources
On Tuesday 27 March 2007 18:17, you wrote: JoaoBR wrote: hi, somebody knows to interprete this scsi error I get after upgrading amd64 with sources from 26/03/ or is this a hardware problem? You either have a failing disk or a power supply that is underpowered and/or failing. In short, check your hardware =-) thank's! I changed two disks into 15k scsis and seems the ps was weak already and/or couldn't stand the faster spin after changing the ps the problem went away, so far ... -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.order wrong (ipfw)
On Saturday 17 March 2007 03:58, Mark Andrews wrote: nothing goes to this machine because by default everything is blocked until you permit it You're absolutely correct, however your original post seems to have taken many of us by surprise, causing some of us (at least me!) to assume that you've changed the default method to allow. I'm obviously misunderstanding, so I apologise for that, but I hope you can see the reasoning behind my comments with what I knew at the time. :) ipfw needs to be before networking or router discovery fails for IPv6. http://www.freebsd.org/cgi/query-pr.cgi?pr=conf/108589 as default any network connection will fail so long as you do not permit it If rtsol fails or is called to early it is an rtsol problem and not an ipfw problem I guess as another example, what if you set a ifconfig_nic0=inet hostname instead of IP address and this hostname is not in /etc/hosts and ipfw is still not up and named is far away to start, then, according to your idea we need to start named and ipfw before netif? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
rc.order wrong (ipfw)
since some time now it seems ipfw starts first of all, I think that is not correct rcorder: file `/etc/rc.d/ipfw' is before unknown provision `NETWORKING' rcorder: requirement `ppp' in file `/etc/rc.d/ipfw' has no providers. /etc/rc.d/ipfw I changed the order for my needs but it might be a good idea to fix this problem. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.order wrong (ipfw)
On Friday 16 March 2007 07:51, Oliver Fromme wrote: JoaoBR [EMAIL PROTECTED] wrote: since some time now it seems ipfw starts first of all, I think that is not correct No, it starts after networking is up, which is the correct behaviour, I think. it should rcorder: file `/etc/rc.d/ipfw' is before unknown provision `NETWORKING' rcorder: requirement `ppp' in file `/etc/rc.d/ipfw' has no providers. That sounds like you have accidentally deleted the files /etc/rc.d/NETWORKING and /etc/rc.d/ppp (or forgot to run mergemaster properly after an update). noo, both are there even if working as supposed NETWORKING is ordered before syslogd and ipfw should better start after syslogd -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.order wrong (ipfw)
On Friday 16 March 2007 08:52, Oliver Fromme wrote: rcorder: file `/etc/rc.d/ipfw' is before unknown provision `NETWORKING' rcorder: requirement `ppp' in file `/etc/rc.d/ipfw' has no providers. That sounds like you have accidentally deleted the files /etc/rc.d/NETWORKING and /etc/rc.d/ppp (or forgot to run mergemaster properly after an update). noo, both are there Then they are broken on your machine. Did you check the provide and require lines in them? The ordering works perfectly fine for me on all of my machines. I checked yes, sure even if working as supposed NETWORKING is ordered before syslogd and ipfw should better start after syslogd No, the packet filter and forwarding rules must be in effect as early as possible, i.e. before any network daemons are started (which includes syslogd). There- fore it must be a requirement of NETWORKING. could you explain your opinion? I don't agree to what you say what sense does it make to have my forward rules up but natd still not? what sense does it makes logging while syslog is not up? If IPFW rules where loaded after daemons such as syslogd are started, that would break several of my machines. (And on some others which have default to accept it would even open a security hole by introducing a race- condition.) oops, so what would break there? I thought, the defaults are to support other defaults and not particular settings because freebsd's ipfw default is to deny all and not to accept the security hole you mention I can not see anywhere ipfw is not on by default so you say here that FreeBSD has a default security hole because it's default is having no ipfw rules? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.order wrong (ipfw)
On Friday 16 March 2007 10:40, Pertti Kosunen wrote: JoaoBR wrote: I don't agree to what you say what sense does it make to have my forward rules up but natd still not? what sense does it makes logging while syslog is not up? What would it forward log when network isn't up? man, starting ipfw after network does not mean that the network is not up -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: rc.order wrong (ipfw)
On Friday 16 March 2007 18:50, Jeremy Chadwick wrote: On Fri, Mar 16, 2007 at 06:00:30PM -0300, JoaoBR wrote: man, starting ipfw after network does not mean that the network is not up Okay, imagine this order: 1) Kernel starts 2) Network driver is loaded 3) Link is brought up 4) Interface is configured for IP (manually or via DHCP) 5) Firewall rules (ipfw or pf) are applied Do you realise that between steps #4 and steps #5 there is a small window of time where someone may be able to send packets to your machine and get responses which would normally be blocked by ipfw/pf? nono that is not exactly how it works unless you change ipfw's default behaviour which is deny all from any to any, nothing goes to this machine because by default everything is blocked until you permit it -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getting garbage faster using FreeBSD?
On Wednesday 21 February 2007 07:16, Ian Smith wrote: It's primarily for item #1 that I hadn't mentioned this earlier, as most readers of -STABLE users are probably looking for a more scalable solution. Scaleable? Easy .. For 2.5 drives, a tack hammer does nicely. For 3.5 to 5 drives, a claw hammer suffices. For 14? IBM disk packs a small sledge is optimal (if short of tanks!) guys I really enjoy this conversation! great stuff! I am just wondering why the list sentinels haven't mucked up yet ;) they almost shot at us for an issue much closer to the list subject. It was about spam and mail server so I am coming to the conclusion that the up-muckers must be professional spammers which of course hate it when some discards their tricks and they appearently are very interested in learning how to destroy the evidence LOL ... or are they still under carnival-side-effects??? here my contribution, even if most like the hard way, h2so4 would do it much smoother and has absolutely no scalability problems at all ;) and the emergency package fit in the laptop case! -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Very slow umass in 6.2-RC2
On Saturday 17 February 2007 09:36, Michael Nottebrock wrote: Has anyone ever managed to get some USB 2.0 - like speeds out of ehci anyway? I'm not seeing quite such abysmal performance as Kevin did, but I don't even need to benchmark to be certain that Windows does *much* better with the devices I own. Here are some numbers: First up, the controller: ehci0: VIA VT6202 USB 2.0 controller mem 0xdfffbd00-0xdfffbdff irq 21 at device 16.4 on pci0 usb4: VIA VT6202 USB 2.0 controller on ehci0 usb4: USB revision 2.0 To be sure the umass device is actually a child of the ehci device: dev.umass.0.%parent: uhub4 dev.uhub.4.%parent: usb4 This is a Panasonic Pro High Speed series 512mb SD-CARD, which theoretically supports burst transfer rates up to 20MB/s on a USB 2.0 multi card reader: da2 at umass-sim0 bus 0 target 0 lun 2 da2: Hama CardReaderMMC/SD 1.9C Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: 472MB (967680 512 byte sectors: 64H 32S/T 472C) I get something between 2-2.5MB when copying from my Sony camera which has a 1Gb card. It does not matter if I copy 10 or 400Mb it is ever the same. I never uploaded anything and have no windows to compare but I ever thought the low speed is caused by the device and not by the computer's port. I have a MP3 with 512MB no card (integrated memory or something) and I can upload with 5-6Mb/s to it. It makes no difference if I connect it to ohci or ehci ports. Then from my cellphone I never get more than 800kb/s. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Tuesday 13 February 2007 04:57, Oliver Fromme wrote: Kevin Way wrote: Oliver Fromme wrote: But you called it confusing. That's just your personal perception. It doesn't mean it is confusing to everybody. If asked what -alias does, would you really reply it removes the primary IP, while leaving the alias? Be honest here. No, I wouldn't answer that, because there is no such thing as a primary IP. All IPs on an interface are equal. The term alias exists only for historical reasons, and it's clearly becoming obsolete. my dear friend I really do not know why you insist on writing this again and again. Firstable it is wrong what you say. IP Aliasing is a correct and perfect term, used since it is possible to set more then one IP and people use it all over the world, in simple networks and specially in hosting environments. So it probably never will become obsolete because firstable it is THE word in use everywhere, it is grammatically correct and it is easy to understand. It does not exist for historical reasons. It is part of IP history and an important one, exist because it is in use and so it will stay with us - in all OSs ... and almost all languages it is understood as it is - perfectly by definition. The only correct thing you say here is that all IPs are equal - and - nobody EVER said something different. Aliasing does not say anything about priority of the Ip it is simply related to the time the interface was set with the IP so the first IP is the one which was set first and the first alias is the one which was set after. So by common sense alias describes an additional IP address which was add to an already existent address. Otherwise it would not be an alias. This understanding, which is completely correct, makes it wrong that ifconfig nic -alias removes an IP address which is unique on this interface. At least when done without warning. And also makes it wrong to remove the IP which was set first on this interface since it is not an alias by common understanding even if it is equal in technical functions. Then, at the end it is perfectly ok when people say primary address because it might be for them THE address of THEIR machine. This is manner of speaking and they are probably fully aware of that the other IPs are equal. And so this must be bethought, you can not run against common sense even if there might be something not exactly expressed. By all respect, you are running against the wall here. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Monday 12 February 2007 12:26, Oliver Fromme wrote: JoaoBR [EMAIL PROTECTED] wrote: ifconfig nic -alias is obviously a wired and confusing behaviour It might be confusing to you. Personally I think that the current behaviour isn't that far off. the question is not you or me, I guess that you are like me perfectly capable of working around messed things. But that does not make it being right or acceptable. First you need to be aware that there is no distinction between a primary IP and alias IPs (such a distinction existed historically, but it's gone). All of the IPs on an interface are equal, just like hardlinks on a file. I said this in shorter words in my post but it is not the point at all. The -alias parameter simply removes an address from an man page tells us that it removes THE specified address ... not AN address interface. The term alias should really be avoided because it is misleading. You can use delete or remove which do the same thing. I think -alias should really be regarded to exist for backwards compatibility only. Personally I always use delete. it is not misleading and it is a perfect term. With alias you add secondary addresses to an interface. Like secondary is probably the better word, as cisco does, but what we have is alias and that is ok. It could be any other word so long as it works as it should. (We do have add also I remember.) also don't forget the following, alias is a perfect and usual term, then when I can add an IP address with the alias cmd then -alias should remove it. I know that I can add the first IP also with alias but that is not the usual way. Also do not forget that the usual way since ever is ifconfig_nic_alias0 to add one. So this thing is confusing. If no IP address is specified, then it's not completely nonsensical to remove the first address. In fact I've used that short-cut to quickly remove the only address from an interface. I've used ifconfig xyz0 delete quite a lot. the man page tells us that -alias removes *the* specified address and not the first, also the man page does not say that there is any further action when *no* IP address specified delete is according to the man page another word for -alias, that means, using grammatical logic that -alias is the main command, then according to the man page there is no other command as -alias *IP* to remove an IP address and -alias only should not remove anything then already beeing here there is more, ifconfig nic alias does not return anything at all That's the same as ifconfig nic add. If you don't tell it anything to add, then it won't add anything, of course. Remember that UNIX always tries to do exactly what you tell it to dao. ;-) you see, now you apply logic because you want to and when not not ... ;) to let it more clear what I mean, you say: you don't tell it anything to add so why the heck ifconfig nic -alias should remove one if I do not tell so? and ifconfig nic -alias on a nic w/o ip returns can't assign requested address ... That error corresponds to EADDRNOTAVAIL, which is the correct errno to return, because there's no address left on the interface. However, I agree that the message is a bit confusing to the unfamiliar. at least one agreement here :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Monday 12 February 2007 16:09, Oliver Fromme wrote: it is not misleading and it is a perfect term. With alias you add secondary addresses to an interface. Like secondary is probably the better word, No, not at all. As soon as you use the terms primary IP address and secondary IP addresses, you imply that they are not equal. But they are equal. It's just a list of IP addresses assigned to an interface which happens to have a certain order. nobody claims that there is an master-slave order or something, alias is the secondary in order of time, but not in value, I do not even understand why you talking so much about this, the point is more than clear Yes, that's why I wrote it should be changed to not contain the word alias anymore, but simply an enumerated list. If no IP address is specified, then it's not completely nonsensical to remove the first address. In fact I've used that short-cut to quickly remove the only address from an interface. I've used ifconfig xyz0 delete quite a lot. yes it is! it does not matter which word, without an IP address it should NOT remove anything the man page tells us that -alias removes *the* specified address and not the first, also the man page does not say that there is any further action when *no* IP address specified That's true. Usually if something is not documented, the behaviour is undefined. undefined is absolutely not similar to remove something .. delete is according to the man page another word for -alias, that means, using grammatical logic that -alias is the main command, No. It means that delete and remove are aliases for -alias. In reality they're simply equal. ;-) then according to the man page there is no other command as -alias *IP* to remove an IP address and -alias only should not remove anything It's not documented that way. As I wrote above. If something is not documented, that doesn't mean that it shouldn't do anything at all. In that case a _lot_ of things wouldn't work. :-) all commands which remove something usally say something when trying to use without value, rm, rmdir, rmuser ... I really do not remember any other then -alias which does so you see, now you apply logic because you want to and when not not ... ;) to let it more clear what I mean, you say: you don't tell it anything to add so why the heck ifconfig nic -alias should remove one if I do not tell so? In the case of adding something, what should be added if nothing is specified? Should the tool invent an arbitrary IP address and add it? Now that would be nonsensical. But when removing something without specifying which one, it makes some sense to simply remove the first existing address on that interface. It would even be OK with me to remove the last one, or an arbitrary one -- I use that shortcut mostely when I need to remove the only address from an interface (or all existing addresses), so it doesn't matter. come on, now your are looking up a way out of this mess ... In fact, it might also make sense to enhance the syntax to allow the specification of a number, for example ifconfig xyz0 delete #2 would remove the second address my god what a horrible idea is that! do you remember # in UNIX the command ifconfig nic -alias IP is OK, perfect, even delete is, the problem and the only problem is that both remove without specifying a value a value and that *IS* wrong behaviour, otherwise *you* must agree that rm removes the first file it finds, rmuser the first user and and and, that is wrong, documented or not However, such a feature will run into problems when the set of ip addresses is not an ordered list anymore, which might very well happen in the future. Then there will be no first and last anymore, but instead the interface will just have an unordered set of IP addresses. In fact I wish that would already be the case, so people saying primary and secondary would shut up already. :-) then they come up in random order on each ifconfig nic :) ??? -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Monday 12 February 2007 16:27, Brooks Davis wrote: Setting media options and the like via _aliasesX variables makes no sense and you don't appear to be doing it so I'm confused by your question. The ifconfig_iface_aliasX syntax exists to add IPv4 addresses to an interface. New ipv4_addrs_iface variable is an attempt to replace that and nothing more. I believe the problem here is that ifconfig_nic=inet IP ifconfig_nic=ether MAC does not work on one line and does not work on two either, the latter overrides and or you get an IP address with original MAC or you get a new MAC without IP. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Monday 12 February 2007 22:37, Joerg Pernfuss wrote:
On Mon, 12 Feb 2007 19:18:54 -0300
JoaoBR [EMAIL PROTECTED] wrote:
I believe the problem here is that
ifconfig_nic=inet IP
ifconfig_nic=ether MAC
does not work on one line and does not work on two either, the latter
overrides and or you get an IP address with original MAC or you get a
new MAC without IP.
Yes, you have to put 'ifconfig nic ether MAC' in /etc/start_if.nic
for this to work afair. Same approach you need to set WEP etc on a
wireless nic if you have ifconfig_nic=DHCP in your rc.conf.
Joerg
if I am remembering well dhcp things you can put into dhclient.conf as
interface nic {
media ssid SSID nwkey KEY;
}
or so to be set before sending the dhcp request.
but this is different but ok and is not related to the -alias thing.
--
João
A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura.
Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Saturday 10 February 2007 01:54, Ian Smith wrote: Secondly, pardon my ignorance, but what does 'NS' refer to here? That string / term occurs nowhere else in ifconfig(8). nameserver -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with IPv6-less kernel and world
On Saturday 10 February 2007 17:08, Spil Oss wrote: Hi Michael, Well, actually I'm proposing a change to the GENERIC kernel and make.conf.example to add to the comment that one should add WITHOUT_IPV6 to the make.conf if you enable NO_INET6. That sounds to me like something completely different than contacting all port-maintainers. even if ipv6 is a real situation it is not the standard, ipv4 is, then, even if ipv6 is some network's standard it is not a global standard, ipv4 is certainly then, it makes no sense that ipv6 is the default, neither for applications nor for the kernel also certain then is that ipv6 is an ADDITIONAL option and who wants it, needs to enable it, either for applications as for the kernel, not the inverse situation as today but this is not only a FBSD wiredness but a general confusion ... but so far as it matters to FBSD it is funny how many core/OS parts simply ignore NO_INET6 even if set ... -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Desired behaviour of ifconfig -alias
On Friday 09 February 2007 20:29, Brooks Davis wrote: On Fri, Feb 09, 2007 at 01:49:08PM -0800, Jeremy Chadwick wrote: On Fri, Feb 09, 2007 at 04:06:56PM -0500, Kevin Way wrote: I recently ran into a bug in the jail startup scripts that caused this command to be executed: ifconfig bce0 -alias It turns out that this command eliminated the primary IP for the device. It's way to late to make this change. This is known behavior and has been for ages. If there's a bug it's in the documentation. wellwell, we also were apes for ages but does not mean that we stay behaving like them and if some still does so it is also never to late to change that ;) ifconfig nic -alias is obviously a wired and confusing behaviour and should firstable do what it says, remove an alias and not the first IP address even if it can be seen as an alias too. Logic would exist when ifconfig nic -alias removes all aliases (or perhaps first of them) but not one by one starting with the first ip. Then when there is no other alias left it should better ask if removing the Ip address is really desired since it is essential to have one. rmuser and other utilities also ask such kind of questions for less reason. then already beeing here there is more, ifconfig nic alias does not return anything at all and ifconfig nic -alias on a nic w/o ip returns can't assign requested address ... -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
