From owner-freebsd-isdn@FreeBSD.ORG Sat Jun 18 09:28:02 2005 Return-Path: X-Original-To: freebsd-isdn@freebsd.org Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBD9816A41C for ; Sat, 18 Jun 2005 09:28:02 +0000 (GMT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from mail2.ewetel.de (mail2.ewetel.de [212.6.122.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E2DF43D4C for ; Sat, 18 Jun 2005 09:28:02 +0000 (GMT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from kalak.lemur.nord.de (dialin-80-228-51-002.ewe-ip-backbone.de [80.228.51.2]) by mail2.ewetel.de (8.12.1/8.12.9) with ESMTP id j5I9RwmY013315; Sat, 18 Jun 2005 11:27:58 +0200 (MEST) Received: from [192.168.2.4] (lullog.lemur.nord.de [192.168.2.4]) by kalak.lemur.nord.de (8.12.3/8.12.3) with ESMTP id j5I8msF8023354; Sat, 18 Jun 2005 10:48:58 +0200 (CEST) (envelope-from Thomas.Wintergerst@nord-com.net) Message-ID: <42B3DFF6.3070705@nord-com.net> Date: Sat, 18 Jun 2005 10:48:54 +0200 From: Thomas Wintergerst User-Agent: Mozilla Thunderbird 0.9 (X11/20041220) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cian Hughes References: <7112CBFA-724E-4846-AA2E-1EFBC4B49CE2@cian.ws> <475744B9-48D9-474F-96E9-4C48869FD970@cian.ws> In-Reply-To: <475744B9-48D9-474F-96E9-4C48869FD970@cian.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-CheckCompat: OK Cc: freebsd-isdn@freebsd.org Subject: Re: Problem with C4B on FreeBSD-Stable X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: twinterg@gmx.de List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jun 2005 09:28:02 -0000 Hi Cian, Could you provide a stack backtrace for the panics? Maybe this could shed some light on where the crash occurs. Is this still 5.4-RELEASE or is it newer? Single- or multi-CPU? Cian Hughes wrote: > (I know I shouldn't reply to my own posts) > [...] > ______ > Now we kernel panic when running capitest: > > # capitest -s -tx 014900248 > capidev: T capidev_open: CAPI device is beeing opened > capidev: D capidev_open: new temp fd 4 allocated > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x6c > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc050b6d1 > stack pointer = 0x10:0xc7dddbd8 > frame pointer = 0x10:0xc7dddbdc > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 558 (capitest) > trap number = 12 > panic: page fault > Uptime: 54s > Cannot dump. No dump device defined. > Automatic reboot in 15 seconds - press a key on the console to abort > > and again when starting asterisk: > > oppy:root:/usr/local/etc/asterisk:0# capidev: T capidev_open: CAPI > device is beeing opened > capidev: D capidev_open: new temp fd 25 allocated > capidev: D capidev_ioctl: CAPI_GET_PROFILE: Result 0x0000, controller 0 > capidev: D capidev_close: Application not registered, only close file > descriptor > capidev: T capidev_open: CAPI device is beeing opened > capidev: D capidev_open: new temp fd 25 allocated > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x6c > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc050b6d1 > stack pointer = 0x10:0xcc445bd8 > frame pointer = 0x10:0xcc445bdc > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 599 (asterisk) > trap number = 12 > panic: page fault > Uptime: 5m14s > Cannot dump. No dump device defined. > > Regards, Cian > [...] -- Gruss, Thomas Wintergerst