Re: Call for FreeBSD 2013Q3 (July-September) Status Reports
Dear FreeBSD Community, Please note that the next submission date for the July to September Quarterly Status Reports is October 7th, 2013, bit more than a week away. Please consult my previous message for the details: On Mon, Sep 9, 2013 at 12:04 AM, Gabor Pali wrote: > They do not have to be very long -- basically they may be about > anything that lets people know what is going on around the FreeBSD > Project. Submission of reports is not restricted to committers: > Anyone who is doing anything interesting and FreeBSD-related can (and > therefore encouraged to) write one! > > The preferred and easiest submission method is to use the XML > generator [1] with the result emailed as an attachment to us, that is, > mont...@freebsd.org [2]. There is also an XML template [3] which can > be filled out manually and attached if preferred. > > To enable compilation and publication of the Q3 report as soon as > possible for the October 7th deadline, please be prompt with any > report submissions you may have. > > We are looking forward to all of your 2013Q3 reports! > > Cheers, > Gabor > > > [1] http://www.freebsd.org/cgi/monthly.cgi > [2] mailto:mont...@freebsd.org > [3] http://www.freebsd.org/news/status/report-sample.xml ___ 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: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On Fri, Sep 27, 2013 at 6:57 PM, David Demelier wrote: > Seriously, I don't understand why people waste time to create jokes like > that instead of working on serious issues. > > You may think I'm putting to much significance on this kind of matter > but I like (and I'm not the only one) serious, clean things. Says the port maintainer of nsnake. Get over yourself. On Fri, Sep 27, 2013 at 7:33 PM, Teske, Devin wrote: > I coded it. You are the wind beneath my wings. Thanks! ___ 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: panic with if_iwi(4) upon "netif restart"
On Wed, Jul 04, 2012 at 06:51:56PM +0200, Bernhard Schmidt wrote: > On Tuesday 19 June 2012 07:28:11 Alexey Dokuchaev wrote: > > On Mon, May 07, 2012 at 08:28:50PM +0200, Bernhard Schmidt wrote: > > > does "ps" in kgdb reveal multiple instances of wpa_supplicant running? > > > If so, this seems to be the well known devd+netif+supplicant+newstate > > > race/missing refcount. > > > > > > Wanna try attached patch? > > > > Bernhard, > > > > Sorry it took so long to get back. With your patch applied, I haven't > > seen this panic for a while, however, double instances of wpa_supplicant > > still persist. So I think you can commit it, but underlying race remains > > to be fixed. > > Ok, thanks. The patch is indeed supposed to only fix the panics. > > The underlying problem is that a "netif restart" results in 2 > calls to "netif wlan0 start", one through the call itself the other > due an event sent to devd. wpa_supplicant itself has a small window > were it is possible that 2 instances are attached to one resource. > I have yet to find a solution for this without adding any regressions. Funny thing: I've just tried 9-stable on this laptop of mine, and it paniced immediately inside iwi_auth_and_assoc() again once I've run wpa_supplicant (this time I did not do any of "netif restart" dances). Applying the same patch fixed it for me and allowed to have working network (typing through it right now). Haven't tried -current yet, but it looks like iwi(4) is unusable at least in 9.2. Can we have this patch committed while real solution is being worked on? It looks like it's going to take a while, and I'd like to have working iwi(4) like, uhm, now. ;-) ./danfe ___ 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: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On 28.09.2013 11:32, Phil Regnauld wrote: > Teske, Devin (Devin.Teske) writes: >> If you work seriously on serious issues long enough... you'll become burned- >> out. Let me just come right out and say it... >> >> I coded it. > And thanks, you got me chuckling - nice to see some humor once in a > while. > > To the offended poster: read the last line of tunefs(8) - there's > probably > many more places you could use serious time looking for deviations from > corporate correctnes. Humor can even be etched in silicon, like e.g. on an IC created by Siemens: http://micro.magnet.fsu.edu/creatures/pages/bunny.html ;-) -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: 9.2-RC4 amd64 panic: vm_page_unwire
On Sat, 28 Sep 2013, 17:27 +0200, Oliver Pinter wrote: > On 9/28/13, John Marshall wrote: > > On Fri, 27 Sep 2013, 11:12 +0300, Konstantin Belousov wrote: > >> On Fri, Sep 27, 2013 at 10:07:28AM +1000, John Marshall wrote: > >> > The first two panics were triggered when shutting down the ntpd daemon > >> > (a recent development snapshot version of ntpd: 4.2.7p387). Exiting a > >> > later release (p388) has not triggered the panic. The system panicked > >> > again overnight, this time while acting as an sftp server receiving > >> > large (GB) files from another system. > > > >> > I have made the core.txt.[0-2] files available in the following > >> > directory. The directory is not browsable. > >> > > >> > http://www.riverwillow.net.au/~john/92rc4/ > >> > >> This might be fixed by r254087-r254090 on stable/9. > > > > Thank you. Those patches applied cleanly to releng/9.2 so I rebuilt a > > patched 9.2. I double-checked and verified that the following patched > > files in my releng/9.2@255904 working copy were identical to the same > > files in stable/9@254090, then I removed /usr/obj/* and built a fresh > > system. > > The system panicked as follows during shutdown after its first boot. > > The corresponding core.txt.3 file is available at the same location > > previously posted. > > I have now seen this panic on a second server as well (also amd64 but > > different hardware vendor). This second (unpatched) system also > > panicked during shutdown as follows. Corresponding file named > > core.txt.0.system2 is available at the same location as above. > try this from 9-STABLE: > https://github.com/freebsd/freebsd/commit/98362329be8e2cdefda1988e5e9d32efbc94855f Thanks Oliver. If I followed the links correctly, that looks like r255507 on stable/9. The second part of that patch didn't apply cleanly to 9.2. I investigated and it looks like that is because r254442 had also been applied since 9.2. I'm guessing I should also apply r254442 as well (first)? I shall proceed with applying both patches, rebuild, and see what happens. -- John Marshall pgpYlMb8rKbe3.pgp Description: PGP signature
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
On Sep 29, 2013, at 3:28 PM, C. P. Ghost wrote: > On 28.09.2013 11:32, Phil Regnauld wrote: >> Teske, Devin (Devin.Teske) writes: >>> If you work seriously on serious issues long enough... you'll become burned- >>> out. Let me just come right out and say it... >>> >>> I coded it. >> And thanks, you got me chuckling - nice to see some humor once in a >> while. >> >> To the offended poster: read the last line of tunefs(8) - there's >> probably >> many more places you could use serious time looking for deviations from >> corporate correctnes. > > Humor can even be etched in silicon, like e.g. on an IC created by Siemens: > > http://micro.magnet.fsu.edu/creatures/pages/bunny.html Cisco too, besides weird Star Wars ROM messages, you have stuff like the "BFR" (Big F*cking Router, after Big F*cking Gun in Doom) screened on the PCB: https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2_001 https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2 I have no idea what Sluggo and Nancy are doing on this board: https://www.kumari.net/gallery/index.php/Technology/Networking/CIMG0988 Charles > > ;-) > > -cpghost. > > -- > Cordula's Web. http://www.cordula.ws/ > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 9.2-PRE: switch off that stupid "Nakatomi Socrates"
Em 29-09-2013 19:11, Charles Sprickman escreveu: On Sep 29, 2013, at 3:28 PM, C. P. Ghost wrote: On 28.09.2013 11:32, Phil Regnauld wrote: Teske, Devin (Devin.Teske) writes: If you work seriously on serious issues long enough... you'll become burned- out. Let me just come right out and say it... I coded it. And thanks, you got me chuckling - nice to see some humor once in a while. To the offended poster: read the last line of tunefs(8) - there's probably many more places you could use serious time looking for deviations from corporate correctnes. Humor can even be etched in silicon, like e.g. on an IC created by Siemens: http://micro.magnet.fsu.edu/creatures/pages/bunny.html Cisco too, besides weird Star Wars ROM messages, you have stuff like the "BFR" (Big F*cking Router, after Big F*cking Gun in Doom) screened on the PCB: https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2_001 https://www.kumari.net/gallery/index.php/Technology/Networking/BFR_2 I have no idea what Sluggo and Nancy are doing on this board: https://www.kumari.net/gallery/index.php/Technology/Networking/CIMG0988 Charles ;-) -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" keep it cool u have others like: man chmod... BUGS There is no perm option for the naughty bits of a horse. and so many others. So... ___ 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: panic with if_iwi(4) upon "netif restart"
Sure, uhm, just remind me to commit it to -HEAD in the next few days. Then I'll get it backported to stable/9. Thanks, -adrian On 29 September 2013 10:03, Alexey Dokuchaev wrote: > On Wed, Jul 04, 2012 at 06:51:56PM +0200, Bernhard Schmidt wrote: > > On Tuesday 19 June 2012 07:28:11 Alexey Dokuchaev wrote: > > > On Mon, May 07, 2012 at 08:28:50PM +0200, Bernhard Schmidt wrote: > > > > does "ps" in kgdb reveal multiple instances of wpa_supplicant > running? > > > > If so, this seems to be the well known devd+netif+supplicant+newstate > > > > race/missing refcount. > > > > > > > > Wanna try attached patch? > > > > > > Bernhard, > > > > > > Sorry it took so long to get back. With your patch applied, I haven't > > > seen this panic for a while, however, double instances of > wpa_supplicant > > > still persist. So I think you can commit it, but underlying race > remains > > > to be fixed. > > > > Ok, thanks. The patch is indeed supposed to only fix the panics. > > > > The underlying problem is that a "netif restart" results in 2 > > calls to "netif wlan0 start", one through the call itself the other > > due an event sent to devd. wpa_supplicant itself has a small window > > were it is possible that 2 instances are attached to one resource. > > I have yet to find a solution for this without adding any regressions. > > Funny thing: I've just tried 9-stable on this laptop of mine, and it > paniced immediately inside iwi_auth_and_assoc() again once I've run > wpa_supplicant (this time I did not do any of "netif restart" dances). > > Applying the same patch fixed it for me and allowed to have working > network (typing through it right now). > > Haven't tried -current yet, but it looks like iwi(4) is unusable at least > in 9.2. Can we have this patch committed while real solution is being > worked on? It looks like it's going to take a while, and I'd like to have > working iwi(4) like, uhm, now. ;-) > > ./danfe > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
