Account De-activation for freebsd-stable@freebsd.org. (Final Warning).
___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
About: Ownership Confirmation of freebsd-stable@freebsd.org
___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
RE: Satellite Broadband Internet Modem IP freebsd-stable@freebsd.org
___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Current problem reports assigned to freebsd-stable@FreeBSD.org
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o i386/179112 stable 9.1 installer panics with a kmem_malloc() failure on i 1 problem total. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-stable@freebsd.org
Paul MacKenzie wrote: last pid: 46013; load averages: 105.30, 67.67, 34.45 up 4+23:59:42 19:08:40 629 processes: 89 running, 540 sleeping CPU: 21.9% user, 0.0% nice, 74.5% system, 3.1% interrupt, 0.4% idle Mem: 1538M Active, 11G Inact, 898M Wired, 303M Cache, 214M Buf, 1346M Free Swap: 8192M Total, 1036K Used, 8191M Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 46000 www 1 650 86728K 15008K RUN1 0:01 12.06% httpd 45994 www 1 560 86728K 15008K CPU1 3 0:01 10.16% httpd 46002 www 1 -40 150M 20648K RUN3 0:00 6.98% httpd 45195 www 1 680 121M 19748K RUN1 0:29 6.88% httpd 45991 www 1 530 150M 21060K select 3 0:01 6.59% httpd 45997 www 1 -40 150M 20992K ufs5 0:01 6.59% httpd 45950 www 1 570 153M 23388K RUN2 0:01 6.49% httpd 45999 www 1 -40 150M 20640K ufs6 0:00 5.96% httpd 45189 www 1 660 161M 29660K RUN6 0:26 5.76% httpd 45974 www 1 -40 151M 21564K ufs3 0:01 5.76% httpd The number of httpd processes in ufs state is too high. Are you using PHP? And if you do, check how large is your PHP sessions' directory. Use a sharded layout if it's of any significant size (see php.ini for details). signature.asc Description: OpenPGP digital signature
freebsd-stable@freebsd.org
of top at a later date with the same problem happening focusing on IO setting in Top: -- last pid: 17984; load averages: 39.26, 37.68, 24.75 up 8+09:25:55 04:34:53 539 processes: 59 running, 480 sleeping CPU: 9.8% user, 0.5% nice, 87.0% system, 2.3% interrupt, 0.4% idle Mem: 1146M Active, 9663M Inact, 875M Wired, 582M Cache, 214M Buf, 3577M Free Swap: 8192M Total, 1036K Used, 8191M Free PID USERNAMEVCSW IVCSW READ WRITE FAULT TOTAL PERCENT COMMAND 17587 www 446 62 0 0 0 0 0.00% httpd 17763 www 515 37 0 0 0 0 0.00% httpd 17860 www 538 47 0 0 0 0 0.00% httpd 17703 www 457 43 0 0 0 0 0.00% httpd 17701 www 485 34 0 0 0 0 0.00% httpd 17550 www 423 29 0 0 0 0 0.00% httpd 17579 www0 0 0 0 0 0 0.00% httpd 17864 www 495 39 0 0 0 0 0.00% httpd 17836 www 520 36 0 0 0 0 0.00% httpd 17847 www 451 28 0 0 0 0 0.00% httpd 17756 www 462 29 0 0 0 0 0.00% httpd 17982 www 445 63 0 0 0 0 0.00% httpd 17581 www 451 60 0 0 0 0 0.00% httpd 17761 www 449 37 0 0 0 0 0.00% httpd 17582 www 509 30 0 0 0 0 0.00% httpd 17709 www 447 28 0 0 0 0 0.00% httpd 17705 www 515 30 0 0 0 0 0.00% httpd 17704 www 469 38 0 0 0 0 0.00% httpd 17706 www 508 53 0 0 0 0 0.00% httpd 17833 www 483 34 0 0 0 0 0.00% httpd 17834 www 499 43 0 0 0 0 0.00% httpd 17974 www 489 38 0 0 0 0 0.00% httpd 17978 www 467 45 0 0 0 0 0.00% httpd 17576 www 447 32 0 0 0 0 0.00% httpd 17570 www 443 37 0 0 0 0 0.00% httpd 17762 www 476 31 0 0 0 0 0.00% httpd 17837 www 508 44 0 0 0 0 0.00% httpd 17548 www 443 32 0 0 0 0 0.00% httpd 17783 www 390 22 0 0 0 0 0.00% httpd 17961 www 534 57 0 0 0 0 0.00% httpd 17590 www 498 50 0 0 0 0 0.00% httpd 17700 www 471 35 0 0 0 0 0.00% httpd 17580 www 438 41 0 0 0 0 0.00% httpd This used to be on a 4.11x system with 1 cpu and only 1gb of ram and ran flawlessly with much less resources with the same web site code for a long time. I do not have this problem on the other 7.0 machine. I originally thought it was just a cpu issue but it is very closely tied to when something is trying to use the raid arrays and this seems to be the way to reproduce it. I am having a hard time determining why the system load is so high. Can you recommend the best way to identify the culprit? Thanks, Paul ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RT256x PCMCIA card under 7.0-BETA2 (repost from freebsd-stable@freebsd.org, to get a broader audience)
Hi all! I just recently bought a RT2561C based (at least I think so) wireless card, which is also happily recognized by the ral-driver: ral0: Ralink Technology RT2561 mem 0x8800-0x88007fff irq 17 at device 0.0 on cardbus0 ral0: MAC/BBP RT2561C, RF RT2527 ral0: Ethernet address: 00:80:5a:51:23:53 ral0: [ITHREAD] As soon as I plug in the card and the netif script starts wpa_supplicant and dhclient, the laptop this is plugged into receives an interrupt storm on cbb0 (having 80% interrupt time), which leads to a noticeable slowdown of the whole system: phoenix# vmstat -i interrupt total rate irq1: atkbd09773 3 irq10: acpi0 729 0 irq14: ata017173 6 irq15: ata1 64 0 irq17: cbb0 cbb1+ 10408993 4217 irq18: pcm0 5753 2 irq19: sis0+ 33302 13 irq20: ohci0 207 0 irq21: ohci1 44261 17 irq23: ehci0 1 0 cpu0: timer 4926468 1996 Total 15446724 6258 phoenix# This snapshot was taken some time after I killed wpa_supplicant (when it had been up for about 10 seconds). When I manually start wpa_supplicant (with no stations in reach), there is no interrupt storm, but just normal activity with around 7-10 interrupts on cbb0 per second. I can also manually scan using the card (but ifconfig scan never finishes, but will show the stations in reach when doing an ifconfig list scan after ^C-ing the ifconfig scan), but cannot attach to any WPA access point in scanning-reach with wpa_supplicant (the only type of stations I have access to; I cannot test with WEP at the moment); enabling net.wlan.debug and net.wlan.0.debug also shows the scan taking place and the keys being set to the card, but nothing else from there. The card itself is a Conceptronic C54RC Version 2.0, which I guess explains the difference (in hardware) between the note in the manpage of ral(4) for this adapter and the actual hardware type it finds: Conceptronic C54RC RT2560 CardBus Anyway, doing a pciconv -lv leads to a different result than the actual driver reports, which is compatible with the hardware specification in the manpage: [EMAIL PROTECTED]:2:0:0:class=0x028000 card=0x3c231948 chip=0x03021814 rev=0x00 hdr=0x00 vendor = 'Ralink Technology, Corp' device = 'RT2525 2.4GHz transceiver + RT2560 MAC/BBP wireless a/b' class = network The kernel all of this runs under is a (slightly) modified GENERIC 7.0-BETA2 (from yesterday evening CET; an older 7.0-BETA2 didn't exhibit the interrupt storm behaviour, but was similar for the rest), with SMP disabled and SCHED_ULE instead of SCHED_4BSD. As debug.ral isn't available under the 7.0 ral-driver (which is referenced in the FreeBSD setup page http://damien.bergamini.free.fr/ral/ral-freebsd.html), I have no immediately obvious means of debugging what's actually happening when the interrupt storm takes place, and why the card won't attach to the AP even though the same wpa_supplicant config works using an ndis-wrapped driver for a different PCMCIA-card (Broadcom-based). Thanks for any hint you can give me! -- Heiko Wundram Product Application Development ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: RT256x PCMCIA card under 7.0-BETA2 (repost from freebsd-stable@freebsd.org, to get a broader audience)
Am Mittwoch, 14. November 2007 16:51:16 schrieb Heiko Wundram (Beenic): snip FSCK, sorry, I meant to repost to [EMAIL PROTECTED] Sorry for the noise... -- Heiko Wundram Product Application Development ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
QUARANTINED: freebsd-stable@freebsd.org
The message freebsd-stable@freebsd.org from Returned mail, sent on 4/28/2006 12:01 was quarantined because it contained either an executable file, a batch file or a screen saver file. All of these types of attachments are considered security risks. Please consult your mail administrator who can release the message. This message was checked by MailScan for WorkgroupMail. www.workgroupmail.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
QUARANTINED: Freebsd-stable@freebsd.org
The message Freebsd-stable@freebsd.org from Bounced mail, sent on 12/6/2005 13:45 was quarantined because it contained either an executable file, a batch file or a screen saver file. All of these types of attachments are considered security risks. Please consult your mail administrator who can release the message. This message was checked by MailScan for WorkgroupMail. www.workgroupmail.com ___ 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
___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
You freebsd-stable@freebsd.org are not member (usagi-users ML)
You are not a member of this mailing list [EMAIL PROTECTED]. If you know the general guide of this list, please send mail with the mail body guide to the address [EMAIL PROTECTED] where guide is equal to GUIDE for case insensitive. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
You freebsd-stable@freebsd.org are not member (cgreek ML)
You are not a member of this mailing list [EMAIL PROTECTED]. If you know the general guide of this list, please send mail with the mail body guide to the address [EMAIL PROTECTED] where guide is equal to GUIDE for case insensitive. ___ 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
freebsd-stable@freebsd.org ___ 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 and [EMAIL PROTECTED]
Would it be possible to force the mailing list software to rename recipient header freebsd-stable@freebsd.org to [EMAIL PROTECTED] or vice versa and then remove duplicates? I mean it seems like half the people on the list use freebsd-stable@freebsd.org address and the other half [EMAIL PROTECTED] A lot of times people manage to add the missing version of the list address to their reply to someone's post and I (along with the rest of the list readers) end up getting the same message twice. It's bad enough when you get the same message twice if you get it both via pm and list, but getting two copies of the same post via list is just stupid. Any chance of having something done to change this? -- Tuomo ... Q: How many hardware engineers does it take to change a lightbulb? A: None. We'll fix it in software ___ 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 subscribe freebsd-stable
subscribe freebsd-stable To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
