NetBSD Problem Report #52204

From www@NetBSD.org  Sun Apr 30 16:25:20 2017
Return-Path: <www@NetBSD.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(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 E9AB57A272
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 30 Apr 2017 16:25:20 +0000 (UTC)
Message-Id: <20170430162519.CDAED7A2B8@mollari.NetBSD.org>
Date: Sun, 30 Apr 2017 16:25:19 +0000 (UTC)
From: miod@online.fr
Reply-To: miod@online.fr
To: gnats-bugs@NetBSD.org
Subject: NeXTstation keyboard is no longer responsive under NetBSD 7.1
X-Send-Pr-Version: www-1.0

>Number:         52204
>Category:       port-next68k
>Synopsis:       NeXTstation keyboard is no longer responsive under NetBSD 7.1
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    tsutsui
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Apr 30 16:30:00 +0000 2017
>Closed-Date:    Sun Feb 05 12:37:12 +0000 2023
>Last-Modified:  Sun Feb 05 12:37:12 +0000 2023
>Originator:     Miod Vallat
>Release:        7.1
>Organization:
>Environment:
>Description:
Non-turbo NeXTstation slab (68040, 25MHz) with non-ADB keyboard.

Keyboard works in NetBSD 1.6 to 5.0. Booting either 7.0.2 or 7.1, the kernel boots multiuser, network works, but key presses seem to be ignored.
>How-To-Repeat:
Boot NetBSD 7.0.2 or 7.1 on slab.
>Fix:

>Release-Note:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-next68k/52204: NeXTstation keyboard is no longer responsive
 under NetBSD 7.1
Date: Mon, 1 May 2017 12:00:57 +0200

 Could you please boot a 7.x (or even -current) kernel (kernel is enough, no
 need to do a full install) and provide dmesg and vmstat -i output (after
 trying to type something on the keyboard)?

 Thanks,

 Martin

From: Miod Vallat <miod@online.fr>
To: gnats-bugs@NetBSD.org
Cc: port-next68k-maintainer@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org
Subject: Re: port-next68k/52204: NeXTstation keyboard is no longer responsive
 under NetBSD 7.1
Date: Mon, 1 May 2017 12:12:50 +0000

 >  Could you please boot a 7.x (or even -current) kernel (kernel is enough, no
 >  need to do a full install) and provide dmesg and vmstat -i output (after
 >  trying to type something on the keyboard)?

 The problem is that all device interrupts on NeXT are on level 3, and
 the next68k port does not have per-device interrupt counters, but only
 per-level interrupt counters.

 There is no difference in dmesg between 5.0 and 7.1, except for the
 few virtual addresses printed. A dmesg of 5.0.2 is:

 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
     2006, 2007, 2008, 2009
     The NetBSD Foundation, Inc.  All rights reserved.
 Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

 NetBSD 5.0.2 (GENERIC) #0: Sat Feb  6 20:21:38 UTC 2010
         builds@b8.netbsd.org:/home/builds/ab/netbsd-5-0-2-RELEASE/next68k/201002061851Z-obj/home/builds/ab/netbsd-5-0-2-RELEASE/src/sys/arch/next68k/compile/GENERIC
 NeXT/MC68040 CPU+MMU+FPU, 4k on-chip physical I/D caches
 total memory = 32760 KB
 avail memory = 28080 KB
 timecounter: Timecounters tick every 10.000 msec
 intrmask: 0x2e9800
 intrstat: 0x2e9000
 mainbus0 (root)
 intio0 at mainbus0
 esp0 at intio0 addr 0x2114000
 zsc0 at intio0 addr 0x3fa000
 zstty0 at zsc0 channel 0
 zstty1 at zsc0 channel 1
 nextdma0 at intio0 addr 0x2000010: channel 0 (scsi)
 nextdma1 at intio0 addr 0x2000110: channel 1 (enetx)
 nextdma2 at intio0 addr 0x2000150: channel 2 (enetr)
 xe0 at intio0 addr 0x2106000
 xe0: MAC address 00:00:0f:00:cd:e2
 xe0: using DMA channels nextdma1 nextdma2
 nextkbd0 at intio0 addr 0x200e000
 wskbd0 at nextkbd0 (mux ignored): console keyboard
 esp0: ESP100A, 20MHz, SCSI ID 7
 scsibus0 at esp0: 8 targets, 8 luns per target
 esp0: using DMA channel nextdma0
 nextdisplay0 at mainbus0: 1120 x 832, 2bpp
 wsdisplay0 at nextdisplay0 (kbdmux ignored): console (mono, vt100 emulation), using wskbd0
 timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
 Looks like a MCS1850 (new style) clock chip.
 scsibus0: waiting 2 seconds for devices to settle...
 boot device: xe0
 root on xe0
 nfs_boot: trying DHCP/BOOTP
 nfs_boot: DHCP next-server: 10.0.1.1
 nfs_boot: my_domain=gentiane.org
 nfs_boot: my_addr=10.0.1.144
 nfs_boot: my_mask=255.255.255.0
 nfs_boot: gateway=10.0.1.1
 root on 10.0.1.1:/netboot/pampeluze/root
 root file system type: nfs
 WARNING: preposterous TOD clock time
 WARNING: using filesystem time
 WARNING: CHECK AND RESET THE DATE!

Responsible-Changed-From-To: port-next68k-maintainer->tsutsui
Responsible-Changed-By: tsutsui@NetBSD.org
Responsible-Changed-When: Fri, 20 Jan 2023 20:51:34 +0000
Responsible-Changed-Why:
I have a candidate fix
 https://mail-index.netbsd.org/port-next68k/2023/01/20/msg000043.html


State-Changed-From-To: open->analyzed
State-Changed-By: tsutsui@NetBSD.org
State-Changed-When: Fri, 20 Jan 2023 20:51:34 +0000
State-Changed-Why:
Due to lack of constraints in bus_space_read_region_4(9) asm statements
nextkbd_read_data() in nextkbd.c was unintentionally optimized out
after this -Wuninitialized fix:
 http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/next68k/dev/nextkbd.c#rev1.15


State-Changed-From-To: analyzed->needs-pullups
State-Changed-By: tsutsui@NetBSD.org
State-Changed-When: Fri, 27 Jan 2023 19:20:44 +0000
State-Changed-Why:
Committed to HEAD, I'll send pullup request later.
 https://mail-index.netbsd.org/source-changes/2023/01/27/msg143027.html


State-Changed-From-To: needs-pullups->pending-pullups
State-Changed-By: tsutsui@NetBSD.org
State-Changed-When: Tue, 31 Jan 2023 16:33:16 +0000
State-Changed-Why:
[pullup-10 #63] [pullup-9 #1581]


State-Changed-From-To: pending-pullups->closed
State-Changed-By: tsutsui@NetBSD.org
State-Changed-When: Sun, 05 Feb 2023 12:37:12 +0000
State-Changed-Why:
Pulled up.


>Unformatted:

Home	PR Database Search