From nobody@FreeBSD.org  Sat Nov 20 17:22:51 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 74B7716A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 20 Nov 2004 17:22:51 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6353E43D1D
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 20 Nov 2004 17:22:51 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id iAKHMpsW089673
	for <freebsd-gnats-submit@FreeBSD.org>; Sat, 20 Nov 2004 17:22:51 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id iAKHMpQc089672;
	Sat, 20 Nov 2004 17:22:51 GMT
	(envelope-from nobody)
Message-Id: <200411201722.iAKHMpQc089672@www.freebsd.org>
Date: Sat, 20 Nov 2004 17:22:51 GMT
From: Normal User <freebsd@falx.port5.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Fatal trap 12: page fault while in kernel mode
X-Send-Pr-Version: www-2.3

>Number:         74171
>Category:       ports
>Synopsis:       [panic] comms/ltmdm: Fatal trap 12: page fault while in kernel mode
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Nov 20 17:30:25 GMT 2004
>Closed-Date:    Tue Dec 27 23:32:49 GMT 2005
>Last-Modified:  Tue Dec 27 23:32:49 GMT 2005
>Originator:     Normal User
>Release:        5.3-RELEASE
>Organization:
>Environment:
FreeBSD  5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov  5 04:19:18 UTC 2004     root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
My test machine has an internal modem which uses the comms/ltmdm driver
(Lucent WinModem), whenever someone calls me the system inmediately crashes
badly. I've been tracking 4-STABLE in this machine for years without any
problem. I did a fresh install of 5.3-RELEASE last week.

The error I receive is:

Fatal trap 12: page fault while in kernel mode
fault virtual address  = 0x138
fault code             = supervisor read, page not present
instruction pointer    = 0x8:0xc183300d
stack pointer          = 0x10:0xcc721c80
frame pointer          = 0x10:0xcc721c90
code segment           = base 0x0, limit 0xfffff, type 0x1b
                       = DPL0, pres1, def32 1, gran 1
procesor eflags        = resume, IOPL = 0
current process        = 35 (swi5: tty:ltmdm++)
trap number            = 12
panic: page fault
Uptime: 3h9m23s

dmesg reports

ltmdm0: <Lucent Winmodem> port 0xe800-0xe8ff,0xec00-0xec07 mem 0xdfffff00-0xdfffffff irq 19 at device 8.0 on pci0
ltmdm0: [GIANT-LOCKED]
ltmdm0: type Virtual 16550A


>How-To-Repeat:
      just dial my phone number...
>Fix:

>Release-Note:
>Audit-Trail:

From: Robert Watson <rwatson@FreeBSD.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: misc/74171: Fatal trap 12: page fault while in kernel mode
Date: Mon, 3 Jan 2005 12:17:35 +0000 (GMT)

 On Sat, 20 Nov 2004, Normal User wrote:
 
 > Fatal trap 12: page fault while in kernel mode
 > fault virtual address  = 0x138
 > fault code             = supervisor read, page not present
 > instruction pointer    = 0x8:0xc183300d
 > stack pointer          = 0x10:0xcc721c80
 > frame pointer          = 0x10:0xcc721c90
 > code segment           = base 0x0, limit 0xfffff, type 0x1b
 >                        = DPL0, pres1, def32 1, gran 1
 > procesor eflags        = resume, IOPL = 0
 > current process        = 35 (swi5: tty:ltmdm++)
 > trap number            = 12
 > panic: page fault
 > Uptime: 3h9m23s
 
 This is a NULL pointer dereference in the kernel or a loaded kernel
 module.  Given that it's in the swi for ltmdm, it's likely a bug in the
 ltmdm driver, perhaps due to changes in the kernel that the driver has not
 been updated for.  For debugging purposes, it would be useful to have a
 DDB stack trace in the PR.  Could you compile your kernel with "options
 DDB", reproduce the panic, and use the "trace" command to generate a stack
 trace?  If performed with a serial console, you won't need to do a manual
 copy-and-paste.  Alternatively, you could build a kernel with debugging
 symbols and use gdb on a core dump, but the DDB trace is usually usefully
 concise.
 
 Thanks!
 
 Robert N M Watson
 
 
 > 
 > dmesg reports
 > 
 > ltmdm0: <Lucent Winmodem> port 0xe800-0xe8ff,0xec00-0xec07 mem 0xdfffff00-0xdfffffff irq 19 at device 8.0 on pci0
 > ltmdm0: [GIANT-LOCKED]
 > ltmdm0: type Virtual 16550A
 > 
 > 
 > >How-To-Repeat:
 >       just dial my phone number...
 > >Fix:
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 > _______________________________________________
 > freebsd-bugs@freebsd.org mailing list
 > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"
 > 
 
State-Changed-From-To: open->feedback 
State-Changed-By: linimon 
State-Changed-When: Thu Oct 27 22:53:15 GMT 2005 
State-Changed-Why:  
Even though this is a kernel panic, it is triggered by a bug in a driver 
which is in ports, so possibly attempt to recategorize this as a ports bug. 

Also note that this PR should have been set to 'feedback' some time ago. 


Responsible-Changed-From-To: freebsd-bugs->freebsd-ports-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Thu Oct 27 22:53:15 GMT 2005 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=74171 
State-Changed-From-To: feedback->closed 
State-Changed-By: pav 
State-Changed-When: Tue Dec 27 23:32:35 UTC 2005 
State-Changed-Why:  
Feedback timeout (backtrace was never received) 

http://www.freebsd.org/cgi/query-pr.cgi?pr=74171 
>Unformatted:
