RE: deinstall ports
Rodrigo Galiano wrote: No, if you make 'deinstall' under a specific port it will only uninstall the software package with the dependencies. If you want to deinstall dependencies do the command 'make clean' to check out what will be actually installed and diff the output with the results obtained with the 'pkg_info' command. Then finally do the command 'pkg_delete #package_name#' to deinstall the dependencies. I believe the original question was if removing a package would by default removes the dependencies of the package too, to which the answer is no. I don't think the intention of the original poster was to attempt to actually deinstall the dependencies. Perhaps I misread the original post. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: deinstall ports
Vladislav Storojenco wrote: Hello all, I'm new user in FreeBSD and have a question about ports.. If a port is depend on others ports, during the deinstall it will deinstall and all dependencies? It depends on what command you issue. If you try and remove an installed package which had other packages dependent upon it, then it will fail. # pkg_delete /var/db/pkg/apache-2.2.4_2/ pkg_delete: package 'apache-2.2.4_2' is required by these other packages and may not be deinstalled: php5-5.2.1_3 php5-mysql-5.2.1_3 php5-pcre-5.2.1_5 php5-posix-5.2.1_3 php5-session-5.2.1_3 php5-simplexml-5.2.1_3 ... But you could force it by using `pkg_delete -f` if you wanted. This on its own will not remove the dependancies, you need to use `pkg_delete -rf` for that. If you run `make deinstall` from the port directory you get the same result as having used `pkg_delete -f` (but not -rf). Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: network performance 6.1 stable vs 4.9
Stephen Clark wrote: Hello List, We have a network appliance that is currently based on 4.9. We are in the process of releasing a new version based on 6.1 stable. You are going to get asked this, so I'll ask first. Whats the reason behind not running a more recent STABLE? I understand developing a product on a moving platform is not ideal, but its going to be mentioned! In our testing using nttcp thru the appliance we see insignifant difference in thruput between the 2 versions in a controlled environment - aproximately 94mbs on a 100mb lan. We have a person that is testing the both system inhouse surfing out over the internet on our T1 link and he complains that he is consistently seeing the 6.1 version being much slower than the 4.9 version (on the same hardware). He has been comparing the 6.1 system to 4.9 system for a couple of weeks and continues to insist the 6.1 version is much slower. You don't mention what the appliance actually does beyond just moving packets about? Surfing implies some sort of proxy or gateway device? Are there any sysctl tunables that may affect performance going over the internet with a slower link, dropped packets, etc that could cause this? Any ideas would be appreciated. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mfs and buildworlds on da SunFire x4600
Mars G. Miro wrote: Greetz, I got my hands on a SunFire x4600. This is a dual-core 8-way Opteron (dmesg shows 16 CPUs) w/c has 32G RAM. FreeBSD 6.2/amd64 runs fine on it despite: - 'reboot' doesnt work, machine just hangs in there. - front USB ports wont work for a USB keyboard, just use da ports at da back. I've read a lot of threads in da past (and da BSDCan 2006 paper) regarding mfs on /usr/src and /usr/obj to speed up buildworlds, unfortunately it doesnt seem to improve things. I've tried both a malloc and swap based async non-softupdates mfs (and rebooted da box every after) but my buildworld speeds seem to be just da same as I do it on da MPT SAS disk w/c is just around ~18mins. When you have 32GB of RAM and 16 CPUs I'm not sure this applies. Is 18 minutes really too long to wait? :-) Yeah, i know there's da tmpfs project but I was just wondering if I may have missed somthing in my mfs adventures. PS. s/da/the/g (please!) Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Reverting to 6.2-RELEASE
On Mon, 19 Mar 2007 11:31:54 + Pete French [EMAIL PROTECTED] wrote: I appear to have a machine which will not run RELENG_6_2, though it runs the released code quite happily. Is there a CVS tag I can use to revert the sources back to the way they were on RELEASE? I want to be able to verify that this is and track down what changed! I don't think it should ever be the case that something which runs X.Y-RELEASE will not run RELENG_X_Y should it ? RELENG_6_2_0_RELEASE You can use CVS Web to look them up: http://www.freebsd.org/cgi/cvsweb.cgi/src/ - Drop down box, Show only files with tag ... Cheers, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: install on usb hdd
On Mon, 12 Feb 2007 16:14:20 +0100 Zoran Kolic [EMAIL PROTECTED] wrote: Hi Andy! IIRC, you can only install to drives that the bios can see. You could try finding a computer whose bios can see the drive and installing from there. As long as you don't touch the internal drives on that machine, everything *should* be safe. YMMV Huh! My bios sees usb flash stick pretty easily. This is 2.5 inch hdd of WD and simple enclosure with two usb connectors for data and power. I've heard that not all enclosures could boot, but no further reading on the net. Could be this new hdd gone dead before even installed. I load umass module and cannot see headers saying WD etc. Does someone use 2.5 usb hdd to install at it at all? I'm stranded in this moment without clue. What data should bios get to add hdd to the boot list? How big is the drive? Perhaps it is too large for the BIOS? Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dd as an imaging solution.
On Sat, 03 Feb 2007 19:43:42 -0500 Sean Bryant [EMAIL PROTECTED] wrote: Several months ago I was using Freesbie 1.x to dd a harddrive across the network as a drive duplication effort. This worked 7 computers got the image. I'm trying to do this again so I got the new Freesbie release 2.0 and fired it up across the computers and tried something simple such as: dd if=/dev/ad0 bs=1m | nc othercomputer 1 on the image provider nc -l 1 | dd of=/dev/ad0 bs=1m on the computer to receive the image. I received an operation not permitted. My first thought was they must be mounted. a quick check, and it seems they weren't. Next, am I really root? And sure enough I was. After a bit of discussion in #freesbie on freenode got me to set kern.geom.debugflags to 16 and I was able to write to ad0 like I had previously done. Yet when I tried to write to an individual slice I was presented with the same error. Anyone have any clue ? The eventual goal is to have a mass imaging all at once with dd, nc and tee Check out G4U (NetBSD based) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsupgrade problem on 6.2-RELEASE
On Fri, 02 Feb 2007 14:31:28 +0100 Georg Bege [EMAIL PROTECTED] wrote: Hi Got a big problem today with portupgrade: ... Look at the other recent posts discussing this problem. The solution is manually upgrade portupgrade, see the other posts for more information. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsupgrade problem on 6.2-RELEASE
On Fri, 02 Feb 2007 15:49:34 +0100 Georg Bege [EMAIL PROTECTED] wrote: Hi Sry I dont get it, I searched now again and didnt find much. There is nothing about this on freebsd.org. If so then tell me where? Please be more clearer and give me an URL or so where its pointed out how to manual upgrade. FYI: This weeks mail to freebsd-stable@ http://docs.freebsd.org/mail/current/freebsd-stable.html -- You need to cv?sup your ports tree. cd /usr/ports/sysutils/portupgrade \ make deinstall clean install This should get you the most current version of portupgrade which has the patch, commited here: http://lists.freebsd.org/pipermail/cvs-ports/2007-February/117217.html Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Loosing spam fight
On Wed, 24 Jan 2007 15:03:06 -0200 Gustavo Feijó [EMAIL PROTECTED] wrote: FEATURE(`dnsbl', `sbl.spamhaus.org', `550 Mail from Try replacing with 'zen.spamhaus.org'. Can't comment on the others. Are you only using RBLs for spam prevention? HTH, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 ipw3945 on HP Pavilion dv6000
On Tue, 23 Jan 2007 11:48:58 +0200 Dominik Zalewski [EMAIL PROTECTED] wrote: Hi All, I'm running FreeBSD 6.2-RELEASE on HP Pavilion dv6000. I have a problem with intel 3945 wireless card. Simply, kernel didnt detect any ipw* device. When I'm loading a module if_ipw nothing happen. I tried also to compile this driver static into the kernel. No results :( I installed /usr/ports/net/ipw-firmware Any ideas? I can't help you specifically but often the output of `pciconf -lv` is useful to the developers. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Read_dma timeout - FreeBSD 6-1
On Fri, 19 Jan 2007 08:02:00 + Ikare.run [EMAIL PROTECTED] wrote: Hi, I've got some troubles with sata disks (Maxtor DiamondMax 10 160go) : this is the second one I use in less than 1 month. With the first one, I got more and more ofently TIMEOUT - READ_DMA errors ... so I changed it last week (I thought the disk was broken) ! And now, 10 days after installing the _new_ one, I re-get the sames errors. They appear randomly ... No log, no debug messages, just TIMEOUT - READ_DMA in dmesg Is there some tools on FreeBSD to test the SATA controler or the disks ? Some known bugs in drivers ? Does anyone get the same problem ? PS : when error occurs, the disk make a click !?!? Sounds like it is dying. What controller is this attached to? Have you tried another cable? SMART reports are useful only if the error is detectable / reported. Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failover-HA-Setup
On Wed, 17 Jan 2007 13:47:37 +0100 Richard [EMAIL PROTECTED] wrote: Hi there! I am looking for a solution for a small problem regarding a high availability setup. I am running heartbeat on a STABLE-system, the failover works fine for IP-adresses and I am able to see that a '/usr/local/etc/rc.d/mysql-server start' statement is issued. BUT since the variables for mysql are not set in rc.conf (Otherwise it would be started at startup), it isn't starting at all. So my question: How to set those rc.conf-variables in order to start services in such an setup? Or is there a better solution? Why have the backup MySQL server stopped at all? Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failover-HA-Setup
On Wed, 17 Jan 2007 14:47:43 +0100 Richard [EMAIL PROTECTED] wrote: Am Mittwoch, den 17.01.2007, 13:16 + schrieb Dominic Marks: setup. I am running heartbeat on a STABLE-system, the failover works fine for IP-adresses and I am able to see that a '/usr/local/etc/rc.d/mysql-server start' statement is issued. BUT since the variables for mysql are not set in rc.conf (Otherwise it would be started at startup), it isn't starting at all. So my question: How to set those rc.conf-variables in order to start services in such an setup? Or is there a better solution? Why have the backup MySQL server stopped at all? I am limited to an active/passive-Setup due to some Decisions in our company But if the IP address is not assigned to the backup system it won't be active. I suppose it depends on your policy, whatever that may be. Cheers, Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Failover-HA-Setup
On Wed, 17 Jan 2007 15:20:32 +0100 Richard Verwayen [EMAIL PROTECTED] wrote: Am Mittwoch, den 17.01.2007, 14:04 + schrieb Dominic Marks: On Wed, 17 Jan 2007 14:47:43 +0100 Richard [EMAIL PROTECTED] wrote: Am Mittwoch, den 17.01.2007, 13:16 + schrieb Dominic Marks: setup. I am running heartbeat on a STABLE-system, the failover works fine for IP-adresses and I am able to see that a '/usr/local/etc/rc.d/mysql-server start' statement is issued. BUT since the variables for mysql are not set in rc.conf (Otherwise it would be started at startup), it isn't starting at all. Why have the backup MySQL server stopped at all? I am limited to an active/passive-Setup due to some Decisions in our company But if the IP address is not assigned to the backup system it won't be active. I suppose it depends on your policy, whatever that may be. Oh, should I have mentioned that it is a shared SCSI-Storage in between? Probably :-) Richard Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fatal Trap 12 in 6.2-PRERELEASE
On Mon, 08 Jan 2007 07:48:54 -0500 J. W. Ballantine [EMAIL PROTECTED] wrote: I rebuilt and installed the kernel and world, and now when I try to boot the system it fails with a Fatal Trap 12: page fault while in kernel mode, with current process of 594 (ntpd). Since it always fails, I can't do any of the checks in FAQ Advance Topics, or other checks. Other than reinstall, is there anything I can do? Try booting the old kernel, which is called kernel.old. See the bottom of this page for how it is done: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-blocks.html Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: keyboard
On Mon, 08 Jan 2007 14:28:41 +0100 Philipp Ost [EMAIL PROTECTED] wrote: Cristian Fatu wrote: I want to disable keyboard port ... can somebody help me ? Comment out the following lines in your kernel configuration: deviceatkbdc # AT keyboard controller deviceatkbd # AT keyboard devicepsm # PS/2 mouse If you take this approach also add the USB keyboard device (ukbd) to this list. I don't know if this would achieve what you want but you could disable the consoles in /etc/ttys instead of removing the device support. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Seemingly) Spontaneous rebooting
On Tue, 19 Dec 2006 13:48:47 + Joe Holden [EMAIL PROTECTED] wrote: Ma wrote: I have almost the same reboots on my server. :( And it may reboot serval times a day. I'd like to know how to get crash dumps? What is added in your rc.conf? -- Ma Jie Hi, I used the rc.conf values as set out in rc,conf(5) [EMAIL PROTECTED] grep crash /etc/defaults/rc.conf dumpdev=NO# Device to crashdump to (device name, AUTO, or NO). dumpdir=/var/crash# Directory where crash dumps are to be stored I set dumpdev to my swap partition, although nothing got dumped, although I did upgrade it to -CURRENT as i'd exhausted everything else, and its not crashed since, not wishing to flame/troll/whatever, but 6.x seems to have a fair few issues. Did you make sure that /var was large enough to accommodate the crash dump? I've made that mistake before. Ta, Joe Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-PRE panic
On Thu, 23 Nov 2006 20:02:23 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: Date: Tue, 21 Nov 2006 16:51:51 + From: Dominic Marks [EMAIL PROTECTED] On Tue, 21 Nov 2006 08:41:00 -0800 Kevin Oberman [EMAIL PROTECTED] wrote: On Fri, 27 Oct 2006, Robert Watson [EMAIL PROTECTED] wrote: On Fri, 27 Oct 2006, Dominic Marks wrote: On Thu, 26 Oct 2006 13:10:41 +0100 Dominic Marks [EMAIL PROTECTED] wrote: On Thu, 26 Oct 2006 12:14:47 +0100 Dominic Marks [EMAIL PROTECTED] wrote: Received this one this morning. I was in Gnome, just opened sylpheed. Had a collection of other apps running, no particular high load. Debug kernel and vmcore available for interested developers (592MB ... I've turned on minidumps now.) And another, looks like the same again. This time I have a minidump (73MB) . Available for developers. I'm going to try going to latest STABLE and see if it goes away. And again, this time with latest STABLE. Help! (please) Ideas for a work-around would be appreciated as well. As before crash info is available to developers (93MB). If you have a serial console set up, could you compile DDB, INVARIANTS, and WITNESS into the kernel? When the panic occurs, run the following commands: show pcpu trace show allpcpu traceall show alllocks Has Dominic followed up on this? I am seeing the same problem on my Athlon 4400+ system (running i386) and have been crashing 3 or 4 times a day on a kernel from Nov. 9. Hi, no I have not. I disabled all the Gnome background bits, dbus, polkit and hald and it went away, and I didn't have time to come back to it as I need my desktop all day. I just updated to 6-Stable of Nov. 21 and it has not yet crashed, but if it fails again, I can provide the requested information. I really would like to see it resolved for the 6.2 release if at all possible. I'll csup and rebuild tonight so see if it has gone for me too. In my case, the crashes have mostly occurred when I was either not on the system at all or when I was just logged into it via SSH from a terminal window on another system. No X-server was running at the time of any crash. (But polkitd and hald are started at boot time, so they were running.) It happened again last night (at almost exactly midnight). Several failures seem to have coincided with crontab jobs and I have never had the system crash while I was logged on the the system directly. Either I was logged in over the net or was not logged in at all. Different experience from me. With a fresh kernel and the gnome daemons running I had an instant reboot, no core dump. Turning of polkitd and hald makes it go away reliably though. I intend to turn one of them back on to see if I can narrow it down further. Due to the holiday (in the US), is did not have an opportunity to do anything other then reboot it. I hope to have time to connect a laptop to the console so I can record everything that happens to submit. This si clearly not a common problem. What hardware do you have? Mine is an Athlon64-4400+ on an MSI mobo with 1GB of RAM. I suppose not. dmesg: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #19: Wed Nov 22 14:26:01 GMT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GDC083 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel (R) Xeon(TM) CPU 3.00GHz (2992.52-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf4a Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Logical CPUs per core: 2 real memory = 1072218112 (1022 MB) avail memory = 1040244736 (992 MB) ACPI APIC Table: DELL PE1420 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic2: Changing APIC ID to 10 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: DELL PE1420 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pci0: unknown at device 0.1 (no driver attached) pcib1: ACPI PCI-PCI bridge irq 16
Re: FreeBSD 6.2-PRE panic
On Fri, 24 Nov 2006 14:18:22 + (GMT) Robert Watson [EMAIL PROTECTED] wrote: On Fri, 24 Nov 2006, Dominic Marks wrote: It happened again last night (at almost exactly midnight). Several failures seem to have coincided with crontab jobs and I have never had the system crash while I was logged on the the system directly. Either I was logged in over the net or was not logged in at all. Different experience from me. With a fresh kernel and the gnome daemons running I had an instant reboot, no core dump. Turning of polkitd and hald makes it go away reliably though. I intend to turn one of them back on to see if I can narrow it down further. Due to the holiday (in the US), is did not have an opportunity to do anything other then reboot it. I hope to have time to connect a laptop to the console so I can record everything that happens to submit. This si clearly not a common problem. What hardware do you have? Mine is an Athlon64-4400+ on an MSI mobo with 1GB of RAM. Is there an open PR on this problem currently? I'm in the process of reviewing my outstanding network PRs for 6.2 and I'm having trouble tracking down all the pieces of this report. Not from me. Summary of my issue is that if I run polkitd/hald my 6.2 system will panic/reset every few hours. I setup a serial console as you suggested but couldn't work out how to get a serial console working in addition to my graphical desktop. Since this is my desktop I had to give up at that point. I've got debug kernel + core dumps which you can have but I don't believe they are very useful, nobody expressed much of an interest in them originally. I don't think my issue is network related although I do have an em NIC it has never given me any problems at all. I've just enabled polkitd without hald, perhaps this will identify that it is explicitly hald which makes my system so unhappy. Thanks, Dominic Thanks, Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: (Seemingly) Spontaneous rebooting
On Fri, 17 Nov 2006 07:37:58 + Joe Holden [EMAIL PROTECTED] wrote: Stefan Bethke wrote: Am 17.11.2006 um 08:05 schrieb Joe Holden: Hi, i'm observing random reboots on a dedicated machine I have with 11. How do you know it's rebbots as opposed to crashes/panics? Enable crashdumps in rc.conf and see if you get a dump. Stefan --Stefan Bethke [EMAIL PROTECTED] Fon +49 170 346 0140 The reason why I said (seemingly) spontaneous reboots was because there is nothing in logs, it looks exactly like its just had the reset button hit. I've added to rc.conf, now i've just got to wait for it to crash, which isn't fun as it could be weeks, heh See if you can get temperature readings from the hardware. Is the system busy? Dominic Ta, Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Installing/Upgrading Ports
On Wed, 15 Nov 2006 13:59:38 + Suhail Choudhury [EMAIL PROTECTED] wrote: Hi, Why trying to install ports via sysinstall - customise - ports, whichever location I try, I get the following message: Most people avoid sysinstall where possible :-) How can I install the ports directory on 6.1-RELEASE-p10? # cd /usr # fetch ftp://ftp.freebsd.org/pub/FreeBSD/ports/ports/ports.tar.gz # tar xzf ports.tar.gz # rm ports.tar.gz You should then use csup to update this ports tree: # cp /usr/share/examples/cvsup/ports-supfile /your/place/ # csup -h cvsup.xx.freebsd.org /your/place/ports-supfile 1. Replace xx with your two letter country code. Of if you have no luck with your country, try a neighbour. 2. If you don't have csup installed then you can install it from ports first: # cd /usr/ports/net/csup make install 3. Installing and learning portaudit and portupgrade (from ports) is also a good idea. Regards, Suhail. HTH, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-PRE panic
On Thu, 26 Oct 2006 13:10:41 +0100
Dominic Marks [EMAIL PROTECTED] wrote:
On Thu, 26 Oct 2006 12:14:47 +0100
Dominic Marks [EMAIL PROTECTED] wrote:
Hello,
Received this one this morning. I was in Gnome, just opened
sylpheed. Had a collection of other apps running, no particular
high load. Debug kernel and vmcore available for interested
developers (592MB ... I've turned on minidumps now.)
Thanks,
Dominic
And another, looks like the same again. This time I have a
minidump (73MB) . Available for developers. I'm going to try
going to latest STABLE and see if it goes away.
Thanks,
Dominic
And again, this time with latest STABLE. Help! (please)
Ideas for a work-around would be appreciated as well. As before
crash info is available to developers (93MB).
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x78
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06f447f
stack pointer = 0x28:0xe3570be0
frame pointer = 0x28:0xe3570be4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 17 (swi6: task queue)
trap number = 12
panic: page fault
Uptime: 46m0s
Physical memory: 1014 MB
Dumping 152 MB: 137 121 105 89 73 57 41 25 9
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06ceb46 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc06cee50 in panic (fmt=0xc095a826 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc0902ab1 in trap_fatal (frame=0xe3570ba0, eva=0) at
/usr/src/sys/i386/i386/trap.c:837
#4 0xc09021c9 in trap (frame=
{tf_fs = -992346104, tf_es = -988217304, tf_ds =
-480837592, tf_edi = -978617968, tf_esi = -995430016, tf_ebp =
-480834588, tf_isp = -480834612, tf_ebx = -995474688, tf_edx =
-995430016, tf_ecx = 4, tf_eax = 4, tf_trapno = 12, tf_err = 0,
tf_eip = -1066449793, tf_cs = 32, tf_eflags = 589831, tf_esp =
-995430016, tf_ss = -480834552})
at /usr/src/sys/i386/i386/trap.c:270
#5 0xc08ef60a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc06f447f in turnstile_setowner (ts=0xc4aa4300, owner=0x4) at
/usr/src/sys/kern/subr_turnstile.c:432
#7 0xc06f47ab in turnstile_wait (lock=0xc5ab79dc, owner=0x4) at
/usr/src/sys/kern/subr_turnstile.c:591
#8 0xc06c344f in _mtx_lock_sleep (m=0xc5ab79dc, tid=3299537280, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:579
#9 0xc06cdef9 in _sema_post (sema=0xc5ab79dc, file=0x0, line=0) at
/usr/src/sys/kern/kern_sema.c:79
#10 0xc04ee013 in ata_completed (context=0xc5ab7990, dummy=1) at
/usr/src/sys/dev/ata/ata-queue.c:481
#11 0xc06f30c4 in taskqueue_run (queue=0xc4af8580) at
/usr/src/sys/kern/subr_taskqueue.c:257
#12 0xc06f3353 in taskqueue_swi_run (dummy=0x0) at
/usr/src/sys/kern/subr_taskqueue.c:299
#13 0xc06b49b2 in ithread_execute_handlers (p=0xc4ab3430, ie=0xc4bab700) at
/usr/src/sys/kern/kern_intr.c:682
#14 0xc06b4af3 in ithread_loop (arg=0xc4b7f020) at
/usr/src/sys/kern/kern_intr.c:765
#15 0xc06b35e9 in fork_exit (callout=0xc06b4a90 ithread_loop, arg=0x4,
frame=0x4) at /usr/src/sys/kern/kern_fork.c:821
#16 0xc08ef66c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208
dmesg: (Dell PowerEdge SC1420)
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992,
1993, 1994 The Regents of the University of California. All
rights reserved. FreeBSD is a registered trademark of The
FreeBSD Foundation. FreeBSD 6.2-PRERELEASE #13: Thu Oct 26
13:18:36 BST 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GDC083
Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel
(R) Xeon(TM) CPU 3.00GHz (2992.51-MHz 686-class CPU) Origin =
GenuineIntel Id = 0xf4a Stepping = 10
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,
SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,
FXSR,SSE,SSE2,SS,HTT,TM,PBE
Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD
Features=0x2010NX,LM AMD Features2=0x1LAHF
Logical CPUs per core: 2
real memory = 1072218112 (1022 MB)
avail memory = 1040244736 (992 MB)
ACPI APIC Table: DELL PE1420
ioapic0: Changing APIC ID to 8
ioapic1: Changing APIC ID to 9
ioapic2: Changing APIC ID to 10
ioapic0 Version 2.0 irqs 0-23 on motherboard
ioapic1 Version 2.0 irqs 24-47 on motherboard
ioapic2 Version 2.0 irqs 48-71 on motherboard
lapic0: Forcing LINT1 to edge trigger
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112,
RF2413, RF5413) acpi0: DELL PE1420 on motherboard
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on
acpi0 cpu0: ACPI CPU on acpi0
acpi_button0: Power Button on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus
Re: FreeBSD 6.2-PRE panic
And again, this time with latest STABLE. Help! (please) Ideas for a work-around would be appreciated as well. As before crash info is available to developers (93MB). If you have a serial console set up, could you compile DDB, INVARIANTS, and WITNESS into the kernel? When the panic occurs, run the following commands: show pcpu trace show allpcpu traceall show alllocks Will do. Serial console might have to wait til Monday. I have a feeling it was being provoked by some of the new Gnome daemons (hald, polkitd). I've turned them off and I'm stable so far (~3 hours). Thanks Robert. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.2-PRE panic
Hello,
Received this one this morning. I was in Gnome, just opened
sylpheed. Had a collection of other apps running, no particular
high load. Debug kernel and vmcore available for interested
developers (592MB ... I've turned on minidumps now.)
Thanks,
Dominic
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x78
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06f39a3
stack pointer = 0x28:0xe3570be0
frame pointer = 0x28:0xe3570be4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 17 (swi6: task queue)
trap number = 12
panic: page fault
Uptime: 23h14m49s
Dumping 1022 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 1022MB (261516 pages) 1006 990 974 958 942 926 910
894 878 862 846 830 814 798 782 766 750 734 718 702 686 670 654
638 622 606 590 574 558 542 526 510 494 478 462 446 430 414 398
382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142
126 110 94 78 62 46 30 14
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06ce06a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc06ce374 in panic (fmt=0xc0959c10 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc0901e81 in trap_fatal (frame=0xe3570ba0, eva=0) at
/usr/src/sys/i386/i386/trap.c:837
#4 0xc0901599 in trap (frame=
{tf_fs = -992346104, tf_es = -988217304, tf_ds =
-480837592, tf_edi = -964483488, tf_esi = -995430016, tf_ebp =
-480834588, tf_isp = -480834612, tf_ebx = -995474688, tf_edx =
-995430016, tf_ecx = 4, tf_eax = 4, tf_trapno = 12, tf_err = 0,
tf_eip = -1066452573, tf_cs = 32, tf_eflags = 65543, tf_esp =
-995430016, tf_ss = -480834552})
at /usr/src/sys/i386/i386/trap.c:270
#5 0xc08ee9da in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc06f39a3 in turnstile_setowner (ts=0xc4aa4300, owner=0x4) at
/usr/src/sys/kern/subr_turnstile.c:432
#7 0xc06f3ccf in turnstile_wait (lock=0xc68326ac, owner=0x4) at
/usr/src/sys/kern/subr_turnstile.c:591
#8 0xc06c2973 in _mtx_lock_sleep (m=0xc68326ac, tid=3299537280, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:579
#9 0xc06cd41d in _sema_post (sema=0xc68326ac, file=0x0, line=0) at
/usr/src/sys/kern/kern_sema.c:79
#10 0xc04ee003 in ata_completed (context=0xc6832660, dummy=1) at
/usr/src/sys/dev/ata/ata-queue.c:481
#11 0xc06f25e8 in taskqueue_run (queue=0xc4af8580) at
/usr/src/sys/kern/subr_taskqueue.c:257
#12 0xc06f2877 in taskqueue_swi_run (dummy=0x0) at
/usr/src/sys/kern/subr_taskqueue.c:299
#13 0xc06b3ed6 in ithread_execute_handlers (p=0xc4ab3430, ie=0xc4bab700) at
/usr/src/sys/kern/kern_intr.c:682
#14 0xc06b4017 in ithread_loop (arg=0xc4b7f020) at
/usr/src/sys/kern/kern_intr.c:765
#15 0xc06b2b0d in fork_exit (callout=0xc06b3fb4 ithread_loop, arg=0x4,
frame=0x4) at /usr/src/sys/kern/kern_fork.c:821
#16 0xc08eea3c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2-PRE panic
On Thu, 26 Oct 2006 12:14:47 +0100
Dominic Marks [EMAIL PROTECTED] wrote:
Hello,
Received this one this morning. I was in Gnome, just opened
sylpheed. Had a collection of other apps running, no particular
high load. Debug kernel and vmcore available for interested
developers (592MB ... I've turned on minidumps now.)
Thanks,
Dominic
And another, looks like the same again. This time I have a
minidump (73MB) . Available for developers. I'm going to try
going to latest STABLE and see if it goes away.
Thanks,
Dominic
Unread portion of the kernel message buffer:
acd1: unknown transfer phase
kernel trap 12 with interrupts disabled
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x78
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06f39a3
stack pointer = 0x28:0xe3570be0
frame pointer = 0x28:0xe3570be4
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= resume, IOPL = 0
current process = 17 (swi6: task queue)
trap number = 12
panic: page fault
Uptime: 1h39m21s
Physical memory: 1014 MB
Dumping 177 MB: (CTRL-C to abort) (CTRL-C to abort) (CTRL-C
to abort) 162 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to
abort) 146 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to
abort) (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to
abort) 130 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to
abort) 114 98 82 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C
to abort) 66 50 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C
to abort) 34 18 2
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06ce06a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc06ce374 in panic (fmt=0xc0959c10 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc0901e81 in trap_fatal (frame=0xe3570ba0, eva=0) at
/usr/src/sys/i386/i386/trap.c:837
#4 0xc0901599 in trap (frame=
{tf_fs = -988151800, tf_es = -988217304, tf_ds =
-480837592, tf_edi = -986352032, tf_esi = -995430016, tf_ebp =
-480834588, tf_isp = -480834612, tf_ebx = -995474688, tf_edx =
-995430016, tf_ecx = 4, tf_eax = 4, tf_trapno = 12, tf_err = 0,
tf_eip = -1066452573, tf_cs = 32, tf_eflags = 589831, tf_esp =
-995430016, tf_ss = -480834552})
at /usr/src/sys/i386/i386/trap.c:270
#5 0xc08ee9da in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#6 0xc06f39a3 in turnstile_setowner (ts=0xc4aa4300, owner=0x4) at
/usr/src/sys/kern/subr_turnstile.c:432
#7 0xc06f3ccf in turnstile_wait (lock=0xc53576ac, owner=0x4) at
/usr/src/sys/kern/subr_turnstile.c:591
#8 0xc06c2973 in _mtx_lock_sleep (m=0xc53576ac, tid=3299537280, opts=0,
file=0x0, line=0)
at /usr/src/sys/kern/kern_mutex.c:579
#9 0xc06cd41d in _sema_post (sema=0xc53576ac, file=0x0, line=0) at
/usr/src/sys/kern/kern_sema.c:79
#10 0xc04ee003 in ata_completed (context=0xc5357660, dummy=1) at
/usr/src/sys/dev/ata/ata-queue.c:481
#11 0xc06f25e8 in taskqueue_run (queue=0xc4af8580) at
/usr/src/sys/kern/subr_taskqueue.c:257
#12 0xc06f2877 in taskqueue_swi_run (dummy=0x0) at
/usr/src/sys/kern/subr_taskqueue.c:299
#13 0xc06b3ed6 in ithread_execute_handlers (p=0xc4ab3430, ie=0xc4bab700) at
/usr/src/sys/kern/kern_intr.c:682
#14 0xc06b4017 in ithread_loop (arg=0xc4b7f020) at
/usr/src/sys/kern/kern_intr.c:765
#15 0xc06b2b0d in fork_exit (callout=0xc06b3fb4 ithread_loop, arg=0x4,
frame=0x4)
at /usr/src/sys/kern/kern_fork.c:821
#16 0xc08eea3c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6-Stable High Interrupt Rate on network
On Thu, 28 Sep 2006 11:57:22 -0300 Alexandre Biancalana [EMAIL PROTECTED] wrote: Hi list, Today I changed the main gateway from our network from PIII 733, 512 MB Ram running FreeBSD 4-STABLE to a Xeon 3.0, 1Gb Ram running FreeBSD 6-STABLE. But the performance of the network is worst than before. How are you measuring the performance? The new machine is a Dell PowerEdge 1800 have one quad DLink DFE-580TX, one quad Adaptec ANA-62044 and one on board Intel em. I enabled the polling on all interfaces, set the HZ to 1000 and set kern.polling.user_frac=30, but this does not happened. What else is the machine doing, firewall, nat, traffic shaping, proxy? -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bug on BTX
John Baldwin wrote: Hmm, are you willing to test a change that should fix that? If so, try http://people.freebsd.org/~jhb/patches/btx_crx.patch You'll need to do a 'make clean make make install' in /sys/boot after applying, and if the make install suceeeds, do a 'bsdlabel -B ad0s1' (replace ad0s1 with the actual slice you boot from). I think it should work (I think it was tested a while ago, but boot2 used to not fit, now it does though). Be warned though that if it doesn't work, you won't be able to boot from your disk. If that happens and you have a 6.x disc 1 lying around, you can boot into rescue mode and re-run 'bsdlabel' and move boot/loader.old to boot/loader on the root partition to get your system back. Ideally you'd try this on a system with data you don't care about (i.e., it's ok to just do a reinstall if it is hosed). Hi John. I tested the patch on my -CURRENT box, both with the BIOS DMA enabled and disabled and I can confirm it works successfully. Test system is was a Compaq EVO D510 CMT desktop. Thanks John, -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
USB keyboard LED lights cause audio to stutter
Hello, Has anyone else noticed this? Here is how to repeat it: 1. USB Keyboard 2. Sound card (CMedia 8738 in my case) 3. Recent -STABLE uname -v FreeBSD 6.2-PRERELEASE #10: Mon Sep 18 15:46:33 BST 2006 Now, play some music (I'm using XMMS) and press on any keyboard key which toggles an LED once a second is enough, just press it often you will observe that the audio slows down immediately and will slow down more the quicker you hammer on NUM-LOCK, CAPS-LOCK etc. Once you stop pressing the key the audio will resume the correct pace. All other activities on the system seem to be unaffected by it. Other keys do not have the same impact. I'm pretty sure this only started happening recently but I could have just not noticed it as much. From watching `systat -vmstat 1` during this it seems that whenever an LED key is pressed atkb receives between 20 and 100 interrupts and the slow down occurs. I'll catch up to -STABLE soon to check if it is still happening. dmesg: http://goodforbusiness.co.uk/~dom/gdc083.dmesg Thanks, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bug on BTX
John Baldwin wrote: Hmm, are you willing to test a change that should fix that? If so, try http://people.freebsd.org/~jhb/patches/btx_crx.patch You'll need to do a 'make clean make make install' in /sys/boot after applying, and if the make install suceeeds, do a 'bsdlabel -B ad0s1' (replace ad0s1 with the actual slice you boot from). I think it should work (I think it was tested a while ago, but boot2 used to not fit, now it does though). Be warned though that if it doesn't work, you won't be able to boot from your disk. If that happens and you have a 6.x disc 1 lying around, you can boot into rescue mode and re-run 'bsdlabel' and move boot/loader.old to boot/loader on the root partition to get your system back. Ideally you'd try this on a system with data you don't care about (i.e., it's ok to just do a reinstall if it is hosed). Certainly. I'll try this out tomorrow and let you know how it goes. I have a machine running -CURRENT which can be used as guinea pig. Thanks John. -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: winbindd won't start
[2006/09/24 11:30:15, 0] libsmb/cliconnect.c:cli_session_setup_spnego(776) Kinit failed: Cannot contact any KDC for requested realm Failed to join domain! As far as I know, nothing has changed. Does anyone have any suggestions? Is your /etc/krb5.conf intact and correct? Do you have a valid ticket? (klist) Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with OpenVPN+routing and creating tun0 interface
Václav Haisman wrote: Hi, I want to set up OpenVPN to create and configure tun0 interface and connect to OpenVPN server. The main obstacle seems to be my inability to configure either OpenVPN or FreeBSD to actually create that tun0 interface. If I try to create it manually I get this: $ ifconfig -v tun create inet 192.168.23.203 192.168.23.1 ifconfig: SIOCIFCREATE: Invalid argument The kernel config has the device tun line and there are tun[0-3] in /dev. So what am I doing wrong? -- Vaclav Haisman I always let OpenVPN create them for me. Just starting the openvpn process seems to do the magic. What happens when you try and do that? Thanks, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bug on BTX
CyberSans AirBort wrote: hello guys, sorry if i send email to wrong address. i have tested 6.2-BETA and the same problem still appear when i want to install it into compaq evo desktop; BTX HALTED. like previous version, it stucks when booting from cd on the first installation. i have follow so many discussion around the internet, and they are blaming compaq BIOS, some of them give solution such as change hdd mode from extended DMA to max PIO, but it won't work. and for your information, this machine had no problem when installed with windows or linux. please guys, i hope there will be a fixed on 6.2 so that it will load, installed, and run on my compaq evo desktop Go into the BIOS, disable BIOS DMA transfers **. After that it will boot normally. I have about 20 EVOs, which this change they run fine. This is true of all versions of FreeBSD I have ever tried. ** I can't remember the exact name of the option, but it is something along those lines. Enjoy, Dominic thank you cybersans ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bug on BTX
dick hoogendijk wrote: On 22 Sep Dominic Marks wrote: CyberSans AirBort wrote: i have tested 6.2-BETA and the same problem still appear when i want to install it into compaq evo desktop; BTX HALTED. Go into the BIOS, disable BIOS DMA transfers **. After that it will boot normally. I have about 20 EVOs, which this change they run fine. This is true of all versions of FreeBSD I have ever tried. Still remains the question on why FreeBSD is not able to boot when bios DMA transfers are set set to on, while XP and linux just do what they're supposed to. It should not be necessary i.m.h.o. Agreed. A very low priority however since it is so easy to work around. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: jail: socket unavaible
[EMAIL PROTECTED] wrote: hi list I'm tring to make apache work inside a jail (6.1) apachctl start gives following errors no listening sockets available, shutting down here's some sysctl values on my host security.jail.allow_raw_sockets: 1 security.jail.enforce_statfs: 2 security.jail.set_hostname_allowed: 1 security.jail.socket_unixiproute_only: 1 security.jail.sysvipc_allowed: 0 security.jail.chflags_allowed: 0 thanks for your helps Try making sure all your HTTPd instances on the system bind to a specific IP. Sounds to me like you have another web server bound to * outside the jail ? Dominic regards ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bind round robin
Oliver Brandmueller wrote: Hi. On Tue, Sep 19, 2006 at 02:00:23PM +0800, pinoyskull wrote: One of my client's domain has multiple IPs for redundancy, i configured his www as such wwwIN A 10.10.10.10 wwwIN A 192.168.0.10 Is there a way to prioritize 10.10.10.10 over 192.168.0.10? How do i configure it? DNS round robin is not about redundancy, the only thing you could have that way is a kind of load balancing (not the most sophisticated way, though). Whenever one of the servers fails, around half of the requests still goes there and then times out/gets conn refused or whatever the problem is. Prioritizing is not easily possible. Probably it helps if you add one of the IPs more often to the set, but I never tried that and did not read the docs on this topic, so before breaking your zone first read the specs, if this works! For serious redundancy with failover and/or load balancing with a good leveling you should consider getting a load balancer (be it hardware or software), better two so you don't have the single point of failure there :-) A good software load balancer which supports weighting is pen. In ports. http://siag.nu/pen /usr/ports/net/pen Dominic - Oliver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bind round robin
From the original message: [1] wwwIN A 10.10.10.10 wwwIN A 192.168.0.10 From pen homepage: This is pen, a load balancer for simple tcp based protocols such as http or smtp. As I know DNS uses both tcp and udp protocols. From the posters excerpt it looks like they are looking to load balance HTTP. [1] For failover you can try OpenBSD Packet Filter with CARP protocol. PF can do load-balacing using different algorithms also. CARP is ported to FreeBSD. More info on: http://pf4freebsd.love2party.net/carp.html Also true. Last time I looked at this however there was a big disclaimer saying that CARP's load balancing was likely to give a distorted distribution of load and I don't believe it does weighting. I believe this would also be a problem considering the example in [1]: From carp(4): Note: ARP balancing only works on the local network segment. It cannot balance traffic that crosses a router, because the router itself will always be balanced to the same virtual host. Cheers, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mod_php4 unavaible
[EMAIL PROTECTED] wrote: hi list I've updated php4 this morning, and my web site using lost php module. the php4 is unavailble on my system. /usr/ports/www/mod_php4 has been removed, and I don't know how to get it workind, From /usr/ports/UPDATING 20060506: AFFECTS: users of PHP AUTHOR: [EMAIL PROTECTED] The old PHP slave ports (phpN-cli, phpN-cgi and mod_phpN) were removed in favour of unified PHP ports that allow building any combination of PHP SAPIs (cli, cgi and apache module). The PHP CGI binary was renamed to php-cgi, so you should update the path in your script. To simplify the update process, *only* for this release a 'php' compatibility symlink to php-cgi will be created if you don't select the CLI SAPI. Before the upgrade you *should* run 'make config' in lang/php4 or lang/php5 to configure the SAPIs you want to install. As a consequence the default binary packages include the CLI and the FastCGI SAPIs. Dominic some ideas? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange behaviour of Samba with md mounted NTFS disc image
Hello, I observed some odd behaviour with a hard disc image I made with g4u (NetBSD based ghost-a-like Live CD). The NTFS file system is mounted read-only in a md device from the file. The mount point has is shared to the network via Samba 3. The strange part is that browsing from a Windows box the directories within the image appear as empty files. From a shell on the system however they seem to be directories. Once a directory has been entered from some means other than Samba (find does the trick) they appear as directories properly when browsing from the Windows system. I have other Samba shares on the system which are not NTFS images and they work as expected. This could be a bug in FreeBSD or Samba, I suppose? I'll file a PR on the issue if this is not already known about, can't find anything in Gnats. Thanks, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems again ... general problem of ICH7 or ATA?
Patrick M. Hausen wrote: Hello! On Mon, Aug 21, 2006 at 02:14:16PM +0100, Matt Dawson wrote: FWIW, the problem takes *far* longer to rear its head when the SATA controller has a PCI INT and IRQ to itself. Put a NIC onto a shared slot (a very Bad Thing [TM] as the BIOS simply maps the INT to a single IRQ and both devices end up sharing it. Now tranfer a large file over the network and watch the ensuing hilarity) and it happens at least every couple of days. Now, with the slot shared with the SATA controller empty, I have six days uptime since the last event, which means I'm probably due one any time now. FWIW - here's the setup of my systems that have not shown the problem so far: Device IRQ -- --- em0 16 em1 17 uhci0 23 uhci1 19 uhci2 18 uhci3 16 ehci0 23 fxp016 atapci1 19 This is the SATA300 controller Is there a method to force the controller to share its IRQ with, say, em0 for testing? You can use device.hints(5) to do this. I have the following in mine to force a RAID card and Sound card to share IRQ 17. You need to modify it to suit your environment. hw.pci3.13.INTA.irq=17 The `13' value is the device number, you can find this in dmesg, same for pciN. HTH, Dominic Regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems again ... general problem of ICH7 or ATA?
Patrick M. Hausen wrote: Hello! On Mon, Aug 21, 2006 at 02:14:16PM +0100, Matt Dawson wrote: FWIW, the problem takes *far* longer to rear its head when the SATA controller has a PCI INT and IRQ to itself. Put a NIC onto a shared slot (a very Bad Thing [TM] as the BIOS simply maps the INT to a single IRQ and both devices end up sharing it. Now tranfer a large file over the network and watch the ensuing hilarity) and it happens at least every couple of days. Now, with the slot shared with the SATA controller empty, I have six days uptime since the last event, which means I'm probably due one any time now. FWIW - here's the setup of my systems that have not shown the problem so far: Device IRQ -- --- em0 16 em1 17 uhci0 23 uhci1 19 uhci2 18 uhci3 16 ehci0 23 fxp016 atapci1 19 This is the SATA300 controller Is there a method to force the controller to share its IRQ with, say, em0 for testing? You can use device.hints(5) to do this. I have the following in mine to force a RAID card and Sound card to share IRQ 17. You need to modify it to suit your environment. hw.pci3.13.INTA.irq=17 The `13' value is the device number, you can find this in dmesg, same for pciN. HTH, Dominic Regards, Patrick M. Hausen Leiter Netzwerke und Sicherheit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ATA problems again ... general problem of ICH7 or ATA?
Patrick M. Hausen wrote: Hi, Dominic! On Mon, Aug 21, 2006 at 02:40:17PM +0100, Dominic Marks wrote: hw.pci3.13.INTA.irq=17 The `13' value is the device number, you can find this in dmesg, same for pciN. So I tried this: em1: Intel(R) PRO/1000 Network Connection Version - 6.0.5 port 0x5000-0x501f mem 0xdc18-0xdc19,0xdc10-0xdc17 irq 17 at device 0.0 on pci5 atapci1: Intel ICH7 SATA300 controller port 0x30e8-0x30ef,0x30dc-0x30df,0x30e0-0x30e7,0x30d8-0x30db,0x30b0-0x30bf mem 0xdc500400-0xdc5007ff irq 19 at device 31.2 on pci0 hw.pci0.31.2.INTA.irq=17 to force atapci1 to the same irq as em1. Didn't work. It's still using 19. Any hints? I myself only learnt about this relatively recently, so afraid not. Have you checked that it doesnt work if you use hw.pci5 I'm just guessing here, but it might be worth a shot. Cheers, Dominic Thanks, Patrick M. Hausen Leiter Netzwerke und Sicherheit ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Device conflict 3ware twe and CMedia sound card
John Baldwin wrote: On Friday 11 August 2006 05:14, Dominic Marks wrote: John Baldwin wrote: On Thursday 10 August 2006 11:27, Dominic Marks wrote: hint.pci3.13.INTA.irq=17 That should make twe0 use IRQ 17. I doesn't seem to have had the desired effect: kenv | grep pci3 hint.pci3.13.INTA.irq=17 grep twe0 /var/run/dmesg.boot twe0: 3ware Storage Controller. [...] port 0xdcb0-0xdcbf mem 0xdf00-0xdf7f irq 49 at device 13.0 on pci3 Erm, that should have worked. Did you just do 'kenv' to set it or did you reboot and set it in the loader? Also, what version are you running, and what revision of /sys/dev/pci/pci.c do you have? I set it in devices.hints and rebooted. FreeBSD gdc083.internal.graphdata.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #2: Mon Jul 17 16:30:13 BST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GDC083 i386 /usr/src/sys/dev/pci/pci.c: $FreeBSD: src/sys/dev/pci/pci.c,v 1.292.2.7 2006/01/31 14:42:43 imp Exp $ Hmm, ok. Well, the next step is to try and see why it isn't working. Can you patch the pci_assign_interrupt() function in /sys/dev/pci/pci.c to printf() the tunable name it generates via sprintf() each time it is invoked? Then boot with that and send me the dmesg? Thanks. A day later than promised: grep DEBUG: /var/run/dmesg.boot DEBUG: hw.pci0.2.INTA.irq DEBUG: hw.pci0.3.INTA.irq DEBUG: hw.pci0.4.INTA.irq DEBUG: hw.pci0.29.INTA.irq DEBUG: hw.pci0.29.INTB.irq DEBUG: hw.pci0.29.INTC.irq DEBUG: hw.pci0.29.INTA.irq DEBUG: hw.pci0.29.INTD.irq DEBUG: hw.pci0.31.INTA.irq DEBUG: hw.pci0.31.INTA.irq DEBUG: hw.pci0.31.INTB.irq DEBUG: hw.pci3.13.INTA.irq (**) DEBUG: hw.pci3.14.INTA.irq DEBUG: hw.pci4.0.INTA.irq DEBUG: hw.pci7.13.INTA.irq tail -1 /boot/device.hints hint.pci3.13.INTA.irq=17 So I'm assuming this is a case of group-blindness :) s/hint/hw/ I'll see how setting hw[...] instead of hint[...] works. Thanks, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Device conflict 3ware twe and CMedia sound card
Dominic Marks wrote: John Baldwin wrote: On Friday 11 August 2006 05:14, Dominic Marks wrote: John Baldwin wrote: On Thursday 10 August 2006 11:27, Dominic Marks wrote: hint.pci3.13.INTA.irq=17 That should make twe0 use IRQ 17. I doesn't seem to have had the desired effect: kenv | grep pci3 hint.pci3.13.INTA.irq=17 grep twe0 /var/run/dmesg.boot twe0: 3ware Storage Controller. [...] port 0xdcb0-0xdcbf mem 0xdf00-0xdf7f irq 49 at device 13.0 on pci3 Erm, that should have worked. Did you just do 'kenv' to set it or did you reboot and set it in the loader? Also, what version are you running, and what revision of /sys/dev/pci/pci.c do you have? I set it in devices.hints and rebooted. FreeBSD gdc083.internal.graphdata.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #2: Mon Jul 17 16:30:13 BST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GDC083 i386 /usr/src/sys/dev/pci/pci.c: $FreeBSD: src/sys/dev/pci/pci.c,v 1.292.2.7 2006/01/31 14:42:43 imp Exp $ Hmm, ok. Well, the next step is to try and see why it isn't working. Can you patch the pci_assign_interrupt() function in /sys/dev/pci/pci.c to printf() the tunable name it generates via sprintf() each time it is invoked? Then boot with that and send me the dmesg? Thanks. A day later than promised: grep DEBUG: /var/run/dmesg.boot DEBUG: hw.pci0.2.INTA.irq DEBUG: hw.pci0.3.INTA.irq DEBUG: hw.pci0.4.INTA.irq DEBUG: hw.pci0.29.INTA.irq DEBUG: hw.pci0.29.INTB.irq DEBUG: hw.pci0.29.INTC.irq DEBUG: hw.pci0.29.INTA.irq DEBUG: hw.pci0.29.INTD.irq DEBUG: hw.pci0.31.INTA.irq DEBUG: hw.pci0.31.INTA.irq DEBUG: hw.pci0.31.INTB.irq DEBUG: hw.pci3.13.INTA.irq (**) DEBUG: hw.pci3.14.INTA.irq DEBUG: hw.pci4.0.INTA.irq DEBUG: hw.pci7.13.INTA.irq tail -1 /boot/device.hints hint.pci3.13.INTA.irq=17 So I'm assuming this is a case of group-blindness :) s/hint/hw/ I'll see how setting hw[...] instead of hint[...] works. YOU ROCK JOHN! Thanks, I can now iozone the stripe with no obvious impact of Desktop performance. Previously even a 1MB/s single file copy would make the system virtually unusable. Thanks again, Dominic Thanks, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Device conflict 3ware twe and CMedia sound card
John Baldwin wrote: On Thursday 10 August 2006 11:27, Dominic Marks wrote: I've had a look, I don't exactly know what to look for, but I have several PCI Express to PCI bridges: [EMAIL PROTECTED]:0:2: class=0x060400 card=0x0044 chip=0x032a8086 rev=0x00 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge B' class= bridge subclass = PCI-PCI You probably are hitting the condition I'm thinking of then. While looking through the pciconf -vl output I also noticed this error: [EMAIL PROTECTED]:13:0: class=0x010400 card=0x100113c1 chip=0x100113c1 rev=0x01 hdr=0x00 vendor = '3ware Inc.' device = '7000/8000 series ATA-133 Storage Controller' ** class= mass storage subclass = RAID ** This actually a SATA 150 Controller. Not a big deal, but still incorrect. It's just a string in /usr/share/misc/pci_vendors, it has no effect on operation or anything in the kernel. :) I thought so, but it is still wrong :) hint.pci3.13.INTA.irq=17 That should make twe0 use IRQ 17. I doesn't seem to have had the desired effect: kenv | grep pci3 hint.pci3.13.INTA.irq=17 grep twe0 /var/run/dmesg.boot twe0: 3ware Storage Controller. [...] port 0xdcb0-0xdcbf mem 0xdf00-0xdf7f irq 49 at device 13.0 on pci3 Erm, that should have worked. Did you just do 'kenv' to set it or did you reboot and set it in the loader? Also, what version are you running, and what revision of /sys/dev/pci/pci.c do you have? I set it in devices.hints and rebooted. FreeBSD gdc083.internal.graphdata.co.uk 6.1-STABLE FreeBSD 6.1-STABLE #2: Mon Jul 17 16:30:13 BST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GDC083 i386 /usr/src/sys/dev/pci/pci.c: $FreeBSD: src/sys/dev/pci/pci.c,v 1.292.2.7 2006/01/31 14:42:43 imp Exp $ Thanks John! Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Network often not responding
Stanislaw Halik wrote: On Wed, Aug 09, 2006, Dominic Marks wrote: Aug 9 15:09:16 cache kernel: xl0: transmission error: 90 Aug 9 15:09:16 cache kernel: xl0: tx underrun, increasing tx start threshold to 120 bytes dc%d: TX underrun -- increasing TX threshold The device generated a transmit underrun error while attempting to DMA and transmit a packet. This happens if the host is not able to DMA the packet data into the NIC's FIFO fast enough. The driver will dynamically increase the ~~ trans- mit start threshold so that more data must be DMAed into the FIFO before the NIC will start transmitting it onto the wire. So it would seem like the card cannot keep pace with the system. What NICs ~ have you tried? Basing on the quoted text, isn't it the opposite? Yep! I should read more than the first line on things, especially when quoting them to others :) Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Device conflict 3ware twe and CMedia sound card
John Baldwin wrote: On Wednesday 09 August 2006 06:15, Dominic Marks wrote: Hello, I seem to have a device conflict on my desktop. When attempting to fsck a gstripe volume attached via the twe card the system becomes 'choppy' and from looking at systat (when it isn't frozen) the system is receiving about 300k interrupts per second from the pcm device. If I leave the system in this state for a few minutes it will do an instant-reset, presumably because it can't cope. Verbose dmesg: http://goodforbusiness.co.uk/~dom/dmesg.boot Specific parts: twe0: 3ware Storage Controller. Driver version 1.50.01.002 port 0xdcb0-0xdcbf mem 0xdf00-0xdf7f irq 49 at device 13.0 on pci3 twe0: Reserved 0x10 bytes for rid 0x10 type 4 at 0xdcb0 ioapic2: routing intpin 1 (PCI IRQ 49) to vector 49 twe0: [GIANT-LOCKED] twe0: AEN: soft reset twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 twe0: Monitor ME7X 1.01.00.040, PCB Rev5, Achip 3.20, Pchip 1.30-66 twe0: port 0: WDC WD3200KS-00PFB0 305245MB twe0: port 1: WDC WD3200KS-00PFB0 305245MB pcm0: CMedia CMI8738 port 0xcc00-0xccff irq 17 at device 13.0 on pci7 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xcc00 ioapic0: routing intpin 17 (PCI IRQ 17) to vector 55 pcm0: [MPSAFE] pcm0: sndbuf_setmap 3e8ee000, 4000; 0xe5408000 - 3e8ee000 pcm0: sndbuf_setmap 3e8ea000, 4000; 0xe540c000 - 3e8ea000 I believe I can use device.hints(5) to work around this, but I am unsure variable I can set in order to resolve this. Does the device 13.0 from dmesg refer to the 'drq' ? Does this system have an Intel PCI-X host bridge in it? If so, it's probably due to brain damage in that chip. You might be able to work around it by making twe0 use the same IRQ as pcm0 by adding the following hint: I've had a look, I don't exactly know what to look for, but I have several PCI Express to PCI bridges: [EMAIL PROTECTED]:0:0: class=0x060400 card=0x0044 chip=0x03298086 rev=0x00 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge A' class= bridge subclass = PCI-PCI [EMAIL PROTECTED]:0:2: class=0x060400 card=0x0044 chip=0x032a8086 rev=0x00 hdr=0x01 vendor = 'Intel Corporation' device = '6700PXH PCI Express-to-PCI Express Bridge B' class= bridge subclass = PCI-PCI While looking through the pciconf -vl output I also noticed this error: [EMAIL PROTECTED]:13:0: class=0x010400 card=0x100113c1 chip=0x100113c1 rev=0x01 hdr=0x00 vendor = '3ware Inc.' device = '7000/8000 series ATA-133 Storage Controller' ** class= mass storage subclass = RAID ** This actually a SATA 150 Controller. Not a big deal, but still incorrect. hint.pci3.13.INTA.irq=17 That should make twe0 use IRQ 17. I doesn't seem to have had the desired effect: kenv | grep pci3 hint.pci3.13.INTA.irq=17 grep twe0 /var/run/dmesg.boot twe0: 3ware Storage Controller. [...] port 0xdcb0-0xdcbf mem 0xdf00-0xdf7f irq 49 at device 13.0 on pci3 Thank you very much John. I'll keep on looking for a solution. Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Device conflict 3ware twe and CMedia sound card
Hello, I seem to have a device conflict on my desktop. When attempting to fsck a gstripe volume attached via the twe card the system becomes 'choppy' and from looking at systat (when it isn't frozen) the system is receiving about 300k interrupts per second from the pcm device. If I leave the system in this state for a few minutes it will do an instant-reset, presumably because it can't cope. Verbose dmesg: http://goodforbusiness.co.uk/~dom/dmesg.boot Specific parts: twe0: 3ware Storage Controller. Driver version 1.50.01.002 port 0xdcb0-0xdcbf mem 0xdf00-0xdf7f irq 49 at device 13.0 on pci3 twe0: Reserved 0x10 bytes for rid 0x10 type 4 at 0xdcb0 ioapic2: routing intpin 1 (PCI IRQ 49) to vector 49 twe0: [GIANT-LOCKED] twe0: AEN: soft reset twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 twe0: Monitor ME7X 1.01.00.040, PCB Rev5, Achip 3.20, Pchip 1.30-66 twe0: port 0: WDC WD3200KS-00PFB0 305245MB twe0: port 1: WDC WD3200KS-00PFB0 305245MB pcm0: CMedia CMI8738 port 0xcc00-0xccff irq 17 at device 13.0 on pci7 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xcc00 ioapic0: routing intpin 17 (PCI IRQ 17) to vector 55 pcm0: [MPSAFE] pcm0: sndbuf_setmap 3e8ee000, 4000; 0xe5408000 - 3e8ee000 pcm0: sndbuf_setmap 3e8ea000, 4000; 0xe540c000 - 3e8ea000 I believe I can use device.hints(5) to work around this, but I am unsure variable I can set in order to resolve this. Does the device 13.0 from dmesg refer to the 'drq' ? Thanks, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Stability of ICH7 sata on FreeBSD 6.1 ?
Jerome Sobecki wrote: Hi all, We have here some Supermicro Superserver 5015P-TR (http://www.supermicro.com/products/system/1U/5015/SYS-5015P-TR.cfm) Those servers, with a ICH7 controler, are currently working with FreeBSD 6.1 and everything seems ok, except that it's the third time, on two different machines, that the system crash because it lost is hard drive. We have a Subversion sever on a Dell box with an ICH7 chipset. No problems so far (with Western Digital drives). Dominic The logs we get on console during the last crash (ad4s1g is /var, so we don't have any other logs): g_vsf_done() :ad4s1g[WRITE(offset=35657547776, length=16384)]error = 6 [...] g_vsf_done() :ad4s1g[WRITE(offset=35662495744, length=16384)]error = 6 g_vsf_done() :ad4s1g[READ(offset=23900815360, , length=16384)]error = 6 handle_workitem_freeblocks: block count The logs we have in /var/log/message during another crash : Jul 26 19:34:07 munster2 kernel: ad6: FAILURE - device detached Jul 26 19:34:07 munster2 kernel: subdisk6: detached Jul 26 19:34:07 munster2 kernel: ad6: detached When the machine crash, the led of the lost DD is fixed on, and a soft reboot doesn't allow to get the disk back : an electric shutdown is necessary. Before the crash, servers had more than 1 mounth of uptime in production, and others are still ok... information about the machine : vieux-lille2% uname -v FreeBSD 6.1-STABLE #3: Thu Jun 8 12:47:45 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC It's right it was not up to date, but I didn't see cvs commit about that problem (but maybe I simply miss it) Does anyone had that problem ? Do you think updating the system from 6.1 sources will be enought ? I let you dmesg, if it could help... : vieux-lille2% dmesg Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE #3: Thu Jun 8 12:47:45 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.40GHz (3400.15-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf43 Stepping = 3 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x649dSSE3,RSVD2,MON,DS_CPL,EST,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM Logical CPUs per core: 2 real memory = 1072562176 (1022 MB) avail memory = 1040637952 (992 MB) ACPI APIC Table: PTLTD APIC ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pci1: base peripheral, interrupt controller at device 0.1 (no driver attached) pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 pci1: base peripheral, interrupt controller at device 0.3 (no driver attached) pcib4: ACPI PCI-PCI bridge irq 17 at device 28.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge irq 17 at device 28.4 on pci0 pci5: ACPI PCI bus on pcib5 em0: Intel(R) PRO/1000 Network Connection Version - 3.2.18 port 0x4000-0x401f mem 0xed20-0xed21 irq 16 at device 0.0 on pci5 em0: Ethernet address: 00:30:48:84:89:58 pcib6: ACPI PCI-PCI bridge irq 16 at device 28.5 on pci0 pci6: ACPI PCI bus on pcib6 em1: Intel(R) PRO/1000 Network Connection Version - 3.2.18 port 0x5000-0x501f mem 0xed30-0xed31 irq 17 at device 0.0 on pci6 em1: Ethernet address: 00:30:48:84:89:59 uhci0: UHCI (generic) USB controller port 0x3000-0x301f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: UHCI (generic) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: UHCI (generic) USB controller port 0x3020-0x303f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: UHCI (generic) USB controller on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: UHCI (generic) USB controller port 0x3040-0x305f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: UHCI (generic) USB controller on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: UHCI (generic) USB controller port 0x3060-0x307f irq
Two panics on recent 6.1-STABLE
Two panics, I've just had:
I had just installed a fresh world+kernel, booted and then received
the first panic. Then reset, booted again and shortly received the
second (although they look identical to me). At the moment everything
seems fine, sending this message from the machine in question.
Rough description of the PC's life:
Gnome Desktop connected using nsswitch/winbind to Active Directory.
Low load.
I can make the dumps available, but at a guess I'd say they don't look
very helpful. I'll recompile with debugging options enabled and see if
I can get some other info. If I do, I'll follow-up with it here.
Thanks,
Dominic
FreeBSD gdc083.internal.graphdata.co.uk 6.1-STABLE FreeBSD 6.1-STABLE
#0: Mon Jul 17 12:43:52 BST 2006
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GDC083
i386
panic #1:
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xfefefe14
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06a031b
stack pointer = 0x28:0xe7383c88
frame pointer = 0x28:0xe7383ca0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 827 (csh)
trap number = 12
panic: page fault
Uptime: 3m47s
Dumping 1022 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 1022MB (261516 pages) 1006 990 974 958 942 926 (CTRL-C to
abort) 910 894 878 (CTRL-C to abort) 862 846 830 814 798 782 766
750 734 718 702 686 670 654 638 622 606 590 574 558 542 526 510 494
478 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222
206 190 174 158 142 126 110 94 78 62 46 30 14
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06a8f7a in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:409
#2 0xc06a9284 in panic (fmt=0xc0925487 %s)
at /usr/src/sys/kern/kern_shutdown.c:565
#3 0xc08d142d in trap_fatal (frame=0xe7383c48, eva=0)
at /usr/src/sys/i386/i386/trap.c:836
#4 0xc08d114d in trap_pfault (frame=0xe7383c48, usermode=0,
eva=4278124052)
at /usr/src/sys/i386/i386/trap.c:744
#5 0xc08d0d37 in trap (frame=
{tf_fs = 8, tf_es = -1056702424, tf_ds = -1056702424, tf_edi =
-415744764, tf_esi = -986172392, tf_ebp = -415744864, tf_isp =
-415744908, tf_ebx = -16843264, tf_edx = 827, tf_ecx = 827,
tf_eax = 4, tf_trapno = 12, tf_err = 0, tf_eip = -1066794213,
tf_cs = 32, tf_eflags = 66182, tf_esp = 64, tf_ss = 2})
at /usr/src/sys/i386/i386/trap.c:434
#6 0xc08bee9a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc06a031b in pgfind (pgid=827) at /usr/src/sys/kern/kern_proc.c:257
#8 0xc06a3567 in setpgid (td=0xc520cd80, uap=0xe7383d04)
at /usr/src/sys/kern/kern_prot.c:436
#9 0xc08d17e3 in syscall (frame=
{tf_fs = 59, tf_es = 59, tf_ds = -1078001605, tf_edi = 2, tf_esi
= 827, tf_ebp = -1077995432, tf_isp = -415744668, tf_ebx = 783,
tf_edx = -1077995488, tf_ecx = 2, tf_eax = 82, tf_trapno = 22,
tf_err = 2, tf_eip = 672532403, tf_cs = 51, tf_eflags = 518,
tf_esp = -1077995460, tf_ss = 59})
at /usr/src/sys/i386/i386/trap.c:981
#10 0xc08beeef in Xint0x80_syscall () at
/usr/src/sys/i386/i386/exception.s:200
#11 0x0033 in ?? ()
Previous frame inner to this frame (corrupt stack?)
panic #2
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xfefefe14
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc06a031b
stack pointer = 0x28:0xe739ec88
frame pointer = 0x28:0xe739eca0
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 827 (csh)
trap number = 12
panic: page fault
Uptime: 5m56s
Dumping 1022 MB (2 chunks)
chunk 0: 1MB (160 pages) ... ok
chunk 1: 1022MB (261516 pages) 1006 990 974 958 (CTRL-C to abort)
942 926 910 894 878 862 846 830 814 798 782 766 750 734 718 702 686
670 654 638 622 606 590 574 558 542 526 510 494 478 462 446 430 414
398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142
126 110 94 78 62 46 30 14
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc06a8f7a in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:409
#2 0xc06a9284 in panic (fmt=0xc0925487 %s) at
/usr/src/sys/kern/kern_shutdown.c:565
#3 0xc08d142d in trap_fatal (frame=0xe739ec48, eva=0) at
/usr/src/sys/i386/i386/trap.c:836
#4 0xc08d114d in trap_pfault (frame=0xe739ec48, usermode=0,
eva=4278124052) at /usr/src/sys/i386/i386/trap.c:744
#5 0xc08d0d37 in trap (frame=
{tf_fs = 8, tf_es = -1056702424, tf_ds = -1056702424, tf_edi =
-415634172, tf_esi = -981162460, tf_ebp = -415634272, tf_isp =
-415634316, tf_ebx =
ACPI related crash on a Dell PowerEdge SC1420 regression since 6.1-RELEASE
Hello, I upgraded a PowerEdge SC1420 which had been installed with 6.1-R to 6.1-S today and now it no longer boots with ACPI enabled. It doesn't give a crash dump so here is the information I managed to note down before it rebooted: This happens after em and twe in the boot process. FVA 0x20:0xc0afce73 SP 0x28:0xc0c20944 FP 0x28:0xc0c20958 Trap 12 in swapper. I've no idea how useful this information is, hopeful it is a clue. Full dmesg below (from a non-ACPI boot, of course), please let me know if there is any other information I can provide. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE #0: Thu Jul 13 15:22:54 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.52-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf4a Stepping = 10 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x641dSSE3,RSVD2,MON,DS_CPL,CNTX-ID,CX16,b14 AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Logical CPUs per core: 2 real memory = 1072218112 (1022 MB) avail memory = 1040330752 (992 MB) MPTable: DELL PE SC1420 ioapic0: Changing APIC ID to 8 ioapic0: Assuming intbase of 0 ioapic1: Changing APIC ID to 9 ioapic1: Assuming intbase of 24 ioapic2: Changing APIC ID to 10 ioapic2: Assuming intbase of 48 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard ioapic2 Version 2.0 irqs 48-71 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) cpu0 on motherboard pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 pcib0: unable to route slot 2 INTA pcib0: unable to route slot 3 INTA pcib0: unable to route slot 4 INTA pci0: unknown at device 0.1 (no driver attached) pcib1: PCI-PCI bridge irq 11 at device 2.0 on pci0 pci1: PCI bus on pcib1 pcib2: MPTable PCI-PCI bridge at device 0.0 on pci1 pci2: PCI bus on pcib2 pci2: display, VGA at device 12.0 (no driver attached) pcib3: MPTable PCI-PCI bridge at device 0.2 on pci1 pci3: PCI bus on pcib3 twe0: 3ware Storage Controller. Driver version 1.50.01.002 port 0xccb0-0xccbf mem 0xdd80-0xddff irq 49 at device 13.0 on pci3 twe0: [GIANT-LOCKED] twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 em0: Intel(R) PRO/1000 Network Connection Version - 3.2.18 port 0xccc0-0xccff mem 0xdd6e-0xdd6f irq 48 at device 14.0 on pci3 em0: Ethernet address: 00:13:72:8b:3c:a9 pcib4: MPTable PCI-PCI bridge irq 11 at device 3.0 on pci0 pci4: PCI bus on pcib4 pcib5: MPTable PCI-PCI bridge irq 11 at device 4.0 on pci0 pci5: PCI bus on pcib5 uhci0: Intel 82801EB (ICH5) USB controller USB-A port 0xff80-0xff9f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801EB (ICH5) USB controller USB-A on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: Intel 82801EB (ICH5) USB controller USB-B port 0xff60-0xff7f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: Intel 82801EB (ICH5) USB controller USB-B on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: Intel 82801EB (ICH5) USB controller USB-C port 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: Intel 82801EB (ICH5) USB controller USB-C on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: Intel 82801EB (ICH5) USB controller USB-D port 0xff20-0xff3f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: Intel 82801EB (ICH5) USB controller USB-D on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: Intel 82801EB/R (ICH5) USB 2.0 controller mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: waiting for BIOS to give up control usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: Intel 82801EB/R (ICH5) USB 2.0 controller on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered umass0: FREECOM. ATAPI-6 Bridge Controller, rev 2.00/0.00, addr 2 umass1: Freecom Classic Mobile 2.5' Hard Disk, rev 2.00/0.33, addr 3 pcib6: MPTable PCI-PCI bridge at device 30.0 on pci0 pci6: PCI bus on pcib6 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH5 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xdc00-0xdfff irq 18 at device 31.1 on
Re: pf buggy on 6.1-STABLE?
Mark Morley wrote: Hi folks, Wondering if this rings any bells for anyone: After upgrading a handful of web servers from FreeBSD 4.11 with ipfw to 6.1-STABLE with pf, customers started reporting that occasionally their server side scripts would fail to connect to the SQL servers (which are still 4.11 and are attached via a separate dedicated gigabit network). A test page that makes 10,000 rapid SQL connections which connected 100% of the time before, now will usually see anywhere from one or two failed connections to a dozen or so (per 10,000) After trying many other things first, we finally found that 'pf' seems to be the culprit. I've experienced the same. If you have a lot of concurrent connections going on it seems that every so often an connection will be blocked, even if it doesnt match any rule. In my case I experienced this with apache22 acting as a reverse proxy/virtual host. Symptoms: 1. Sudden burst of traffic to a specific virtual host. 2. After some time, normally 30 seconds one of the connection attempts is reset. 3. Apache immediately stops proxying for any subsequent connections and returning a 'too busy message'. The project this was related to got shelved so it hasn't bothered me again yet, but I didn't find any workaround. Disabling pf with pfctl -d allows 100% of all connections to work, and as soon as we enable it we see connection failures again. Snap. I've tried changing the pf rule set in different ways, with and without scrubbing, with and without queues, even to the point where I have a single rule that just allows everything. It doesn't seem to matter what the rules actually are, just whether or not pf is enabled. Same as me. I recompiled the kernel with pf disabled and ipfw enabled, and it works fine with 100% successful connections. We have no funky compiler options or anything like that. Any thoughts? Mark -- Mark Morley Owner / Administrator Islandnet.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Cheers, Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1-STABLE + devel/php5-pcre incompatible?
Jonathan Noack wrote: Pertti Kosunen wrote: Dominic Marks wrote: Is the php5-pcre module really incompatible with FreeBSD 6.1? If so, is there a workaround or a version I can roll back to? Also, it is just me (:-)) or is the php5 port complaining about a checksum mismatch for everyone else? I had some problems yesterday. Had to remove mod_php5, config install lang/php5 and update php5*. Note the entry in /usr/ports/UPDATING: 20060506: AFFECTS: users of PHP AUTHOR: [EMAIL PROTECTED] The old PHP slave ports (phpN-cli, phpN-cgi and mod_phpN) were removed in favour of unified PHP ports that allow building any combination of PHP SAPIs (cli, cgi and apache module). The PHP CGI binary was renamed to php-cgi, so you should update the path in your script. To simplify the update process, *only* for this release a 'php' compatibility symlink to php-cgi will be created if you don't select the CLI SAPI. Before the upgrade you *should* run 'make config' in lang/php4 or lang/php5 to configure the SAPIs you want to install. As a consequence the default binary packages include the CLI and the FastCGI SAPIs. Thanks Jonathan. I forget that ports/UPDATING exists, I should have read this. -Jonathan Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.1-STABLE + devel/php5-pcre incompatible?
Hello, Is the php5-pcre module really incompatible with FreeBSD 6.1? If so, is there a workaround or a version I can roll back to? Also, it is just me (:-)) or is the php5 port complaining about a checksum mismatch for everyone else? Thanks, Dominic Portupgrade --- Session started at: Tue, 16 May 2006 11:46:27 +0100 --- Fresh installation of devel/php5-pcre started at: Tue, 16 May 2006 11:46:29 +0100 --- Installing 'php5-pcre-5.1.4' from a port (devel/php5-pcre) --- Build of devel/php5-pcre started at: Tue, 16 May 2006 11:46:29 +0100 --- Building '/usr/ports/devel/php5-pcre' === Building for php5-pcre-5.1.4 /bin/sh /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/libtool --mode=compile cc -DEXPORT= -DNEWLINE=10 -DSUPPORT_UTF8 -DSUPPORT_UCP -DLINK_SIZE=2 -DPOSIX_MALLOC_THRESHOLD=10 -DMATCH_LIMIT=1000 -DMATCH_LIMIT_RECURSION=1000 -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/pcrelib -I. -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre -DPHP_ATOM_INC -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/include -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/main -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -DHAVE_CONFIG_H -O2 -fno-strict-aliasing -pipe -c /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c -o php_pcre.lo cc -DEXPORT= -DNEWLINE=10 -DSUPPORT_UTF8 -DSUPPORT_UCP -DLINK_SIZE=2 -DPOSIX_MALLOC_THRESHOLD=10 -DMATCH_LIMIT=1000 -DMATCH_LIMIT_RECURSION=1000 -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/pcrelib -I. -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre -DPHP_ATOM_INC -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/include -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/main -I/usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre -I/usr/local/include/php -I/usr/local/include/php/main -I/usr/local/include/php/TSRM -I/usr/local/include/php/Zend -I/usr/local/include/php/ext -DHAVE_CONFIG_H -O2 -fno-strict-aliasing -pipe -c /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c -fPIC -DPIC -o .libs/php_pcre.o /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1630: error: `fifth_arg_force_ref' undeclared here (not in a function) /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1630: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1630: error: (near initialization for `pcre_functions[2].arg_info') /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1630: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1630: error: (near initialization for `pcre_functions[2]') /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1631: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1631: error: (near initialization for `pcre_functions[3].arg_info') /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1631: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1631: error: (near initialization for `pcre_functions[3]') /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1632: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1632: error: (near initialization for `pcre_functions[4]') /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1633: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1633: error: (near initialization for `pcre_functions[5]') /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1634: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1634: error: (near initialization for `pcre_functions[6]') /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1635: error: initializer element is not constant /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre/php_pcre.c:1635: error: (near initialization for `pcre_functions[7]') *** Error code 1 Stop in /usr/ports/devel/php5-pcre/work/php-5.1.4/ext/pcre. *** Error code 1 Stop in /usr/ports/devel/php5-pcre. --- Build of devel/php5-pcre ended at: Tue, 16 May 2006 11:46:30 +0100 (consumed 00:00:00) --- Fresh installation of devel/php5-pcre ended at: Tue, 16 May 2006 11:46:30 +0100 (consumed 00:00:00) --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! devel/php5-pcre (stdio compatibility) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Session ended at: Tue, 16 May 2006 11:46:30 +0100 (consumed 00:00:03) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
xdm + pam + winbind, what am i missing?
Hello, I must be missing something because I can't get xdm to work happily with pam_winbind. The 6.1 system is joined to a Windows domain and aware of domain users. I log on to the machine using my domain account via SSH and all is well. I've enabled xdm and restarted init. Connections from any host are permitted. I have also modified the pam.d/xdm file to use the winbind pam module for authentication. I get a login screen and my username and password are correctly checked against Active Directory. I have setup a ~/.xsession file which should log me in and start a Gnome environment. What actually happens is that the connection seems to drop and reconnect and I end up back at an xdm prompt. In the system messages log I have the following: xdm: pam_sm_close_session(): no utmp record for DESKTOP:0 * DESKTOP is the hostname of my desktop system from which I am connecting. I tried commenting out the session line in pam.d/xdm which this message comes from, it removes the error but doesn't change the behaviour so I assume it is not directly related. I couldn't find anything in the Handbook to help me on my way. If anyone could tell me the missing link I would appreciate it greatly. Thanks, Dominic Marks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm + pam + winbind, what am i missing?
Dominic Marks wrote: Hello, I must be missing something because I can't get xdm to work happily with pam_winbind. The 6.1 system is joined to a Windows domain and aware of domain users. I log on to the machine using my domain account via SSH and all is well. I've enabled xdm and restarted init. Connections from any host are permitted. I have also modified the pam.d/xdm file to use the winbind pam module for authentication. I get a login screen and my username and password are correctly checked against Active Directory. I have setup a ~/.xsession file which should log me in and start a Gnome environment. What actually happens is that the connection seems to drop and reconnect and I end up back at an xdm prompt. In the system messages log I have the following: xdm: pam_sm_close_session(): no utmp record for DESKTOP:0 * DESKTOP is the hostname of my desktop system from which I am connecting. I tried commenting out the session line in pam.d/xdm which this message comes from, it removes the error but doesn't change the behaviour so I assume it is not directly related. I couldn't find anything in the Handbook to help me on my way. If anyone could tell me the missing link I would appreciate it greatly. Well, it works with gdm. I still don't know why xdm didn't work though. Dominic Thanks, Dominic Marks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xdm + pam + winbind, what am i missing?
Michael Butler wrote:
Dominic Marks wrote:
xdm: pam_sm_close_session(): no utmp record for DESKTOP:0
does winbind implement pam_{open|close}_session?
If so, does adding a session line as well as the auth line to
/etc/pam.d/xdm help?
I tried that and didn't get anywhere, but maybe I did it wrong. I just
duplicated the auth line and swapped auth for session.
Dominic
--
Michael Butler, CISSP
Security Architect
Protected Networks
http://www.protected-networks.net
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_4 - 5 - 6: significant performance regression
Peter Jeremy wrote: On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: Does 'makeoptions DEBUG=-g' add any kind of performance hit or overhead as I noticed it wasnt default in 5.4 but is in 6.0. No. It just means that a debug kernel is built in addition to the normal kernel. The major benefit is that if you do get a panic, you can debug it without needing to rebuild the kernel. I've often thought that the default should be for this to be on instead of off. Does anyone know why the current state is so? I suppose it incurs a small amount of additional disc space but the benefits are considerable for everyone involved. Cheers, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RELENG_4 - 5 - 6: significant performance regression
Dominic Marks wrote: Peter Jeremy wrote: On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: Does 'makeoptions DEBUG=-g' add any kind of performance hit or overhead as I noticed it wasnt default in 5.4 but is in 6.0. No. It just means that a debug kernel is built in addition to the normal kernel. The major benefit is that if you do get a panic, you can debug it without needing to rebuild the kernel. I've often thought that the default should be for this to be on instead of off. Does anyone know why the current state is so? I suppose it incurs a small amount of additional disc space but the benefits are considerable for everyone involved. Clarifying what I was getting at (it does default to on) I meant that it has to be turned on with an option not turned off. Cheers, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DMA timeouts with Adapter ASH-1205SA SATA PCI Card
Tim Soderstrom wrote: I am trying to jump into the world of FreeBSD and have been having some nasty problems with some things. The latest of which is the fact that FreeBSD is noting DMA timeouts with my SATA card, particularly when performing writes: As far as I am aware it is not resolved and is actually not fixable. However I gave up on these cards a while ago so I might be out of date. See below. ad4: FAILURE - WRITE_DMA48 status=51READYDSC,ERROR error=10NID_NOT_FOUND LBA=273370735 g_vfs_done():ad4s1g[WRITE(offset=115279347712, length=131072)]error = 5 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=276000431 These repeat sometimes to the point of FreeBSD going into an emergency reboot mode, although this has not yet happened since I updated to 6.0-RELEASE-p7. Speaking of, I am confused as to if that is the STABLE branch (which I want to get on)? RELENG_6 is the current STABLE. Although it won't call itself stable if you build it, it will be named RC1. Its still STABLE though, names change prior to a release occurring and 6.1 is due shortly. In any case, I am concerned as to whether or not these errors represent a real problem and what I can go about doing with them. This box is designed to be a file-server, so I had hoped that it would be as stable as, well, if not a rock, at least play-dough :) This card is based on a Silicon Image chip. You might as well chuck the card I have never got a machine stable with one of these controllers, I tried three cards all based on this chip, including an Adaptec 1210SA. All the same, completely unstable. I suggest you acquire one of these instead: http://froogle.google.com/froogle?q=3ware+escalade+8000+2+port Save yourself a lot of pain (really) and get one :) With one of these the rock-like stability should be easy to achieve, hopefully. Regards, Tim S. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Cheers, Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: kouwell ata raid
Ondra Holecek wrote: hello, i'm looking for some cheap hardware ata raid (mirror) for freebsd 6 i think about KOUWELL KW-571B, it uses Silicon Image Sil 0680 chip. I heard that this chip was not supported in FreeBSD, but as I look to man ad, it seems, it is supported now. My question is, does somebody use it? and works it? is there some management software (ie. disk failure signalization)? If it is anything like the previous Sil chipsets it will not be reliable. I'd be very sceptical about it indeed. I would be interested if you could provide some information on your experiences with it. Also if is worth knowing that at least on some hardware RAID implementations they are not really hardware at all (from what I understand). This is true one at least one system (a low-end Dell PowerEdge). HTH, Dominic Thank for help Ondra ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA RAID: Adaptec 1420SA, Promise TX4300?
Tenebrae wrote: On Sat, 1 Apr 2006, Lars Cleary wrote: Why don't you just use gmirror(8) and do software RAID 1? IMHO a controller just for RAID 1 is unnecessary, as the OS together with a reasonable motherboards disk controller is just as fast as any RAID controller. Ah, I knew I should have mentioned this. The motherboard I will be using has no native SATA support so I will need to purchase a(n) SATA controller anyway. Also, I tend to prefer hardware solutions to software solutions (*cough*evilWinModem*cough*). I started using only 3ware cards a while ago. It was a good choice. Lots of other seem to have the same experience too. Also maybe see: http://people.freebsd.org/~rse/mirror/ for more details. Thanks. I'll have a look. -Tenebrae. --- The sending of any unsolicited email advertising messages to this domain may result in the imposition of civil liability against you in accordance with Cal. Bus. Prof. Code Section 17538.45. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fresh install on gmirror'ed disks?
Mike Jakubik wrote: Patrick M. Hausen wrote: Hello! Is it possible to boot off the install CD, setup a gmirror, and then reboot and install on the mirror (and expect things to work ok)? Anyone try this? It would be nice if the installer let you do this... AFAIK, no. Install a minimal system on the first disk, then follow these instructions: http://ezine.daemonnews.org/200502/diskmirror.html Thats what i figured. Its sad that the fbsd installer is so behind the linux ones, in terms of setting up raid and lvm during install. Someone could be funded to work on this like the TCP/IP performance project. I'd be willing to make a donation, as I am sure you would Mike. All that is required is a willing + able person and enough donations to make it worth his or her while. Volunteers? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Dom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Getting a patch integrated into -STABLE?
On Monday 21 November 2005 18:14, Alan Amesbury wrote: Last week I sent a patch in to fix a problem with 'du' (bug report #89090). Unfortunately, I failed to indicate in the synopsis line that I'd included a patch (albeit one that should probably be looked at by someone with more clue than me). Is there a) an easy way for me to update the bug report to indicate this, and b) is there a typical time-to-fix for this sort of thing? send-pr and no :) Thanks in advance! -- Alan Amesbury University of Minnesota ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dominic Marks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: vmcore.4
Elliot Finley wrote: my system panicked and I got a /var/crash/vmcore.4 file. The corresponding info.4 file is: postmaster root:/var/crash#less info.4 Dump header from device /dev/ar0s1b Architecture: i386 Architecture Version: 16777216 Dump Length: 2146631680B (2047 MB) Blocksize: 512 Dumptime: Sat Sep 3 14:15:04 2005 Hostname: postmaster.etv.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 5.4-RELEASE-p3 #4: Fri Jul 1 00:22:45 MDT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Panic String: kmem_malloc(4096): kmem_map too small: 335544320 total allocated Dump Parity: 290305146 Bounds: 4 Dump Status: good Is there some sysctl that I can tweak to keep this from happening? Or is this a bug? Google says: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/book.html#KMEM-MAP-TOO-SMALL TIA Elliot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] HTH, -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell Latitude D510
Brian Doherty wrote: Hi all, I'm a bit of a newbie, with 5.x and hope someone can help me. :-) Here goes ... I have a dell Latitude D510 with the mist recent BIOS installed. I have win XP factory installed, boots fine. I have tried installing the following on a partition: 5.4 FreeBSD BTX Halted and goes no further straight after the install option screen, ie 1 - FreeBSD, 2 - FreeBSD without ACPI Tried booting without ACPI? I have quite a few machines at work which do this, mostly old(ish) PII/PIII systems with low-quality motherboards. 5.3 FreeBSD Gets a little further, but drops out on a panic, while trying to load the usb devices, I think 4.11 FreeBSD Same as 5.3 4.10 FreeBSD Same as 4.10 Try the 6.0 BETA3, it's not too scary, but you will want to recompile your kernel after you install (assuming it works) to get decent performance (hint: remove the debugging options). If you haven't done this don't worry, it isn't complicated and is well covered in the Handbook. If the USB problem comes back, you can still work around it, although it may be challenging for someone new to FreeBSD. However, you will learn quite a bit in the process! Assuming you have a spare machine lying around, or another FreeBSD box already, you can compile your own kernel, removing the USB bits and then modify the ISO image file replacing the stock kernel with your own one. This isn't actually as hard as it might sound :-) You can mount the ISO image (using mdconfig and mount_cd9660) then copy your USB-less kernel over the one on the CD, then burn a copy of the ISO file again and it will have your own special-purpose install CD (haven't tried this but I think it will work, the kernel on the CD is not 'special' as far as I know). If this all sounds far too complex for you, I can probably make you the CD described above as I have a D510 here (which I'm typing from) although it's not running FreeBSD and I won't be fully test the install (it's not really mine). Try the simpler options first, and if not, send the list another E-Mail and see what comes your way. I did a google, looked in the handbook, but couldn't find anything that it might be. Regards, Brian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Cheers, -- Dominic Marks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 STABLE to 5.4 buildkernel error
On Monday 04 July 2005 15:22, misael wrote: Hello freebsd-stable, i'm trying to update/upgrade my box from 5.3 STABLE to the latest version of 5 branch. but when i'm doing make buildkernel i bumped in to some errors, Sometimes it is worth trying to cvsup against a different cvsup mirror and running a clean build. The GENERIC kernel configuration is unmodified, I suppose? here it is the error messages: stage 2.3: build tools -- cd /usr/obj/usr/src/sys/GENERIC; MAKESRCPATH=/usr/src/sys/dev/aic7xxx/aicasm make -DNO_CPU_CFLAGS -f /usr/src/sys/dev/aic7xxx/aicasm/Makefile Warning: Object directory not changed from original /usr/obj/usr/src/sys/GENERIC cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm.c cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src/sys/dev/aic7xxx/aicasm -c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c: In function `symbol_delete': /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:91: warning: passing arg 2 of pointer to function from incompatible pointer type /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:91: error: too few arguments to function /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c: In function `symtable_open': /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:135: warning: assignment makes pointer from integer without a cast /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c: In function `symtable_close': /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:151: error: structure has no member named `seq' /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:151: error: `R_FIRST' undeclared (first use in this function) /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:151: error: (Each undeclared identifier is reported only once /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:151: error: for each function it appears in.) /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:157: error: too few arguments to function /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c: In function `symtable_get': /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:176: warning: passing arg 2 of pointer to function from incompatible pointer type /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:176: error: too few arguments to function /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:189: warning: passing arg 2 of pointer to function from incompatible pointer type /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:189: error: too few arguments to function /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c: In function `symtable_dump': /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:486: error: `R_FIRST' undeclared (first use in this function) /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:487: error: structure has no member named `seq' /usr/src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c:524: error: `R_NEXT' undeclared (first use in this function) *** Error code 1 i'm using GENERIC kernel for this and still error. for some information these are my cvsup file : *default host=cvsup12.FreeBSD.org *default base=/usr *default prefix=/usr # The following line is for 4-stable. If you want 3-stable or 2.2-stable, # change RELENG_4 to RELENG_3 or RELENG_2_2 respectively. *default release=cvs tag=RELENG_5 *default delete use-rel-suffix and my current FreeBSD version: [EMAIL PROTECTED] src]# uname -v FreeBSD 5.3-STABLE #7 any helps, hints or clues are highly appreciated. TIA -- Best regards, zen mailto:[EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dominic Marks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Old messages
On Sunday 03 July 2005 17:02, Andy Gilligan wrote: Ok, is it just me or did anyone else receive a bunch of mails to -stable from about 6-7 months ago? I think I got them earlier also. -Andy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Jails that won't die...
On Tuesday 28 June 2005 09:37, Eirik Øverby wrote: Hi, I have, since upgrading to 5.x and updating my management tools, seen a number of problems relating to stopping jails. I'm maintaining several hosts with a number of full-featured jails (i.e. full virtual FreeBSD installations in each jail), and in general this works fine. However, whenever I stop a jail using 'jexec id kill -SIGNAL -1' or 'jexec id /bin/sh /etc/rc.shutdown' (in various combinations), jails have a tendency to stick around for minutes or hours - according to 'jls'. Often I see an entry in 'netstat -a' indicating that there is one or more sockets in FIN_WAIT state, preventing the jail from coming down. Taking the virtual network interface (alias) down does not help. All I can do at this point is wait. You could use tcpdrop(8) to close them? That might be enough to kick the jail out. I normally use 'jls' to determine whether or not a jail can be restarted (i.e. it's not running), but this is pretty useless in such cases. And right now I have a case where 'netstat -a' shows me nothing pertaining to the jail, though it has no processes running. I have therefore force-started the jail again, which seems to work nicely, but now 'jls' gives me two entries for this jail, with different JIDs. What am I doing wrong here? /Eirik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
On Friday 01 July 2005 16:34, Alan Jay wrote: Further to this the same ATA Timeout is seen in the latest SNAP binaries (1st July). Do you see them with ATA mkIII as well? http://people.freebsd.org/~sos/ATA/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
On Friday 01 July 2005 17:12, Tony Byrne wrote: Hello Dominic, DM Do you see them with ATA mkIII as well? I tried the ATA mkIII patches a few weeks ago on one of servers, which was suffering DMA TIMEOUTs, but they made no difference. Tried Linux on the same hardware? A strange suggestion perhaps, but I suspect that something is wrong with the hardware, or its configuration. It might turn up something interesting, at least it will rule the possibility of bad hardware in, or out. This problem may only occur with certain combinations of controller and SATA hard drive. For example, I have a workstation with an ICH5 controller which had been frequently emitting TIMEOUT messages when it had a 80Gb 7200k Seagate Barracuda SATA drive installed. As a test See below for what is possibily a very similar story. this afternoon, I swapped out the Seagate for a new 250Gb Western Digital SATA drive, and installed 5.4 RELEASE. The machine is now in the process of building world, and I've yet to see any TIMEOUTs. I have lots of ICH5 and ICH6 systems and I haven't had any WRITE_DMA errors on them (to my knowledge). All of my problems in this area are to with Sil3112 based cards. An 80GB seagate drive attached to an Adaptec RAID controller with the Sil3112 in had absolutely terrible performance, about 4MB/s (r+w) at best. Replacing the Seagate disc with a Maxtor fixed the problem. I wasn't looking for these messages at the time, so they may have been a factor. What I did notice is that the drive (according to gstat) was improbably busy almost all the time for the minor load I was placing on it. I have another two Sil3112 based cards from no-name suppliers, these also seem to have issues - but they vary quite a lot. Just this week I have been setting up a SATA RAID using graid3 and 3x 250GB WD discs. In my test system I installed two of the Sil3112 cards, in addition to the integrated ICH6 onboard. Attaching a drive to each controller gives good performance ~105MB/s peak according to diskinfo. However trying to use the raid array in this configuration results in either of the drives dedicated to data having frequent problems, including the drives dropping out of the array at random during periods of load because of write FAILUREs. This makes the array useless since it is incapable of sustaining even a rebuild of the array without one, or both of the data drives failing. I never have any errors from the disc used for parity, which I put on the ICH6. If I reconfigure the machine and put both data discs on one of the Sil3112 controllers the system is stable and I can work with it. Performance suffers quite a bit, dropping to a peak of 98MB/s (ok, it's not much to cry about :-)). If I put the parity drive on either of the Sil3112 controllers I normally get a write failure, followed by a panic within minutes. What concerns me more about this configuration is that the speed limit on a rebuild of array. If I place a drive on each controller the rebuild runs at ~50MB/s (from memory, might be a little less). However, in the stable configuration the rebuild cannot pass 20MB/s. Which on a 500GB array, makes quite a difference to the rebuild time. Incidentally, this configuration is only stable on one of the Sil3112 cards I have (no RAID). I have one with RAID (probably almost exactly like the Adaptec), and one without. If your stuck with the hardware you have, like I am, I suggest that you setup a gmirror of your two dodgy drives, if one of them happens to encounter a read/write failure its less likely to take the system down. Hardly a fix though. Mikhail, I hope you don't mind me CC'ing you here. I read in a message that you had cured some problems like this by changing some of the PCI timers (?). Could you possibly say a little about what you did? Regards, Tony. Cheers, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350
On Friday 01 July 2005 17:27, Alan Jay wrote: Thanks for this - I haven't try but will do so - but I do need a little help. I have downloaded the STABLE version and put it onto my machines. Do I have to compile the ATA driver into the system and if so how do I do so (sorry to ask no instructions on the web site below). This should be the procedure, but I could be wrong. o Get a fresh RELENG_5 o Copy the ata mkIII update to your source tree o Apply the diff for RELENG_5 to your source tree o Build a fresh world + kernel For proper instructions Google about for [EMAIL PROTECTED]'s original instructions. I think the subject was 'UPDATE: ATA mkIII patches' or something along those lines. Thanks. -Original Message- From: Dominic Marks [mailto:[EMAIL PROTECTED] Sent: Friday, July 01, 2005 5:00 PM To: freebsd-stable@freebsd.org; [EMAIL PROTECTED] Subject: Re: SATA Problems - ATA_Identify timeout ERROR - using Tyan S5350 On Friday 01 July 2005 16:34, Alan Jay wrote: Further to this the same ATA Timeout is seen in the latest SNAP binaries (1st July). Do you see them with ATA mkIII as well? http://people.freebsd.org/~sos/ATA/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Two Options: which to choose?
On Thursday 30 June 2005 22:53, Matt Juszczak wrote: After changing to PF I did not notice single crash for month (production servers with, sometimes, heavy load). I would try FreeBSD with PF anyway. Works perfectly. You say it didn't crash for a month, but then you say to try FreeBSD with PF because it works perfectly. To me, a month of uptime isn't perfectly. Can you elaborate? Is your machine still crashing even though its taking a month instead of a few days like it did previously? Could you not use pfsync to mitigate the problem (at least partially)? As for your original question, I think its less work to change your hardware to something you know works than changing operating systems. Why not use single CPU machines for this? Thanks, Matt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
graid3 + rsync + 5.4-STABLE repeatable panic (Fatal trap 12: page fault while in kernel mode)
Hello, I'm trying to use graid3 to create a raid volume from three 250GB SATA discs. I can successfully label, format, and mount the disc. The problem arises when I try and migrate some data on to the new volume. I'm using rsync to do this from over the local network, unfortunately this seems to be produce an immediate and reproduceable panic (hand copied): Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc30f8000 fault code = supervisor write, page not present instruction pointer = 0x8:0xc05e9783 stack pointer = 0x10:0xd8030c38 frame pointer = 0x10:0xd8030c80 code segment = base 0x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 617 (g_raid3 raid) trap number = 12 panic: page fault Other programs (touch, ls, diskinfo, etc) do not seem to provoke the panic, but rsync will kill the system within a second. I got a dump (once), but I think it is corrupt in some way because I have not been able to get a backtrace or any other useful data from it. # kgdb kernel.debug /usr/crash/vmcore.0 kgdb: kvm_read: invalid address (f9) (This line is printed again, and again, and again ...) This may be because I compiled my debugging kernel after I had installed the system, although it should have been an identical source tree ... I'm currently rebuilding the system to the freshest available -STABLE in the hope that may give a full backtrace. FreeBSD mrt.helenmarks.co.uk 5.4-STABLE FreeBSD 5.4-STABLE #0 Mon Jun 27 09:34:02 BST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEV i386 The only thing slightly odd about the machine is that each disc is one its own SATA controller. One disc is attached to an Intel ICH6 the other two are attached two Silicon Image (3112) based cards. The root device is ad2, since the additional cards have pushed themselves to the front. This is a temporary setup to facilitate migration of data from system to system. If I can do anything to help track the problem down, please say. I really want this to work, and I have some time in which to run tests. * A side note, I have noticed that the panic is often accompanied by a ATA DMA timeout (ad1). Could this cause the panic to occur? Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #0: Mon Jun 27 09:34:02 BST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEV WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: DELL PESC420 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.53GHz (2527.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE real memory = 526958592 (502 MB) avail memory = 509628416 (486 MB) ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL PESC420 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci0: display, VGA at device 2.0 (no driver attached) pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom BCM5751 Gigabit Ethernet, ASIC rev. 0x4001 mem 0xdfdf-0xdfdf irq 16 at device 0.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5750 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:11:c3:2c:91 pcib3: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0 pci3: ACPI PCI bus on pcib3 pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: serial bus, USB at device 29.2 (no driver attached) pci0: serial bus, USB at device 29.3 (no driver attached) pci0: serial bus, USB at device 29.7 (no driver attached) pcib4: ACPI PCI-PCI bridge at device 30.0 on pci0 pci4: ACPI PCI bus on pcib4 atapci0: SiI 3112 SATA150 controller port 0xdce0-0xdcef,0xdcb4-0xdcb7,0xdcc8-0xdccf,0xdcb0-0xdcb3,0xdcc0-0xdcc7 mem 0xdfaffc00-0xdfaffdff irq 17 at device 1.0 on pci4 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: SiI 3112 SATA150 controller port 0xdcf0-0xdcff,0xdcbc-0xdcbf,0xdcd8-0xdcdf,0xdcb8-0xdcbb,0xdcd0-0xdcd7 mem 0xdfaffe00-0xdfaf irq 18 at device 2.0 on pci4 ata4: channel #0 on
Re: graid3 + rsync + 5.4-STABLE repeatable panic (Fatal trap 12: page fault while in kernel mode)
On Wednesday 29 June 2005 18:14, Kris Kennaway wrote: On Wed, Jun 29, 2005 at 04:42:49PM +0100, Dominic Marks wrote: This may be because I compiled my debugging kernel after I had installed the system, although it should have been an identical source tree ... I'm currently rebuilding the system to the freshest available -STABLE in the hope that may give a full backtrace. Yes, you can have this kind of problem if you compile a kernel.debug after the fact and it doesn't quite match. Good to know, thank you. I've just built a fresh -stable system, so I will attempt to get the panic again with some useful information this time. Kris Cheers, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: graid3 + rsync + 5.4-STABLE repeatable panic (Fatal trap 12: page fault while in kernel mode)
On Wednesday 29 June 2005 16:42, Dominic Marks wrote: Hello, I'm trying to use graid3 to create a raid volume from three 250GB SATA discs. I can successfully label, format, and mount the disc. The problem arises when I try and migrate some data on to the new volume. I'm using rsync to do this from over the local network, unfortunately this seems to be produce an immediate and reproduceable panic (hand copied): Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc30f8000 fault code = supervisor write, page not present instruction pointer = 0x8:0xc05e9783 stack pointer = 0x10:0xd8030c38 frame pointer = 0x10:0xd8030c80 code segment = base 0x0, limit 0xf type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 617 (g_raid3 raid) trap number = 12 panic: page fault Having recompiled I can no longer produce the panic. I think I may have caused it myself, I had forgotten that I had been tinkering with some values in sys/sys/param.h last week, but it didn't ring a bell when the system went down. I'd been running with MAXPHYS and DFLTPHYS at 256 and it seems graid3 does not like one of those paramters being raised, I suspect its DFLTPHYS and that perhaps graid3 depends on its value for some calculations. This is pure speculation. My apologies for the incorrect report. Other programs (touch, ls, diskinfo, etc) do not seem to provoke the panic, but rsync will kill the system within a second. I got a dump (once), but I think it is corrupt in some way because I have not been able to get a backtrace or any other useful data from it. # kgdb kernel.debug /usr/crash/vmcore.0 kgdb: kvm_read: invalid address (f9) (This line is printed again, and again, and again ...) This may be because I compiled my debugging kernel after I had installed the system, although it should have been an identical source tree ... I'm currently rebuilding the system to the freshest available -STABLE in the hope that may give a full backtrace. FreeBSD mrt.helenmarks.co.uk 5.4-STABLE FreeBSD 5.4-STABLE #0 Mon Jun 27 09:34:02 BST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEV i386 The only thing slightly odd about the machine is that each disc is one its own SATA controller. One disc is attached to an Intel ICH6 the other two are attached two Silicon Image (3112) based cards. The root device is ad2, since the additional cards have pushed themselves to the front. This is a temporary setup to facilitate migration of data from system to system. If I can do anything to help track the problem down, please say. I really want this to work, and I have some time in which to run tests. * A side note, I have noticed that the panic is often accompanied by a ATA DMA timeout (ad1). Could this cause the panic to occur? Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #0: Mon Jun 27 09:34:02 BST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DEV WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. ACPI APIC Table: DELL PESC420 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Celeron(R) CPU 2.53GHz (2527.01-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf41 Stepping = 1 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR, PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PB E real memory = 526958592 (502 MB) avail memory = 509628416 (486 MB) ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger npx0: math processor on motherboard npx0: INT 16 interface acpi0: DELL PESC420 on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci0: display, VGA at device 2.0 (no driver attached) pcib2: ACPI PCI-PCI bridge irq 16 at device 28.0 on pci0 pci2: ACPI PCI bus on pcib2 bge0: Broadcom BCM5751 Gigabit Ethernet, ASIC rev. 0x4001 mem 0xdfdf-0xdfdf irq 16 at device 0.0 on pci2 miibus0: MII bus on bge0 brgphy0: BCM5750 10/100/1000baseTX PHY on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:11:c3:2c:91 pcib3: ACPI PCI-PCI bridge irq 17 at device 28.1 on pci0 pci3: ACPI PCI bus on pcib3 pci0: serial bus, USB at device 29.0 (no driver attached) pci0: serial bus, USB at device 29.1 (no driver attached) pci0: serial bus, USB
Re: Buffalo WLI-PCI-G54
On Friday 24 June 2005 03:13, Balgansuren.B wrote: Hello, I have driver disk for the Windows 98/Me/2000/XP of the Buffalo WLI-PCI-G54 wireless NIC. If possible I want to know ndiscvt command convert Windows driver to FreeBSD driver module. snip/ These two links explain what you need to do. http://caia.swin.edu.au/reports/041221A/ http://www.FreeBSD.org/cgi/man.cgi?ndiscvt Thanks, Balgaa HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dmesg queries
snip/ kernel: Interrupt storm detected on irq19: uhci0 uhci2; throttling interrupt source kernel: Interrupt storm detected on irq18: bge0 uhci1+; throttling interrupt source I get this as well. I don't use USB so I turned that off at the BIOS and removed it from my kernel, but I still get interrupt storm on my bge0 device. No idea why. I had a similar problem on an itx board, enabling DEVICE_POLLING fixed it. I found on this system around 8-10% of CPU time - when idle was used for interrupts alone without this change. That was achieved without disabling USB, which I also need. Performance is not all that great on this box disk-wise, but CPU wise it is acceptably fast. I run FreeBSD/amd64 on it rather than FreeBSD/ i386. Vivek Khera, Ph.D. +1-301-869-4449 x806 -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portinstall .vs. make install clean
On Sunday 26 June 2005 19:12, Maher Mohamed wrote: can some tell me what is the difference bitween portinstall and make install clean, and in which way should one portupgrade its ports? portinstall is a ruby program which comes with portupgrade which you can use to build and install ports. It can do some things which you can't do with a simple 'make install'. For example, I often use portinstall to create packages for a port and its dependancies. See the portupgrade manual page for details about how to use it. You should also look at /usr/local/etc/pkgtools.conf for how to set more advanced configurations for your system. thnk you in advanced -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portinstall .vs. make install clean
On Sunday 26 June 2005 19:32, Sergey Spivak wrote: Hi! portinstall is a ruby program which comes with portupgrade portinstall = portupgrade -N Oh. Makes me wonder why 'portinstall' exists at all. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Which driver for Soekris lan1641?
On Wednesday 15 June 2005 13:40, Constant, Benjamin wrote: Thanks to all for the details... Soekris lan1641 is using chipset National Semicondutor DP83816 which is not referenced in sis(4), that's why I was a bit confused. Is there a path to follow to request an update of the man page? send-pr(1). Benjamin Constant TI Automotive -Original Message- From: Eric Masson [mailto:[EMAIL PROTECTED] Sent: mercredi 15 juin 2005 14:20 To: Constant, Benjamin Cc: freebsd-stable@freebsd.org Subject: Re: Which driver for Soekris lan1641? Constant, Benjamin [EMAIL PROTECTED] writes: Hi, Ethernet chipset is National Semicondutor DP83816 but I can't find any reference to it in the hardware notes for 5.4. I need to know if ALTQ is available for this card. man 4 sis man 4 altq Éric Masson -- D'accord, mais si on se met à utiliser des arguments intelligents dans ce genre de débat, il devient impossible de discuter. Vous sombrez dans la facilité. -+- TS in GNU : La dialectique n'est plus ce qu'elle était. The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. This communication is from TI Automotive. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NFS on 5.4
On Monday 13 June 2005 13:18, Goran Gajic wrote: Ups, I forgot: Hello Goran, If you would reply to existing messages instead of posting new threads that would be very helpful it makes browsing the mail archive, and following conversation in a threaded mail reader much easier. Also you seem to be E-mailing [EMAIL PROTECTED], this clearly works but seems to confuse my mail client (KMail) and causes it to setup a reply to freebsd-stable@freebsd.org, and [EMAIL PROTECTED] by default, meaning replies to your posts from my client, and perhaps others, will be duplicated unless the sender removes the @www themselves. If you could send your messages to freebsd-stable@freebsd.org, I don't think this would occur. #vmstat -z | grep Mbuf MbufClust: 2048,25600, 4934, 0, 9085312 Mbuf:256,0, 4995,855, 199904149 Regards, gg. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] Thanks very much for your report, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
On Thursday 09 June 2005 12:42, Goran Gajic wrote: Hi, RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive (jmg: I cc'd you on the off chance you have not seen this already, another user identified your changes as related, but I have not tested this myself.) Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and other things) in -STABLE. See these messages for related reports. 1 [EMAIL PROTECTED] 2 [EMAIL PROTECTED] HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
On Thursday 09 June 2005 16:44, John-Mark Gurney wrote: Dominic Marks wrote this message on Thu, Jun 09, 2005 at 12:56 +0100: On Thursday 09 June 2005 12:42, Goran Gajic wrote: Hi, RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive (jmg: I cc'd you on the off chance you have not seen this already, another user identified your changes as related, but I have not tested this myself.) Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and other things) in -STABLE. See these messages for related reports. could you try backing out uipc_socket.c v1.208.2.19? If it broke because of my commits, it would of been this one, though I'm puzzeled as to why it didn't break in -current... Will do. P.S. Could you teach your mailer not to cc -stable twice? (once as freebsd.org and again as www.freebsd.org) Sorry about that. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive
On Thursday 09 June 2005 16:57, Dominic Marks wrote: On Thursday 09 June 2005 16:44, John-Mark Gurney wrote: Dominic Marks wrote this message on Thu, Jun 09, 2005 at 12:56 +0100: On Thursday 09 June 2005 12:42, Goran Gajic wrote: Hi, RPCPROG_NFS: RPC: Port mapper failure - RPC: Unable to receive (jmg: I cc'd you on the off chance you have not seen this already, another user identified your changes as related, but I have not tested this myself.) Yes, it seems that changes to the kernel (specifically kqueue?) broke NFS (and other things) in -STABLE. See these messages for related reports. could you try backing out uipc_socket.c v1.208.2.19? If it broke because of my commits, it would of been this one, though I'm puzzeled as to why it didn't break in -current... Will do. That fixes it. Thank you. P.S. Could you teach your mailer not to cc -stable twice? (once as freebsd.org and again as www.freebsd.org) Sorry about that. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.4-RC2 freezing - ATA related?
On Tuesday 17 May 2005 15:58, Brent Casavant wrote: snip You can add a fourth. Ever since 5.1 (my first 5.x install) I have experienced the same problem, again with an Intel ICH5 ATA controller. The symptoms are exactly the same -- the hang is normally triggered during the periodic runs just after 3AM. The hang does occur at other times as well, but with nowhere near the same consistency. I've got four machines with ICH5/6 chips in, no stability problems whatsoever, and thats been the case since I installed them, around 5.2.1. Perhaps it is something to do with your workload, or another piece of hardware in the system. The machines do a lot of disc i/o so during their working days. The only solution I found at that time was reverting to 4.10, though that is obviously suboptimal. I could be persuaded to reinstall 5.x on the machine if I'd be sure to get someone to look into this. Thanks, Brent Casavant HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: gmirror
On Saturday 14 May 2005 10:22, [EMAIL PROTECTED] wrote: Hardware: SATA RAID adapter with SiliconImage 3114 chip. 2 SATA HDD. I did gmirror. snip a) This is gmirror feature ? b) This is hardware feature (SiliconImage 3114 chip) ? I don't think is related to your hardware. I have a Dell PowerEdge SC1425 which is exhibiting the same behaviour from gmirror, my disc controller is an onboard Intel ICH5. System: FreeBSD 5.4-STABLE @ Sun Apr 10 14:07:46 UTC 2005 atapci1: Intel ICH5 SATA150 controller port 0xccc0-0xcccf,0xccd8-0xccdb, 0xcce0-0xcce7,0xccf0-0xccf3,0xccf8-0xccff irq 18 at device 31.2 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 mail# dmesg | grep ad4 ad4: 76293MB ST380013AS/8.12 [155009/16/63] at ata2-master SATA150 mail# diskinfo -t ad4 snip Seek times: Full stroke: 250 iter in 5.606627 sec = 22.427 msec Half stroke: 250 iter in 4.382610 sec = 17.530 msec Quarter stroke: 500 iter in 6.969860 sec = 13.940 msec Short forward:400 iter in 1.940076 sec =4.850 msec Short backward: 400 iter in 2.349238 sec =5.873 msec Seq outer: 2048 iter in 0.228509 sec =0.112 msec Seq inner: 2048 iter in 0.237599 sec =0.116 msec Transfer rates: outside: 102400 kbytes in 1.755089 sec =58345 kbytes/sec middle:102400 kbytes in 2.106003 sec =48623 kbytes/sec inside:102400 kbytes in 3.496732 sec =29284 kbytes/sec Pretty reasonable results. mail# dmesg | grep ad6 ad6: 76319MB ST380817AS/3.42 [155061/16/63] at ata3-master SATA150 The second drive achieves slightly better seeking, but lower throughput. But the variation between ad4 and ad6 is very small as I would expect for two virtually identical drives. mail# diskinfo -t ad6 snip Seek times: Full stroke: 250 iter in 4.936300 sec = 19.745 msec Half stroke: 250 iter in 3.675749 sec = 14.703 msec Quarter stroke: 500 iter in 5.970199 sec = 11.940 msec Short forward:400 iter in 1.937453 sec =4.844 msec Short backward: 400 iter in 2.347955 sec =5.870 msec Seq outer: 2048 iter in 0.211831 sec =0.103 msec Seq inner: 2048 iter in 0.218748 sec =0.107 msec Transfer rates: outside: 102400 kbytes in 1.754634 sec =58360 kbytes/sec middle:102400 kbytes in 2.107054 sec =48599 kbytes/sec inside:102400 kbytes in 3.522545 sec =29070 kbytes/sec Now the same test against the gmirror: mail# diskinfo -t /dev/mirror/gmirror0 snip Seek times: Full stroke: 250 iter in 1.347611 sec =5.390 msec Half stroke: 250 iter in 1.335664 sec =5.343 msec Quarter stroke: 500 iter in 2.653382 sec =5.307 msec Short forward:400 iter in 2.254421 sec =5.636 msec Short backward: 400 iter in 2.057330 sec =5.143 msec Seq outer: 2048 iter in 0.265052 sec =0.129 msec Seq inner: 2048 iter in 0.274519 sec =0.134 msec Transfer rates: outside: 102400 kbytes in 2.774400 sec =36909 kbytes/sec middle:102400 kbytes in 3.138420 sec =32628 kbytes/sec inside:102400 kbytes in 4.498140 sec =22765 kbytes/sec The seek times are way down, which is great, and makes sense using a round-robin strategy on the mirror, but my peak transfer rate has been almost halved too. I don't mind this too much as in my application low seek times are worth more than high transfer rates, but it is still puzzling to me to see such a remarkable drop in throughput. Thanks very much for insight, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange top(1) output
On Thursday 12 May 2005 11:39, you wrote: On 2005-05-11 13:50, Gavin Atkinson [EMAIL PROTECTED] wrote: Ah, yes! Good thought. This could affect the width of the USERNAME column and push everything too far to the right. If this is the case, I'd probably vote for optionally limiting the length of the username column to, say, 8 columns at most. I would also vote for limiting it to 8 characters. Even with longer usernames, I suspect 8 characters will be enough to identify particular users (and if it's not there is always they UID view). That's an option too. I'm currently trying to get top to display something like this (80 columns are used for text, so use a slightly wider terminal to view this properly: --- + last pid: 11090; load averages: 1.27, 1.26, 0.86up 0+01:11:11 03:07:43| 71 processes: 3 running, 68 sleeping | CPU states: 11.2% user, 0.0% nice, 77.1% system, 0.8% interrupt, 10.9% idle | Mem: 50M Active, 348M Inact, 70M Wired, 20M Cache, 60M Buf, 6340K Free | Swap: 5000M Total, 5000M Free | PID USERNAME PRI NICE SIZERES STATETIME WCPU COMMAND/NTHR | 4738 root 1080 1360K 836K RUN 1:28 22.80% find/1 | 638 giorgos-80 13496K 4672K pcmwr1:33 1.03% mpg123/1 | 11062 giorgos960 2428K 1520K RUN 0:00 1.54% top/1 | --- + If you don't mind I will share my thoughts on these changes. This includes at least the following changes (some not visible): + The entire header line is limited to the window width too. + The USERNAME column is hard-limited to 8 characters. This makes me a little uneasy. Its a typical idiom, at least at my Business, to have usernames which are of the form 'firstnamelastname', for this reason they can be quite long and often the first 5-8 characters will be frequently repeated, for example the following contrived names: rogermoore - rogermoo rogermoody - rogermoo charlottelane - charlott charlottedaniels - charlott If there are many processes (samba, imap, etc) running as these users (also typical in my environment, and I guess elsewhere too). If I use top to view the active processes now I will be unable to tell what is really going on. I know that I could run top and just display the UIDs, or I could use ps, but top is great for seeing the status at a glance, so loosing this information entirely in top would make life harder. Also, imagine a system where you have 200 users with UIDs ranging from 2000 to 2200. Picking out and distinguishing between lots of these numbers from a moving top display, is likely to be a very error prone task, no? I suppose it could be argued that using usernames of that format is a poor choice on my part, and if that is the consensus of opinion then I'll have to look at fixing my own setup. I use long format usernames because it do not wish to have to remember that rm5, rmoore (many other possible ways) is a particular person. If this behaviour could be turned on and off, I'd be very happy. + The THR column is displayed as /1 after the COMMAND, like the prstat(1M) command of recent Solaris versions. I like this. + The CPU/WCPU columns occupy the same space and can be toggled with the 'C' keyboard command. I like this too. + When UID numbers are displayed, hitting 'u' will read a UID instead of a username. + When the view is toggled between processes/threads, the NTHR part becomes the thread ID of the particular thread. Okay, not really sure what this will look like to me but no need to explain I'll wait until they hit -CURRENT and see for myself. Hopefully, I'll have these changes running on CURRENT before the weekend. If no strong objections are voiced for any of these changes, I'll test it on CURRENT for a while, then ask for approval of a commit to HEAD and merge it to 5-STABLE after it's been tested enough on CURRENT. Thanks for your work ! - Giorgos -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange top(1) output
On Thursday 12 May 2005 14:13, Tuomo Latto wrote: Dominic Marks wrote: This includes at least the following changes (some not visible): + The entire header line is limited to the window width too. + The USERNAME column is hard-limited to 8 characters. ... I suppose it could be argued that using usernames of that format is a poor choice on my part, and if that is the consensus of opinion then I'll have to look at fixing my own setup. I use long format usernames because it do not wish to have to remember that rm5, rmoore (many other possible ways) is a particular person. finger? True, that would work, but it does increase the amount of time needed to get a proper idea of the current state of the system significantly, which is the purpose of top (to me). If this behaviour could be turned on and off, I'd be very happy. How about making it a command line parameter? The field size, I mean. -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Serial ATA
On Monday 02 May 2005 17:22, O'Reilly, Stuart wrote: % --- snipped I have good experiences with RocketRAID 1520 and 1640. I'm running a 1640 with three SATA drives since one year without problems; it's just a little bit slow. Highpoint offers binary FreeBSD drivers for these controllers, but I think that people don't like this kind of support because Highpoint neglects it for older models and this dependency might be dangerous in future. Keep in mind: you'll get what you pay for. Regards Björn Can someone just answer a quick question. One of the suggestions mentioned was the Highpoint RocketRAID 1520 controller which is a low cost solutions however support for FreeBSD stopped at v5.1. However, scrolling down the list of driver software for the RocketRAID 1520, Highpoint offer the option of downloading the Linux Open Source Driver and compiling it yourself. To quote the website: Support Linux kernel version 2.2.x to 2.6.x on x86 and x86_64 platform. Would this be a suitable option since (as I understand it), FreeBSD is i386. FreeBSD has an i386 version, but it isn't only available for i386. See: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/archs.html Regarding the driver for Linux: Often the guts of drivers distributed in this way are binary and the interface which brings the binary and the kernel together is all that is publicly accessible. You will (quite literally) have more luck getting a binary Windows driver to work on FreeBSD than a binary Linux driver. Sorry if I sound like i'm trying to get blood from a stone. ;) Be wary of cheap controllers which burden your system with extra work instead of less. Stuart, ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] HTH, -- Dominic GoodforBusiness.co.uk I.T. Services for SMEs in the UK. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and NMAP
On Tuesday 19 April 2005 12:11, pck wrote: Hi, How can i hide from nmap that my OS is FreeBSD? Is this possible? # sysctl -ad | grep random_id net.inet.ip.random_id: Assign random ip_id values # echo 'net.inet.ip.random_id=1' /etc/sysctl.conf Best Regards, p. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Need really cheap IDE mirroring PCI controlled for FreebBSD 4.10
Artem Kuchin said: pete wright [EMAIL PROTECTED] wrote: On Wed, 2 Mar 2005 17:27:07 +0300, Artem Kuchin [EMAIL PROTECTED] wrote: Can anybody recommend cheap IDE mirroring PCI (2.0, not 2.1 or 2.2) controller with just 2 IDE ports which works fine with FreeBSD 4.10 ? It is to be installed on a very old motherboard (1998) and two 40GB IDE driver (more or less modern ones, at least not used ones for sure). sorry I don't know of any really cheap one's off hand, altho I do have experience with 3Ware RAID cards on 4.x. They seemed to work well, and they are less expensive than proper SCSI cards...altho slower. If cost really an issue would it be worth mirroring your disks in software via VINUM? Well, i don't trust software raids. But 3ware is probably one of the most expensive raid 0,1 controllers. There must be something around 40$ which freebsd supports. Does anyone known any model? Highpoint Rocket RAID ATA-133 which I found in the catalogue of a UK computer parts retailer seems to be what you want. 2 channel ATA-133 which does RAID 0/1 (don't know if it does it all on the card). It's slightly over your price target of $40 though, from this retailer its about £60. http://www.highpoint-tech.com/USA/r133.htm I have a similar SATA controller which from Highpoint which seems to work pretty well. -- Regards, Artem Kuchin IT Legion Ltd. Moscow, Russia www.itlegion.ru [EMAIL PROTECTED] +7 095 232-0338 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Dominic ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FBSD 5.3 w/ Silicon Image SATA
Hi Mark, You should be able to boot from one of the discs in the array, thats what I did when the RAID 1 on one of my servers dissappeared after an upgrade (not fun). Try booting from ad4, thats what I did to get things back on for the time being, no RAID at the moment I'm afraid. I'm now using it as a ordinary two channel controller while some scripts mirror the data until I get round to replacing the card. Just out of interest can anyone tell me why it was decided that support for this card should be removed/ broken without warning (no UPDATING heads-up ?) it was working perfectly for me :-( I can only assume it was some very nasty data loss potential? -- Dominic -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Mark Gebert Sent: 10 January 2005 02:47 To: freebsd-stable@freebsd.org Subject: FBSD 5.3 w/ Silicon Image SATA I have a Asus A7N8X-E Deluxe with a Silicon Image Sil 3112a controller. I was able to create the ar0 device while loading the OS but cannot boot off the resulting load (the image is mirrored on both drives). The ar0 device does not appear in the kernel messages. The error I get is: Mounting root from ufs:/dev/ar0s1a setrootbyname failed ffs_mountroot: can't find rootvp Root mount failed: 6 Any advice on how to make the system load? --geeb -- Mark A Gebert ThugsRUs Networks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise FastTrak Tx4200 FreeBSD 5.3
Mark Kirkwood said: fredrik engberg wrote: Hey. I'm having some trouble getting my promise fasttrak tx4200 (PDC20619) to work on FreeBSD 5.3. It wont show up on dmesg or when i use atacontrol list. when i use pciconf -lv it give me this. [EMAIL PROTECTED]:8:0: class=0x010400 card=0x3519105a chip=0x3519105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID Interesting - PDC20619 is listed in ata(4) manual page for 5.3 Release, so one would expect it to show up. From a quick look in sys/ata and Google the PDC20619 seems to be the TX4000 rather than the TX4200. Promise's website is, ... less than helpful in finding these sorts of things out. Cheers, Dominic Not sure if this is very useful, but here is what I see for a TX2000: $ pciconv -lv [EMAIL PROTECTED]:20:0: class=0x010485 card=0x4d68105a chip=0x6269105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' device = 'PDC20271 FastTrak TX2000 EIDE controller' class= mass storage subclass = RAID $ dmesg atapci1: Promise PDC20271 UDMA133 controller port 0xec00-0xec0f,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc07 mem 0xd900-0xd900 irq 11 at device 20.0 on pci0 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 regards Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Promise FastTrak Tx4200 FreeBSD 5.3
Hello Fredrik, I think you are out of luck at the moment. The Linux driver is a binary/source hybrid which isn't usually a good sign. Good luck, Dominic -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of fredrik engberg Sent: 07 January 2005 21:34 To: freebsd-stable@freebsd.org Subject: Promise FastTrak Tx4200 FreeBSD 5.3 Hey. I'm having some trouble getting my promise fasttrak tx4200 (PDC20619) to work on FreeBSD 5.3. It wont show up on dmesg or when i use atacontrol list. when i use pciconf -lv it give me this. [EMAIL PROTECTED]:8:0: class=0x010400 card=0x3519105a chip=0x3519105a rev=0x02 hdr=0x00 vendor = 'Promise Technology Inc' class = mass storage subclass = RAID I have asked around and tried to get info from freebsd.org and google.com, but i cant seem to find any good info. the people i have talked to said to add device ataraid to the kernel so i did but it didn't help. So any tips and hints would be grateful. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interpreting netstat -m output
On Wed, Sep 04, 2002 at 01:47:58PM -0700, Mike Hoskins wrote: On Wed, 4 Sep 2002, Charles Sprickman wrote: What is the difference between the mbufs in use line and the mbuf clusters in use line? An mbuf is a fixed length structure which contains network data. An mbuf cluster is associated with an area of memory which is used for storing more data than you can fit in a single mbuf. According the DI 4.4 an mbuf is 128 bytes and (not all of this is available for data storage), an mbuf cluster varies in size, but defaults to 1024 bytes (but according to the book this may be different depending on CPU architecture). I've wondered precisely this; perhaps one specifically relates to the network? The farthest I got was netstat(1), which points to a nonexistant mbuf(9). Later, -Mike Hey Mike :-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- Dominic Marks Computer Politics Geek [work]::[npl.co.uk] dominic.marks at npl.co.uk [educ]::[umist.ac.uk] notyet-known at umist.ac.uk [home]::[btinternet] dominic_marks at btinternet.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: interpreting netstat -m output
On Thu, Sep 05, 2002 at 02:04:05AM +0400, Dmitry Morozovsky wrote: On Wed, 4 Sep 2002, Dominic Marks wrote: DM An mbuf is a fixed length structure which contains network data. DM DM An mbuf cluster is associated with an area of memory which is used for DM storing more data than you can fit in a single mbuf. DM DM According the DI 4.4 an mbuf is 128 bytes and (not all of this is DM available for data storage), an mbuf cluster varies in size, but DM defaults to 1024 bytes (but according to the book this may be different DM depending on CPU architecture). AFAIK according to /usr/src/sys/*/param.h, mbuf size if 256 (at least for i386, see /usr/src/sys/i386/include/param.h, and is not defined for Alphas); and mbcluster size defaults to 2k (I suppose the smallest 2^x to cover standard Ethernet frame) however, in /usr/src/sys/i386/boot/dosboot/param.h, MCLBYTES defined as 2^12 (4k). Don't know whether this value is really used. I would not be surprised to find that these are the current values. I quoted directly from the book which is a bit old. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- [EMAIL PROTECTED] *** -- Dominic Marks Computer Politics Geek [work]::[npl.co.uk] dominic.marks at npl.co.uk [educ]::[umist.ac.uk] notyet-known at umist.ac.uk [home]::[btinternet] dominic_marks at btinternet.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Crash with KVM monitoring in place ...
On Sun, Sep 01, 2002 at 12:35:15PM -0700, Matthew Dillon wrote: : :On Sun, 1 Sep 2002, Matthew Dillon wrote: : : : : 'trace'. If over several crashes it dies in the same place : : then we at least have an idea where to look. : : : : How large is your swap space, or your largest free partition? : : : :My swap is only ~2gig, and my drive looks like: : : Right... then do as I suggested in a previous email. Reduce : the machine's memory to 2G via /boot/loader.conf: : : hw.physmem=2048m : : Then reboot and turn on dumps to the swap device. If you : can reproduce the crash with the machine downgraded to 2G : we should get a dump we can work with. : :Okay, just to confirm, my swap device looks like: : :venus# pstat -s :Device 1K-blocks UsedAvail Capacity Type :/dev/amrd0s1b 2097024 8708 2088316 0%Interleaved : :which is just under 2048m, at 2039m instead ... so ... should I sent it :down to 2000m even, or ... ? : :And all I need to do is set 'dumpdev=/dev/amrd0s1b' in /etc/rc.conf ... :no other settings I need? pstat -s reports 128K less then the actual size of the partition, so you have 2097152 = 2G exactly. 2048m should be fine. Yes, setting dumpdev=/dev/amrd0s1b in /etc/rc.conf should do it. You might want to set the dumpdir variable too, you'll need the location for the dumps to have enough space, or when your machine boots up it will try and read the dump from the swap space onto /var/crash (default) obviously its no good if it runs out of space while it is doing this. Good Luck. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- Dominic Marks Computer Politics Geek [work]::[npl.co.uk] dominic.marks at npl.co.uk [educ]::[umist.ac.uk] notyet-known at umist.ac.uk [home]::[btinternet] dominic_marks at btinternet.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
frequent page fault panic
Hi, I'm getting the same panic repeatedly on -STABLE. The time length between panic's varies between about half an hour and several days. It doesn't appear to be related to system load. The machine is used as a Desktop - with a few things running. I put some load on the machine (average of around 40.5 or so and lots of swapping) for an hour. The machine was fine. That also makes me doubtful that this hardware related. I have been unable to determine any particular pattern for the occurance of these panics. There doesn't seem to be a trigger that I've noticed. = Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc0bf9953 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02842ff stack pointer = 0x10:0xcca0ff38 frame pointer = 0x10:0xcca0ff44 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 3 current process = 67995 (XFree86) interrupt mask = net trap number = 12 panic: page fault = = (gdb) bt #0 0xc0131fa2 in dumpsys () #1 0xc0131d6c in boot () #2 0xc01321b9 in panic () #3 0xc01dafac in trap_fatal () #4 0xc01dac41 in trap_pfault () #5 0xc01da793 in trap () #6 0xc02842ff in ?? () #7 0xc02844ae in ?? () #8 0xc0284af1 in ?? () #9 0xc01ddeb3 in intr_mux () #10 0x87401af in ?? () #11 0x8740e35 in ?? () #12 0x8741d5e in ?? () #13 0x878a9b6 in ?? () #14 0x81616c5 in ?? () #15 0x816a4a7 in ?? () #16 0x816851e in ?? () #17 0x878afea in ?? () #18 0x81618e8 in ?? () #19 0x816a524 in ?? () #20 0x816b937 in ?? () #21 0x816ba21 in ?? () #22 0x80ac801 in ?? () #23 0x80bbb19 in ?? () #24 0x806a155 in ?? () = I'm currently rebuilding my kernel with debug sumbols so I can provide a more meaningful backtrace. I shall try and find out the problem, but my skills are still immature. I can provide dmesg and other information on request. I'm also not subscribed to freebsd-stable, so please keep me in the CC: chain. Thank You -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: frequent page fault panic
On Fri, Feb 22, 2002 at 01:03:41PM -0500, Matthew Emmerton wrote: What version of X are you using? 3.3.6 or 4.x? 4.1 built from ports. -- Matthew Emmerton || [EMAIL PROTECTED] GSI Computer Services || http://www.gsicomp.on.ca On Fri, 22 Feb 2002, Dominic Marks wrote: Hi, I'm getting the same panic repeatedly on -STABLE. The time length between panic's varies between about half an hour and several days. It doesn't appear to be related to system load. The machine is used as a Desktop - with a few things running. I put some load on the machine (average of around 40.5 or so and lots of swapping) for an hour. The machine was fine. That also makes me doubtful that this hardware related. I have been unable to determine any particular pattern for the occurance of these panics. There doesn't seem to be a trigger that I've noticed. = Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc0bf9953 fault code = supervisor write, page not present instruction pointer = 0x8:0xc02842ff stack pointer = 0x10:0xcca0ff38 frame pointer = 0x10:0xcca0ff44 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 3 current process = 67995 (XFree86) interrupt mask = net trap number = 12 panic: page fault = = (gdb) bt #0 0xc0131fa2 in dumpsys () #1 0xc0131d6c in boot () #2 0xc01321b9 in panic () #3 0xc01dafac in trap_fatal () #4 0xc01dac41 in trap_pfault () #5 0xc01da793 in trap () #6 0xc02842ff in ?? () #7 0xc02844ae in ?? () #8 0xc0284af1 in ?? () #9 0xc01ddeb3 in intr_mux () #10 0x87401af in ?? () #11 0x8740e35 in ?? () #12 0x8741d5e in ?? () #13 0x878a9b6 in ?? () #14 0x81616c5 in ?? () #15 0x816a4a7 in ?? () #16 0x816851e in ?? () #17 0x878afea in ?? () #18 0x81618e8 in ?? () #19 0x816a524 in ?? () #20 0x816b937 in ?? () #21 0x816ba21 in ?? () #22 0x80ac801 in ?? () #23 0x80bbb19 in ?? () #24 0x806a155 in ?? () = I'm currently rebuilding my kernel with debug sumbols so I can provide a more meaningful backtrace. I shall try and find out the problem, but my skills are still immature. I can provide dmesg and other information on request. I'm also not subscribed to freebsd-stable, so please keep me in the CC: chain. Thank You -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- Dominic To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
