From owner-freebsd-bugs Sun Jan 21 14:33:42 2001 Delivered-To: freebsd-bugs@freebsd.org Received: from news.lucky.net (news.lucky.net [193.193.193.102]) by hub.freebsd.org (Postfix) with ESMTP id 3FD9137B698 for ; Sun, 21 Jan 2001 14:33:20 -0800 (PST) Received: (from mail@localhost) by news.lucky.net (8.Who.Cares/8.Who.Cares) id AMU18256 for freebsd-bugs@freebsd.org; Mon, 22 Jan 2001 00:33:17 +0200 (envelope-from news@news.ntu-kpi.kiev.ua) From: Andrey Simonenko To: freebsd-bugs@freebsd.org Subject: Re: kern/24511: keyboard lockups on boot Date: Mon, 22 Jan 2001 00:42:12 +0200 Organization: NTUU "KPI" Message-ID: References: <200101211939.f0LJd8T00579@ix.netcom.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: igloo.uran.net.ua 980115875 42577 10.0.1.184 (21 Jan 2001 22:24:35 GMT) X-Complaints-To: newsmaster@news.ntu-kpi.kiev.ua In-Reply-To: <200101211939.f0LJd8T00579@ix.netcom.com> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Do you hit Enter button during bootstraping to speed up bootstrap process? I have the same problems when I hit Enter button during bootstraping: system becomes locked. I'm not sure, because I don't remember exactly, but I wasn't able to telnet to locked system. If somebody try to fix this bug, take in consideration my additional information. On Sun, 21 Jan 2001 root@ix.netcom.com wrote: > > >Number: 24511 > >Category: kern > >Synopsis: keyboard lockup on boot (about 1/3 of the time) > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Sun Jan 21 12:00:01 PST 2001 > >Closed-Date: > >Last-Modified: > >Originator: Charlie & > >Release: FreeBSD 4.2-STABLE i386 > >Organization: > home user > >Environment: > > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-STABLE #2: Mon Dec 18 20:32:49 PST 2000 > root@bradbsd:/usr/src/sys/compile/BRAD > Timecounter "i8254" frequency 1193182 Hz > CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 > Features=0x8001bf > AMD Features=0x80000800 > real memory = 134217728 (131072K bytes) > config> di sn0 > No such device: sn0 > Invalid command or syntax. Type `?' for help. > config> di lnc0 > No such device: lnc0 > Invalid command or syntax. Type `?' for help. > config> di le0 > No such device: le0 > Invalid command or syntax. Type `?' for help. > config> di ie0 > No such device: ie0 > Invalid command or syntax. Type `?' for help. > config> di fe0 > No such device: fe0 > Invalid command or syntax. Type `?' for help. > config> di cs0 > No such device: cs0 > Invalid command or syntax. Type `?' for help. > config> di bt0 > No such device: bt0 > Invalid command or syntax. Type `?' for help. > config> di aic0 > No such device: aic0 > Invalid command or syntax. Type `?' for help. > config> di aha0 > No such device: aha0 > Invalid command or syntax. Type `?' for help. > config> di adv0 > No such device: adv0 > Invalid command or syntax. Type `?' for help. > config> q > avail memory = 127365120 (124380K bytes) > Preloaded elf kernel "kernel" at 0xc0349000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc034909c. > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at 0.0 irq 11 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xe000-0xe00f at device 7.1 on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > chip1: at device 7.3 on pci0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > ed0 at port 0x280-0x29f iomem 0xd8000 irq 10 on isa0 > ed0: address 00:40:33:d0:f7:a1, type NE2000 (16 bit) > IP Filter: v3.4.8 initialized. Default = pass all, Logging = enabled > ad0: 8010MB [16276/16/63] at ata0-master UDMA33 > acd0: CDROM at ata0-slave using PIO4 > Mounting root from ufs:/dev/ad0s3a > WARNING: / was not properly dismounted > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout tag=0 serv=0 - resetting > ata0: resetting devices .. done > ad0: WRITE command timeout tag=0 serv=0 - resetting > ad0: trying fallback to PIO mode > ata0: resetting devices .. done > sio0: 1 more silo overflow (total 1) > >Description: > > About 1/3 of the time, my FreeBSD machine keyboard locks up at boot > time. The system itself continue to work and boot normally, but the > keyboard just won't work. Since this is a home machine, this is an > annoying problem. > > NOTE: in the past, this machine has run Linux 2.0/2.2, NetBSD 1.4, and > FreeBSD 3.X. This problem began with my 4.1.1 install and continues with > 4.2 (as of December 18) as well. > > >How-To-Repeat: > > If I reboot 3 or 4 times, this will happen once. > > >Fix: > > None really. . .just hit the reset button. NOTE: I would cheerfully > test patches that resolve this problem. > > >Release-Note: > >Audit-Trail: > >Unformatted: > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message