Kernel Debugging Options

Hello everyone I have a two-part question: I have a minimally customized GENERIC kernel, with the only changes being: options KDB options KDB_UNATTENDED options DDB and 'sysctl debug.debugger_on_panic' shows: debug.debugger_on_panic: 0 However, after a panic loading the

Re: Kernel Debugging Options

On Sat, Jun 6, 2009 at 9:16 AM, Glen Barberglen.j.bar...@gmail.com wrote: Hello everyone I have a two-part question: I have a minimally customized GENERIC kernel, with the only changes being: options         KDB options         KDB_UNATTENDED options         DDB and 'sysctl

Panic resource_list_alloc 7.2 stable

Greetings This problem seems the same as this one from May of this year http://lists.freebsd.org/pipermail/freebsd-stable/2009-May/050088.html This happens on an older HP laptop. It was running on 7.1 prerelease fine and then I updated to 7.2 Stable yesterday. FreeBSD hp.shasta204.local

Re: Big problem still remains with 7.2-STABLE locking up

2009/6/6 NAKAJI Hiroyuki nak...@jp.freebsd.org: Hi, I noticed, some months ago, frequent lockups on my RELENG_6 server with ECS PM800-M2, Celeron 2.6GHz (UP), 2GB ram, ATA HDDs and 3Com NIC(xl0), and then I gave up this old server. Last month, I replaced this 'unstable' server to the new

Re: Big problem still remains with 7.2-STABLE locking up

My story is very similar to Pete's. http://lists.freebsd.org/pipermail/freebsd-stable/2009-January/047487.html My problem, which you link to there, tturrned out to be due to ICMP redirects, and is most definitely fixed in 7.2. So, your problem is not the same as mine, but some of the tips given

Re: make installworld and securelevel

Bruce Cran br...@cran.org.uk writes: On Fri, 05 Jun 2009 18:41:13 -0400 Lowell Gilbert freebsd-stable-lo...@be-well.ilk.org wrote: Bruce Cran br...@cran.org.uk writes: On Fri, 5 Jun 2009 17:45:50 +0200 FLEURIOT Damien m...@my.gd wrote: Hello list, I apologize if this

Stable from May 31 - zfs list locked

Hello, I encounter this problem for the second time. The system is working perfectly well but suddenly the command `zfs list' don't work and can't be killed. Here is a procstat of the culprit: [r...@morzine ~]# procstat -k 91766 PIDTID COMM TDNAME KSTACK 91766

Re: Big problem still remains with 7.2-STABLE locking up

In e1mcxfn-000bzm...@dilbert.ticketswitch.com Pete French petefre...@ticketswitch.com wrote: I followed some instructions in the list thread. But unfortunately, the big problem still remains. 7.2-STABLE server locks up frequently. Are you using the latest STABLE ? I am rolling out the

Re: Big problem still remains with 7.2-STABLE locking up

In 3bbf2fe10906060749xbbc2f2fy4c09f67711a...@mail.gmail.com Attilio Rao atti...@freebsd.org wrote: The kernel configuration is: include GENERIC ident   HEIMAT options MSGBUF_SIZE=81920 makeoptions     DEBUG=-g options KDB options DDB options BREAK_TO_DEBUGGER options

Re: Stable from May 31 - zfs list locked

Hello, I encounter this problem for the second time. The system is working perfectly well but suddenly the command `zfs list' don't work and can't be killed. Here is a procstat of the culprit: [r...@morzine ~]# procstat -k 91766 PIDTID COMM TDNAME KSTACK

Re: ZFS isntall requirements

On Fri, 5 Jun 2009, Kirk Strauser wrote: KS On Friday 05 June 2009 06:27:23 am Willem Jan Withagen wrote: KS Hi, KS KS I'm trying to get my world to 7.2-stable(amd64),but run into: KS install -o root -g wheel -m 444 kgzldr.o /usr/lib KS === sys/boot/i386/libi386 (install) KS ===

Re: Big problem still remains with 7.2-STABLE locking up

NAKAJI Hiroyuki wrote: Note that this is a lot of printout so you won't be able of collecting all these informations if not with a serial connection. The box does not have any serial port. Is there any other way? Is it possible to use dcons(4) for that purpose, if I add firewire PCI board?

Re: Stable from May 31 - zfs list locked

Henri Hennebert wrote: Hello, I encounter this problem for the second time. The system is working perfectly well but suddenly the command `zfs list' don't work and can't be killed. Here is a procstat of the culprit: [r...@morzine ~]# procstat -k 91766 PIDTID COMM TDNAME

Re: Kernel Debugging Options

On Sat, Jun 6, 2009 at 9:20 AM, Glen Barberglen.j.bar...@gmail.com wrote: Hello everyone I have a two-part question: I have a minimally customized GENERIC kernel, with the only changes being: options         KDB options         KDB_UNATTENDED options         DDB and 'sysctl