Date: Wed, 3 Dec 2008 11:30:17 +0000 (UTC) From: Vadim Goncharov <vadim_nuclight@mail.ru> To: freebsd-geom@freebsd.org Subject: Re: System freeze with gvinum Message-ID: <slrngjcre9.2j6c.vadim_nuclight@server.filona.x88.info> References: <fmg3j4lkbngkmcm41lvbrjvuj2o4iagcvb@4ax.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Hilko Meyer! On Sat, 29 Nov 2008 23:47:59 +0100; Hilko Meyer wrote about 'System freeze with gvinum': > Every time I tried to run newfs on one of the volumes it stucked and the > complete system freezed, so I cannot provide a coredump. The system runs > 6.4-RELEASE that was compiled today. What can I do to debug this problem? You can try to call panic manually. Change your keymap first, e.g.: vadim@hostel:~>grep key /etc/rc.conf keymap="ru.koi8-r.vg" keyrate="fast" vadim@hostel:~>grep panic ru.koi8-r.vg.kbd 001 esc esc nop nop 155 155 debug panic O 092 nscr pscr debug debug nop nop nop panic O 104 slock saver slock saver susp nop susp panic O 129 esc esc nop nop 155 155 debug panic O 220 nscr pscr debug debug nop nop nop panic O 232 slock saver slock saver susp nop susp panic O Then do 'sysctl machdep.enable_panic_key=1' (may be add this to /etc/sysctl.conf). Then, if your dump device is configured, keymap is applied and sysctl enabled, you can press Alt-Shift-Ctrl-Esc on the console, and machine will panic with coredump. Of course it is better to fall into kernel debugger with Alt-Ctrl-Esc, but that requires debuger compiled into kernel and you knowing what to do with it :) -- WBR, Vadim Goncharov. ICQ#166852181 mailto:vadim_nuclight@mail.ru [Moderator of RU.ANTI-ECOLOGY][FreeBSD][http://antigreen.org][LJ:/nuclight]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?slrngjcre9.2j6c.vadim_nuclight>