8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem)
Hi! I use onboard ICH7 SATA controller with two disks attached: atapci1: Intel ICH7 SATA300 controller port 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0-0x30af irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] ata2: ATA channel 0 on atapci1 ata2: [ITHREAD] ata3: ATA channel 1 on atapci1 ata3: [ITHREAD] ad4: 1430799MB Seagate ST31500541AS CC34 at ata2-master SATA150 ad6: 1430799MB WDC WD15EADS-00P8B0 01.00A01 at ata3-master SATA150 The disks are used for mirrored ZFS pool. I have noticed that the system periodically locks up on disk operations. After approx. 10 min of very slow disk i/o (several KB/s) the speed of disk operations restores to normal. gstat has shown that the problem is in ad6. For example, there is a filtered output of iostat -x 1: extended device statistics device r/s w/skr/skw/s wait svc_t %b ad6 818.6 0.0 10840.2 0.00 0.4 34 ad6 300.6 642.0 3518.5 24830.3 50 24.8 72 ad61.0 639.363.7 17118.30 62.1 98 ad6 404.5 4.0 6837.7 4.00 0.5 18 ad6 504.5 0.0 13667.2 0.01 0.7 32 ad6 633.3 0.0 13190.3 0.01 0.7 38 ad6 416.3 384.5 8134.7 24606.20 16.3 57 ad6 538.9 76.7 9772.8 2982.2 55 2.9 40 ad6 31.9 929.5 801.0 37498.60 27.2 82 ad6 635.5 0.0 13087.1 0.01 0.6 35 ad6 579.6 0.0 16669.8 0.00 0.8 43 ad6 603.6 0.0 11697.4 0.01 0.7 40 ad6 538.0 0.0 10438.7 0.00 0.9 47 ad6 30.9 898.4 868.6 40585.40 36.6 78 ad6 653.3 86.6 8566.6 202.71 0.8 40 ad6 737.1 0.0 6429.4 0.01 0.6 42 ad6 717.1 0.0 3958.7 0.00 0.5 36 ad6 1179.5 0.0 2058.9 0.00 0.1 15 ad6 1191.2 0.0 1079.6 0.01 0.1 15 ad6 985.1 0.0 5093.9 0.00 0.2 23 ad6 761.8 0.0 9801.3 0.01 0.4 31 ad6 698.7 0.0 9215.1 0.00 0.4 30 ad6 434.2 513.9 5903.1 13658.3 48 10.2 55 ad63.0 762.8 191.2 28732.30 57.6 99 ad6 10.0 4.0 163.9 4.01 1.6 2 Before this line we have a normal operations. Then the behaviour of ad6 changes (pay attention to high average access time and percent of busy significantly greater than 100): ad60.0 0.0 0.0 0.01 0.0 0 ad61.0 0.0 0.5 0.01 1798.3 179 ad61.0 0.0 1.5 0.01 1775.4 177 ad60.0 0.0 0.0 0.01 0.0 0 ad6 10.0 0.075.2 0.01 180.3 180 ad60.0 0.0 0.0 0.01 0.0 0 ad6 83.7 0.0 862.9 0.01 21.4 179 ad60.0 0.0 0.0 0.01 0.0 0 ad61.0 0.063.7 0.01 1707.4 170 ad61.0 0.0 9.0 0.00 1791.0 178 ad6 10.9 0.0 172.2 0.02 0.2 0 ad6 24.9 0.0 553.7 0.01 143.3 179 ad60.0 0.0 0.0 0.07 0.0 0 ad62.0 23.932.4 1529.91 336.3 177 ad60.0 0.0 0.0 0.01 0.0 0 ad6 68.7 0.0 1322.8 0.01 26.3 181 ad60.0 0.0 0.0 0.01 0.0 0 ad6 27.9 0.0 193.7 0.01 61.6 172 ad61.0 0.0 2.5 0.01 1777.4 177 ad60.0 0.0 0.0 0.01 0.0 0 ad61.0 0.0 2.0 0.01 1786.9 178 ad60.0 0.0 0.0 0.01 0.0 0 ad62.0 0.0 6.5 0.01 899.4 179 ad60.0 0.0 0.0 0.01 0.0 0 ad61.0 0.0 2.0 0.01 1786.7 178 ad60.0 0.0 0.0 0.01 0.0 0 And so on for about 10 minutes. Then the disk i/o is reverted to normal: ad6 139.4 0.0 8860.5 0.01 4.4 61 ad6 167.3 0.0 10528.7 0.01 3.3 55 ad6 60.8 411.5 3707.6 8574.81 19.6 87 ad6 163.4 0.0 10334.9 0.01 4.4 72 ad6 157.4 0.0 9770.7 0.01 5.0 78 ad6 108.5 0.0 6886.8 0.00 3.9 43 ad6 101.6 0.0 6381.4 0.00 2.6 27 ad6 109.6 0.0 7013.9 0.00 2.0 22 ad6 121.4 0.0 7769.7 0.00 2.4 29 ad6 92.5 0.0 5922.6 0.01 3.4 31 ad6 122.4 19.9 7833.0 1273.70 3.9 54 ad6 83.6 0.0 5349.5 0.00 3.9 33 ad65.0 0.0 318.4 0.00 8.1 4 There are no ata error messages neither in the system log, nor on the console. The manufacture's diagnostic test is passed on ad6 without any errors. The ad6 also contains swap partition. I have tried to run several (10..20) instances of dd, which read and write data from and to the swap partition simultaneously, but it has not called the lockup. So there is a probability that this problem is ZFS related. I have been forced to switch ad6 to the offline state... :( Any suggestions on this problem? -- Alexander Zagrebin
Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem)
On Wed, Dec 16, 2009 at 11:59:31AM +0300, Alexander Zagrebin wrote:
{snip}
There are no ata error messages neither in the system log, nor on the
console. The manufacture's diagnostic test is passed on ad6 without
any errors. The ad6 also contains swap partition. I have tried to
run several (10..20) instances of dd, which read and write data from
and to the swap partition simultaneously, but it has not called the
lockup. So there is a probability that this problem is ZFS related.
I have been forced to switch ad6 to the offline state... :(
Any suggestions on this problem?
My first guess would be that yes, this is a sign of something ZFS is
doing, but I'm not positive. It'd be useful to see zpool status
output from your system (when ad6 is in the ONLINE state).
Have you tried doing zpool scrub pool to make sure there's no read,
write, or checksum errors causing problems behind the scenes? I don't
know how this would manifest itself in that manner, but worth a shot.
Otherwise, if you could install sysutils/smartmontools and provide the
full output of smartctl -a /dev/ad6 I'll be happy to perform a brief
analysis of the drive itself and if it's performing badly or oddly.
Please note that SMART stats don't keep track of anything pertaining to
the drive's on-PCB cache (which could be going bad, but you'd almost
certainly see that at all times not, occasionally).
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP: 4BD6C0CB |
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Using RELENG_8 to compile for older RELENG_x
I'm on RELENG_8, works great. I've been bugged to compile some things for RELENG_4 boxes. Due to administrative fiat, I have to compile externally and ship them the results, no login. So in general, how do I use my RELENG_8 boxes to compile apps that will run on RELENG_4? Similarly, how can I make buildworld/buildkernel/release for RELENG_4 on RELENG_8? I have RELENG_4 sources on disk, but of course things don't compile/run right. Going forward is easy, I've just no idea how to go backwards :) ___ 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: update to 8.0-RELEASE -- partition gone
Hej Marcel, On Tue, 15 Dec 2009 16:46:27 -0800, Marcel Moolenaar xcl...@mac.com wrote: Yes, if you have ad2a and not ad2s1a, then you have a proper dangerously dedicated disk and FreeBSD 8.x will work correctly with your disk. If you installed dangerously dedicated and ended up with ad0s1a (note the s1), then you have an invalid partitioning and FreeBSD 8.x will not give you what you've been getting on FreeBSD 7.x. Most of the time you only need to wipe out the second sector on the disk to clean it up and have FreeBSD 8.x also give you ad0s1a. okay... but how do I wipe out the second sector? dd if=/dev/zero of=/dev/ad8 count=1 would wipe out the first 512 bytes. I'm always confused with sectors vs. bytes. hm... since this disk is my second disk and was only used for backups, I might as well bsdlabel and newfs it again. Losing all data then, but well, sounds easier so far to me. And I'd like to avoid reboots, if possible. Again, I'm booting from ad4 and this works fine. I should be able to toy around with ad8 without rebooting or going into single user. Thanks so far, Marian ___ 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: Using RELENG_8 to compile for older RELENG_x
On Wed, Dec 16, 2009 at 04:15:01AM -0500, grarpamp wrote: I'm on RELENG_8, works great. I've been bugged to compile some things for RELENG_4 boxes. Due to administrative fiat, I have to compile externally and ship them the results, no login. The best thing to do is to convince the guys running RELENG_4 to join the rest of us in the 21st century, and switch to 8.0 or at least 7.x. Support for the 4.x base system has ended some time ago, and the current ports tree isn't guaranteed to work on it either. So in general, how do I use my RELENG_8 boxes to compile apps that will run on RELENG_4? Create a virtual machine with RELENG_4 on it, that is probably the most foolproof way. (If you are running an i386 machine, maybe a jail will work.) Try to compile the software on it. If that software is in ports and the current port doesn't compile or run, either roll back your ports tree to a version that works, or try to patch the port to make it work. Similarly, how can I make buildworld/buildkernel/release for RELENG_4 on RELENG_8? Ditto. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp2biSdUZmah.pgp Description: PGP signature
RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem)
There are no ata error messages neither in the system log, nor on the console. The manufacture's diagnostic test is passed on ad6 without any errors. The ad6 also contains swap partition. I have tried to run several (10..20) instances of dd, which read and write data from and to the swap partition simultaneously, but it has not called the lockup. So there is a probability that this problem is ZFS related. I have been forced to switch ad6 to the offline state... :( Any suggestions on this problem? My first guess would be that yes, this is a sign of something ZFS is doing, but I'm not positive. It'd be useful to see zpool status output from your system (when ad6 is in the ONLINE state). Nothing special: $ zpool status pool: pool state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-9P scrub: resilver completed after 0h1m with 0 errors on Wed Dec 16 13:26:00 2009 config: NAME STATE READ WRITE CKSUM pool ONLINE 0 0 0 mirror ONLINE 0 0 0 gpt/pool0 ONLINE 0 0 0 2,20M resilvered gpt/pool1 ONLINE 0 172K 0 196M resilvered errors: No known data errors Write errors (172K) was accumulated during offline state of the gpt/pool1 aka ad6. Have you tried doing zpool scrub pool to make sure there's no read, write, or checksum errors causing problems behind the scenes? I don't know how this would manifest itself in that manner, but worth a shot. Yes, I did. zpool scrub doesn't found any errors, but it took lo-o-ong time due to periodic lockups. Otherwise, if you could install sysutils/smartmontools and provide the full output of smartctl -a /dev/ad6 I'll be happy to perform a brief analysis of the drive itself and if it's performing badly or oddly. Please note that SMART stats don't keep track of anything pertaining to the drive's on-PCB cache (which could be going bad, but you'd almost certainly see that at all times not, occasionally). Imho, the smart data is fine. It's the new drive. Today I'll try to change disks in places to eliminate faulty south bridge. = $ sudo smartctl -a /dev/ad6 smartctl version 5.38 [amd64-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD15EADS-00P8B0 Serial Number:WD-WCAVU0296075 Firmware Version: 01.00A01 User Capacity:1 500 301 910 016 bytes Device is:Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Wed Dec 16 13:29:36 2009 MSK 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: (32700) seconds. Offline data collection capabilities:(0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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:( 2) minutes. Extended self-test routine recommended polling time:( 255) minutes. Conveyance self-test routine recommended polling time:( 5) minutes. SCT capabilities:
Re: Using RELENG_8 to compile for older RELENG_x
On Wed, Dec 16, 2009 at 11:28:51AM +0100, Roland Smith wrote: the current ports tree isn't guaranteed to work on [4.x] either. s/isn't guaranteed to/is guaranteed not to/ (sorry) You might want to experiment with checking out a ports tree as of tag RELEASE_4_EOL and trying to pull in newer pieces from there. But basically, you're trying to piece together modern ports with something that was released 01/25/2005 and went EOL on 01/31/2007 (coming up on 3 years ago). mcl ___ 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: update to 8.0-RELEASE -- partition gone
on 16/12/2009 11:28 Marian Hettwer said the following: Hej Marcel, On Tue, 15 Dec 2009 16:46:27 -0800, Marcel Moolenaar xcl...@mac.com wrote: Yes, if you have ad2a and not ad2s1a, then you have a proper dangerously dedicated disk and FreeBSD 8.x will work correctly with your disk. If you installed dangerously dedicated and ended up with ad0s1a (note the s1), then you have an invalid partitioning and FreeBSD 8.x will not give you what you've been getting on FreeBSD 7.x. Most of the time you only need to wipe out the second sector on the disk to clean it up and have FreeBSD 8.x also give you ad0s1a. okay... but how do I wipe out the second sector? dd if=/dev/zero of=/dev/ad8 count=1 would wipe out the first 512 bytes. You need to add seek=1 (or oseek=1, which is the same but a little bit more obvious) to that command. I'm always confused with sectors vs. bytes. You are not confused this time, HDD sector is 512 bytes. This is the default dd block size too. -- Andriy Gapon ___ 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: update to 8.0-RELEASE -- partition gone
If you installed dangerously dedicated and ended up with ad0s1a (note the s1), then you have an invalid partitioning and FreeBSD 8.x will not give you what you've been getting on FreeBSD 7.x. Most of the time you only need to wipe out the second sector on the disk to clean it up and have FreeBSD 8.x also give you ad0s1a. So what's an easy recipe we can run on 7.x hosts to see whether we would have problems with 8.x? Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ 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
Problems with Atheros card and hostpd
Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: Atheros 5212 mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with device ath_ar5212 but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' -- Best regards, Derek mailto:tak...@takeda.tk Wear short sleeves! Support your right to bare arms! ___ 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: update to 8.0-RELEASE -- partition gone
Hej Ho, On Wed, 16 Dec 2009 12:55:38 +0200, Andriy Gapon a...@icyb.net.ua wrote: on 16/12/2009 11:28 Marian Hettwer said the following: Hej Marcel, On Tue, 15 Dec 2009 16:46:27 -0800, Marcel Moolenaar xcl...@mac.com wrote: Yes, if you have ad2a and not ad2s1a, then you have a proper dangerously dedicated disk and FreeBSD 8.x will work correctly with your disk. If you installed dangerously dedicated and ended up with ad0s1a (note the s1), then you have an invalid partitioning and FreeBSD 8.x will not give you what you've been getting on FreeBSD 7.x. Most of the time you only need to wipe out the second sector on the disk to clean it up and have FreeBSD 8.x also give you ad0s1a. okay... but how do I wipe out the second sector? dd if=/dev/zero of=/dev/ad8 count=1 would wipe out the first 512 bytes. You need to add seek=1 (or oseek=1, which is the same but a little bit more obvious) to that command. gee, thanks! That worked. r...@talisker:/root# ls /dev/ad8* /dev/ad8/dev/ad8s1 /dev/ad8s1a r...@talisker:/root# mount /dev/ad8s1a /BACKUP/ r...@talisker:/root# umount /BACKUP/ but, hm, whats that? r...@talisker:/root# fsck /dev/ad8s1a fsck: Could not determine filesystem type I'm always confused with sectors vs. bytes. You are not confused this time, HDD sector is 512 bytes. This is the default dd block size too. Good to know! Cheers, Marian ___ 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
Error upgrading 7.0 to 7.2 (buildword in gnu/usr.bin/binutils/libopcodes setp)
Hi all, I get the next nasty error: === gnu/usr.bin/binutils/libopcodes (all) cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/usr/src/gnu/usr.bin/binutils/libopcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/include -DARCH_i386 -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/bfd -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes/i386-dis.c cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/usr/src/gnu/usr.bin/binutils/libopcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/include -DARCH_i386 -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/bfd -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes/dis-buf.c cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/usr/src/gnu/usr.bin/binutils/libopcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/include -DARCH_i386 -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/bfd -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes/dis-init.c cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/usr/src/gnu/usr.bin/binutils/libopcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libopcodes/../libbfd -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/include -DARCH_i386 -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes -I/usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/bfd -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libopcodes/../../../../contrib/binutils/opcodes/disassemble.c building static opcodes library ranlib libopcodes.a === gnu/usr.bin/binutils/libbinutils (all) cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/usr/src/gnu/usr.bin/binutils/libbinutils -I/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/include -DTARGET=\x86_64-obrien-freebsd\ -DBFD_VERSION_STRING=\2.15 [FreeBSD] 2004-05-23\ -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/bfd -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils/arsup.c cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/usr/src/gnu/usr.bin/binutils/libbinutils -I/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/include -DTARGET=\x86_64-obrien-freebsd\ -DBFD_VERSION_STRING=\2.15 [FreeBSD] 2004-05-23\ -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/bfd -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils/bucomm.c cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I. -I/usr/src/gnu/usr.bin/binutils/libbinutils -I/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd -I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/binutils/libbinutils/../libbfd -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/include -DTARGET=\x86_64-obrien-freebsd\ -DBFD_VERSION_STRING=\2.15 [FreeBSD] 2004-05-23\ -D_GNU_SOURCE -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils -I/usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/bfd -I/usr/obj/usr/src/tmp/legacy/usr/include -c /usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils/debug.c cc -O2 -fno-strict-aliasing -pipe -DBFD_DEFAULT_TARGET_SIZE=64 -I.
Re: Using RELENG_8 to compile for older RELENG_x
On Wed, Dec 16, 2009 at 04:55:46AM -0600, Mark Linimon wrote: On Wed, Dec 16, 2009 at 11:28:51AM +0100, Roland Smith wrote: the current ports tree isn't guaranteed to work on [4.x] either. s/isn't guaranteed to/is guaranteed not to/ That's what I thought, but I couldn't quickly locate a reference to that event. I seem to recall a mailing list message to that event, but as I was already running a later version it didn't quite register. In the days before 5.3 or even 6.0 I could understand why people clung to 4.x. But now it seems like inviting trouble. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpOrhjP2tmvn.pgp Description: PGP signature
Re: update to 8.0-RELEASE -- partition gone
Quoth sth...@nethelp.no: If you installed dangerously dedicated and ended up with ad0s1a (note the s1), then you have an invalid partitioning and FreeBSD 8.x will not give you what you've been getting on FreeBSD 7.x. Most of the time you only need to wipe out the second sector on the disk to clean it up and have FreeBSD 8.x also give you ad0s1a. So what's an easy recipe we can run on 7.x hosts to see whether we would have problems with 8.x? From what's been said so far: If you have adXsY devices in 7, *and* bsdlabel adX finds a valid label (*note*: that is the whole disk, not the slice), then you have conflicting BSD and MBR labels at the start of the disk and you will have a problem in 8. Ben ___ 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: Problems with Atheros card and hostpd
Multi-BSS support in 8.0 means that you first need to create a wlan pseudo-device, and run hostapd with that. The rc.conf lines look like this: wlans_ath0=wlan0 create_args_wlan0=wlanmode hostap ifconfig_wlan0=ssid networkname media autoselect up -Boris Derek Kulinski wrote: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: Atheros 5212 mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with device ath_ar5212 but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ___ 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: Problems with Atheros card and hostpd
Am 16.12.2009 um 12:19 schrieb Derek Kulinski: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): Things got a bit more complicated (and more powerful) with 8.0: you now have to configure a virtual wireless interface, attached to the physical one. Unfortunatly, the handbook has not quite caught up with this change. Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Error upgrading 7.0 to 7.2 (buildword in gnu/usr.bin/binutils/libopcodes setp)
on 16/12/2009 13:45 Jordi Espasa Clofent said the following: [snip] /usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils/debug.c:2407: internal compiler error: Bus error: 10 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error after the classical $ chflags -R noschg /usr/obj/usr cd /usr/src make cleandir make cleandir make -j10 buildworld I've sync the source tree (with 7_2 tag) previously, of course. ¿Any clues? I've never seen this kind ok error in builworld stage. Internal compiler errors during kernel/world build typically[*] point to hardware problems. Especially so on stable branches. [*] 'Typically' is a great under-emphasizing here. -- Andriy Gapon ___ 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
Basic SMART info out of the box
Am 15.12.2009 um 21:24 schrieb Jeremy Chadwick: [1]: It's hardly done and needs a *lot* of work, but I'll eventually get it into a state where it could be committed and people could hack on it/improve it. It's no where near as defined as smartmontools (re: disk vendor/model one-offs for attribute parsing and so on), but I figured FreeBSD users might want something out-of-the-box which might give them stats which are most commonly focused on (sector reallocation, drive temperature, high spin-up times, CRC errors, etc.). I guess you could say I'm a bit proud of myself given that I was able to figure out how to accomplish it by looking at some smartmontools source (messy, let me tell you...) and ata(4) bits (since the ioctls aren't documented). [2]: Yes, I'm still working on writing that doc that explains how to read SMART data. Going to have to end up doing it for work as well... oh the joys. :-) Yes please, I'd like to see basic SMART diagnostics out of the box in the base system! I've looked at doing something similar on and off for a long time, but never really got beyond the basic ioctl proof of concept stage. Since it appears ata and atacontrol might be replaced by CAM, and SCSI devices can also support SMART, would it be possible to add this to camcontrol or a similar utility? Thanks, Stefan -- Stefan Bethke s...@lassitu.de Fon +49 151 14070811 ___ 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: Error upgrading 7.0 to 7.2 (buildword in gnu/usr.bin/binutils/libopcodes setp)
Jordi Espasa Clofent jespa...@minibofh.org writes: /usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils/debug.c: In function 'debug_write_name': /usr/src/gnu/usr.bin/binutils/libbinutils/../../../../contrib/binutils/binutils/debug.c:2407: internal compiler error: Bus error: 10 Please submit a full bug report, with preprocessed source if appropriate. See URL:http://gcc.gnu.org/bugs.html for instructions. *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error after the classical $ chflags -R noschg /usr/obj/usr cd /usr/src make cleandir make cleandir make -j10 buildworld I've sync the source tree (with 7_2 tag) previously, of course. ¿Any clues? I've never seen this kind ok error in builworld stage. Does it always happen in the same place (if not, it's a hardware problem)? Does it happen the same way without the '-j' option (that can make the output less useful)? ___ 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: Using RELENG_8 to compile for older RELENG_x
On Wed, Dec 16, 2009 at 12:54:52PM +0100, Roland Smith wrote: In the days before 5.3 or even 6.0 I could understand why people clung to 4.x. But now it seems like inviting trouble. 5.3 still had a lot of sharp edges (a lot of things were merged into it just prior to release). But at this point, we're even phasing out 6.x. Really, I would hope that everyone except people embedding FreeBSD into their products (and thus have long development cycles) would be on 7.x by now. It has a much better chance of running on modern hardware. mcl ___ 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: Problems with Atheros card and hostpd
On Wed, 2009-12-16 at 03:19 -0800, Derek Kulinski wrote: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): The ifconfig usage changed in 8.0 The Handbook is not correct: http://www.freebsd.org/doc/en/books/handbook/network-wireless.html see: http://forums.freebsd.org/showthread.php?t=8784 and a small tutorial from my hand: http://martenvijn.nl/trac/wiki/ap may show usefull command and config for you. Here: http://www.freebsd.org/doc/en/books/handbook/network-wireless.html the Handbook is not correct... I hope this helps, cheers, Marten [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: Atheros 5212 mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with device ath_ar5212 but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' -- Marten Vijn linux 2.0.18 OpenBSD 3.6 FreeBSD 4.6 http://martenvijn.nl http://opencommunitycamp.org http://wifisoft.org ___ 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: freebsd / gpt boot
On Tue, 2009-12-15 at 17:11 -0500, Adam Jacob Muller wrote: On Dec 14, 2009, at 10:46 AM, Robert Noland wrote: On Sun, 2009-12-13 at 23:21 +0100, Rolf G Nielsen wrote: Adam Jacob Muller wrote: Hi, I'm trying to setup a system with a very large RAID array (total ~10TB), I would ideally like to have the system boot directly off that 10TB array, so i'm trying to get the system setup with GPT but running into an issue. The initial pre-loader (boot0 I think? -- i'm not sure what this is called) is unable to find loader at /boot/loader nor can it load /boot/kernel/kernel Is the partitioning done correctly (have you created a small boot partition, 15 sectors is enough for booting from ufs, but the tutorials I've found deal mainly with booting from zfs and they recommend 128 sectors to make future bootcode changes easier)? You will need to be doing all of this from a current 8-STABLE. One bug in dealing with larger zfs raidz volumes was fixed and made it into 8.0. Another, which deals with GPT/ZFS and large volumes did not make it and only exists in 8-STABLE, iirc. Also, with the gptzfsboot code from -STABLE, it will request to load /boot/zfsloader by default (and LOADER_ZFS_SUPPORT is no longer required). gpart add -b 34 -s 128 -t freebsd-boot -i 1 da0 Have you embedded the correct boot code? gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 da0 (for booting from ufs). or gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0 (for booting from zfs). You may also need to set it active by gpart set -a active -i 1 da0 The above step is no longer needed on -STABLE, the pmbr will be marked active when you install bootcode. Robert, Do either of these bugs affect GPT/UFS, which is what I am using here. I thought that one of them was relevant, but looking back at the patch, I believe that it only impacted gpt + zfs. robert. These bugs are affecting the actual older versions of the tools (IE using the gpart from an 8.0-pre or earlier could cause issues like this)? Also, perhaps not coincidentally, booting the FreeBSD memstick image produces the same error (boot0 can't find loader). -Adam robert. And of course, substitute your arrays device node for da0 in my examples. Copying /boot/loader to /loader allows me to enter /loader at the boot: prompt and the loader will load, however, its unable to load the kernel. If I do an ls at the loader prompt I can see boot listed as a directory (with a d before it) Trying to do ls boot inexplicably it says boot: not a directory re-applying my /boot/loader.conf settings (for some reason vfs.root.mountfrom=ufs:/dev/label/root is required, or else I get a mountroot) and then: load /kernel boot does work, and lets the system boot normally and everything is as expected (/boot is a directory etc). Anyone have any ideas about either of these things (the vfs.root.mountfrom is minor i guess but i'm curious if they are related?) Thanks in advance, -Adam ___ 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 ___ 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 -- Robert Noland rnol...@freebsd.org FreeBSD ___ 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 -- Robert Noland rnol...@freebsd.org FreeBSD ___ 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
freebsd-questions mailing list
Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ Jamie ___ 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: update to 8.0-RELEASE -- partition gone
If you installed dangerously dedicated and ended up with ad0s1a (note the s1), then you have an invalid partitioning and FreeBSD 8.x will not give you what you've been getting on FreeBSD 7.x. Most of the time you only need to wipe out the second sector on the disk to clean it up and have FreeBSD 8.x also give you ad0s1a. So what's an easy recipe we can run on 7.x hosts to see whether we would have problems with 8.x? From what's been said so far: If you have adXsY devices in 7, *and* bsdlabel adX finds a valid label (*note*: that is the whole disk, not the slice), then you have conflicting BSD and MBR labels at the start of the disk and you will have a problem in 8. So presumably if I have root on ad4s1a today, and bsdlabel shows # bsdlabel ad4 bsdlabel: /dev/ad4: no valid label found then I am ready for FreeBSD 8.x? Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ 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: Dell D830, nVidia and FreeBSD-8/amd64
On Tue, 2009-12-15 at 15:51 -0500, John Baldwin wrote: On Tuesday 15 December 2009 2:47:03 pm Jonathan Chen wrote: On Tue, Dec 15, 2009 at 10:18:36AM -0500, John Baldwin wrote: On Monday 14 December 2009 9:37:51 pm Jonathan Chen wrote: On Mon, Dec 14, 2009 at 10:46:27AM -0500, John Baldwin wrote: On Sunday 13 December 2009 2:19:05 pm Jonathan Chen wrote: Hi, This is a general rehash of a problem that I've been having with my Dell Latitude D830 with an nVidia Quadro NVS 140M internal graphics card. I've been using the XOrg's vesa driver ever since something in the code rendered the nvidia driver inoperable in 7-STABLE sometime mid last year. With nVidia's new 195.22 (BETA) drivers, I had hoped that I could bypass the problem. Unfortunately, I seem to be experiencing the same problem as described in the following thread: http://www.nvnews.net/vbulletin/showthread.php?t=142391 which appears to be implying that something in the kernel is interfering with memory allocation. Would it be possible for someone with deeper kernel-fu be able to take a look at this issue? Do you have a verbose dmesg available? I've attached a dmesg with a verbose boot. I hope this is what you're looking for. Ok, can you grab the output of 'devinfo -r' and 'devinfo -ur'? I suspect that when the bridge allocates the prefetch resource range from the parent it is failing somehow. For a quick hack try something like this: [...] I've attatched the requested output. Unfortunately, the patch didn't result in anything different. I/O memory addresses: 0xdff0-0xe06f (acpi0) 0xe070-0xe0700fff (cbb0) 0xe0701000-0xf3ff (root0) The root0 range is ok (it really means free), but the cbb0 and acpi0 ranges here conflict with the prefetch BAR for the video adapter. The cbb0 one I think is because that range is free when cbb0 needs to allocate a fresh range of resources. The real bug is why your BIOS thinks that a system resource is using 0xe000-0xe06f which conflicts with the nvidia card. You can try disabling ACPI's system-resource handling (set debug.acpi.disabled=sysres from the loader). I'm not sure what is the root issue, but we have seen system resource conflicts like this reasonably often with Nvidia graphics. I've never some across this issue with any other display adapter. But I've had at least a handful of reports of noveau not working due to this issue. robert. -- Robert Noland rnol...@freebsd.org FreeBSD ___ 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: freebsd-questions mailing list
On Wed, Dec 16, 2009 at 7:41 AM, Jamie Griffin j...@koderize.com wrote: Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ Sign me up for a me too. The last message from that list in my mailbox is the (overly drawn out) Root Exploit thread. -- Glen Barber ___ 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: update to 8.0-RELEASE -- partition gone
On Wed, Dec 16, 2009 at 12:27:15PM +0100, Marian Hettwer wrote: but, hm, whats that? r...@talisker:/root# fsck /dev/ad8s1a fsck: Could not determine filesystem type If you don't have an entry for /dev/ad8s1a in your fstab, you need to specify the filesystem type with -t. Jeff ___ 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: freebsd-questions mailing list
On Wed, Dec 16, 2009 at 08:53:43AM -0500, Glen Barber typed: On Wed, Dec 16, 2009 at 7:41 AM, Jamie Griffin j...@koderize.com wrote: Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ Sign me up for a me too. The last message from that list in my mailbox is the (overly drawn out) Root Exploit thread. Yup, I noticed this too. Last message in the archives is from Sun Dec 13 17:10:40 UTC 2009 ___ 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: Basic SMART info out of the box
On Wed, Dec 16, 2009 at 01:47:33PM +0100, Stefan Bethke wrote: Am 15.12.2009 um 21:24 schrieb Jeremy Chadwick: [1]: It's hardly done and needs a *lot* of work, but I'll eventually get it into a state where it could be committed and people could hack on it/improve it. It's no where near as defined as smartmontools (re: disk vendor/model one-offs for attribute parsing and so on), but I figured FreeBSD users might want something out-of-the-box which might give them stats which are most commonly focused on (sector reallocation, drive temperature, high spin-up times, CRC errors, etc.). I guess you could say I'm a bit proud of myself given that I was able to figure out how to accomplish it by looking at some smartmontools source (messy, let me tell you...) and ata(4) bits (since the ioctls aren't documented). [2]: Yes, I'm still working on writing that doc that explains how to read SMART data. Going to have to end up doing it for work as well... oh the joys. :-) Yes please, I'd like to see basic SMART diagnostics out of the box in the base system! I've looked at doing something similar on and off for a long time, but never really got beyond the basic ioctl proof of concept stage. Since it appears ata and atacontrol might be replaced by CAM, and SCSI devices can also support SMART, would it be possible to add this to camcontrol or a similar utility? Highly likely. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iSCSI initiator and Dell PowerVault MD3000i
Daniel Braniss wrote: Hi all, I am playing with iscsi_initiator on FreeBSD 7-STABLE and Dell PowerVault MD3000i. This is the first time I am testing iSCSI... Does anyone have FreeBSD's iSCSI initiator in production / heavy load? Or does somebody have experiences with Dell MD3000i? One thing is poor performance ~ 60 - 70MB/s depending on RAID level used. (poor performance compared to plain SATA disk which have 110MB/s - both tested for reading as it is our planned load - multimedia streaming and downloads) The other thing is some problem with compatibility of initiator and Dell MD3000i. If I setup RAID 5 'Disk Group' consisted of 4x 1TB SATA drives (in MD3000i) and then created for example 2 'Virtual Disks', both are detected by iscontrol and added to /dev/ as da0 and da1, but da1 spams log with messages like this: [...] Can somebody advice some tweaks to get better performance and solution of the errors above? hi Miroslav, firstly, in case you haven't yet, get the latest from: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz the slowness is probably due to the scsi errors, which I need some scsi expert (hence the cc to s...@freebsd.org, hint, hint). In the mean time, and if you can/want, you can allow me access to an iscsi partition so that I can better debug the issue. oh, and yes, we use it here. danny Hi Danny, thank you for your reply. I will test iSCSI 2.2.3 and if it fails, I will give you an access to the machine to let you debug the errors. Thank you again! Miroslav Lachman ___ 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: net/mpd5, ppp, proxy-arp issues
Thank you ! The problem with proxy-arp has disappeared (FreeBSD 8-STABLE amd64 with mpd5). Please, somebody fix the bug kern/141285... Li, Qing wrote: Hi, Recently there have been several reports regarding issues with ppp, mpd5 and proxy-arp configuration over the ppp links. I read through the various postings and the problems seem to be: 1. Unable to add proxy-arp entries for the remote ppp clients. 2. Log showing ifa_add_loopback_route: insertion failed causing some userland applications to fail. May I ask that you try applying patch http://people.freebsd.org/~qingli/ppp-proxy-arp-patch-121515.diff and report back if the patch fixes your problems. And if not, please describe what additional issues you are having. Thanks, -- Qing ___ freebsd-...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to freebsd-net-unsubscr...@freebsd.org ___ 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: freebsd-questions mailing list
Jamie Griffin j...@koderize.com writes: Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ I asked the postmaster, and got a reply that the reply isn't really well understood yet. I don't know mailman that well, or I'd've volunteered to help out. ___ 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
Possible ZFS livelock or SCHED_ULE bug ?
Hi all !
I got a UniProcessor AMD64 box, with 512 MB ram with 2 ZFS pools as a
home-NAS.
I got some IO issues since I moved from 7.2 to 8.0.
With a GENERIC kernel (or a stripped down one), during high IO activity
(as a make buildword can cause), I encounter random hangs or deadlocks.
top show system CPU usage at 99%, the most CPU using process being
[zfskern] ( {txg_thread_enter} if I switch to thread view).
The box still respond to ping. Current processes can still run, but I
can't run new ones.
Sometimes, I can return to normal by Ctrl-C-ing the buildworld (or other
operation), sometimes I can't, I got to reboot the box.
The Issue seemed to become less frequent with 8.0-stable instead of
8.0-RELEASE, but still present (I get approximately 75% chance of hang
with a buildworld).
I got the hang with Prefetch enabled or disabled. Idem for ZIL.
I tried to enable kernel dumps, but the box hangs saving the dump (root
is on ZFS) or when starting kdbg on it.
I recompiled kernel with SCHED_4BSD, and it seems I can't reproduce the
hang.
What do you think ?
Did I misconfigured something ?
cat /boot/loader.conf
zfs_load=YES
vfs.root.mountfrom=zfs:unsafe/root
vm.kmem_size=512M
vm.kmem_size_max=512M
vfs.zfs.arc_max=100M
vfs.zfs.vdev.cache.size=10M
vfs.zfs.prefetch_disable=0
vfs.zfs.zil_disable=1
[carenath] ~ zpool status
pool: tank
state: ONLINE
scrub: none requested
config:
NAMESTATE READ WRITE CKSUM
tankONLINE 0 0 0
raidz1ONLINE 0 0 0
ad6p1 ONLINE 0 0 0
ad10p1 ONLINE 0 0 0
ad8p1 ONLINE 0 0 0
ad4p1 ONLINE 0 0 0
errors: No known data errors
pool: unsafe
state: ONLINE
scrub: none requested
config:
NAMESTATE READ WRITE CKSUM
unsafe ONLINE 0 0 0
ad0p3 ONLINE 0 0 0
errors: No known data errors
___
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: Error upgrading 7.0 to 7.2 (buildword in gnu/usr.bin/binutils/libopcodes setp)
Lowell Gilbert escribió: Does it always happen in the same place (if not, it's a hardware problem)? Hi Lowel, Yes, always at same point. Does it happen the same way without the '-j' option (that can make the output less useful)? Wonderful. I've used times the same command (1) without -j flag and... it works perfectly! It's curious, because of I always use the -j flag in buildworld with successs. It has been the first time that I've experienced this problem (1) chflags -R noschg /usr/obj/usr cd /usr/src make cleandir make cleandir make -j10 buildworld Thanks for all. ;) -- I must not fear. Fear is the mind-killer. Fear is the little-death that brings total obliteration. I will face my fear. I will permit it to pass over me and through me. And when it has gone past I will turn the inner eye to see its path. Where the fear has gone there will be nothing. Only I will remain. Bene Gesserit Litany Against Fear. ___ 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: Error upgrading 7.0 to 7.2 (buildword in gnu/usr.bin/binutils/libopcodes setp)
Jordi Espasa Clofent jespa...@minibofh.org writes: Lowell Gilbert escribió: Does it always happen in the same place (if not, it's a hardware problem)? Hi Lowel, Yes, always at same point. Good. Based on the information you gave, I was expecting a hardware problem. Does it happen the same way without the '-j' option (that can make the output less useful)? Wonderful. I've used times the same command (1) without -j flag and... it works perfectly! It's curious, because of I always use the -j flag in buildworld with successs. It has been the first time that I've experienced this problem buildworld is supposed to work with -j, but I've never used a value that large. Unless you have 8 or more CPU cores available, I would expect builds to be faster if you reduced that value. (1) chflags -R noschg /usr/obj/usr cd /usr/src make cleandir make cleandir make -j10 buildworld I don't think chflags should be needed any more. The cleandir isn't supposed to be necessary either; I only do that when I have a problem. Glad to hear you're making progress. ___ 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: Possible ZFS livelock or SCHED_ULE bug ?
On Dec 16, 2009, at 11:04 AM, Arnaud Houdelette wrote:
Hi all !
I got a UniProcessor AMD64 box, with 512 MB ram with 2 ZFS pools as a
home-NAS.
I got some IO issues since I moved from 7.2 to 8.0.
With a GENERIC kernel (or a stripped down one), during high IO activity (as
a make buildword can cause), I encounter random hangs or deadlocks.
top show system CPU usage at 99%, the most CPU using process being [zfskern]
( {txg_thread_enter} if I switch to thread view).
The box still respond to ping. Current processes can still run, but I can't
run new ones.
Sometimes, I can return to normal by Ctrl-C-ing the buildworld (or other
operation), sometimes I can't, I got to reboot the box.
The Issue seemed to become less frequent with 8.0-stable instead of
8.0-RELEASE, but still present (I get approximately 75% chance of hang with a
buildworld).
I got the hang with Prefetch enabled or disabled. Idem for ZIL.
I tried to enable kernel dumps, but the box hangs saving the dump (root is on
ZFS) or when starting kdbg on it.
I recompiled kernel with SCHED_4BSD, and it seems I can't reproduce the hang.
What do you think ?
Did I misconfigured something ?
This sounds similar to something I ran into on CURRENT last year:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=832196+0+archive/2009/freebsd-current/20090322.freebsd-current
The immediate problem was a priority inversion problem between the
txg_thread_enter threads and the spa_zio threads. This should be solved (or at
least mitigated) on 8.0 now that these threads have explicit priorities set.
Can you check to see what priorities these threads are at on your machine?
They should have priorities something like -8 for txg_thread_enter and -16 for
spa_zio.
- Ben
___
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: Possible ZFS livelock or SCHED_ULE bug ?
Ben Kelly wrote:
On Dec 16, 2009, at 11:04 AM, Arnaud Houdelette wrote:
Hi all !
I got a UniProcessor AMD64 box, with 512 MB ram with 2 ZFS pools as a home-NAS.
I got some IO issues since I moved from 7.2 to 8.0.
With a GENERIC kernel (or a stripped down one), during high IO activity (as a
make buildword can cause), I encounter random hangs or deadlocks.
top show system CPU usage at 99%, the most CPU using process being [zfskern] (
{txg_thread_enter} if I switch to thread view).
The box still respond to ping. Current processes can still run, but I can't run
new ones.
Sometimes, I can return to normal by Ctrl-C-ing the buildworld (or other
operation), sometimes I can't, I got to reboot the box.
The Issue seemed to become less frequent with 8.0-stable instead of
8.0-RELEASE, but still present (I get approximately 75% chance of hang with a
buildworld).
I got the hang with Prefetch enabled or disabled. Idem for ZIL.
I tried to enable kernel dumps, but the box hangs saving the dump (root is on
ZFS) or when starting kdbg on it.
I recompiled kernel with SCHED_4BSD, and it seems I can't reproduce the hang.
What do you think ?
Did I misconfigured something ?
This sounds similar to something I ran into on CURRENT last year:
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=832196+0+archive/2009/freebsd-current/20090322.freebsd-current
The immediate problem was a priority inversion problem between the
txg_thread_enter threads and the spa_zio threads. This should be solved (or at
least mitigated) on 8.0 now that these threads have explicit priorities set.
Can you check to see what priorities these threads are at on your machine?
They should have priorities something like -8 for txg_thread_enter and -16 for
spa_zio.
- Ben
As far as I can tell, this is the priorities that I see on my machine.
I'm doing another test. This once with ULE but without options SMP set.
I'm currently building world, and so far, I did not encountered any
hang. (and the system seems more responsive that with 4BSD). I'll keep
testing and report...
Arnaud
___
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: problems with SATA controller after recent RELENG_8 upgrade
Hi Alexander, Alexander Motin wrote: --- ata-promise.c.prev 2009-12-15 21:35:43.0 +0200 +++ ata-promise.c 2009-12-15 21:35:24.0 +0200 @@ -957,6 +957,7 @@ ata_promise_mio_dmainit(device_t dev) ata_dmainit(dev); /* note start and stop are not used here */ ch-dma.setprd = ata_promise_mio_setprd; +ch-dma.max_iosize = 65536; } I applied the patch and then the error went away and the system boots up successfully. To be sure it was no other (build related) problem I removed the line again, did a make kernel again and then I got the same error as before. So - this line definitly makes my system work again. If you want to add a comment (so none else removes it in the future again ;)) - my exactl model is Promise SATA300 TX2+ atap...@pci0:0:17:0:class=0x018000 card=0x3d73105a chip=0x3d73105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'SATAII 300 TX2+ (PDC40775)' class = mass storage -- Oliver Lehmann http://www.pofo.de/ http://wishlist.ans-netz.de/ ___ 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: update to 8.0-RELEASE -- partition gone
On Dec 16, 2009, at 3:27 AM, Marian Hettwer wrote: gee, thanks! That worked. r...@talisker:/root# ls /dev/ad8* /dev/ad8/dev/ad8s1 /dev/ad8s1a r...@talisker:/root# mount /dev/ad8s1a /BACKUP/ r...@talisker:/root# umount /BACKUP/ but, hm, whats that? r...@talisker:/root# fsck /dev/ad8s1a fsck: Could not determine filesystem type I minor inconvenience for the time being. fsck hasn't been thought about getting partition types from gpart, so that it can do a best-effort attempt at guessing which variant to run. For now, you need to be explicit: fsck -t ufs /dev/ad0s1a Alternatively, add an entry to /etc/fstab. FYI, -- Marcel Moolenaar xcl...@mac.com ___ 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: update to 8.0-RELEASE -- partition gone
On Dec 16, 2009, at 2:33 AM, sth...@nethelp.no wrote:
If you installed dangerously dedicated and ended up
with ad0s1a (note the s1), then you have an invalid
partitioning and FreeBSD 8.x will not give you what
you've been getting on FreeBSD 7.x. Most of the time
you only need to wipe out the second sector on the
disk to clean it up and have FreeBSD 8.x also give
you ad0s1a.
So what's an easy recipe we can run on 7.x hosts to see whether we
would have problems with 8.x?
If
1. fdisk ${D} shows FreeBSD slices, and
2. your mount points are within these slices (i.e your device name
has a prefix of ${D}s1, ${D}s2, ${D}s3, etc *OR* they have a
prefix of ${D}cs1 ${D}cs2 ${D}cs3, etc), and
3. bsdlabel ${D} shows that there's a (possibly empty) BSD disklabel
then you have an invalidly created danerously dedicated disk.
You can wipe out the second sector on the disk to clear the bogus
BSD disklabel.
The most important thing to look at is how you currently mount.
If fdisk ${D} and bsdlabel ${D} show valid information and you
mount from ${D}a, ${D}d, etc -- then your disk is not necessarily
invalid in the same sense that having a PMBR with slices in front
of a GPT is not considered invalid.
FYI,
--
Marcel Moolenaar
xcl...@mac.com
___
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: Error upgrading 7.0 to 7.2 (buildword in gnu/usr.bin/binutils/libopcodes setp)
On Wed, Dec 16, 2009 at 4:32 PM, Lowell Gilbert freebsd-stable-lo...@be-well.ilk.org wrote: Jordi Espasa Clofent jespa...@minibofh.org writes: Lowell Gilbert escribió: Wonderful. I've used times the same command (1) without -j flag and... it works perfectly! It's curious, because of I always use the -j flag in buildworld with successs. It has been the first time that I've experienced this problem buildworld is supposed to work with -j, but I've never used a value that large. Unless you have 8 or more CPU cores available, I would expect builds to be faster if you reduced that value. Running more concurrent processes will use more CPU and more memory (you'd hope, anyways). This could lead it to use bits of hardware with -j 8 that it wouldn't use without it, potentially exposing hardware flaws. Cheers Tom ___ 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: freebsd-questions mailing list
On Wed, Dec 16, 2009 at 10:46:13AM -0500, Lowell Gilbert typed: Jamie Griffin j...@koderize.com writes: Has anyone else noticed a problem with this list, I haven't received a message from the freebsd-questions list for over 24 hours :0/ I asked the postmaster, and got a reply that the reply isn't really well understood yet. I don't know mailman that well, or I'd've volunteered to help out. Mailman's not rocket science. And the list is offline now for 3 days! I volunteer! ___ 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: Problems with Atheros card and hostpd
Hello Boris, I checked the handbook, UPDATING, and nothing mentioned this thing, why? I would think I'm not the only one with this problem, or am I? Anyway it seems to work, I'm getting: Starting hostapd. Configuration file: /etc/hostapd.conf wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported. Using interface wlan0 with hwaddr 00:11:95:e5:70:df and ssid 'mayumi-ap' Is it something I should worry about? Also how to create wlan device by hand? ifconfig ath0 wlandev wlan0 doesn't seem to work. What initially was worrying me was this: ath0: Atheros 5212 mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 I thought that ath0 was using a different driver than it supposed to. There's one more question, though not related to this problem. I have an android phone, and it doesn't seem to work with my FreeBSD AP, while it works on others. After sniffing the traffic, it looks like it is a power management issue: https://supportforums.motorola.com/message/87903#87903 Someone traced the problem to WME/WMM in his case. I don't know if that's the case for me yet, I tried to disable/enable wme on the AP but it doesn't seem to do anything. Is it possible that I might fix it by enabling some option? Anyway, thanks for everyone who helped me fix the initial issue. Derek Wednesday, December 16, 2009, 4:28:49 AM, you wrote: Multi-BSS support in 8.0 means that you first need to create a wlan pseudo-device, and run hostapd with that. The rc.conf lines look like this: wlans_ath0=wlan0 create_args_wlan0=wlanmode hostap ifconfig_wlan0=ssid networkname media autoselect up -Boris Derek Kulinski wrote: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: Atheros 5212 mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with device ath_ar5212 but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' -- Best regards, Derekmailto:tak...@takeda.tk -- I can see clearly now, the brain is gone... ___ 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: Problems with Atheros card and hostpd
On Wednesday 16 December 2009 01:39:25 pm Derek Kulinski wrote: Also how to create wlan device by hand? ifconfig ath0 wlandev wlan0 doesn't seem to work. You have it backwards. It should be: ifconfig wlan0 create wlandev ath0 ___ 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: iSCSI initiator and Dell PowerVault MD3000i
On 16. 12. 2009 15:57, Miroslav Lachman wrote: Daniel Braniss wrote: Hi all, I am playing with iscsi_initiator on FreeBSD 7-STABLE and Dell PowerVault MD3000i. This is the first time I am testing iSCSI... [...] If I setup RAID 5 'Disk Group' consisted of 4x 1TB SATA drives (in MD3000i) and then created for example 2 'Virtual Disks', both are detected by iscontrol and added to /dev/ as da0 and da1, but da1 spams log with messages like this: [...] I use MD300i with FreeBSD 7.0 and 7.1 with iscsi-2.2.2. It work fine. But be careful to configure MD3000i. MD3000i assign by default first disk to preferred controller 0, second disk to preferred controller 1, third disk to preferred controller 0, and so on. First, third, fifth... disks is usable from FreeBSD, but second, fourth,... disks result unusable. Work around: manually assign all disks to controller 0. I'm talking with Dell's technical support, but Dell not support FreeBSD! In any case, technical support tell me, the problem (maybe) is the multipath. FreeBSD use only one path (only one IP) to communicate to MD3000i. Second net interface in unused. I hope that I have been helpful. By -- Sossi Andrej - DotCom Information technology Via Trento, 16 34132 - Trieste (TS) Italy tel: +39 040 2158191 fax: +39 040 0641954 E-mail: aso...@dotcom.ts.it Ai sensi del D.lgs n. 196 del 30.06.03 (Codice Privacy) si precisa che le informazioni contenute in questo messaggio sono riservate e ad uso esclusivo del destinatario. Qualora il messaggio in parola Le fosse pervenuto per errore, La preghiamo di eliminarlo senza copiarlo e di non inoltrarlo a terzi, dandocene gentilmente comunicazione. Grazie This message, for the D.lgs n. 196 / 30.06.03 (Privacy Code), may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. ___ 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: Using RELENG_8 to compile for older RELENG_x
This would simply involve downloading some canonical tarball, say bind, and compiling it... perhaps even statically. Ports and it's issues related to this would certainly not be considered. I'd thought about the jails, emulation, installing 4.11 on spare boxes [a] and whatnot. Seemed there might be a more elegant way to cross compile and do everything on the RELENG_8 box natively. Maybe by pointing the toolchain at a copy of /lib /include from RELENG_4 or whatever. Then expand that method to back compile for RELENG_x. I think I'll try unpacking 4.11's release tarballs into an empty jail, doing whatever else the install does and launching that. I'm guessing I should be able to compile/install world/kernel/release/apps in there. Assuming the running RELENG_8 parent kernel services don't cause issues. If it doesn't work I can always fall back to [a]. Yeah, you could consider it 'embedded' all right. Like deep in a dusty corner, driving some critical legacy shims that they forgot about in the migration plan, oops. As a side note, it would be nice if freebsd-archive containted packages-x-stable too, copied over as part of the rm process from the regular ftp.freebsd.org when it happens. And all the distfiles ever used too, I don't think they're currently rm'ed though. ___ 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: Dell D830, nVidia and FreeBSD-8/amd64
On Tue, Dec 15, 2009 at 03:51:30PM -0500, John Baldwin wrote: On Tuesday 15 December 2009 2:47:03 pm Jonathan Chen wrote: [...] I/O memory addresses: 0xdff0-0xe06f (acpi0) 0xe070-0xe0700fff (cbb0) 0xe0701000-0xf3ff (root0) The root0 range is ok (it really means free), but the cbb0 and acpi0 ranges here conflict with the prefetch BAR for the video adapter. The cbb0 one I think is because that range is free when cbb0 needs to allocate a fresh range of resources. The real bug is why your BIOS thinks that a system resource is using 0xe000-0xe06f which conflicts with the nvidia card. You can try disabling ACPI's system-resource handling (set debug.acpi.disabled=sysres from the loader). The debug.acpi.disabled setting allows me to load up the driver and displays a usable X screen on the internal monitor - however, my xorg.conf was configured to use the *external* monitor. When X quits on the internal monitor, the console display reverts back to the external monitor with a scratchy display. I've also just updated the BIOS in the hope that it would resolve the conflict, but that didn't appear to do anything. I've also noticed that cbb0 complains about Bad Vcc requested on boot and shutdown. Thanks for looking into this, btw. -- Jonathan Chen j...@chen.org.nz -- Beer. Now there's a temporary solution. - Homer Simpson ___ 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: Possible scheduler (SCHED_ULE) bug?
From: Jacob Myers [mailto:ja...@whotookspaz.org] Jaime Bozza wrote: From: Arnaud Houdelette [mailto:arnaud.houdele...@tzim.net] I haven't tried larger files - Maybe the boundary is different on amd64? Doing some quick tests right now, I was able to upload a 100MB file without a problem, but this is an AMD64 system with SMP, plus the filesystem is all ZFS, so there are too many things different. I'll have to setup a system that closely mirrors the rest of my tests (UFS, ULE, no SMP, etc) before I can say I'm not having a problem there. Jaime I had the same issue using 7.1 amd64, with ZFS, no SMP. Not really sure what is the size boundary. I can't really test either, as the machine is remote. But I confirm that each tentative upload of certain relatively 'big' files (around 1MB) with wordpress hanged the system before I switched from sendfile to writev. I might do some test on amd64 7.2 with no SMP if it can be of any use ? Arnaud I was able to duplicate the problem on 7.2-STABLE amd64 no SMP - Problem didn't seem to happen with SMP on. While I wasn't able to get a crash dump, the crash looked similar. Jaime FWIW, there was a fix committed for this: http://svn.freebsd.org/viewvc/base?view=revisionrevision=198853 See if it helps. Sorry for the delay in testing this - Everything seems to be working fine now. I'm not able to force a lockup anymore under the same conditions. Thanks for the fix! Jaime ___ 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: Problem with kern.icp.shmseg
On Tuesday 15 December 2009 9:01:57 pm Alexander Petrovsky wrote: Hello! I have problem with kern.icp.shmseg, when a change value from 128 to 256, 512 in /boot/loader.conf. When system loading the value kern.icp.shmseg doesn't change. # cat /boot/loader.conf # Number of shared memory identifiers kern.ipc.shmmni=2048 # Number of segments per process #2048 kern.icp.shmseg=256 s/icp/ipc/. :) -- John Baldwin ___ 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: Dell D830, nVidia and FreeBSD-8/amd64
On Wednesday 16 December 2009 8:47:56 am Robert Noland wrote: On Tue, 2009-12-15 at 15:51 -0500, John Baldwin wrote: On Tuesday 15 December 2009 2:47:03 pm Jonathan Chen wrote: On Tue, Dec 15, 2009 at 10:18:36AM -0500, John Baldwin wrote: On Monday 14 December 2009 9:37:51 pm Jonathan Chen wrote: On Mon, Dec 14, 2009 at 10:46:27AM -0500, John Baldwin wrote: On Sunday 13 December 2009 2:19:05 pm Jonathan Chen wrote: Hi, This is a general rehash of a problem that I've been having with my Dell Latitude D830 with an nVidia Quadro NVS 140M internal graphics card. I've been using the XOrg's vesa driver ever since something in the code rendered the nvidia driver inoperable in 7-STABLE sometime mid last year. With nVidia's new 195.22 (BETA) drivers, I had hoped that I could bypass the problem. Unfortunately, I seem to be experiencing the same problem as described in the following thread: http://www.nvnews.net/vbulletin/showthread.php?t=142391 which appears to be implying that something in the kernel is interfering with memory allocation. Would it be possible for someone with deeper kernel-fu be able to take a look at this issue? Do you have a verbose dmesg available? I've attached a dmesg with a verbose boot. I hope this is what you're looking for. Ok, can you grab the output of 'devinfo -r' and 'devinfo -ur'? I suspect that when the bridge allocates the prefetch resource range from the parent it is failing somehow. For a quick hack try something like this: [...] I've attatched the requested output. Unfortunately, the patch didn't result in anything different. I/O memory addresses: 0xdff0-0xe06f (acpi0) 0xe070-0xe0700fff (cbb0) 0xe0701000-0xf3ff (root0) The root0 range is ok (it really means free), but the cbb0 and acpi0 ranges here conflict with the prefetch BAR for the video adapter. The cbb0 one I think is because that range is free when cbb0 needs to allocate a fresh range of resources. The real bug is why your BIOS thinks that a system resource is using 0xe000-0xe06f which conflicts with the nvidia card. You can try disabling ACPI's system-resource handling (set debug.acpi.disabled=sysres from the loader). I'm not sure what is the root issue, but we have seen system resource conflicts like this reasonably often with Nvidia graphics. I've never some across this issue with any other display adapter. But I've had at least a handful of reports of noveau not working due to this issue. This is not specific to Nvidia adapters. These are just incompetent BIOS writers. We should probably trust any BARs set by the BIOS over what is listed in the ACPI system resources. This it not super easy to fix now, but I can see how to handle that as part of the multipass device resource stuff. -- John Baldwin ___ 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: freebsd update for 8.0-REL-p1 ?
hmm, the answer is: freebsd-update binarys availalble only for i386 and amd64, for sparc not... On 12/6/09, Oliver Pinter oliver.p...@gmail.com wrote: [r...@argos /home/op]# uname -a FreeBSD argos 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 22:40:34 UTC 2009 r...@araz.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC sparc64 [r...@argos /home/op]# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching public key from update5.FreeBSD.org... failed. Fetching public key from update4.FreeBSD.org... failed. Fetching public key from update2.FreeBSD.org... failed. No mirrors remaining, giving up. when manualy fetch pub.ssl and place its dir, then become this error message: Fetching metadata signature for 8.0-RELEASE-p1 from update4.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update5.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update2.FreeBSD.org... failed. On 12/6/09, Arnaud Houdelette arnaud.houdele...@tzim.net wrote: Kurt Jaeger wrote: Hi! Now that the rtld patch is available, how do I upgrade using freebsd-update ? freebsd-update -r 8.0-RELEASE-p1 upgrade says: [...] Fetching metadata signature for 8.0-RELEASE-p1 from update4.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update5.FreeBSD.org... failed. Fetching metadata signature for 8.0-RELEASE-p1 from update2.FreeBSD.org... failed. No mirrors remaining, giving up. So it does not upgrade 8-( Hi. Just do : freebsd-update fetch then : freebsd-update install Arnaud ___ 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 ___ 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: update to 8.0-RELEASE -- partition gone
Quoth Marcel Moolenaar xcl...@mac.com: On Dec 16, 2009, at 3:27 AM, Marian Hettwer wrote: gee, thanks! That worked. r...@talisker:/root# ls /dev/ad8* /dev/ad8/dev/ad8s1 /dev/ad8s1a r...@talisker:/root# mount /dev/ad8s1a /BACKUP/ r...@talisker:/root# umount /BACKUP/ but, hm, whats that? r...@talisker:/root# fsck /dev/ad8s1a fsck: Could not determine filesystem type I minor inconvenience for the time being. fsck hasn't been thought about getting partition types from gpart, so that it can do a best-effort attempt at guessing which variant to run. For now, you need to be explicit: I for one would rather *not* see fsck extended in this way. The whole point of fsck is that you're running it on a potentially-broken disk; guessing is not helpful at that point :). Ben ___ 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: update to 8.0-RELEASE -- partition gone
Quoth sth...@nethelp.no: So what's an easy recipe we can run on 7.x hosts to see whether we would have problems with 8.x? From what's been said so far: If you have adXsY devices in 7, *and* bsdlabel adX finds a valid label (*note*: that is the whole disk, not the slice), then you have conflicting BSD and MBR labels at the start of the disk and you will have a problem in 8. So presumably if I have root on ad4s1a today, and bsdlabel shows # bsdlabel ad4 bsdlabel: /dev/ad4: no valid label found then I am ready for FreeBSD 8.x? I think so (but I'm no expert). This setup isn't in any way 'dangerously dedicated', though, so there's no reason to think it wouldn't work. My question was whether mounting from ad2d (with no MBR on ad2 at all) would work; apparently it will, as long as there isn't an invalid BSD disklabel in sector 2 of the first track. Ben ___ 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: Using RELENG_8 to compile for older RELENG_x
On Wed, Dec 16, 2009 at 03:18:17PM -0500, grarpamp wrote: I think I'll try unpacking 4.11's release tarballs into an empty jail, doing whatever else the install does and launching that. I'm guessing I should be able to compile/install world/kernel/release/apps in there. Assuming the running RELENG_8 parent kernel services don't cause issues. If it doesn't work I can always fall back to [a]. If I understand correctly, you want to use the jail to run a 4.11 userland on an 8.x kernel? If you are not running GENERIC on the host, remember to include the COMPAT_FREEBSD4..COMPAT_FREEBSD7 options in your kernel. You'll need that to run 4.x binaries. Running older binaries is possible. But on the other hand running a userland that is not in sync with the kernel not supported and known to be able to cause trouble. See e.g. §24.7 of the Handbook. It will be an interesting experiment at least. :-) I'd probably try installing 4.11 on a old spare machine first. Yeah, you could consider it 'embedded' all right. Like deep in a dusty corner, driving some critical legacy shims that they forgot about in the migration plan, oops. Oops indeed. Old+'dusty corner'+'critical' is not a good combination in my experience. If the scenario also contains the element 'no backups', its time to run for the hills. :-/ Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp4NfTbyZXxe.pgp Description: PGP signature
RELENG_7: gdm after portupgrade does not allow logins
Dear colleagues,
after portupgrade'ing on last gnome update I have very strange situation:
gdm does not show neither login list not username text field; after pressing
space, some unlabelled text field opens (symbols are echoed, so I suppose it's
like login name field); however, entering anything there does not lead
anywhere.
portupgrade -f gdm does not help; portupgrade -f ${direct gdm dependencies}
does not help, either.
And, of course, I even rebooted the machine without a bit of success.
Any hints? Thanks in advance!
--
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: ma...@freebsd.org ]
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru ***
___
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: Problems with Atheros card and hostpd
Derek Kulinski wrote: Hello Boris, I checked the handbook, UPDATING, and nothing mentioned this thing, why? I would think I'm not the only one with this problem, or am I? Well, I learned about it because I follow the -current@ and -net@ mailing lists, but there is at least some mention of it in /usr/src/UPDATING: 20080420: The 802.11 wireless support was redone to enable multi-bss operation on devices that are capable. The underlying device is no longer used directly but instead wlanX devices are cloned with ifconfig. This requires changes to rc.conf files. For example, change: ifconfig_ath0=WPA DHCP to wlans_ath0=wlan0 ifconfig_wlan0=WPA DHCP see rc.conf(5) for more details. In addition, mergemaster of /etc/rc.d is highly recommended. Simultaneous update of userland and kernel wouldn't hurt either. As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta modules were merged into the base wlan module. All references to these modules (e.g. in kernel config files) must be removed. Anyway it seems to work, I'm getting: Starting hostapd. Configuration file: /etc/hostapd.conf wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported. Using interface wlan0 with hwaddr 00:11:95:e5:70:df and ssid 'mayumi-ap' Is it something I should worry about? I don't think so. The same thing happens on my access points. It looks like the channel and rate remain properties of the underlying device, which makes sense, since all wlan pseudo-devices use the same channel and rate. Also how to create wlan device by hand? ifconfig ath0 wlandev wlan0 doesn't seem to work. What initially was worrying me was this: ath0: Atheros 5212 mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 I thought that ath0 was using a different driver than it supposed to. There's one more question, though not related to this problem. I have an android phone, and it doesn't seem to work with my FreeBSD AP, while it works on others. After sniffing the traffic, it looks like it is a power management issue: https://supportforums.motorola.com/message/87903#87903 Someone traced the problem to WME/WMM in his case. I don't know if that's the case for me yet, I tried to disable/enable wme on the AP but it doesn't seem to do anything. Is it possible that I might fix it by enabling some option? Don't know anything about this, I'm afraid. Anyway, thanks for everyone who helped me fix the initial issue. Derek Wednesday, December 16, 2009, 4:28:49 AM, you wrote: Multi-BSS support in 8.0 means that you first need to create a wlan pseudo-device, and run hostapd with that. The rc.conf lines look like this: wlans_ath0=wlan0 create_args_wlan0=wlanmode hostap ifconfig_wlan0=ssid networkname media autoselect up -Boris Derek Kulinski wrote: Hello, I just upgraded my access point (from 7.1 to 8.0) and can't make hostapd work (looks like wide-dhcp relay also has a problem with ath0): [mayumi]:/root# hostapd -P /var/run/hostapd.pid -dd /etc/hostapd.conf Configuration file: /etc/hostapd.conf Line 2: DEPRECATED: 'debug' configuration variable is not used anymore ctrl_interface_group=0 (from group name 'wheel') pcap_open_live: ifname='ath0' bsd driver initialization failed. ath0: Unable to setup interface. rmdir[ctrl_interface]: No such file or directory Exit 255 Output from dmesg: ath0: Atheros 5212 mem 0xf400-0xf400 irq 3 at device 11.0 on pci0 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 The interface seems to exist, but seems it lost some of its functionality: [mayumi]:/root# ifconfig ath0 ath0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 2290 ether 00:11:95:e5:70:df media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier [mayumi]:/root# ifconfig ath0 list cap ifconfig: Don't know how to list cap for ath0 What's going on? The card worked pretty well with 7.1. I tried to compile kernel just with device ath_ar5212 but I'm only getting this: ah.o(.text+0x212): In function `ath_hal_rfprobe': /usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__start_set_ah_rfs' ah.o(.text+0x21f):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ah.o(.text+0x235):/usr/src/sys/dev/ath/ath_hal/ah.c:142: undefined reference to `__stop_set_ah_rfs' ___ 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: Problems with Atheros card and hostpd
Hello Boris, Wednesday, December 16, 2009, 5:18:57 PM, you wrote: 20080420: The 802.11 wireless support was redone to enable multi-bss operation on devices that are capable. The underlying device is no longer used directly but instead wlanX devices are cloned with ifconfig. This requires changes to rc.conf files. For example, change: ifconfig_ath0=WPA DHCP to wlans_ath0=wlan0 ifconfig_wlan0=WPA DHCP see rc.conf(5) for more details. In addition, mergemaster of /etc/rc.d is highly recommended. Simultaneous update of userland and kernel wouldn't hurt either. As part of the multi-bss changes the wlan_scan_ap and wlan_scan_sta modules were merged into the base wlan module. All references to these modules (e.g. in kernel config files) must be removed. Ok, now I'm quite embarrassed =) Anyway, thanks for your help. -- Best regards, Derekmailto:tak...@takeda.tk The great thing about Object Oriented code is that it can make small, simple problems look like large, complex ones. ___ 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
