Re: core.txt.N not created anymore on panic

On Thu, Jul 18, 2013 at 12:00:26PM +0300, Mikolaj Golub wrote:
> On Wed, Jul 17, 2013 at 09:21:51AM +0200, Jeremie Le Hen wrote:
> > On Wed, Jul 17, 2013 at 09:16:55AM +0200, Jeremie Le Hen wrote:
> > > Hi,
> > > 
> > > Early May I set ddb_enable="YES" (crashinfo_enable="YES" by default).
> > > Upon panic, it created the following kind of files:
> > > 
> > > -rw-------  1 root  wheel         549 Jun 26 22:09 info.0
> > > -rw-------  1 root  wheel  1518501888 Jun 26 22:09 vmcore.0
> > > -rw-------  1 root  wheel      196981 Jun 26 22:09 core.txt.0
> > > -rw-------  1 root  wheel         546 Jun 26 23:15 info.1
> > > -rw-------  1 root  wheel   472608768 Jun 26 23:15 vmcore.1
> > > -rw-------  1 root  wheel      207034 Jun 26 23:15 core.txt.1
> > > -rw-------  1 root  wheel         546 Jun 27 00:47 info.2
> > > -rw-------  1 root  wheel   667717632 Jun 27 00:47 vmcore.2
> > > -rw-------  1 root  wheel      208745 Jun 27 00:48 core.txt.2
> > > -rw-------  1 root  wheel         549 Jul  3 14:40 info.3
> > > -rw-------  1 root  wheel  1455198208 Jul  3 14:40 vmcore.3
> > > -rw-------  1 root  wheel      208173 Jul  3 14:41 core.txt.3
> > > 
> > > The core.txt.N files contained crashinfo(8) informations along with
> > > ddb textdump, because crashinfo(8) outputs dmesg.
> > > 
> > > 
> > > Yesterday, I upgraded to latest -CURRENT from one from June 9th.  While
> > > stress-testing overnight, I got a couple of panics but core.txt.N are
> > > not created anymore.
> > > 
> > > -rw-------  1 root  wheel         530 Jul 17 01:10 info.5
> > > -rw-------  1 root  wheel       75776 Jul 17 01:10 textdump.tar.5
> > > -rw-------  1 root  wheel         529 Jul 17 02:01 info.6
> > > -rw-------  1 root  wheel       74240 Jul 17 02:01 textdump.tar.6
> > > -rw-------  1 root  wheel         530 Jul 17 04:20 info.7
> > > -rw-------  1 root  wheel       74752 Jul 17 04:20 textdump.tar.7
> > > -rw-------  1 root  wheel         530 Jul 17 07:50 info.8
> > > -rw-------  1 root  wheel       92672 Jul 17 07:50 textdump.tar.8
> > > -rw-------  1 root  wheel         531 Jul 17 08:44 info.9
> > > -rw-------  1 root  wheel      110592 Jul 17 08:44 textdump.tar.9
> > > 
> > > Each textdump.tar.N contains:
> > > 
> > > tar tvf /var/crash/textdump.tar.9 
> > > -rw-------  0 root   wheel   49152 Jul 17 08:30 ddb.txt
> > > -rw-------  0 root   wheel    3179 Jul 17 08:30 config.txt
> > > -rw-------  0 root   wheel   54137 Jul 17 08:30 msgbuf.txt
> > > -rw-------  0 root   wheel      88 Jul 17 08:30 panic.txt
> > > -rw-------  0 root   wheel     120 Jul 17 08:30 version.txt
> > > 
> > > Any idea changed in between?  I checked svn log in etc/ but I found
> > > nothing relevant.
> 
> Before your system was configured to generate vmcore dumps. Now it is
> configured to generate textdumps. crashinfo(8) works with vmcore.
> 
> > 
> > For the record:
> > 
> > debug.ddb.capture.bufoff: 0
> > debug.ddb.capture.maxbufsize: 5242880
> > debug.ddb.capture.inprogress: 0
> > debug.ddb.capture.bufsize: 49152
> > debug.ddb.capture.data: 
> > debug.ddb.scripting.scripts: lockinfo=show locks; show alllocks; show
> > lockedvnods
> > kdb.enter.panic=textdump set; capture on; run lockinfo; show pcpu; bt;
> 
> 'textdump set' tells ddb to store dumps in textdump format. Remove
> this from /etc/ddb.conf (and run /etc/rc.d/ddb) if you want
> crashinfo(8) data.

That was it, thanks!

I'm still confused why until recently, it worked as if textdump wasn't
enabled.  ddb capture was and I have never modified ddb.conf.

-- 
Jeremie Le Hen

Scientists say the world is made up of Protons, Neutrons and Electrons.
They forgot to mention Morons.