NetBSD Problem Report #50182

From www@NetBSD.org  Fri Aug 28 05:33:04 2015
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [149.20.53.66])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.netbsd.org", Issuer "Postmaster NetBSD.org" (verified OK))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 573EEA654F
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 28 Aug 2015 05:33:04 +0000 (UTC)
Message-Id: <20150828053303.21D49A6554@mollari.NetBSD.org>
Date: Fri, 28 Aug 2015 05:33:03 +0000 (UTC)
From: swiftgriggs@gmail.com
Reply-To: swiftgriggs@gmail.com
To: gnats-bugs@NetBSD.org
Subject: Crash + core possibly related to USB KVM switching or g910 keyboard
X-Send-Pr-Version: www-1.0

>Number:         50182
>Category:       kern
>Synopsis:       Crash + core possibly related to USB KVM switching or g910 keyboard
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 28 05:35:00 +0000 2015
>Last-Modified:  Mon Nov 02 16:05:00 +0000 2015
>Originator:     Swift Griggs
>Release:        7.0_RC2
>Organization:
>Environment:
NetBSD oreo 7.0_RC2 NetBSD 7.0_RC2 (GENERIC.201507240251Z) i386
>Description:
I switch back and forth with my startech 2-port DVI + USB KVM switch. Once I've switched "away" and then "back" I often lose control of the system (though video stick around sometimes - frozen). Once I reboot I get a core in /var/crash. I thought you folks might want to take a look.

Let me know how to send the core files. 
>How-To-Repeat:
Switch with a Startech KVM using a Logitech G910 keyboard (a strange expensive beast of a keyboard with many unrecognized keycodes for special keys)
>Fix:
Reset switch.

>Audit-Trail:
From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/50182: Crash + core possibly related to USB KVM switching
 or g910 keyboard
Date: Sun, 6 Sep 2015 00:24:33 +0000

 On Fri, Aug 28, 2015 at 05:35:00AM +0000, swiftgriggs@gmail.com wrote:
  > I switch back and forth with my startech 2-port DVI + USB KVM
  > switch. Once I've switched "away" and then "back" I often lose
  > control of the system (though video stick around sometimes -
  > frozen). Once I reboot I get a core in /var/crash. I thought you
  > folks might want to take a look.
  > 
  > Let me know how to send the core files. 

 Sending the crash dumps is expensive (they're large) and probably not
 worthwhile. Instead, the best bet is probably for you to run gdb on
 one and tell us what comes up.

 The method for doing that is as follows (if anyone seeing this mail
 wants to expand/clarify/correct please do):

  - first, uncompress the core file as gdb can't read them while
 compressed:
 	# cd /var/crash
 	# gunzip netbsd.6.core.gz   (or whichever one seems good)

 If you don't have space for it in /var/crash you can copy/move it
 somewhere else.

  - run gdb on /netbsd if it's the same kernel that crashed (I have
 found lately that the copy saved in /var/crash by savecore doesn't
 work, so if you've rebuilt the kernel or anything since you got the
 core speak up)
 	# gdb /netbsd

  - load the core and get a stack trace
 	(gdb) target kvm netbsd.6.core
 	   :
 	(gdb) backtrace

 Send us what gdb prints.

 This is the first step -- there may be other useful information
 available, but that will depend on what this turns up.

  > Switch with a Startech KVM using a Logitech G910 keyboard (a
  > strange expensive beast of a keyboard with many unrecognized
  > keycodes for special keys)

 It will probably also be helpful to send in the parts of dmesg.boot
 that pertain to this; or if you aren't sure, all of dmesg.boot.

 -- 
 David A. Holland
 dholland@netbsd.org

From: Swift Griggs <swiftgriggs@gmail.com>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/50182
Date: Mon, 2 Nov 2015 09:03:18 -0700 (MST)

 Here is more information:

 * It's still a problem with NetBSD 7.0 (i386 and AMD64 both seem to crash 
 but I only have the backtrace from i386).

 Here is the 'dmesg' from the crash:

 uvm_fault(0xc0ff0d00, 0x62756000, 1) -> 0xe
 fatal page fault in supervisor mode
 trap type 6 code 0 eip c09f2e0f cs 8 eflags 210246 cr2 62756877 ilevel 0 
 esp c4bf0324
 curlwp 0xc4b73d20 pid 0 lid 38 lowest kstack 0xdc1242c0
 panic: trap
 cpu0: Begin traceback...
 vpanic(c0dc7a1b,dc125e84,dc125f00,c096ad3a,c0dc7a1b,dc125f0c,dc125f0c,26,dc1242c0,210246) 
 at netbsd:vpanic+0x121
 snprintf(c0dc7a1b,dc125f0c,dc125f0c,26,dc1242c0,210246,62756877,0,c4bf0324,c0fa6d20) 
 at netbsd:snprintf
 trap_tss() at netbsd:trap_tss
 --- trap via task gate ---
 c4bf0324:
 cpu0: End traceback...

 dumping to dev 0,1 offset 2968
 dump


 Here is the backtrace from the core:

 # gdb netbsd.1
 ...
 (gdb) target kvm netbsd.1.core
 0xc06cdf06 in cpu_reboot ()
 (gdb) bt
 #0  0xc06cdf06 in cpu_reboot ()
 #1  0xc0918752 in vpanic ()
 #2  0xc09187dc in panic ()
 #3  0xc096ad3a in trap ()
 #4  0xc010ce78 in alltraps ()
 #5  0xdc125f0c in end ()
 #6  0xc0650010 in execve_runproc ()
 #7  0xc09ee48c in usb_task_thread ()
 #8  0xc0100321 in lwp_trampoline ()

 and another from another core:

 (gdb) bt
 #0  0xc06cdf06 in cpu_reboot ()
 #1  0xc0918752 in vpanic ()
 #2  0xc09187dc in panic ()
 #3  0xc096ad3a in trap ()
 #4  0xc010ce78 in alltraps ()
 #5  0xdd99fbe0 in ?? ()
 #6  0xc0300082 in ehci_allocm ()
 #7  0xc09f2123 in usbd_transfer ()
 #8  0xc09f248c in usbd_open_pipe_intr ()
 #9  0xc09c525c in uhidev_open ()
 #10 0xc09e7ec4 in ums_enable ()
 #11 0xc0a6965a in wsmuxopen ()
 #12 0xc090b40d in cdev_open ()
 #13 0xc08f4125 in spec_open ()
 #14 0xc0a474e4 in VOP_OPEN ()
 #15 0xc0a31d04 in vn_open ()
 #16 0xc0a2b23d in do_open ()
 #17 0xc0a2b37c in do_sys_openat ()
 #18 0xc0a2b442 in sys_open ()
 #19 0xc093ccff in syscall ()
 #20 0xc010055d in Xsyscall ()
 #21 0xdd99ffa8 in ?? ()
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)

 Thanks!
    Swift

Home	PR Database Search