freebsd-stable Digest, Vol 188, Issue 10
Stephen Liss
stephen.liss at gmail.com
Mon Jan 1 15:02:26 PST 2007
Help
--
Stephen Liss
847-858-6549 (mobile)
Yahoo! IM: ic_stephen_liss
-----Original Message-----
From: freebsd-stable-request at freebsd.org
Date: Mon, 1 Jan 2007 12:00:42
To:freebsd-stable at freebsd.org
Subject: freebsd-stable Digest, Vol 188, Issue 10
Send freebsd-stable mailing list submissions to
freebsd-stable at freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
or, via email, send a message with subject or body 'help' to
freebsd-stable-request at freebsd.org
You can reach the person managing the list at
freebsd-stable-owner at freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-stable digest..."
Today's Topics:
1. Audio (Record) not functioning... (record interrupt timeout)
(Ben H.)
2. Re: BIND-9.3.2 (from 5.5-STABLE) segfault under load...
(Chuck Swiger)
3. 6.2-RC2 atkbd0 freezes system (Gardner Bell)
4. mpt0 timed out (wsk)
5. Re: 6.2-PRE: Fatal Trap? (Chris)
----------------------------------------------------------------------
Message: 1
Date: Sat, 30 Dec 2006 19:51:51 -0800 (PST)
From: "Ben H." <strbenjr at yahoo.com>
Subject: Audio (Record) not functioning... (record interrupt timeout)
To: questions FBSD <freebsd-questions at FreeBSD.ORG>, Stable FBSD
<freebsd-stable at FreeBSD.ORG>
Message-ID: <20061231035151.68350.qmail at web33005.mail.mud.yahoo.com>
Content-Type: text/plain; charset=ascii
Thanks in advance for any help you can provide... On reply please cc my email address.
http://www.bsdforums.org/forums/showthread.php?t=45514 [HISTORY]
http://lists.freebsd.org/pipermail/...rch/003877.html [Related Link]
I am trying to get Skype or Vonage softphone(via wine) working on my notebook.
My problem is getting the input from the mic to the application.
The "mic" is working because I can talk and hear the sound via the
external speakers. If (on command line mixer) I turn the "rec" and
"igain" to 0 the I CAN still hear any sound I make via the mic on the
attached speakers. If I turn "mic" to 0 then I cannot hear any sound I
make via the mic on the attached speakers.
Here is the error I am seeing on the system console:
pcm0:record:0:dsp0.0: record interrupt timeout, channel dead
Here are my settings:
user at sony$ uname -a
FreeBSD sony.family.hom 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #2: Tue Dec 19 16:55:50 EST 2006 root at sony.family.hom:/usr/obj/usr/src/sys/SONY01 i386
user at sony$ cat /dev/sndstat
FreeBSD Audio Driver (newpcm)
Installed devices:
pcm0: <Acer Labs M5451> at io 0x1800 irq 9 kld snd_t4dwave (4p/1r/4v channels duplex default)
user at sony$ dmesg | grep pcm
pcm0: <Acer Labs M5451> port 0x1800-0x18ff mem 0xe8100000-0xe8100fff at device 6.0 on pci0
pcm0: <Yamaha YMF753 AC97 Codec>
pcm0: [GIANT-LOCKED]
pcm0:record:0:dsp0.0: record interrupt timeout, channel dead
pcm0:record:0:dsp0.0: record interrupt timeout, channel dead
user at sony$ sysctl hw.snd
hw.snd.report_soft_formats: 1
hw.snd.targetirqrate: 32
hw.snd.verbose: 1
hw.snd.maxautovchans: 4
hw.snd.unit: 0
hw.snd.pcm0.buffersize: 4096
hw.snd.pcm0.vchans: 4
More info at: http://www.bsdforums.org/forums/showthread.php?t=46469
STRBen
strbenjr{a}yahoo.com
ben_hacker{a}inter-op.net
-- -- --
http://www.coeba.org
http://www.inter-op.net
------------------------------
Message: 2
Date: Sun, 31 Dec 2006 11:45:43 -0500
From: Chuck Swiger <cswiger at mac.com>
Subject: Re: BIND-9.3.2 (from 5.5-STABLE) segfault under load...
To: Doug Barton <dougb at FreeBSD.org>
Cc: FreeBSD mailing list <freebsd-stable at freebsd.org>
Message-ID: <4597E937.90300 at mac.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Doug Barton wrote:
> Chuck Swiger wrote:
>> Hi--
>>
>> I had named segfault a day or so ago under high load ("adnslogres -c
>> 200" against a webserver logfile) after logging the following:
>
> Hard to tell if your problem here is related to running on 5.5 or not,
> but of course recommendation number one is to consider upgrading to
> 6.x. Recommendation number two is to upgrade BIND to 9.3.3, preferably
> by upgrading to 6.2-RC2, or by upgrading to the head of RELENG_5, or
> as a last resort by using the port, with or without the option to
> replace the base BIND.
Noted, thanks. I've been following 6-STABLE on a pair of test machines, but
I've recently been bitten by whatever the bug was earlier this week or last
which resulted in daemon processes dying early in the boot, so I'd prefer to
be a bit more conservative until 6-STABLE settles down more.
>> [ ... ]
>>> Dec 28 03:38:56 <daemon.notice> pi named[1853]: enforced
>>> delegation-only for 'AR' (ctina.ar/A/IN) from 137.39.1.3#53
>
> If you're using this option, please make sure that you know why you
> are using it, and what the potential side effects are. That discussion
> is off topic for this list, but feel free to take it up on
> bind-users at isc.org if you wish.
The primary function of the machine in question is a SMTP relay; a secondary
major purpose is running Apache. Having various top-level domains return
non-delegation records (ie SiteFinder) breaks some of my anti-spam checking...
>>> Dec 28 03:50:23 <daemon.warn> pi named[1853]: client 127.0.0.1#53077:
>>> no more recursive clients: quota reached
>
> There is extensive discussion about this problem in the bind-users
> archives. Take a look at file:///usr/share/doc/bind9/arm/ and check
> out the quota options to get this adjusted to where it needs to be for
> your situation. Alternatively, if you're sure that the excess load is
> caused by the adnslogres program, try lowering the number of
> concurrent connections.
I'm quite sure the load is being caused by adnslogres; the "-c 200" flag
refers to the number of outstanding connection requests that program will
create. When performing DNS resolution of various IPs from a logfile, the
more connections permitted, the faster the resolution of the file completes as
you are mostly being held up by non-responsive nameservers which will time-out.
What strikes me as odd is that the BIND docs claim that recursive-clients
defaults to a value of 1000...? The named processes' memory usage shoots up
from a nominal starting point of 5 MB to around 45 MB after being queried
under this load.
Anyway, I've reduced adnslogres to using 50 outstanding connection requests.
>> As the subject mentions, this is a Dell 1850 (rackmount PowerEdge)
>> running FreeBSD-5.5 & BIND-9.3.2; until just now, everything had been
>> running stably for months at a time.
>
> I assume you've checked the usual suspects, dead fans, other hardware
> problems, etc?
Within reason, yes. I haven't taken the system down to perform 24-hours of
testing with Memtest86 or something like that, but the fans are OK (it's a
P3-based system; it doesn't run nearly as hot as the later Xeon-based models),
and there are no ECC warnings from the RAM, and drives are in a RAID-1 mirror
which is reporting no signs of trouble.
Thanks for your feedback,
--
-Chuck
------------------------------
Message: 3
Date: Sun, 31 Dec 2006 14:38:55 -0500 (EST)
From: Gardner Bell <gbell72 at rogers.com>
Subject: 6.2-RC2 atkbd0 freezes system
To: freebsd-stable at freebsd.org
Message-ID: <20061231193855.9492.qmail at web88013.mail.re2.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
Immediately after booting into 6.2-RC2 my system froze up and dropped
into ddb. Here is the relevant information. If any further info is
required please let me know.
db> trace
Tracing pid 24 tid 100020 td 0xffffff003d807000
kdb_enter() at kdb_enter+0x2f
scgetc() at scgetc+0x342
sckbdevent() at sckbdevent+0x83
atkbd_intr() at atkbd_intr+0x53
ithread_loop() at ithread_loop+0x163
fork_exit() at fork_exit+0x86
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffffffa5318d00, rbp = 0 ---
db> s
[thread pid 24 tid 100020]
Stopped at kdb_enter+0x30: leave
db> ps
pid ppid pgrp uid state wmesg wchan cmd
613 606 613 1001 S+ select 0xffffffff804c8bb0 top
606 581 606 1001 S+ wait 0xffffff002e021358 sh
600 580 600 1001 S+ ttyin 0xffffff000077e810 sh
583 1 583 0 Ss+ ttyin 0xffffff0000684c10 getty
582 1 582 0 Ss+ ttyin 0xffffff0000685810 getty
581 1 581 0 Ss+ wait 0xffffff003d80ea08 login
580 1 580 0 Ss+ wait 0xffffff002de1ea08 login
578 577 34 0 S+ nanslp 0xffffffff804bbb60 sleep
577 575 34 0 S+ wait 0xffffff0025615000 sh
576 1 34 0 S+ piperd 0xffffff0026c18900 logger
575 1 34 0 S+ wait 0xffffff002fddf000 sh
535 1 535 0 Ss nanslp 0xffffffff804bbb60 cron
415 1 415 0 Ss select 0xffffffff804c8bb0 syslogd
294 1 294 65 Ss select 0xffffffff804c8bb0 dhclient
274 1 34 0 S+ select 0xffffffff804c8bb0 dhclient
145 1 145 0 Ss pause 0xffffff0025410718 adjkerntz
33 0 0 0 SL - 0xffffffffa534fbe4 [schedcpu]
32 0 0 0 SL sdflush 0xffffffff804cd5a0 [softdepflush]
31 0 0 0 SL syncer 0xffffffff804bb840 [syncer]
30 0 0 0 SL vlruwt 0xffffff003daa6a08 [vnlru]
29 0 0 0 SL psleep 0xffffffff804c9478 [bufdaemon]
28 0 0 0 SL pgzero 0xffffffff804d2720 [pagezero]
27 0 0 0 SL psleep 0xffffffff804ce5ec [vmdaemon]
26 0 0 0 SL psleep 0xffffffff804ce59c [pagedaemon]
25 0 0 0 WL [swi0: sio]
24 0 0 0 RL CPU 0 [irq1: atkbd0]
23 0 0 0 WL [irq29: bge1]
22 0 0 0 WL [irq28: bge0]
21 0 0 0 WL [irq15: ata1]
20 0 0 0 WL [irq14: ata0]
19 0 0 0 WL [irq9: acpi0]
9 0 0 0 SL - 0xffffff0000096a00 [kqueue_taskq]
8 0 0 0 SL - 0xffffff0000096b00 [acpi_task_2]
7 0 0 0 SL - 0xffffff0000096b00 [acpi_task_1]
6 0 0 0 SL - 0xffffff0000096b00 [acpi_task_0]
18 0 0 0 WL [swi6: task
queue]
17 0 0 0 WL [swi6: Giant
taskq]
5 0 0 0 SL - 0xffffff0000804100 [thread taskq]
16 0 0 0 WL [swi5: +]
15 0 0 0 SL - 0xffffffff804b66c0 [yarrow]
4 0 0 0 SL - 0xffffffff804b7288 [g_down]
3 0 0 0 SL - 0xffffffff804b7280 [g_up]
2 0 0 0 SL - 0xffffffff804b7270 [g_event]
14 0 0 0 WL [swi1: net]
13 0 0 0 WL [swi3: vm]
12 0 0 0 WL [swi4: clock sio]
11 0 0 0 RL [idle: cpu0]
10 0 0 0 RL CPU1 [idle: cpu1]
1 0 1 0 SLs wait 0xffffff003db5c000 [init]
0 0 0 0 WLs [swapper]
db> show pcpu
cpuid = 0
curthread = 0xffffff003d807000: pid 24 "irq1: atkbd0"
curpcb = 0xffffffffa5318d10
fpcurthread = none
idlethread = 0xffffff003db58980: pid 11 "idle: cpu0"
I had to manually type this all in as I don't have a null modem
available where I am. Please Cc me as I'm not subscribed to the list.
Regards
Gardner
------------------------------
Message: 4
Date: Mon, 01 Jan 2007 18:17:09 +0000
From: wsk <wsk at gddsn.org.cn>
Subject: mpt0 timed out
To: stable at freebsd.org, current at freebsd.org
Message-ID: <45995025.8000103 at gddsn.org.cn>
Content-Type: text/plain; charset=GB2312
hi, scsi card connected to a disk array.and get follow error after less
than 10 days
thanks in advance.
mpt0: <LSILogic 1030 Ultra4 Adapter> port 0xcc00-0xccff mem
0xfcef0000-0xfceffff
f,0xfcee0000-0xfceeffff irq 24 at device 3.0 on pci2
mpt0: [GIANT-LOCKED]
mpt0: MPI Version=1.2.12.0
Trying to mount root from ufs:/dev/da1s1a
mpt0: request 0xc4bf9fd0:2297 timed out for ccb 0xc6d20000 (req->ccb
0xc6d20000)
mpt0: attempting to abort req 0xc4bf9fd0:2297 function 0
mpt0: completing timedout/aborted req 0xc4bf9fd0:2297
mpt0: abort of req 0xc4bf9fd0:0 completed
mpt0: request 0xc4bfa450:2321 timed out for ccb 0xc6d17c00 (req->ccb
0xc6d17c00)
mpt0: attempting to abort req 0xc4bfa450:2321 function 0
mpt0: completing timedout/aborted req 0xc4bfa450:2321
mpt0: abort of req 0xc4bfa450:0 completed
mpt0: request 0xc4bfa4e0:2324 timed out for ccb 0xc4bf2000 (req->ccb
0xc4bf2000)
mpt0: attempting to abort req 0xc4bfa4e0:2324 function 0
mpt0: completing timedout/aborted req 0xc4bfa4e0:2324
mpt0: abort of req 0xc4bfa4e0:0 completed
mpt0: request 0xc4bfa660:2332 timed out for ccb 0xc6d19000 (req->ccb
0xc6d19000)
mpt0: attempting to abort req 0xc4bfa660:2332 function 0
mpt0: completing timedout/aborted req 0xc4bfa660:2332
mpt0: abort of req 0xc4bfa660:0 completed
mpt0: request 0xc4bfa780:2338 timed out for ccb 0xc6d0e800 (req->ccb
0xc6d0e800)
mpt0: attempting to abort req 0xc4bfa780:2338 function 0
mpt0: completing timedout/aborted req 0xc4bfa780:2338
mpt0: abort of req 0xc4bfa780:0 completed
mpt0: request 0xc4bfa810:2342 timed out for ccb 0xc6d20000 (req->ccb
0xc6d20000)
mpt0: attempting to abort req 0xc4bfa810:2342 function 0
mpt0: completing timedout/aborted req 0xc4bfa810:2342
mpt0: abort of req 0xc4bfa810:0 completed
mpt0: request 0xc4bfa840:2344 timed out for ccb 0xc6d17c00 (req->ccb
0xc6d17c00)
mpt0: attempting to abort req 0xc4bfa840:2344 function 0
mpt0: completing timedout/aborted req 0xc4bfa840:2344
mpt0: abort of req 0xc4bfa840:0 completed
mpt0: request 0xc4bfa870:2346 timed out for ccb 0xc4bf2000 (req->ccb
0xc4bf2000)
mpt0: attempting to abort req 0xc4bfa870:2346 function 0
mpt0: completing timedout/aborted req 0xc4bfa870:2346
mpt0: abort of req 0xc4bfa870:0 completed
mpt0: request 0xc4bfa900:2350 timed out for ccb 0xc6d19000 (req->ccb
0xc6d19000)
mpt0: attempting to abort req 0xc4bfa900:2350 function 0
mpt0: completing timedout/aborted req 0xc4bfa900:2350
mpt0: abort of req 0xc4bfa900:0 completed
mpt0: request 0xc4bfa930:2352 timed out for ccb 0xc6d0e800 (req->ccb
0xc6d0e800)
mpt0: attempting to abort req 0xc4bfa930:2352 function 0
mpt0: completing timedout/aborted req 0xc4bfa930:2352
mpt0: abort of req 0xc4bfa930:0 completed
mpt0: request 0xc4bfa9c0:2356 timed out for ccb 0xc6d20000 (req->ccb
0xc6d20000)
mpt0: attempting to abort req 0xc4bfa9c0:2356 function 0
mpt0: completing timedout/aborted req 0xc4bfa9c0:2356
mpt0: abort of req 0xc4bfa9c0:0 completed
mpt0: request 0xc4bfa9f0:2358 timed out for ccb 0xc6d17c00 (req->ccb
0xc6d17c00)
mpt0: attempting to abort req 0xc4bfa9f0:2358 function 0
mpt0: completing timedout/aborted req 0xc4bfa9f0:2358
mpt0: abort of req 0xc4bfa9f0:0 completed
mpt0: request 0xc4bfaa20:2360 timed out for ccb 0xc4bf2000 (req->ccb
0xc4bf2000)
mpt0: attempting to abort req 0xc4bfaa20:2360 function 0
mpt0: completing timedout/aborted req 0xc4bfaa20:2360
mpt0: abort of req 0xc4bfaa20:0 completed
mpt0: request 0xc4bfaab0:2364 timed out for ccb 0xc6d19000 (req->ccb
0xc6d19000)
mpt0: attempting to abort req 0xc4bfaab0:2364 function 0
mpt0: completing timedout/aborted req 0xc4bfaab0:2364
mpt0: abort of req 0xc4bfaab0:0 completed
mpt0: request 0xc4bfaae0:2366 timed out for ccb 0xc6d0e800 (req->ccb
0xc6d0e800)
mpt0: attempting to abort req 0xc4bfaae0:2366 function 0
mpt0: completing timedout/aborted req 0xc4bfaae0:2366
mpt0: abort of req 0xc4bfaae0:0 completed
mpt0: request 0xc4bfab70:2370 timed out for ccb 0xc6d20000 (req->ccb
0xc6d20000)
mpt0: attempting to abort req 0xc4bfab70:2370 function 0
mpt0: completing timedout/aborted req 0xc4bfab70:2370
mpt0: abort of req 0xc4bfab70:0 completed
mpt0: request 0xc4bfaba0:2372 timed out for ccb 0xc6d17c00 (req->ccb
0xc6d17c00)
mpt0: attempting to abort req 0xc4bfaba0:2372 function 0
mpt0: completing timedout/aborted req 0xc4bfaba0:2372
mpt0: abort of req 0xc4bfaba0:0 completed
mpt0: request 0xc4bfabd0:2374 timed out for ccb 0xc4bf2000 (req->ccb
0xc4bf2000)
mpt0: attempting to abort req 0xc4bfabd0:2374 function 0
mpt0: completing timedout/aborted req 0xc4bfabd0:2374
mpt0: abort of req 0xc4bfabd0:0 completed
mpt0: request 0xc4bfac60:2378 timed out for ccb 0xc6d19000 (req->ccb
0xc6d19000)
mpt0: attempting to abort req 0xc4bfac60:2378 function 0
mpt0: completing timedout/aborted req 0xc4bfac60:2378
mpt0: abort of req 0xc4bfac60:0 completed
mpt0: request 0xc4bfac90:2380 timed out for ccb 0xc6d0e800 (req->ccb
0xc6d0e800)
mpt0: attempting to abort req 0xc4bfac90:2380 function 0
mpt0: completing timedout/aborted req 0xc4bfac90:2380
mpt0: abort of req 0xc4bfac90:0 completed
mpt0: request 0xc4bfad20:2384 timed out for ccb 0xc6d20000 (req->ccb
0xc6d20000)
mpt0: attempting to abort req 0xc4bfad20:2384 function 0
mpt0: completing timedout/aborted req 0xc4bfad20:2384
g_vfs_done():da0s1d[WRITE(offset=641334870016, length=131072)]error = 5
mpt0: abort of req 0xc4bfad20:0 completed
mpt0: request 0xc4bfad50:2386 timed out for ccb 0xc6d17c00 (req->ccb
0xc6d17c00)
mpt0: attempting to abort req 0xc4bfad50:2386 function 0
mpt0: completing timedout/aborted req 0xc4bfad50:2386
g_vfs_done():da0s1d[WRITE(offset=641332428800, length=16384)]error = 5
mpt0: abort of req 0xc4bfad50:0 completed
mpt0: request 0xc4bfad80:2388 timed out for ccb 0xc4bf2000 (req->ccb
0xc4bf2000)
mpt0: attempting to abort req 0xc4bfad80:2388 function 0
mpt0: completing timedout/aborted req 0xc4bfad80:2388
g_vfs_done():da0s1d[WRITE(offset=641336442880, length=32768)]error = 5
mpt0: abort of req 0xc4bfad80:0 completed
mpt0: request 0xc4bfae10:2392 timed out for ccb 0xc6d19000 (req->ccb
0xc6d19000)
mpt0: attempting to abort req 0xc4bfae10:2392 function 0
mpt0: completing timedout/aborted req 0xc4bfae10:2392
g_vfs_done():da0s1d[WRITE(offset=641279819776, length=16384)]error = 5
mpt0: abort of req 0xc4bfae10:0 completed
mpt0: request 0xc4bfae40:2394 timed out for ccb 0xc6d0e800 (req->ccb
0xc6d0e800)
mpt0: attempting to abort req 0xc4bfae40:2394 function 0
mpt0: completing timedout/aborted req 0xc4bfae40:2394
g_vfs_done():da0s1d[WRITE(offset=641332477952, length=16384)]error = 5
mpt0: abort of req 0xc4bfae40:0 completed
mpt0: request 0xc4bfaed0:2399 timed out for ccb 0xc6d17c00 (req->ccb
0xc6d17c00)
mpt0: attempting to abort req 0xc4bfaed0:2399 function 0
mpt0: completing timedout/aborted req 0xc4bfaed0:2399
mpt0: abort of req 0xc4bfaed0:0 completed
mpt0: request 0xc4bfaf60:2405 timed out for ccb 0xc6d0e800 (req->ccb
0xc6d0e800)
mpt0: request 0xc4bfaf90:2406 timed out for ccb 0xc6d20000 (req->ccb
0xc6d20000)
mpt0: request 0xc4bfafc0:2407 timed out for ccb 0xc4c74000 (req->ccb
0xc4c74000)
mpt0: request 0xc4bfaff0:2408 timed out for ccb 0xc4bf2000 (req->ccb
0xc4bf2000)
mpt0: attempting to abort req 0xc4bfaf60:2405 function 0
mpt0: completing timedout/aborted req 0xc4bfaf60:2405
mpt0: abort of req 0xc4bfaf60:0 completed
mpt0: attempting to abort req 0xc4bfaf90:2406 function 0
mpt0: completing timedout/aborted req 0xc4bfaf90:2406
mpt0: abort of req 0xc4bfaf90:0 completed
mpt0: attempting to abort req 0xc4bfafc0:2407 function 0
mpt0: completing timedout/aborted req 0xc4bfafc0:2407
mpt0: abort of req 0xc4bfafc0:0 completed
mpt0: attempting to abort req 0xc4bfaff0:2408 function 0
mpt0: completing timedout/aborted req 0xc4bfaff0:2408
mpt0: abort of req 0xc4bfaff0:0 completed
mpt0: request 0xc4bfb020:2409 timed out for ccb 0xc6d1e400 (req->ccb
0xc6d1e400)
mpt0: attempting to abort req 0xc4bfb020:2409 function 0
mpt0: completing timedout/aborted req 0xc4bfb020:2409
mpt0: abort of req 0xc4bfb020:0 completed
mpt0: request 0xc4bfb0b0:2412 timed out for ccb 0xc6d18000 (req->ccb
0xc6d18000)
mpt0: attempting to abort req 0xc4bfb0b0:2412 function 0
mpt0: completing timedout/aborted req 0xc4bfb0b0:2412
mpt0: abort of req 0xc4bfb0b0:0 completed
mpt0: request 0xc4bfb1d0:2419 timed out for ccb 0xc6d17c00 (req->ccb
0xc6d17c00)
mpt0: attempting to abort req 0xc4bfb1d0:2419 function 0
mpt0: completing timedout/aborted req 0xc4bfb1d0:2419
mpt0: abort of req 0xc4bfb1d0:0 completed
------------------------------
Message: 5
Date: Mon, 1 Jan 2007 11:31:21 +0000
From: Chris <chrcoluk at gmail.com>
Subject: Re: 6.2-PRE: Fatal Trap?
To: "Ivan Voras" <ivoras at fer.hr>
Cc: freebsd-stable at freebsd.org
Message-ID:
<3aaaa3a0701010331u72d70e90p714a0171fe9f292a at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 30/12/06, Ivan Voras <ivoras at fer.hr> wrote:
> Karol Kwiatkowski wrote:
>
> > This works: FreeBSD 6.2-PRERELEASE #0: Thu Dec 14 11:34:36 CET 2006
> > This doesn't: FreeBSD 6.2-PRERELEASE #0: Sat Dec 30 11:27:11 CET 2006
>
> > I'm not sure it that's all that matters, I can supply more information
> > if needed.
>
> Yes, you'll need to send at least a kernel stack backtrace. See here:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html
>
> Get it to start the debugger on panic and post the backtrace (bt).
>
>
>
>
Is it possible to make it auto run debugger, then auto run backtrace
then dump the output to disk so people who have no local access can
get backtraces?
Chris
------------------------------
_______________________________________________
freebsd-stable at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
End of freebsd-stable Digest, Vol 188, Issue 10
***********************************************
More information about the freebsd-stable
mailing list