8.1-RELEASE hangs on reboot
Hello, my 8.1-R system has just started hanging on reboot. Specifically after I svn up'd my source and updated from 8.1-R-p1 to -p2. Some kind of hang occurs on every reboot attempt. Usually it hangs at the "Rebooting..." message, but sometimes the thing just locks up before it even syncs disks. shutdown -p now seems to shutdown the system successfully each time. So I booted into single-user mode, executed "reboot" and during the "Syncing disks" I pressed Ctrl-Alt-Escape to break into the debugger. There I single-stepped with the "s" command until the thing simply stopped doing anything. (Even if I pressed NumLock, the LED on the keyboard wouldn't turn off.) The screen content at the moment of hang is (dutifully typed over as the thing is dead and I don't have a serial cable): [thread pid 12 tid 100017 ] Stopped at sckbdevent+0x5f: call _mtx_unlock_flags db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags: pushq %rbp db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x1: movq %rsp,%rbp db> [thread pid 12 tid 100017 ] Stopped at _mtx_unloock_flags+0x4: subq $0x20,%rsp db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0x8: movq %rbx,(%rsp) db> [thread pid 12 tid 100017 ] Stopped at _mtx_unlock_flags+0xc: movq %r12,0x8(%rsp) db> [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x11: movq %rdi,%rbx db> [thread pid 12 pid 100017 ] Stopped at _mtx_unlock_flags+0x14: movq %r13,0x10(%rsp) db> E Including that "E" at the end. As I said, it's 8.1-RELEASE-p2; it's on AMD64. I'm using custom kernel which only differs from GENERIC by addition of the debugging options: options INVARIANTS options INVARIANT_SUPPORT options WITNESS options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC I tried rebooting with ACPI disabled, but the thing paniced on boot with panic: Duplicate free of item 0xff00025e from zone 0xff00bfdcc2a0(1024) cpuid = 0 KDB: enter: panic [thread pid 0 tid 10 ] Stopped at kdb_enter+0x3d: movq $0, 0x6b2d20(%rip) db> bt Tracing pid 0 tid 10 td 0x80c63fc0 kdb_enter() at kdb_enter+0x3d panic() at panic+0x17b uma_dbg_free() at uma_dbg_free+0x171 uma_zfree_arg() at uma_zfree_arg+0x68 free() at free+0xcd device_set_driver() at device_set_driver+0x7c device_attach() at device_attach+0x19b bus_generic_attach() at bus_generic_attach+0x1a pci_attach() at pci_attach+0xf1 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a legacy_pcib_attach() at legacy_pcib_attach+0x70 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a legacy_attach() at legacy_attach+0x19 device_attach() at device_attach+0x69 bus_generic_attach() at bus_generic_attach+0x1a nexus_attach() at nexus_attach+0x68 device_attach() at device_attach+0x69 bus_generic_new_pass() at bus_generic_new_pass+0xd6 bus_set_pass() at bus_set_pass+0x7a configure() at configure+0xa mi_startup() at mi_startup+0x59 btext() at btext+0x2c db> reboot That panic is 100% repeatable -- every time I try booting with ACPI disabled, I get exactly the same panic. So -- what can I do about it? I'll gladly provide more information of course. Ondra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: display and manipulate math symbols?
On 9 February 2010 20:27, Polytropon wrote: > As you intendedly state that you're not searching for a > solution in the field of typesetting - where LaTeX comes > to mind immediately - I could imagine that you can do it > the hard way. > > First, see the symbols here: > > http://web.ift.uib.no/Fysisk/Teori/KURS/TeX/symALL.html > > Split the images into individual ones, and then use a > graphics suite, such as Gimp or OpenOffice Draw, to drag > them around the screen and combine a formula from them. > > Surely, you would be massively faster doing it with LaTeX, > but there's no mouse involved. :-) There is also this site: http://detexify.kirelabs.org/classify.html . It allows you to draw a mathematical symbol -- with your mouse -- and it will guess how you write that in LaTeX. As I guess the main reason for wanting to move symbols around visually is so that you don't have to remember tons of TeX sequences, this could be rather helpful. ~ Ondra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Suggestion for the fdisk(8) manual page...
On Sun, 20 Dec 2009 20:40:48 +0100, Modulok wrote: List, Just a suggestion: In the 'Bugs' section of the 'fdisk(8)' man page, could we get a note that informs users that fdisk is kind of... broken and obsolete? Something like: "fdisk is slowly being replaced by gpart(8). fdisk may not work correctly. If you see errors such as "fdisk: Class not found", use gpart(8) instead." That way, when you're confronted by the initially mysterious, "fdisk: Class not found" error, you don't waste tons of time double and triple checking slice table syntax and what not. Maybe even right at the top of the man page. Yes, it bit me today. Looking through the archives, apparently I'm not the only one. Thanks! -Modulok- Wow.. I wish I knew there *was* any gpart at the first place! I'm still kinda new to FreeBSD -- been using it since 7.0-RELEASE. Every time I had to make some changes to my partition table, I looked WTF-ly at fdisk manpage, then grabbed a Fedora live CD and made the changes from there. gpart looks like something that would do what I needed to do and would not require me to wonder if I got some obscure syntax right when modifying my partitions. So I'd like to second your suggestion: Mentioning gpart in man fdisk would've definitely saved my time. ~ Ondra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: 'X' vs. 'Mouse'
2009/12/12 Polytropon : > On Sat, 12 Dec 2009 11:50:33 -0700 (MST), Warren Block > wrote: >> I had thought about putting a footnote about that, but it was already >> too long. Also, I don't know about non-English keyboards. Maybe >> there's a mechanism in hal to detect preferred keyboard layout from the >> LANG setting. > > But if LANG isn't set, and LC_* settings differ? I think > detecting the keyboard layout from the keyboard itself is > not possible at all (how should it?). Yeah -- for instance, my LANG and all LC_* variables are set to en_US.UTF-8, so guess what my keyboard layout is? Yes, it is "us" and "cz_qwerty". When I was briefly using HAL, it took a lot of cursing to tell HAL that I want to have a second layout and that I want to be able to switch layouts using a keyboard shortuct. Using xorg.conf it is ridiculously easy. ~ Ondra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: update/upgrade question
2009/12/8 Alex Huth : > * Matthew Seaman schrieb: >> Alex Huth wrote: >> >> Yes. If you want to track one of the development branches (HEAD, RELENG_N) >> then you have to update sources by csup(1) or various other mechanisms and >> then compile your kernel+world yourself. >> >> Alternatively you can track release branches (RELENG_N_M) in the same way, >> or so long as the release branch is still in support, you can use >> freebsd-update(8) to pull down pre-built binary updates. >> >> > thx, this was a good explanation. Maybe one last (hopefully ;) ) question to > this topic. How can i see if a update has a kernel update, to prevent > unnessecary reboots? You can just csup your base system -- csup prints what files are being patched as it goes, if it doesn't list anything, then you already are at the latest revision of the branch you chose. But basically, if you're using -RELEASE, the sources won't change much -- only when a patch is released (for instance, 8.0-RELEASE-p1, p1 meaning first patch for 8.0-R) or when a new minor or major is released -- both will be announced on the freebsd-announce mailing list and usually on the forums as well. If you're tracking -STABLE or -CURRENT, the sources are likely to change often, so if you update after some reasonable time (a few days, perhaps hours -- just don't expect there to be anything new each five minutes), you'll always get something new. ~ Ondra ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Mouse and keyboard don't work in Xorg 7.4
2009/10/20 Polytropon : > >> Mouse and keyboard works without it too. > > I just re-read the chapters on X in the handbook. Setting > a specific keyboard language (german in my case) now involves > messing with XML in the HAL configuration. > > I'm just keen to know where I now have to set my mouse in > order to work properly. It's a three-button mouse from Sun. > > In the past, all X settings (resolution, mouse, keyboard, > fonts etc.) could be controlled via one centralized file. > Sadly, this seems to be scattered among many subsystems > now... You can still do it this way -- just disable HAL device autodetection and everything works as usual. I also have keyboard layouts set up in my xorg.conf file. In fact, I'd be willing to bet that your current xorg.conf will work on a newer X.org version, if you just add the line to disable HAL autodetection. ~ Ondra M. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: how to i designate the current function...?
On Mon, 01 Jun 2009 00:31:40 +0200, Gary Kline wrote:
I'm not sure this is std yet, but think it is available in gcc.
If I'm calling funtion bar(char *, char) with one of the args
incorrect, is there a way to have gcc name bar() in an error message?
Are you looking for the __FUNCTION__ macro?
void baz( char yes_no ) {
if ( yes_no == 'Y' || yes_no == 'N' ) {
// Do stuff...
} else {
printf( "%s: %s\n", __FUNCTION__, "I got an invalid arg" );
}
}
AFAIK, this isn't standard C, but well supported on GCC.
Ondra
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
