Re: Kernel panic with PF
On Fri, Jul 21, 2006 at 02:15:33PM +, Martin Beran wrote: I think this is not the case. The proxy uses either DIOCXBEGIN + DIOCBEGINADDRS + DIOCADDADDR + DIOCADDRULE + DIOCXCOMMIT or DIOCCHANGERULE(PF_CHANGE_GET_TICKET) + DIOCBEGINADDRS + DIOCADDADDR + DIOCCHANGERULE(PF_CHANGE_ADD_TAIL). The first method is used in the first call to create the ruleset. In the subsequent call, the second method is used to modify the ruleset. I did an experiment - repeated adding and deleting rules in two processes, as fast as possible. I expected EBUSY from time to time, but I also received EINVAL indeterministically. It seems to me that when the PF ioctl() is called simultaneously by two processes, it sometimes retuns EINVAL, although it sould be possible to either complete the operation (parameters are correct), or return EBUSY. -- Martin Beran Senior Developer Trusted Network Solutions, a.s. mobil: +420 603 820 932 [ www.tns.cz ] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Your message to ISN awaits moderator approval
Your mail to 'ISN' with the subject Returned mail: Data format error Is being held until the list moderator can review it for approval. The reason it is being held: Post by non-member to a members-only list Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://www.attrition.org/mailman/confirm/isn/b9d793d3f30dd3434a8e7b542cb9f55d57583ca8 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic
Graham Menhennitt wrote: On Wed, 19 Jul 2006, Stephen Montgomery-Smith wrote: I just had a kernel panic. This happened seconds after I started a reboot using alt-ctl-del, at about the time just after it it said it was writing the entropy file. Here is the kernel config file, the results of the dump, and dmesg. Do you want anything else? I hope this info helps. Fatal trap 12: page fault while in kernel mode current process = 479 (mountd) I have the same panic reproducibly. Shutting off nfs_server_enable (i.e. mountd) in rc.conf prevents it. This is with 6-STABLE cvsupped yesterday. I'll get some more info and follow up the PR. I rebuilt my kernel (to enable debugging) and now it doesn't panic. So it seems that an old kernel (from around the end of May) with a new mountd (from Sunday) will crash. But a new kernel with a new mountd won't. Graham ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filesystem full error with inumber
On Mon, 24 Jul 2006 17:14:27 +0200 (CEST) Oliver Fromme [EMAIL PROTECTED] wrote: Nobody else has answered so far, so I try to give it a shot ... The filesystem full error can happen in three cases: 1. The file system is running out of data space. 2. The file system is running out of inodes. 3. The file system is running out of non-fragmented blocks. The third case can only happen on extremely fragmented file systems which happens very rarely, but maybe it's a possible cause of your problem. I rebooted that server, and df then reported that disk at 108%, so it appears that df was reporting incorrect figures prior to the reboot. Having cleaned up, it appears by my best calculations to be showing correct figures now. kern.maxfiles: 2 kern.openfiles: 3582 Those have nothing to do with filesystem full. Yeah, that's what I figured. Looking again at dumpfs, it appears to say that this is formatted with a block size of 8K, and a fragment size of 2K, but tuning(7) says: [...] Reading this makes me think that when this server was installed, the block size was dropped from the 16K default to 8K for performance reasons, but the fragment size was not modified accordingly. Would this be the root of my problem? I think a bsize/fsize ratio of 4/1 _should_ work, but it's not widely used, so there might be bugs hidden somewhere. Such as df not reporting the actual data usage, which is now my best working theory. I don't know what df bases it's figures on, perhaps it either slowly got out of sync, or more likely, got things wrong once the disk filled up. I'll monitor it to see if this happens again, but hopefully won't keep that configuration around for too much longer anyway. Thanks, -fr. -- Feargal Reilly. PGP Key: 0x847DE4C8 (expires: 2006-11-30) Web: http://www.helgrim.com/ | ICQ: 109837009 | YIM: ectoraige Visit http://ie.bsd.net/ - BSDs presence in Ireland signature.asc Description: PGP signature
gmirror problem/question
Dear All I'm trying to implement gmirror file system for my cluster. Does someone using geom/gmirror solutions for that? any comments? I'm confused with the algorithm of moving gmirrored volume from one server to another. And how to add failed provider to a volume. I'm trying to stop the volume, then start ggatec on another server (all volumes are always exported with ggated on both servers), then I'm recreating mirror with gmirror label.. Sometimes when I'm adding/moving the volume I'm getting /dev/da1s1h device busy error, sometimes ggatec dies, sometimes I'm getting device not connected message. Looks like some kind of voodoo for me. The only way i can bring all volumes up - is to reboot both servers. Does someone solve this? Any suggestions? Please. OS is 6.1-RELEASE-p2. HW is Intel JR2 sever with hot swap scsi discs under mpt driver. Servers are cross linked via em1 (gigabit Ethernet). -- Best regards, Anton Nikiforov smime.p7s Description: S/MIME Cryptographic Signature
crashes on newly updated freebsd 6.1 box..
I was running 6.0 stable on my dual Pentium III/733Mhz box and was running fine and dandy.. I did makeworld to upgrade to 6.1 and its been crashing weekly if not less.. the only thing I get on the console is Sleeping thread (tid 100075, pid 4401) owns a non-sleepable lock panic: sleeping thread cpuid = 0 KDB: enter: panic I couldnt break in on the console and had to hard reboot the box. I was thinking this is kern/99094 but im not sure. I dont have any linux fs references in my /etc/fstab.. [EMAIL PROTECTED] jason $ cat /etc/fstab # DeviceMountpoint FStype Options DumpPass# /dev/idad0s1b noneswapsw 0 0 /dev/idad0s1a / ufs rw 1 1 /dev/idad0s1e /tmpufs rw 2 2 /dev/idad0s1f /usrufs rw 2 2 /dev/idad0s1d /varufs rw 2 2 /dev/idad1s1d /stuff ufs rw 2 2 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 proc/proc procfs rw 0 0 [EMAIL PROTECTED] jason $ but I do have [EMAIL PROTECTED] jason $ kldstat Id Refs AddressSize Name 15 0xc040 6540b0 kernel 21 0xc4f8c000 16000linux.ko [EMAIL PROTECTED] jason $ should I disable linux compatibility? or what? this is getting very annoying. [EMAIL PROTECTED] jason $ uname -a FreeBSD mj.org 6.1-STABLE FreeBSD 6.1-STABLE #1: Sat Jul 22 17:40:37 EDT 2006 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/BEAST i386 regards, Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: interface announcement MFC
On Sun, Jul 23, 2006 at 10:33:06PM +1200, Andrew Thompson wrote: I would quite like to MFC the autobridge feature but it depends on this change, http://lists.freebsd.org/pipermail/cvs-src/2006-May/064529.html I cant see it being a problem MFCing this to stable as the existing devd announcement still exists, it just adds another that includes pseudo ones too. Does anyone forsee any problems? I think it should be OK. We haven't seen any problems on -current and there should be enough time for things to settle before 6.2 in any case. -- Brooks pgpgf4eLXhZqH.pgp Description: PGP signature
Re: How to setup polling on 'bge' interface
A few points: - Polling and SMP are compatible in 6.1. In fact, they were compatible in earlier versions too; basically it's just the compile-time check that had to be fixed. - You may have to adjust some parameters in the kern.polling sysctl tree - specifically, kern.polling.burst_max, kern.polling.each_burst and kern.polling.user_frac might need tweaking. - The polling feedback algorithm does not work very well if your workload is focused largely on per-packet tasks (such as routing or bridging). You'll find that there is still idle CPU time at the point you start dropping packets. I have some work in progress to address this, but it's not yet committed. - Polling's major advantage is the avoidance of livelock on UP systems, and not improved performance. What level of traffic are you putting through this box? Is it routing/ bridging, or an endpoint like a web server? It's an endpoint with no more than 1k pkts/s in normal condition. Almost all traffic is UDP. I really intend to avoid locking my system in a high load situation. -- Att., Marcelo Gardini ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to setup polling on 'bge' interface
The limited testing I've done on a Sun V20z at work suggests that you can get better routing throughput in interrupt mode than polling mode. YMMV and this is before tweaking the polling parameters. (My testing also suggests that I don't really need to do any tweaking because the limiting factor is the gigabit interfaces rather than the V20z). I've noticed a higher (and variable) RTT with polling mode activated, without tweaking any parameters. This might not apply to bge, but the adaptive polling + fast interrupt changes that I made to if_em earlier in the year were a huge win over the standard polling code in terms of CPU utilization and packets per second. I think it also survived a load that caused normal polling to essentially livelock the machine. And, it had the advantage of automatically adapting to bursty loads. -- Att., Marcelo Gardini ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to setup polling on 'bge' interface
Marcelo Gardini do Amaral wrote: The limited testing I've done on a Sun V20z at work suggests that you can get better routing throughput in interrupt mode than polling mode. YMMV and this is before tweaking the polling parameters. (My testing also suggests that I don't really need to do any tweaking because the limiting factor is the gigabit interfaces rather than the V20z). I've noticed a higher (and variable) RTT with polling mode activated, without tweaking any parameters. Yes, the RTT will vary based on whether the interface has to wait a full tick or only a partial tick for the polling loop to become active. Adaptive polling eliminates most of this variance. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6-STABLE locks solid - current ok, why?
Hi, Got a testbed Proliant DL380G2, internal SmartArray 5i disabled, have SmartArray 5300 with 6 disks. Installed 6.1-REL last week, rebuilt to -STABLE three times since without a problem. However, when I try to add various (random) applications the box locks up solid during configure or make. Apps tested are postfix, jdk15, OpenOffice-2.0 and more. When it hangs the only thing remaining is power cycling, no keyboard access possible. What puzzles me here is that now I installed -CURRENT from yesterday on same box without any other changes and it works like charm, so far I'm through building close to 50 ports including kde with dependencies. Next step I guess is to go back to RELENG and check again. Meanwhile, does anyone out there have an idea where I should look? This box is going into production and I'm not brave enough to run -CURRENT... Thanks, ___ 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 locks solid - current ok, why?
Daniel Bond wrote: On 22:22 Mon 24 Jul, Per olof Ljungmark wrote: Hi, Got a testbed Proliant DL380G2, internal SmartArray 5i disabled, have SmartArray 5300 with 6 disks. Installed 6.1-REL last week, rebuilt to -STABLE three times since without a problem. However, when I try to add various (random) applications the box locks up solid during configure or make. Apps tested are postfix, jdk15, OpenOffice-2.0 and more. When it hangs the only thing remaining is power cycling, no keyboard access possible. What puzzles me here is that now I installed -CURRENT from yesterday on same box without any other changes and it works like charm, so far I'm through building close to 50 ports including kde with dependencies. Next step I guess is to go back to RELENG and check again. Meanwhile, does anyone out there have an idea where I should look? This box is going into production and I'm not brave enough to run -CURRENT... Hi, try to disable ACPI. It can be usefull for reading CPU temperature and fan speeds, but has no real function on a server. It's mostly usefull for power managment, supend and resume support. From the handbook: Most system hangs are a result of lost interrupts or an interrupt storm. Chipsets have a lot of problems based on how the BIOS configures interrupts before boot, correctness of the APIC (MADT) table, and routing of the System Control Interrupt (SCI). Interrupt storms can be distinguished from lost interrupts by checking the output of vmstat -i and looking at the line that has acpi0. If the counter is increasing at more than a couple per second, you have an interrupt storm. If the system appears hung, try breaking to DDB (CTRL+ALT+ESC on console) and type show interrupts. Your best hope when dealing with interrupt problems is to try disabling APIC support with hint.apic.0.disabled=1 in loader.conf Sorry, I should have mentioned that I tried both ways with same outcome. ___ 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 locks solid - current ok, why?
The 5300 have a battery backed up cache, I guess I should try to run the box off the 5i to check. Have several 360/380 G1/2/3's here too and never saw this before. I did: * Installed hw; iLO card + one Intel em0 + the 5300 * Booted 6.1-REL CD, installed base system including ports tree and sources * pkg_add -r cvsup-without-gui * fetched 6-STABLE sources * Edit the kernel config (took out 486/586, added SMP/APIC) * rebuilt and installed world (I usually do this a few times over to check for hardware problems) * Installed postfix, that worked ok. * Next app (don't remeber which one sorry) hung the box * fetched 6-STABLE sources again * rebuilt and installed world, worked fine * tried again to complie apps, no joy. Hangs at random places, no error messages, just locks. * fetched 6-STABLE sources again * rebuilt and installed world, worked fine and finally, fetched -CURRENT, rebuilt and now everything is just great. ACPI is enabled. Reason I'm running -STABE is that I expect this one to go into production about the time 6.2 is released. Thanks, Mark Saad wrote: Hello I use many 380's here G2 G3 and G4's and I have not see this yet . I am currently using a G3 w/o any issues with RELENG_6. This box is a jumpstart and buildmaster for my office and this is the DL I use 6.1 on the most. As for the G2 I moved away from them for the most part, but I have one here in my office I could check out if you have a list of what you did. I have two questions for you first, Why are you using the SA5300 , and are you running famd or ganim on the server; or a nfs client attached to the server ? Per olof Ljungmark wrote: Hi, Got a testbed Proliant DL380G2, internal SmartArray 5i disabled, have SmartArray 5300 with 6 disks. Installed 6.1-REL last week, rebuilt to -STABLE three times since without a problem. However, when I try to add various (random) applications the box locks up solid during configure or make. Apps tested are postfix, jdk15, OpenOffice-2.0 and more. When it hangs the only thing remaining is power cycling, no keyboard access possible. What puzzles me here is that now I installed -CURRENT from yesterday on same box without any other changes and it works like charm, so far I'm through building close to 50 ports including kde with dependencies. Next step I guess is to go back to RELENG and check again. Meanwhile, does anyone out there have an idea where I should look? This box is going into production and I'm not brave enough to run -CURRENT... Thanks, ___ 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]
Cardbus0: CIS pointer != 0 problem.
I have a colleague who installed FreeBSD 6.1-stable onto an Alienware MJ-12 laptop. A verbose dmesg is at http://troutmask.apl.washington.edu/~kargl/alienware.dmesg We are trying to getting his wireless nic up, but seem to have run into a cardbus issue. I've built a custom kernel and stripped out all unneeded device drives. During boot,r we see cardbus0: CIS pointer is 0! cardbus0: Resource not specified in CIS: id=10, size=100 cardbus0: Resource not specified in CIS: id=14, size=0 cardbus0: Resource not specified in CIS: id=1c, size=100 cardbus0: Resource not specified in CIS: id=24, size=80 cbb alloc res fail found- vendor=0x10de, dev=0x0299, revid=0xa1 bus=2, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit Has anyone seen this problem and do you have some recommendations to fix or work around the issue? -- Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cardbus0: CIS pointer != 0 problem.
Steve Kargl wrote: I have a colleague who installed FreeBSD 6.1-stable onto an Alienware MJ-12 laptop. A verbose dmesg is at http://troutmask.apl.washington.edu/~kargl/alienware.dmesg We are trying to getting his wireless nic up, but seem to have run into a cardbus issue. I've built a custom kernel and stripped out all unneeded device drives. During boot,r we see cardbus0: CIS pointer is 0! cardbus0: Resource not specified in CIS: id=10, size=100 cardbus0: Resource not specified in CIS: id=14, size=0 cardbus0: Resource not specified in CIS: id=1c, size=100 cardbus0: Resource not specified in CIS: id=24, size=80 cbb alloc res fail found- vendor=0x10de, dev=0x0299, revid=0xa1 bus=2, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit Has anyone seen this problem and do you have some recommendations to fix or work around the issue? This message most commonly comes up when the NIC/PCCARD is NOT supported by a native FreeBSD driver. For example: cardbus0: CIS pointer is 0! cardbus0: Resource not specified in CIS: id=10, size=2000 ndis0: Belkin 802.11g Network Adapter mem 0xf6002000-0xf6003fff irq 11 at device 0.0 on cardbus0 ndis0: NDIS API version: 5.1 ndis0: Ethernet address: 00:11:50:7b:ba:b1 is the output for my Broadcom-based wireless NIC. I use a WinDoze driver and the ndis interface. jmc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cardbus0: CIS pointer != 0 problem.
On Mon, Jul 24, 2006 at 09:20:37PM -0500, John Merryweather Cooper wrote: Steve Kargl wrote: cardbus0: CIS pointer is 0! cardbus0: Resource not specified in CIS: id=10, size=100 cardbus0: Resource not specified in CIS: id=14, size=0 cardbus0: Resource not specified in CIS: id=1c, size=100 cardbus0: Resource not specified in CIS: id=24, size=80 cbb alloc res fail Has anyone seen this problem and do you have some recommendations to fix or work around the issue? This message most commonly comes up when the NIC/PCCARD is NOT supported by a native FreeBSD driver. For example: The card has a atheros chip, and I know that it worked with FreeBSD 6.1-RELEASE. However, because of patches, I upgraded to 6.1-stable, and a acpi failure may be confusing cardbus. -- Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
