Re: nvidia-driver-295.49 is highly unstable
On 06/04/12 03:12, Chris wrote: On Sun, 27 May 2012 20:50:59 -0300 Mario Lobol...@bsd.com.br wrote: On Sunday 27 May 2012 14:05:16 Yuri wrote: On 05/27/2012 10:01, David Wolfskill wrote: So, at least in my case, I respectfully disagree with the assessment in the Subject. i386 is one difference (I use amd64) FX 770M is another difference (I use 9400GT) I also have everything updated with the similar portmaster command. Yuri I use 8-STABLE amd64 with 295.40/9800GT and been using it since I can remember. Except for some quircks with early VirtualBox versions, I have NEVER had a problem with ANY version of the driver I've used. FWIW uname -a FreeBSD udns 8.3-STABLE FreeBSD 8.3-STABLE #2: Sun May 20 22:25:10 PDT 2012 root@udns:/usr/obj/usr/src/sys/AMD64 amd64 Xorg.0.log NVIDIA GPU GeForce 7800 GT (G70) PCI:*(0:1:0:0) 10de:0092:3842:c518 NVIDIA Corporation G70 [GeForce 7800 GT] rev 161 NVIDIA dlloader X Driver 295.40 Thu Apr 5 21:27:46 PDT 2012 Has always worked w/o any issues -- ever. Hi Everyone, You know what it could be? I just had to rebuild my user-land because of KDE updates and I use variables in my make.conf to switch between base GCC and CLANG. I forgot to switch back to base gcc before compiling the nvidia driver. I installed the driver and rebooted, xorg came up but as soon as I logged in, kwin crashed, then the machine kernel panicked and rebooted. I rebooted and crashed a few more times before realizing what I had done. I recompiled the driver with GCC and the machine has been rock-stable with the nvidia driver. Maybe the OP has done the same thing and not realized it? Ta Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: [clang] Build error on r232474 (and a few before, don't know exactly which)
On Sunday 04 March 2012 02:29:08 Brandon Falk wrote: If you define WITHOUT_GCC, a cc isn't created in /usr/obj/usr/src/tmp/usr/bin but if you go into the directory and do a symbolic link from clang, and restart make with -DNO_CLEAN it'll work and complete. One of the programs hardcodes cc and doesn't check the environment, I forget which. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org Built the code until it failed. Then did a `ln -s /usr/obj/root/src/tmp/usr/bin/clang /usr/obj/root/src/tmp/usr/bin/cc` and a `make -DNO_CLEAN -j12 buildworld` and it finished just fine. Thanks for the help, although we've got to sort this hardcode out somewhere :P Brandon, I had the same problem for a while but what I did to get around the problem was define WITH_CLANG_IS_CC=no in the /etc/src.conf and that created cc and the build continued. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Getting PRs fixed (was: Re: ...focus, longevity, and lifecycle)
Idea 1: Fix 'n' PRs, get a tee-shirt, fridge magnet, plush daemon, ... Idea 2: Give it status. Set up a web page with PR fixing stats name/handle..total PRs fixed...fixed in last 12 months...average fixed/year Sheldon..150...9072 Leonard..131..11067 Howard...104...2052 Raj...80...8080 You should get extra points for difficult PR's. One way to measure this would be to give more points for fixing older PR's than newer PR's. Number of points = number of days or weeks that a PR has been in the system before triage ? I would think this would put some emphasis on either triaging old PRs before new ones or actually postponing and assigning a status that cannot accumulate a higher amount of points. But then what? What to do with the points after they accumulate? Wouldn't it be cool if there was some funding or backing where you could trade your points in for a pint or a cup of coffee? Call it Coffee for Coders or the CC fund 8-) You know.. That might be a funny way of assigning points for a PR. How many cups of coffee you expect to be drunk during the fixing of a PR. All meant tongue to cheek, of course 8-) Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Does anyone use nscd?
On Wednesday 05 October 2011 10:46:47 Eugene Grosbein wrote: 04.10.2011 22:47, Sean M. Collins пишет: I've never heard of the utility until you mentioned it. I'd nuke it, since really there are more popular alternatives like Redis and Memcached in the ports tree that most people will reach for first. I had not used it before I saw this thread.. But now I am 8-) I kind of like it, actually.. Especially for DNS caching.. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: kern+world / ports make options
On Sunday 25 April 2010 11:17:40 Ulrich Spörlein wrote:
On Sat, 24.04.2010 at 16:42:37 +, Pegasus Mc Cleaft wrote:
It may already be implemented, but it would be nice if there was
something defined while the kernel and/or world is being built to that a
nested block of ifdefs can select which env variables to be set.
src.conf has already been mentioned, I don't use it myself but have the
following set in make.conf
.if ${.CURDIR:M*/usr/ports/*}
NOCLEANDEPENDS= true
WRKDIRPREFIX= /usr/obj
.include /etc/ports.conf
.endif
Hi Ulrich,
Thank you for that. This is pretty much what I was looking for as I can
use the .if block to add in only the pieces I want. The src.conf solution was
an option, but since both make.conf and src.conf are called, I ended up
basically undoing everything in src.conf that I did in make.conf; and that
didn't work so well as I kept breaking the build (couldn't find headers and
all sorts of thing). No doubt, it was the way that I did it.. Your solution is
cleaner and makes sense to me.
Thanks again,
Peg
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
kern+world / ports make options
Hello Hackers Current, I was wondering it if is possible, or if it can be done so a separate set of CC, CXX, etc can be specified for building the world and kernel independently of a ports build? Right now, I use the base GCC to compile the world and kernel, and GCC44 for most of the other ports (when it complies cleanly). But I have to keep editing the /etc/make.conf file to switch between the two. It may already be implemented, but it would be nice if there was something defined while the kernel and/or world is being built to that a nested block of ifdefs can select which env variables to be set. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Compiling kernel with gcc43 [SOLVED]
On Thursday 01 April 2010 15:27:41 Oliver Fromme wrote: Mario Lobo l...@bsd.com.br wrote: [...] It's compiling right now. I'll post my findings and impressions on results and performance right after the next reboot. So, how is it going? Any benchmarks yet? I'm curious if the new gcc version will really make a significant difference. I would love to see the /etc/make.conf, /etc/src.conf and /etc/libmap.conf files that were used for the build. I have tried compiling in VBox a current kernel and world, but it usually just bombs out for me. I would like to give this a go as well. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Changes in IPv6 Configuration
Hello Current and Hackers, With the recent changes to /etc/rc.d for network start-up. I was wondering what is now correct. The previously working ipv6 configuration no longer creates a static default route, and I have not been able to figure out why. After boot, if I manually add the default route for ipv6, all works OK but I must be missing something to make it happen automatically. Currently, I have this in my /etc/rc.conf and this does not work. Any help would be appreciated. ipv6_prefer=YES ifconfig_re0_ipv6=inet6 2001:4d48:ad51:32:21d:7dff:fe07:241a prefixlen 64 ipv6_defaultrouter=2001:4d48:ad51:32::3 ipv6_network_interfaces=auto ipv6_default_interface=re0 Thanks in advance, Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Changes in IPv6 Configuration
On Sunday 13 September 2009 18:58:02 Bjoern A. Zeeb wrote:
On Sun, 13 Sep 2009, Pegasus Mc Cleaft wrote:
Hi,
With the recent changes to /etc/rc.d for network start-up. I was
wondering what is now correct. The previously working ipv6 configuration
no longer creates a static default route, and I have not been able to
figure out why. After boot, if I manually add the default route for ipv6,
all works OK but I must be missing something to make it happen
automatically. Currently, I have this in my /etc/rc.conf and this does
not work. Any help would be appreciated.
ipv6_prefer=YES
ifconfig_re0_ipv6=inet6 2001:4d48:ad51:32:21d:7dff:fe07:241a prefixlen
64 ipv6_defaultrouter=2001:4d48:ad51:32::3
ipv6_network_interfaces=auto
ipv6_default_interface=re0
can you try this change (just pasted in):
Index: etc/rc.d/routing
===
--- etc/rc.d/routing(revision 197153)
+++ etc/rc.d/routing(working copy)
@@ -132,7 +132,7 @@
if [ -n ${ipv6_static_routes} ]; then
for i in ${ipv6_static_routes}; do
ipv6_route_args=`get_if_var $i ipv6_route_IF`
- route ${_action} -inet6 ${route_args}
+ route ${_action} -inet6 ${ipv6_route_args}
done
fi
/bz
Hi Bjoern,
Thank you very much. That change did work and now the IPv6 default
gateway
is being added to the route table on start-up.
Cheers,
Peg
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Fatal trap 12 ever since r195851 on AMD64
Hello Current, I dont know if there is a current issue with other systems or if it is localized to me, but ever since r195914 I am getting a fatal trap on boot. The process is always in the swapper and is always a 12. System is AMD64 Core2-Quad, 4 Gigs, gptzfsboot from a mirror with zraid's mounted for /usr, /usr/home, etc.. Is anyone else seeing this as well? FreeBSD 8.0-BETA2 #137 r195914: Mon Jul 27 19:10:17 BST 2009 snip Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x288 fault code = supervisor read data, page not present instruction pointer = 0x20:0x805c482d stack pointer = 0x28:0x81076c90 frame pointer = 0x28:0x81076cc0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) trap number = 12 panic: page fault cpuid = 0 Uptime: 1s Cannot dump. Device not defined or unavailable. Automatic reboot in 15 seconds - press a key on the console to abort Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Fatal trap 12 ever since r195851 on AMD64
ACK! Sorry.. I messed up the revision number in the message body... On Monday 27 July 2009 21:18:22 Pegasus Mc Cleaft wrote: I dont know if there is a current issue with other systems or if it is localized to me, but ever since r195914 I am getting a fatal trap on ^r195815 Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Fatal trap 12 ever since r195851 on AMD64
Crud! Just shoot me! I'm very sorry about this.. Typing to fast and not checking.. On Monday 27 July 2009 21:23:36 Pegasus Mc Cleaft wrote: ACK! Sorry.. I messed up the revision number in the message body... On Monday 27 July 2009 21:18:22 Pegasus Mc Cleaft wrote: I dont know if there is a current issue with other systems or if it is localized to me, but ever since r195914 I am getting a fatal trap on ^r195815 ^r195851 (triple checked this time) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
DAD Detected duplicate ipv6 address - 7.2 Stable
Hi Hackers, I was wondering if someone could give me some advice. I just updated one of my servers from 7.2-pre to 7.2-stable (07/05/2009) and lost my IPv6 connectivity. The machine has been given a static IPv6 address and ND is not used (I set the address in the rc.conf file). On reboot, I get messages like this in the dmesg: vr0: DAD detected duplicate IPv6 address 2001:49f0:2023::2: NS in/out=3/1, NA in=0 vr0: DAD complete for 2001:49f0:2023::2 - duplicate found vr0: manual intervention required vr0: DAD detected duplicate IPv6 address fe80:1::213:8fff:fe5c:1a5f: NS in/out=3/1, NA in=0 vr0: DAD complete for fe80:1::213:8fff:fe5c:1a5f - duplicate found vr0: manual intervention required vr0: possible hardware address duplication detected, disable IPv6 hercules$ ifconfig vr0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=2808VLAN_MTU,WOL_UCAST,WOL_MAGIC ether 00:13:8f:5c:1a:5f inet6 fe80::213:8fff:fe5c:1a5f%vr0 prefixlen 64 duplicated scopeid 0x1 inet 66.90.118.40 netmask 0xff00 broadcast 66.90.118.255 inet6 2001:49f0:2023::2 prefixlen 64 duplicated media: Ethernet autoselect (100baseTX full-duplex) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT metric 0 mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST metric 0 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 This fault has only shown up since the upgrade and I am at a loss for what to try to do to fix this or debug. Any advice would be appreciated. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
ping6 and traceroute6 trouble
Hi Current and Hackers, I have only seen this recently and was wondering if anyone else can confirm this as a bug or perhaps a setup problem on my end. I think it started to appear with 8-Current from about the 25th of march. Any time I do a ping6 or traceroute6 I receive an error stating Invalid value for hints. However, I am able to do all other functions (telnet, ssh, etc.) feathers# ping6 ipv6.google.com ping6: Invalid value for hints feathers# traceroute6 ipv6.google.com traceroute6: Invalid value for hints my If config looks like: re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC ether 00:1d:7d:07:24:1a inet 78.33.110.3 netmask 0xffe0 broadcast 78.33.110.31 inet6 fe80::21d:7dff:fe07:241a%re0 prefixlen 64 scopeid 0x1 inet6 2001:4d48:ad51:32:21d:7dff:fe07:241a prefixlen 64 autoconf media: Ethernet autoselect (100baseTX full-duplex) status: active Thanks in advance, Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: ping6 and traceroute6 trouble
Hi Hajimu, ken Any time I do a ping6 or traceroute6 I receive an error stating Invalid ken value for hints. However, I am able to do all other functions (telnet, ssh, ken etc.) ken feathers# ping6 ipv6.google.com ken ping6: Invalid value for hints ken feathers# traceroute6 ipv6.google.com ken traceroute6: Invalid value for hints I've committed the change to lib/libc/net/getaddrinfo.c little while ago that also fixed the problem. Please re-cvsup and try it. http://svn.freebsd.org/viewvc/base/head/lib/libc/net/getaddrinfo.c?r1=19041 6r2=190525view=patch Yes, that fixed things nicely. Thank you. Best regards, Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: ETA for ZFS v. 13 Merge From HEAD ?
Hi Adrian, I am not sure, but I didnt think ZFS 13 was ever going to be merged into 7-stable. I thought the kernel memory requirements were to great (just going back in my memory on that one). Also, I think there are still a few bugs left with the zil being enabled (and/or prefetch) causing lockups on machine with a lot of IO. I know I have hit that bug a few times on my machine when using various torrent clients when they want to preallocate large amounts of diskspace. I personally cant wait until a later version of ZFS is imported that supports encryption. I can finally say good-bye to our GEOM ELI USB drives for backups!! Never the less, I am quite thankfull to thoes involved in porting V13 to FreeBSD. Its a wonderfull improvement and my FS of choice when installing on new machines (especially zfs boot) Best regards, Peg - Original Message - From: Adrian Penisoara a...@freebsd.ady.ro To: Pawel Jakub Dawidek p...@freebsd.org Cc: freebsd...@freebsd.org; freebsd-hackers@freebsd.org Sent: Sunday, March 15, 2009 7:09 PM Subject: ETA for ZFS v. 13 Merge From HEAD ? Hi Pawel, Coming back to the subject, when do you think we might have a merge of r185029 (import of ZFS version 13) from head back into -stable ? Is there anything we can help with to speed up the process (e.g. testing) ? PS: ZFS-FUSE on Linux has also reached v 13... Thank you, Adrian Penisoara ROFUG / EnterpriseBSD --- Date: Wed, 26 Nov 2008 10:52:41 +0100 From: Pawel Jakub Dawidek p...@freebsd.org Subject: Re: svn commit: r185029 - in head: cddl/compat/opensolaris/include cddl/compat/opensolaris/misc cddl/contrib/opensolaris/cmd/zdb cddl/contrib/opensolaris/cmd/zfs cddl/contrib/opensolaris/cmd/zinject cd... To: Attila Nagy b...@fsn.hu Cc: svn-src-h...@freebsd.org, svn-src-...@freebsd.org, src-committ...@freebsd.org Message-ID: 20081126095241.ga3...@garage.freebsd.pl Content-Type: text/plain; charset=us-ascii On Wed, Nov 26, 2008 at 10:15:58AM +0100, Attila Nagy wrote: Hello, Pawel Jakub Dawidek wrote: Author: pjd Date: Mon Nov 17 20:49:29 2008 New Revision: 185029 URL: http://svn.freebsd.org/changeset/base/185029 Log: Update ZFS from version 6 to 13 and bring some FreeBSD-specific changes. This, and other changes stabilized ZFS by a great level in HEAD. Do you plan to MFC these to 7-STABLE? Yes, but ETA yet. -- Pawel Jakub Dawidek http://www.wheel.pl p...@freebsd.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
bsdtar lockup on Current-03/10/2009
Hi Current Hackers, I was wondering if anyone else is seeing this problem: Any use of bsdtar to create a new archive causes the process to be unresponsive to all signals and consumes 100% cpu time. The machine I am testing on is a Core 2 quad running in AMD64 (8 gigs ram, zfs boot, root, et al.) I have tried disabling the zil and prefetch as a precaution but can still cause the failure by doing the command below(trying to eliminate zfs writes as being the problem): #tar -cvf /dev/null * Unarchiving from tar seems to work OK. The bug may have been introduced a few days ago. I just noticed my machine doing this tonight when I tried to do a portupgrade and the creation of the backups locked up. Thanks, Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: ich watchdog vs intel smm code
- Original Message - From: Andriy Gapon a...@icyb.net.ua To: freebsd-hackers@freebsd.org; freebsd-a...@freebsd.org Sent: Monday, January 19, 2009 12:11 PM Subject: ich watchdog vs intel smm code Some time earlier I reported that ichwd driver doesn't produce any effect on my system with Intel DG33TL motherboard when watchdog timer is allowed to expire. I did some investigation and also discussed the issue with a maintainer of Linux iTCO_wdt driver, Wim Van Sebroeck. He told me that the issue is present on most of Intel motherboards with ICH9 chipset. All evidence seems to point in one direction - Intel SMM code. It seems that ICH9 always gets configured by BIOS to produce an SMI when a watchdog timer expires. Also, ICH watchdog has a logic to cause a reboot if its timer expires twice in a row, this is to avoid a potential hang in SMI handler. ICH9 allows SMI to be globally enabled and disabled. BIOS configures it to be enabled. Sometimes this bit is locked down (by BIOS), so it's not possible to change it, but sometimes it is not locked. So, if we globally disable SMI, then the watchdog in ICH9 does indeed cause a reboot. Evidently this happens after the timer expires twice in row. My conclusion is that SMI handler installed by BIOS somehow acknowledges watchdog SMI (e.g. clears a certain status bit, or performs watchdog timer reload). But it doesn't execute any corrective action. My guess is there might some configuration (or some other form of massaging) that needs to be done in order to convince SMM code to perform a reboot upon watchdog SMI. It would be nice if we had some Intel insiders who could provide a glimpse into Intel SMM code logic with respect to the watchdog. Finally some technical details: NMI2SMI_EN and TCO_LOCK bits of TCO1_CNT are set 1: pmbase+0x0068: 0x1200 (TCO1_CNT) in SMI_EN register TCO_EN bit is 1, GBL_SMI_EN is 1, End of SMI (EOS) bit is 1 and (not sure if this matters) LEGACY_USB_EN is 1: pmbase+0x0030: 0x203b (SMI_EN) No Reboot (NR) bit of GCS register is zero: 0x3410: 0x00c01444 I have a simmilar problem on my gigabyte motherboard (one of the X48 ones), however, I believe the fault to be in hardware and not in firmware or software.. Mentioned in the datasheet for the ICH9, the speaker pin is used as a configuration pin while reset it asserted. If a logic 1 is present on this pin when reset is deasserted, the ICH9 chip locks out the ability for software to enable the watchdog. With the ichwd driver for BSD, this condition is announced with a message like Watchdog present, but disabled in BIOS. (Well.. something close to that) ~Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Problems with zfsboot loader if raidz present on any drive
On Sunday 07 December 2008 09:22:16 Doug Rabson wrote: On 7 Dec 2008, at 03:19, Pegasus Mc Cleaft wrote: Hello Hackers, Recently and friend and I have been trying to get the new gptzfsboot working on our machines and ran into a interesting problem. Initially I was building the world without the environment variable LOADER_ZFS_SUPPORT=YES in the /etc/make.conf and this, of course, didnt work very well. Every time the machine booted, it would throw 2 lines after the pin-wheel and then reboot. I couldent read what the lines were it went so fast. My friend had a bit more luck and got his machine working OK with a single drive and later a mirror drive added. I added the environment variable and rebuilt everything and installed. This time, I could see the bios drives and a further 2 lines of ZFS something and a reboot... No matter what I tried, I couldent get the machine to boot up to a point where I could try and fix the problem, so I started pulling devices out and found the following: If there is a raidz pool on any drive (not necessarily the one that you are trying to boot from) the loader dies and reboots the machine. My friend, as an experiment created 3 gpt partitions (in addition to the single partition that he had been previously booted from) on his single drive and made a raidz pool for testing. His machine showed the same condition as mine, however he was able to capture the message before the machine rebooted: message ZFS: can only boot from disk or mirror vdevs ZFS: inconsistent nvlist contents The zfsboot code in current doesn't support raidz or raidz2. I have been working on adding that support but its not ready yet. The code works in my test harness but crashes instantly when I put it in the boot code :(. I should have time to finish debugging it soon. Hi Doug, In my haste to put a message to the group, I didnt do a very good job of explaining or give what platform I was working with. I set up a single disk pool with the gptzfsboot code on it as a boot drive. My idea was to have a single disk boot (and after it boots and I can kill the UFS drive I am currently booting from) convert it to a mirror. But I have 6 other drives in the machine that I have as a raidz for my /usr/home, et al. If the 6 raidz drives are present at boot time, the machine starts to cyclic reboot just after the pin-wheel. The machine I am working on is running FBSD8.0-Current as of midnight 7/12/2008 and the platform is AMD64. If I can help test in any way I would be more than happy to try, or provide any information necessary.. ~Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with zfsboot loader if raidz present on any drive
Hello Hackers, Recently and friend and I have been trying to get the new gptzfsboot working on our machines and ran into a interesting problem. Initially I was building the world without the environment variable LOADER_ZFS_SUPPORT=YES in the /etc/make.conf and this, of course, didnt work very well. Every time the machine booted, it would throw 2 lines after the pin-wheel and then reboot. I couldent read what the lines were it went so fast. My friend had a bit more luck and got his machine working OK with a single drive and later a mirror drive added. I added the environment variable and rebuilt everything and installed. This time, I could see the bios drives and a further 2 lines of ZFS something and a reboot... No matter what I tried, I couldent get the machine to boot up to a point where I could try and fix the problem, so I started pulling devices out and found the following: If there is a raidz pool on any drive (not necessarily the one that you are trying to boot from) the loader dies and reboots the machine. My friend, as an experiment created 3 gpt partitions (in addition to the single partition that he had been previously booted from) on his single drive and made a raidz pool for testing. His machine showed the same condition as mine, however he was able to capture the message before the machine rebooted: message ZFS: can only boot from disk or mirror vdevs ZFS: inconsistent nvlist contents / /message ~Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ZFS make install with exec=no in /tmp
Hello hackers, I was wondering if there is a work around for this... In 8.0-current I have installed the new version of ZFS and upgraded the filing systems to 13. I had a thought that I would make a zfs for /tmp and set the exec to no (thinking that nothing should ever be executed in the tmp). All seemed to work ok, however, I ran into a problem when I was installing a new world. The script immediately bombed out with a permission denied message. I remembered seeing that type of message before when I was testing the no- exec bit in /tmp before, so I reset it to 'yes' and all is well and installed fine.. Is there any way to specify what directory is used for building and executing the install scripts? Ta, Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FBSD 7.1 BETA2 and RTL8168/8111 problem
On Friday 28 November 2008 17:14:33 Fernando Apesteguía wrote: Hi, I forward my orginal mail to freebsd-questions. I hope someone can shed some light here... -- Forwarded message -- From: Fernando Apesteguía [EMAIL PROTECTED] Date: Fri, Nov 28, 2008 at 9:33 AM Subject: FBSD 7.1 BETA2 and RTL8168/8111 problem To: FreeBSD [EMAIL PROTECTED] Hi all, I recently installed FreeBSD 7.1 BETA2 on my system. During installation using FTP option, I could notice the following: After some random time (two, five or six minutes, for instance) the installation stalled and sysinstall lost the connection. I was taken back to the Select FTP site screen, and I had to configure my NIC again. Then, the install resumed and I got a usable system (MINIMAL + docs + manpages) But the problem persists. From time to time, it seems the kernel can't see the NIC. It happens during normal operation and no message is shown in /var/log/messages. ifconfig doesn't show my 're0' device, so I can't run dhclient on it and I have to reboot. I have to say that sometimes, even when I reboot, the NIC (RTL8168/8111 PCI Express) is not present. This device works fine in the same computer with either Vista or Fedora 9, though I have to say I had similar problems with earlier versions of Fedora (device disappearing or not present after boot), but after a kernel upgrade everything run smoothly. Does FreeBSD use the same driver than Linux does? Anybody else with this problem? Hi Fernando, I have seen this problem on my machine as well with both 7.X and 8.0-current. I am using a RTL8111C chip on a ICH9 GigaByte GA-48X-DS5 motherboard. If the problem you are experiencing is the same as mine, the clue will be in the dmesg. If you take a look, you may see an error message saying something about a MAC without a PHY (I cant remember the exact message). The motherboard I have has 2 ethernet ports on it, and randomly it would be missing one or both of them. I gave up on trying to get mine to work and turned off the ethernet option in BIOS and installed an Intel Pro/1000 based card. I have found the em driver to be rock stable. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Removing zpool log device - 8.0-Current
Hello Hackers, I was wondering if anyone knows a work around for this. I have added a log device to one of my zfs pools (it is a unused ATA drive slice that has no activity on it after boot up as most other directories live in there own zfs filing systems). I have added a SSD to the machine and have successfully moved the cache to this device, but wanted to also move the ZIL to another slice on the SSD unit. When I type 'zpool remove PegaBase ar0s1e' I receive the following error: feathers# zpool remove PegaBase ar0s1e cannot remove ar0s1e: only inactive hot spares or cache devices can be removed I know this is a known bug: http://bugs.opensolaris.org/view_bug.do?bug_id=6574286 However, someone mentioned that if you were to flush the ZIL by closing all transactions, you can then remove the device. Does anyone know how this can be done? I have tried the usual fsync, but that dosent seem to flush the zil back to the pool. There seems to be a static amount of information held in the zil and never seems to flush back. Atleast that is how it seems. I would be grateful for any ideas.. Ta Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: build problems with gptzfsboot (AMD64) 8.0-CURRENT
- Original Message -
From: Doug Rabson [EMAIL PROTECTED]
To: Olivier SMEDTS [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Pegasus Mc Cleaft
[EMAIL PROTECTED]; Pascal Hofstee [EMAIL PROTECTED]
Sent: Monday, November 24, 2008 10:35 AM
Subject: Re: build problems with gptzfsboot (AMD64) 8.0-CURRENT
On 20 Nov 2008, at 19:41, Olivier SMEDTS wrote:
2008/11/20 Olivier SMEDTS [EMAIL PROTECTED]:
2008/11/20 Olivier SMEDTS [EMAIL PROTECTED]:
2008/11/20 Pascal Hofstee [EMAIL PROTECTED]:
On Thu, 20 Nov 2008 01:46:31 -
Pegasus Mc Cleaft [EMAIL PROTECTED] wrote:
Hi everyone,
I am having difficulties rebuilding the world after some patches
were made today. I was wondering if anyone else is experiencing the
same troubles?
ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x0 -o
gptzfsboot.out /usr/obj/usr/src/sys/boot/i386/gptzfsboot/../btx/
lib/crt0.o
zfsboot.o sio.o gptzfsboot.o ld: gptzfsboot.o: No such file: No such
file or directory *** Error code 1
Stop in /usr/src/sys/boot/i386/gptzfsboot.
*** Error code 1
I am experiencing the exact same problem with a fresh svn checkout
Just my me too.
I did not experience the problem 24 hours ago (after ZFS version 13
update and zfsboot import).
That's it. Seems to work with the following patch :
--- sys/boot/i386/gptzfsboot/Makefile.orig 2008-11-20
19:58:45.0 +0100
+++ sys/boot/i386/gptzfsboot/Makefile 2008-11-20 20:01:53.0
+0100
@@ -65,7 +65,7 @@
zfsboot.o: ${.CURDIR}/../../zfs/zfsimpl.c
.if ${MACHINE_ARCH} == amd64
-beforedepend gptzfsboot.o: machine
+beforedepend gptzfsboot.bin: machine
CLEANFILES+= machine
machine:
ln -sf ${.CURDIR}/../../../i386/include machine
Sorry for replying again to my own post :)
The patch is crap, in fact it just breaks the already broken
conditional. At least I can buildworld on amd64 now (I don't use the
recently introduced gptzfsboot).
Makefile experts ?
I think I fixed this in r185175. Sorry for the inconvenience.
Hi Doug,
Yes and thank you. I am able to build the world now : No appologies
necessary, I'm just glad it wasent something I did on my machine (The build
failure happened exactly at the same time I moved /usr/src and /usr/obj into
a seperate zfs..
-Peg
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
who on FreeBSD 8.0 - AMD64
Hello Hackers, I noticed something the other day that I thought was a bit weird. I had a high amount of HD activity, so I wanted to see who was on my machine. I tried using the who command and received no information (not even for myself). I have found that various methods of signing in cause different behavior, presumably due to being assigned different terminal names. For instance: If I open an Xterm, or telnet into the machine, I will not see any information (Although a who -q does), however, if I SSH or sign in on the console, I get the results I was expecting. Am I missing something or being a bit thick? (please see below for examples) Peg [through a xterm] feathers$ who feathers$ [through a telnet] feathers$ telnet localhost Trying ::1... Connected to localhost. Escape character is '^]'. Trying SRA secure login: User (XX): Password: [ SRA accepts you ] FreeBSD/amd64 (feathers.peganest.com) (pts/2) SNIP You have new mail. feathers$ who feathers$ [Through a SSH connection] titan$ ssh feathers Enter passphrase for key '/home/X/.ssh/id_rsa': Last login: Mon Nov 24 01:45:08 2008 from localhost Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 8.0-CURRENT (FEATHERS) #1: Sat Nov 22 16:07:04 UTC 2008 SNIP feathers$ feathers$ who X pts/3Nov 24 01:47 (XXX.XXX.XXX.XXX) feathers$ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: who on FreeBSD 8.0 - AMD64
On Monday 24 November 2008 02:19:40 Garrett Cooper wrote: On Nov 23, 2008, at 5:52 PM, Pegasus Mc Cleaft wrote: Hello Hackers, SNIP `who' works perfectly fine for me on CURRENT/AMD64 synced up 3 days ago, via an ssh terminal. Can you provide more details, e.g. when was your last sync date, did you blow away your utmp directory, etc? Thanks, -Garrett Hi Garrett, Its actually the other way around. If I SSH into the machine, I see my login in the 'who', however, if I telnet in or use a xterm I dont.. The last sync/build world/build kernel I have done was about 24 hours ago, however, I think the problem has been going on for a while now. I noticed it about a month ago and forgot about it until the other day when I tried using 'who' again. I havent blown away the utmp directory (or touched it, for that matter). I can try clearing if, if you think it may help? Ta Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: who on FreeBSD 8.0 - AMD64
On Monday 24 November 2008 02:42:08 you wrote: On Sun, Nov 23, 2008 at 6:26 PM, Pegasus Mc Cleaft [EMAIL PROTECTED] wrote: On Monday 24 November 2008 02:19:40 Garrett Cooper wrote: On Nov 23, 2008, at 5:52 PM, Pegasus Mc Cleaft wrote: Hello Hackers, SNIP `who' works perfectly fine for me on CURRENT/AMD64 synced up 3 days ago, via an ssh terminal. Can you provide more details, e.g. when was your last sync date, did you blow away your utmp directory, etc? Thanks, -Garrett Hi Garrett, Its actually the other way around. If I SSH into the machine, I see my login in the 'who', however, if I telnet in or use a xterm I dont.. The last sync/build world/build kernel I have done was about 24 hours ago, however, I think the problem has been going on for a while now. I noticed it about a month ago and forgot about it until the other day when I tried using 'who' again. I havent blown away the utmp directory (or touched it, for that matter). I can try clearing if, if you think it may help? Ta Peg Actually, no please don't blow it. After hearing that it occurs only over ssh I tried with a local login and it functions exactly the same as with the ssh terminal. 1. What's the exit code after you try and execute who? 2. `ls -l /var/run/utmp'? Should be set to mode 00644. Thanks, -Garrett Hi Garrett, I'm not sure of the exit code, but it dosent display any errors, just returns nothing. The /var/run/utmp is set to 00644 as well.. Can you try telneting into your box (even as a localhost) and see if if it still functions correctly? Using a telnet login or a xterm window is the only time I see it fail. Ta Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: build problems with gptzfsboot (AMD64) 8.0-CURRENT
On Thursday 20 November 2008 18:57:53 Olivier SMEDTS wrote: What is your MACHINE_ARCH ? Mine is amd64, I think there's a problem with the conditional in sys/boot/i386/gptzfsboot/Makefile. ld doesn't need gptzfsboot.o on i386. Olivier 2008/11/20 Olivier SMEDTS [EMAIL PROTECTED]: 2008/11/20 Pascal Hofstee [EMAIL PROTECTED]: On Thu, 20 Nov 2008 01:46:31 - Pegasus Mc Cleaft [EMAIL PROTECTED] wrote: Hi everyone, I am having difficulties rebuilding the world after some patches were made today. I was wondering if anyone else is experiencing the same troubles? SNIP Hi Oliver, My machine is an Core2 Quad running under AMD64. (CPUTYPE?=core2) Thanks for replying. It puts my mind to ease because I was thinking it was a problem I created (I recently moved the /usr/src directory into a seperate zfs filing system) Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
build problems with gptzfsboot (AMD64) 8.0-CURRENT
Hi everyone, I am having difficulties rebuilding the world after some patches were made today. I was wondering if anyone else is experiencing the same troubles? ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x0 -o gptzfsboot.out /usr/obj/usr/src/sys/boot/i386/gptzfsboot/../btx/lib/crt0.o zfsboot.o sio.o gptzfsboot.o ld: gptzfsboot.o: No such file: No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/gptzfsboot. *** Error code 1 Stop in /usr/src/sys/boot/i386. *** Error code 1 Stop in /usr/src/sys/boot. *** Error code 1 Stop in /usr/src/sys. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. feathers# ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Doubt] Can a PCI device communicate with another PCI or other device?
On Tuesday 14 October 2008 19:32:47 Srinivas wrote: Hello, I have a small doubt. Suppose I have a PCI card with a general purpose CPU on it. Could it be able to communicate with another PCI device or ISA device(lets say IDE hard disk)? Hi Srinivas, Others may have a different opinion on this, and I am curious to see there input to this question as well. I tried doing something like this years ago with the Blackfin processor, but I found it to be not a good idea. While I could DMA transfer memory from the DSP into the physical memory of another device (In my case, the HD controller) I couldn't take control of IRQ´s. Other potential problems arose that turned me off to the whole idea (Data concurrency between the DSP-HD and the host-HD). Even if you got past these problems you would still face having to deal with any number of filing systems formats. I found it much easier to make a device driver and service/daemon on the host machine that proxi-requested things for the DSP board and burped it into ram that the DSP could then grab and process (or dump to disk from, in the other direction). While the speed may not be brilliant, it made things a lot easier for me to manage on a software level. In later revisions, I re-spun the PCB so it had an IDE controller local to the DSP and stuck an PLX-Tech PCI to PCI bridge between the host and the DSP so I could manage 2 small memory windows between the two (One for API commands, and the other data) with a single IRQ back to the host. This allowed me to have a high-speed IDE port local to the DSP where it was needed, and a slower link back to the host CPU for pulling video files, etc. Hope this helps, Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol broken in 7.1-PR
On Monday 29 September 2008 05:07:13 Andrey V. Elsukov wrote: Bruce Cran wrote: I'm also seeing this problem on my amd64 7.1-PRERELEASE system: atacontrol list ATA channel 0: Master: acd0 HL-DT-ST DVD+/-RW GSA-T11N/A102 ATA/ATAPI revision 5 Slave: no device present atacontrol: ioctl(IOCATADEVICES): Device not configured I've attached the dmesg, and truss output from atacontrol list. This is known problem and it fixed in CURRENT. You need to apply this patch: http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/atacontrol/atacontrol.c.diff ?r1=1.47;r2=1.48 I cc'ed person, who commited this fix. Hi, Poul-Henning, I think it should be MFCed before release. Thanks everyone, I just got up this morning and used the above patch and now everything is working great! Thanks to everyone for your help Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: atacontrol broken in 7.1-PR
Again I would like to extend my thanks to everyone who helped with this problem, and a special thank you Jeremy and Bruce for trying to sus out where the fault might be. Your input and support is deeply appreciated. Peg -Original Message- From: Dag-Erling Smørgrav [mailto:[EMAIL PROTECTED] Sent: 29 September 2008 16:01 To: Poul-Henning Kamp Cc: Bruce Cran; freebsd-hackers@freebsd.org; Andrey V. Elsukov; Pegasus McCleaft Subject: Re: atacontrol broken in 7.1-PR Dag-Erling Smørgrav [EMAIL PROTECTED] writes: I'll take care of it. kib beat me to it... DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.7.4/1695 - Release Date: 29/09/2008 07:40 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: atacontrol broken in 7.1-PR
On Sunday 28 September 2008 21:42:41 Jeremy Chadwick wrote: On Sun, Sep 28, 2008 at 10:43:58AM +, Pegasus McCleaft wrote: I was wondering if anyone else is experiencing this problem. I have recently reloaded my machine (due to a meltdown of my primary boot drive) and noticed that under 7.0-rel the atacontrol command seems to work great, however, under 7.1 I get and error atacontrol: ioctl(IOCATADEVICES): Device not configured What arguments did you give atacontrol? Sorry, forgot to add that in. I was typing from a terminal window while xorg was rebuilding. Perhapse some more usefull information to follow : feathers# atacontrol list atacontrol: ioctl(IOCATADEVICES): Device not configured Has anyone else seen this error. I wouldent be conserned if it wasent for the fact that it worked under 7.0-rel but now dosent. The machine is using both the: atapci0: SiI SiI 3132 SATA300 controller atapci1: JMicron JMB363 SATA300 controller atapci is just the PCI portion, and doesn't show any sign of the ATA driver being attached. Do you have ataX (e.g. ata0) devices showing up in dmesg? Yea.. The machine is otherwise running fine, and also loaded the driver for the ata raid controller (I made the machine boot off a raid-1 pack and made slices on the pack for /, /usr, /var . The rest zfs for /usr/home) Thinking about it, I also added atapicd in the kernel config so I could use things like K3B and xcdroast.. I dont know if maybe that shim might be causing issues. I'll try making another kernel without it and giving that a try. feathers# dmesg | grep ata atapci0: SiI SiI 3132 SATA300 controller port 0x9000-0x907f mem 0xe7004000-0xe700407f,0xe700-0xe7003fff irq 16 at device 0.0 on pci3 atapci0: [ITHREAD] ata2: ATA channel 0 on atapci0 ata2: [ITHREAD] ata3: ATA channel 1 on atapci0 ata3: [ITHREAD] atapci1: JMicron JMB363 SATA300 controller mem 0xec10-0xec101fff irq 19 at device 0.0 on pci5 atapci1: [ITHREAD] atapci1: AHCI called from vendor specific driver atapci1: AHCI Version 01.00 controller with 2 ports detected ata4: ATA channel 0 on atapci1 ata4: [ITHREAD] ata5: ATA channel 1 on atapci1 ata5: [ITHREAD] atapci2: JMicron JMB363 UDMA133 controller port 0xb000-0xb007,0xb100-0xb103,0xb200-0xb207,0xb300-0xb303,0xb400-0xb40f irq 16 at device 0.1 on pci5 atapci2: [ITHREAD] ata6: ATA channel 0 on atapci2 ata6: [ITHREAD] atapci3: Intel AHCI controller port 0xe600-0xe607,0xe700-0xe703,0xe800-0xe807,0xe900-0xe903,0xea00-0xea1f mem 0xec406000-0xec4067ff irq 19 at device 31.2 on pci0 atapci3: [ITHREAD] atapci3: AHCI Version 01.20 controller with 6 ports detected ata7: ATA channel 0 on atapci3 ata7: [ITHREAD]
Re: atacontrol broken in 7.1-PR
On Sunday 28 September 2008 23:37:09 Jeremy Chadwick wrote: snip Yea.. The machine is otherwise running fine, and also loaded the driver for the ata raid controller (I made the machine boot off a raid-1 pack and made slices on the pack for /, /usr, /var . The rest zfs for /usr/home) I don't know what filesystems you have assigned to what drives, but please be aware there are known major problems with Silicon Image controllers on FreeBSD, Linux, and Windows. The most common problem is silent data corruption. I can refer you to previous discussions of this problem if you'd like. If at all possible, disable this controller in the BIOS, and do not use it. I didnt know that, so thanks for telling me. As luck would have it, I just have the DVD-RW drive on the Silicon Image controller. I originally tried to use the SI controller for the primary boot, but the driver support was not there for it with the 7.0 boot disks, so I played with the cables and put the two raid-1 drives on the JMicron controller. It was only after I got a 7.1 kernel installed that it showed back up and I got use of the DVD-Rom drive. I see the system has an Intel AHCI-based controller (probably an ICH10 chip, since the ICH10 is the first to support 6 SATA channels). I would recommend using that for as much as you can (I see you have disks ad14 through ad24 off that controller). Its actually a ICH9R based motherboard by Gigabyte (GS-X48-DS5). It seems to be a decent board, with the exception of, what I believe to be a hardware fault with the watchdog timer. I think they have put a pull-up resistor on the speaker line on the ICH9 that on release of reset is hardware disabling the watchdog timer function. I have gone round and round with them on this, but I can not adequately explain the problem to there tech-support as there is a language barrier. Thinking about it, I also added atapicd in the kernel config so I could use things like K3B and xcdroast.. I dont know if maybe that shim might be causing issues. I'll try making another kernel without it and giving that a try. I highly doubt that's the problem. Can you please include your kernel configuration file here? Also, please do not copy/paste the file; I noticed in your dmesg|grep ata output, all of the lines had trailing spaces (I've stripped them off). Sure, I'll attach the config file and also a full dmesg. Forgive the state of the config file.. Its basically a copy of the GENERIC with a bunch of stuff added at the end. I've CC'd [EMAIL PROTECTED] who maintains ata(4). I see no reason why atacontrol list would be returning such an error. Thank you... I'm not sure why I'm having the problem either. I just thought it was strange that it worked using the GENERIC kernel from 7.0-REL but once I built the latest 7.1-PR it stopped working. My machine (feathers) is actually a sister machine from one I built at work so I could test things out at home and then make changes to the production machine. The other machine does not have the SI controller in it (everything else is the same) and it also will not do the atacontrol list without erroring in the same way. I will hold my hands up and say that it could very well be something I have done in the config file by adding so much 'Stuff' to it.. There could be a conflict there I dont know about.. Thanks again for you time, Peg # # GENERIC -- Generic kernel configuration file for FreeBSD/amd64 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/amd64/conf/FEATHERS,v 1.484.2.7 2008/04/10 22:09:21 rwatson Exp $ cpu HAMMER ident FEATHERS # To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints # Default places to look for devices. #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler options PREEMPTION # Enable kernel thread preemption options INET# InterNETworking options INET6 # IPv6 communications protocols options SCTP# Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options
Re: Call for testers - new ichwd ids
On Monday 25 August 2008 12:52:48 Olivier SMEDTS wrote: Hello hackers, If you have an Intel ICH chipset and the ichwd driver doesn't work for you, please test this patch : Oliver, Thanks for the patch, but sadly this didnt help the situation I have with my motherboard. It identifies the ICH9R chipset, but sadly looks like the motherboard company has disabled the watchdog action. I have already spoken to the motherboard producers and they sware they have not, but looking at the code I cant see any other explanation for the behavior. The motherboard is a Gigabyte GA-X48-DS5 Bios F7 (latest) Output is: ichwd0: Intel ICH9R watchdog timer on isa0 ichwd0: ICH WDT present but disabled in BIOS or hardware device_attach: ichwd0 attach returned 6 I looked at the datasheet for the ICH9 chipset and I believe they have a pull-up on the speaker line that is telling the chip to disable the watchdog functions. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
RFC Newer binutils
Hello everyone, I was wondering if anyone knows if there is planned an update to the binutils for the base system planned? The reason why I'm asking is (occasionally) I use a later gcc then what comes with the system to take advantage of the newer opcodes in the Core 2. Unfortunately the base assembler dosent understand these new opcodes and things bomb out. I have installed the latest (2.18) version of buntuils and I can compile at that point. Things just get sorta ickey having two versions of binutils on the machine and thought it would be much simpler to have an update to the base. I know there are still problems with the later gcc versions (like 4.3) and can understand why FBSD hasent moved to it yet, but didnt think there was any harm in updating to the later versions of as, etc.. Ta Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: IPv6 CVS
On Thursday 07 August 2008 19:47:31 David Malone wrote: On Tue, Aug 05, 2008 at 10:34:09PM +0100, Bruce Cran wrote: The problem is cvsupd - since it's written in Modula3 and doesn't support IPv6 you have to use an inetd/netcat hack to accept IPv6 connections on the server. As mentioned in http://lists.freebsd.org/pipermail/freebsd-current/2008-July/086710.html cvsup18.freebsd.org and cvsup4.ru.freebsd.org both accept IPv6 connections. cvsup.ie.freebsd.org also offers cvsup over IPv6: http://lists.freebsd.org/pipermail/freebsd-stable/2003-July/001983.html Thanks David, I just tried cvsup.ie.freebsd.org and it worked a treat as well.. I appreciate the information. Amazingly, it was announced exactly 5 years to the day before the message about cvsup18 above. Synchronisities... Dont you just love them ; I thought about setting up a v6 cvsup server, if the community thought that another mirror would be useful. Don't know how that may be received, however.. Useful or just redundant? Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
IPv6 CVS
Hi all, Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As in receiving the STABLE and ports branches) I currently use cvs.freebsd.org but it dosent have an record. Ta Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: IPv6 CVS
-Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Stefan Sperling Sent: 05 August 2008 11:51 To: Maxim Konovalov Cc: freebsd-hackers@freebsd.org; Pegasus Mc Cleaft; Tim Clewlow Subject: Re: IPv6 CVS On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: Hi all, Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As in receiving the STABLE and ports branches) I currently use cvs.freebsd.org but it dosent have an record. Ta Peg dig cvsup4.freebsd.org cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an ipv6 address as well. AFAIK the Modula3 runtime does not support IPv6. Stefan Thanks everyone, Looks like Tim is correct where I am able to ping cvsup4, but unfortunately the csup utility reports a fail (Connection Refused) as it tries to connect to the V6 address. It will quite happily connect to the same machine V4. Stefan's explanation may be the reason for this.. Dono.. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: IPv6 CVS
-Original Message- From: Jeremy Chadwick [mailto:[EMAIL PROTECTED] Sent: 05 August 2008 13:28 To: Pegasus Mc Cleaft Cc: 'Stefan Sperling'; 'Maxim Konovalov'; freebsd-hackers@FreeBSD.org; 'Tim Clewlow' Subject: Re: IPv6 CVS On Tue, Aug 05, 2008 at 12:04:33PM +0100, Pegasus Mc Cleaft wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Stefan Sperling Sent: 05 August 2008 11:51 To: Maxim Konovalov Cc: freebsd-hackers@freebsd.org; Pegasus Mc Cleaft; Tim Clewlow Subject: Re: IPv6 CVS On Tue, Aug 05, 2008 at 02:16:35PM +0400, Maxim Konovalov wrote: On Tue, 5 Aug 2008, 19:52+1000, Tim Clewlow wrote: Hi all, Does anyone know if there are any IPv6 CVS servers for FreeBSD? (As in receiving the STABLE and ports branches) I currently use cvs.freebsd.org but it dosent have an record. Ta Peg dig cvsup4.freebsd.org cvs != cvsup. Speaking of cvsup -- cvsup4.ru.freebsd.org has an ipv6 address as well. AFAIK the Modula3 runtime does not support IPv6. Stefan Thanks everyone, Looks like Tim is correct where I am able to ping cvsup4, but unfortunately the csup utility reports a fail (Connection Refused) as it tries to connect to the V6 address. It will quite happily connect to the same machine V4. csup is written in C; it does not use Modula3/ezm3. cvsup uses Modula3/ezm3. cvsup4, despite having a public IPv6 address, does not have the cvsup server bound to IPv6. Meaning: it's IPV4 only. Try a different server. Get a list (in sh/bash): for i in `jot 30 1`; do echo == cvsup$i ; (host cvsup$i.freebsd.org) | grep -i ipv6; done Jeremy, AH HA! Ok.. Thanks for the bash script. I tried it and ran through all the servers... The only server that seems to have cvsup bound to the V6 stack is cvsup18.freebsd.org (raines.cse.buffalo.edu) That helps a lot. Thank you very much.. Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel Memeory - AMD64
Hello everyone, I was wondering if you guys could comment or give guidance to the following question: By watching the threads here and also in the CVS commit group, I see there has been (or will be) a change to the way the kernel addresses memory. Specifically in its ability to use memory beyond the 2 gig boundry? At the moment, I have increased the limits on my box by adding the following to the /boot/loader.conf file: vm.kmem_size_max=1073741824 vm.kmem_size=1073741824 I did this because of ZFS and its requirements for memory (Just take a moment here to say thank you to the people involved in porting ZFS to the BSD platform. I love it! And I use it all the time on my machines) But with the recent changes to how the kernel addresses memory and its limits, am I better off removing these entries and letting the kernel grow is memory usage as needs be, or should I increase the limits further? If the answer is application specific, one of the boxes is a mysql server, Q6600 w/ 4 Gigs.. The other is a Q9450 w/ 8 Gigs of ram that serves as my desktop machine (xorg, kde, kdevelop, etc) Thank you in advance for your comment, Peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 3D for AMD64 (was Re: Lack of Flash support is no longer acceptable. Bounty established...)
http://gitweb.freedesktop.org/?p=xorg/driver/xf86-video-radeonhd;a=summary -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED] On Behalf Of Robert Huff Sent: 27 June 2008 14:59 To: Sean Cavanaugh Cc: freebsd-hackers@freebsd.org Subject: RE: 3D for AMD64 (was Re: Lack of Flash support is no longer acceptable. Bounty established...) Sean Cavanaugh writes: AMD is actively working to opensource the *nic drivers for the ATI cards starting with the most recent. From a news article iI came across they were actually hiring a whole new department whose sole purpose was to add more of the older cards to the open sorce drivers as well as eventually having 3d acceleration. As for the NEW 4000 series, the card will come with full drivers for windows and Linux on the install CD. granted there is still some coding to get BSD drivers, but AMD is making life better for *nix user with ATI cards. Is there any place (web site, wiki, blog) where the public can track this effort? Robert Huff ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers- [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: AMD Geode LX crypto accelerator (glxsb)
On Sunday 22 June 2008 19:20:41 Patrick Lamaizière wrote: On FreeBSD 7, OpenSSL does not use the cryptodev engine by default. This is a known problem. See http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-06/msg00076.ht ml openssl speed -evp aes-128-cbc -elapsed -engine cryptodev Try patching openssl to force the use of the crypto hardware by default (like ssh, etc) ~Peg --- eng_cryptodev.c.orig2008-02-05 18:10:31.0 + +++ eng_cryptodev.c 2008-06-14 18:25:36.175353823 +0100 @@ -1127,6 +1127,7 @@ } ENGINE_add(engine); + ENGINE_set_default_ciphers(engine); ENGINE_free(engine); ERR_clear_error(); } ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Looking for *cheap* embedded platform w- 2 ethernets
On Saturday 21 June 2008 14:44:02 Anish Mistry wrote: On Friday 20 June 2008, joe mcguckin wrote: I'm looking for a cheap and small embedded platform to use as a portable vpn endpoint. It doesn't have to be fast, it just has to run *BSD. Any suggestions?? www.pcengines.ch Take a look at the sokeris pcb's. I have had good luck making embedded routers out of them. www.sokeris.com ~peg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Hifn 7955 doesn't work with Freebsd 7.0-release
Hi all.. I found the same problem recently, but I also found someone's post on the Internet that suggested a change to the /usr/src/crypto/openssl/crypto/engine/eng_cryptodev.c file. I made the change to the file and it definitely does force openssl to use the crypto hardware. I am not sure if there is any backlash to this patch, but I have used it on 2 of my servers with the Hifn 7955 hardware and it seems to be fine. --- eng_cryptodev.c.orig2008-02-05 18:10:31.0 + +++ eng_cryptodev.c 2008-06-14 18:25:36.175353823 +0100 @@ -1127,6 +1127,7 @@ } ENGINE_add(engine); + ENGINE_set_default_ciphers(engine); ENGINE_free(engine); ERR_clear_error(); } 0n Wed, May 21, 2008 at 08:19:26PM -0700, Sam Leffler wrote: Unfortunately openssl doesn't use the accelerator by default. This means all apps that use openssl likewise are not automatically accelerated. I suggested a patch but it was not accepted. I can't recall how you force openssl and/or consumers to use the device. How annoying is that. Why wasn't the patch accepted ? -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. Ifyou have received this email in error, you are requested to contact the sender and delete the email. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
