thread_lock vs panic/trap
Can a current thread panic or receive a trap while some other thread holds its thread_lock (the same lock as pointed to by the td_lock)? And a related question, can there be a reason for a thread in panic or kdb context to try to get the thread_lock? Thank you! -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: ZFS pool lost
Quoting Stefan Esser (from Thu, 05 May 2011 13:04:59 +0200): Sorry for the follow-up to my own posting, but I noticed, that I left out significant information. The system is an Athlon64 (X2, but was running with SMP disabled at the time) in 32 bit mode (i386) with 4GB RAM running 8-STABLE in a ZFS only configuration (one UFS partition was mounted but not accessed; it contains an emergency system which allows me to boot the exact kernel and access /rescue in exactly the version that was installed on ZFS). The panic occurs under 8-STABLE/i386 and with identical message when booting a -CURRENT live file-system from CD. The current is from which date? If it is one without zfs v28, please try one with zfs v28 (if you want to have a 8.2-release with v28 patched in: http://mfsbsd.vx.sk/). Maybe the problem is fixed in v28. If the import/export into v28 (it does not updeate the pool automatically, and updating the pool manually is not necessary) and a reimport into v15 does not solve the issue, you could try a "import -F" on v28 and then export + reimport in v15. Bye, Alexander. -- BOFH excuse #176: vapors from evaporating sticky-note adhesives http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: [UPDATE] New Boot-Loader Menu -- version 1.4
On May 5, 2011, at 7:21 PM, Devin Teske wrote: >> -Original Message- >> From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd- >> hack...@freebsd.org] On Behalf Of Ivan Voras >> Sent: Thursday, May 05, 2011 8:00 AM >> To: freebsd-hackers@freebsd.org >> Subject: Re: [UPDATE] New Boot-Loader Menu -- version 1.4 >> >> On 05/05/2011 15:40, Warren Block wrote: >>> On Thu, 5 May 2011, Devin Teske wrote: >>> Running on i386-compatible hardware supporting ACPI: B&W (standard): http://twitpic.com/4tlsin Color (loader_color=YES): http://twitpic.com/4tlt6l >>> >>> Looks nice. Options 3, 4, and 5 could be changed to >>> >>> 3. Safe Mode >>> 4. Single User Mode >>> 5. Verbose >>> >>> On/Off or Enabled/Disabled might be bikeshedably better than Yes and No. >> >> If we're going to nitpick, then the style of >> >> *Enable* Safe Mode : *YES | NO* >> >> may be even better :) While at it, I'd also suggest aligning the YES | >> NO fields vertically for better readability. >> >> But these are minor suggestions, it is ok the way it is :) >> > > Suggestions are good. I'm always open to them. Both are good suggestions. > > It's with great undulating frivolity (think: Steve Ballmer or Billy Mays) > that I invite anyone to simply edit the decidedly Forth-free /boot/menu.rc > where the captions are configured simply as a series of carefully-named > environment variables. If you find something you like, report back the > values that you used and I'll test them out. If it's a definite improvement, > I'll definitely make the change. > > The current boot loader menu, you have to go mucking through Forth to change > the captions (which can be tricky with any stack-based language let alone a > reverse polish one such as FICL). In general, I really like things becoming more modular. For FreeNAS's boot loader, I hacked a copy and put it as a patch to the FreeNAS build Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
RE: [UPDATE] New Boot-Loader Menu -- version 1.4
> -Original Message- > From: Warner Losh [mailto:i...@bsdimp.com] > Sent: Friday, May 06, 2011 8:31 AM > To: Devin Teske > Cc: 'Ivan Voras'; freebsd-hackers@FreeBSD.org > Subject: Re: [UPDATE] New Boot-Loader Menu -- version 1.4 > > > On May 5, 2011, at 7:21 PM, Devin Teske wrote: > > >> -Original Message- > >> From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd- > >> hack...@freebsd.org] On Behalf Of Ivan Voras > >> Sent: Thursday, May 05, 2011 8:00 AM > >> To: freebsd-hackers@freebsd.org > >> Subject: Re: [UPDATE] New Boot-Loader Menu -- version 1.4 > >> > >> On 05/05/2011 15:40, Warren Block wrote: > >>> On Thu, 5 May 2011, Devin Teske wrote: > >>> > Running on i386-compatible hardware supporting ACPI: > B&W (standard): http://twitpic.com/4tlsin > Color (loader_color=YES): http://twitpic.com/4tlt6l > >>> > >>> Looks nice. Options 3, 4, and 5 could be changed to > >>> > >>> 3. Safe Mode > >>> 4. Single User Mode > >>> 5. Verbose > >>> > >>> On/Off or Enabled/Disabled might be bikeshedably better than Yes and > No. > >> > >> If we're going to nitpick, then the style of > >> > >>*Enable* Safe Mode : *YES | NO* > >> > >> may be even better :) While at it, I'd also suggest aligning the YES | > >> NO fields vertically for better readability. > >> > >> But these are minor suggestions, it is ok the way it is :) > >> > > > > Suggestions are good. I'm always open to them. Both are good > suggestions. > > > > It's with great undulating frivolity (think: Steve Ballmer or Billy > Mays) > > that I invite anyone to simply edit the decidedly Forth-free > /boot/menu.rc > > where the captions are configured simply as a series of carefully-named > > environment variables. If you find something you like, report back the > > values that you used and I'll test them out. If it's a definite > improvement, > > I'll definitely make the change. > > > > The current boot loader menu, you have to go mucking through Forth to > change > > the captions (which can be tricky with any stack-based language let > alone a > > reverse polish one such as FICL). > > In general, I really like things becoming more modular. For FreeNAS's > boot loader, I hacked a copy and put it as a patch to the FreeNAS > build > > Warner Awesome! Absolutely Fantastic! That's what the BSD license is all about! (although... maybe I should have released it under the Beerware license -- with a Guinuess clause, lol). -- Devin _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: thread_lock vs panic/trap
On Friday, May 06, 2011 5:11:57 am Andriy Gapon wrote: > > Can a current thread panic or receive a trap while some other thread holds its > thread_lock (the same lock as pointed to by the td_lock)? I'm sure it's theoretically possible. If the thread is running just about anywhere and another thread is changing its cpuset for example, then you could run into this. > And a related question, can there be a reason for a thread in panic or kdb > context to try to get the thread_lock? I think it isn't safe to try to grab one's own thread lock in panic or kdb for this reason. -- John Baldwin ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
function typo in xfs sources
hi there,
while experimenting with 'gcc -Wmissing-declarations', i stumbled upon the
following typo. it would be nice, if anybody could correct this.
thanks in advance.
alex
--
a13x
diff --git a/sys/gnu/fs/xfs/FreeBSD/support/kdb.c
b/sys/gnu/fs/xfs/FreeBSD/support/kdb.c
index 274f23d..b133dfe 100644
--- a/sys/gnu/fs/xfs/FreeBSD/support/kdb.c
+++ b/sys/gnu/fs/xfs/FreeBSD/support/kdb.c
@@ -56,7 +56,7 @@ kdb_getarea_size(void *res, unsigned long addr, size_t size)
}
int
-db_putarea_size(unsigned long addr, void *res, size_t size)
+kdb_putarea_size(unsigned long addr, void *res, size_t size)
{
return 0;
}
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
