From owner-freebsd-bugs Sun Jan 27 13:10:18 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2BD6E37B41B for ; Sun, 27 Jan 2002 13:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0RLA1321135; Sun, 27 Jan 2002 13:10:01 -0800 (PST) (envelope-from gnats) Received: from h33.erkki.ton.tut.fi (h33.erkki.ton.tut.fi [193.166.84.86]) by hub.freebsd.org (Postfix) with ESMTP id 9C30537B400 for ; Sun, 27 Jan 2002 13:02:39 -0800 (PST) Received: from gpi.ru (chu@localhost [127.0.0.1]) by h33.erkki.ton.tut.fi (8.11.6/8.11.6) with ESMTP id g0RL2XS81433 for ; Sun, 27 Jan 2002 23:02:37 +0200 (EET) (envelope-from chu@gpi.ru) Message-Id: <3C546AE8.C6EAEE60@gpi.ru> Date: Sun, 27 Jan 2002 23:02:32 +0200 From: Vladimir Tchoukharev To: FreeBSD-gnats-submit@freebsd.org References: <200201271735.g0RHZlT48919@h33.erkki.ton.tut.fi> Subject: i386/34352: USB joystick causes panic on boot Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34352 >Category: i386 >Synopsis: USB joystick makes panic on boot >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Jan 27 13:10:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Vladimir Chukharev >Release: FreeBSD 4.4-STABLE i386 >Organization: >Environment: System: FreeBSD svak.h33.erkki.ton.tut.fi 4.4-STABLE FreeBSD 4.4-STABLE #1: Sat Dec 29 01:26:24 EET 2001 root@svak.h33.erkki.ton.tut.fi:/usr/src/sys/compile/H33 i386 >Description: I have a multi-OS box. Recently I get a Logitec WingMan Extrem Digital 3D joystick. It has a USB connector (actually with game/USB adaptor, but I do use the adaptor always). If this joystick is connected to the computer, FreeBSD cannot be booted, it panics with trap 12 while detecting the USB devices, then tries to reboot again. OK, here goes my dmesg whithout joystick connected. --------------- Copyright (c) 1992-2001 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.4-STABLE #1: Sat Dec 29 01:26:24 EET 2001 root@svak.h33.erkki.ton.tut.fi:/usr/src/sys/compile/H33 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (869.61-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 268369920 (262080K bytes) avail memory = 257556480 (251520K bytes) Preloaded elf kernel "kernel" at 0xc0388000. VESA: v3.0, 32768k memory, flags:0x1, mode table:0xc031b002 (1000022) VESA: NVidia netsmb_dev: loaded Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00fdd50 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 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 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd800-0xd81f irq 9 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered chip1: at device 7.4 on pci0 pcm0: port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 11 at device 7.5 on pci0 chip2: port 0xe800-0xe8ff irq 11 at device 7.6 on pci0 rl0: port 0xec00-0xecff mem 0xde000000-0xde0000ff irq 11 at device 10.0 on pci0 rl0: Ethernet address: 00:40:f4:24:d1:e9 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0:
Hi,
 
A = patch is attached=20 with this PR. Could somebody approve and commit the = fix.
 
Thanks.
Umesh.
 
------=_NextPart_000_0004_01C1A9F7.81726A60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:41:30 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 04FF537B404; Thu, 31 Jan 2002 01:41:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9eYH65181; Thu, 31 Jan 2002 01:40:34 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:40:34 -0800 (PST) From: Message-Id: <200201310940.g0V9eYH65181@freefall.freebsd.org> To: secure@SPAMFREEsysadmins.com, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/34476: Memory Overflow Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Memory Overflow State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 01:39:49 PST 2002 State-Changed-Why: Superceded by kern/34477. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34476 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:42: 7 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id ABD8B37B402 for ; Thu, 31 Jan 2002 01:42:05 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16WDm0-000KAx-00; Thu, 31 Jan 2002 11:44:52 +0200 From: Sheldon Hearn To: Aaron Surina Cc: bugs@freebsd.org Subject: Re: Advisory In-reply-to: Your message of "Wed, 30 Jan 2002 19:07:55 PST." Date: Thu, 31 Jan 2002 11:44:52 +0200 Message-ID: <77558.1012470292@axl.seasidesoftware.co.za> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 30 Jan 2002 19:07:55 PST, Aaron Surina wrote: > I am writing to confirm my Advisory was recieved. > Please reply, as I don't want to notify anyone before you have been > notified. You submitted two PRs about the same problem. They've both been closed, because FreeBSD already provides a mechanism for controlling the problem. In future, you may wish to discuss issues on the mailing lists before reporting them as problems. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:51:32 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 550AC37B404; Thu, 31 Jan 2002 01:51:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9n5r67137; Thu, 31 Jan 2002 01:49:05 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:49:05 -0800 (PST) From: Message-Id: <200201310949.g0V9n5r67137@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, green@FreeBSD.org Subject: Re: misc/34458: 4.5S/sshd forwarding problems Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: 4.5S/sshd forwarding problems Responsible-Changed-From-To: freebsd-bugs->green Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 01:48:51 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34458 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:51:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2C90437B405; Thu, 31 Jan 2002 01:51:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9mKT66970; Thu, 31 Jan 2002 01:48:20 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:48:20 -0800 (PST) From: Message-Id: <200201310948.g0V9mKT66970@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, sos@FreeBSD.org Subject: Re: misc/27893: can't burn audio cds on LG CD-RW CED-8083B Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: can't burn audio cds on LG CD-RW CED-8083B Responsible-Changed-From-To: freebsd-bugs->sos Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 01:48:09 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=27893 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:51:36 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2834937B417; Thu, 31 Jan 2002 01:51:30 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9gTi65552; Thu, 31 Jan 2002 01:42:29 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:42:29 -0800 (PST) From: Message-Id: <200201310942.g0V9gTi65552@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, ru@FreeBSD.org Subject: Re: kern/28713: NEW IPFW FEATURE [PATCHES]: Dynamic rule expiration lifetime fine-grained control Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: NEW IPFW FEATURE [PATCHES]: Dynamic rule expiration lifetime fine-grained control Responsible-Changed-From-To: freebsd-bugs->ru Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 01:42:16 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28713 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:51:37 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 165AE37B41B; Thu, 31 Jan 2002 01:51:31 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9iIU65801; Thu, 31 Jan 2002 01:44:18 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:44:18 -0800 (PST) From: Message-Id: <200201310944.g0V9iIU65801@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, obrien@FreeBSD.org Subject: Re: misc/34455: [PATCH] /sbin/dhclient-script overwrites /etc/resolv.conf without any relevant information Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] /sbin/dhclient-script overwrites /etc/resolv.conf without any relevant information Responsible-Changed-From-To: freebsd-bugs->obrien Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 01:44:07 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34455 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:51:41 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E3B2137B400; Thu, 31 Jan 2002 01:51:31 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9kmx66542; Thu, 31 Jan 2002 01:46:48 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:46:48 -0800 (PST) From: Message-Id: <200201310946.g0V9kmx66542@freefall.freebsd.org> To: dforste@qwest.net, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, sound@FreeBSD.org Subject: Re: kern/24141: emu10k1 has trouble playing non-44.1KHz samples (like 22KHz and 11KHz) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: emu10k1 has trouble playing non-44.1KHz samples (like 22KHz and 11KHz) State-Changed-From-To: feedback->open State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 01:46:11 PST 2002 State-Changed-Why: Problem persists in 4.5-RELEASE. Responsible-Changed-From-To: freebsd-bugs->sound Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 01:46:11 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24141 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 1:53:17 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from freebsd.dk (fw-rl0.freebsd.dk [212.242.86.114]) by hub.freebsd.org (Postfix) with ESMTP id CAAC037B404; Thu, 31 Jan 2002 01:53:14 -0800 (PST) Received: (from sos@localhost) by freebsd.dk (8.11.6/8.11.6) id g0V9rDg78003; Thu, 31 Jan 2002 10:53:13 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <200201310953.g0V9rDg78003@freebsd.dk> Subject: Re: misc/27893: can't burn audio cds on LG CD-RW CED-8083B In-Reply-To: <200201310948.g0V9mKT66970@freefall.freebsd.org> To: sheldonh@FreeBSD.org Date: Thu, 31 Jan 2002 10:53:13 +0100 (CET) Cc: freebsd-bugs@FreeBSD.org, sos@FreeBSD.org Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org It seems sheldonh@FreeBSD.org wrote: > Synopsis: can't burn audio cds on LG CD-RW CED-8083B > > Responsible-Changed-From-To: freebsd-bugs->sos > Responsible-Changed-By: sheldonh > Responsible-Changed-When: Thu Jan 31 01:48:09 PST 2002 > Responsible-Changed-Why: > Over to maintainer. Known problem on the LG devices, somebody needs to sit down and debug this problem, or send me a drive to experiment with... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2: 0: 5 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5CA9237B400 for ; Thu, 31 Jan 2002 02:00:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VA01R68857; Thu, 31 Jan 2002 02:00:01 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 02:00:01 -0800 (PST) Message-Id: <200201311000.g0VA01R68857@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/32420: syslogd accumulates "repeated" messages [...] Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/32420; it has been noted by GNATS. From: Sheldon Hearn To: bug-followup@freebsd.org Cc: Subject: Re: bin/32420: syslogd accumulates "repeated" messages [...] Date: Thu, 31 Jan 2002 11:55:11 +0200 On Wed, 30 Jan 2002 06:10:02 PST, Sheldon Hearn wrote: > Okay, please bug me before MFC'ing this, in case I find time to work on > a syslog.conf language extension to replace the new option. For the sake of the audit trail, Archie informs me that this has already been MFC'd. It's a real pretty the normal protocol of delaying MFC's wasn't followed, because this isn't the best solution, but the best solution would duplicate part of the new functionality, and warrant deprecation of the new feature. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2: 1:32 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 122DD37B419; Thu, 31 Jan 2002 02:01:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9rSx67788; Thu, 31 Jan 2002 01:53:28 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:53:28 -0800 (PST) From: Message-Id: <200201310953.g0V9rSx67788@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, sound@FreeBSD.org Subject: Re: misc/34427: SMP Kernel/ES1370 audio - hangs regularly Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: SMP Kernel/ES1370 audio - hangs regularly Responsible-Changed-From-To: freebsd-bugs->sound Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 01:53:14 PST 2002 Responsible-Changed-Why: Over to maintainer./ http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34427 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2: 1:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0CE0F37B404; Thu, 31 Jan 2002 02:01:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VA0xG69035; Thu, 31 Jan 2002 02:00:59 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 02:00:59 -0800 (PST) From: Message-Id: <200201311000.g0VA0xG69035@freefall.freebsd.org> To: jester@core.usrlib.org, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/34148: burncd(8) fails to write audio CDs Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: burncd(8) fails to write audio CDs State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 02:00:47 PST 2002 State-Changed-Why: Duplicate of misc/27893. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34148 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2: 1:34 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E717A37B41A; Thu, 31 Jan 2002 02:01:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0V9srd68040; Thu, 31 Jan 2002 01:54:53 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 01:54:53 -0800 (PST) From: Message-Id: <200201310954.g0V9srd68040@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, alfred@FreeBSD.org Subject: Re: kern/34463: COMPAT_SVR4 enabled kernel fails to build in latest -CURRENT Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: COMPAT_SVR4 enabled kernel fails to build in latest -CURRENT Responsible-Changed-From-To: freebsd-bugs->alfred Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 01:54:30 PST 2002 Responsible-Changed-Why: Over to the person responsible for the deltas suspected. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34463 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:10: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 65F3837B402 for ; Thu, 31 Jan 2002 02:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAA2Z73870; Thu, 31 Jan 2002 02:10:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 02:10:02 -0800 (PST) Message-Id: <200201311010.g0VAA2Z73870@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: gnu/13525: gcc fails load against library with both C++ and C modules Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR gnu/13525; it has been noted by GNATS. From: Sheldon Hearn To: iedowse@FreeBSD.org Cc: bug-followup@freebsd.org Subject: Re: gnu/13525: gcc fails load against library with both C++ and C modules Date: Thu, 31 Jan 2002 12:06:21 +0200 On Mon, 21 Jan 2002 17:12:18 PST, iedowse@FreeBSD.org wrote: > Synopsis: gcc fails load against library with both C++ and C modules > > State-Changed-From-To: feedback->open > State-Changed-By: iedowse > State-Changed-When: Mon Jan 21 17:11:47 PST 2002 > State-Changed-Why: > > Still a bug. As contributed software, it's very unlikely that this will be fixed unless it's reported to the GCC distribution maintainers. Has this been done? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:10:11 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9E79637B405 for ; Thu, 31 Jan 2002 02:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAA3T73877; Thu, 31 Jan 2002 02:10:03 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 02:10:03 -0800 (PST) Message-Id: <200201311010.g0VAA3T73877@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: gnu/13427: gdb reports wrong info Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR gnu/13427; it has been noted by GNATS. From: Sheldon Hearn To: Giorgos Keramidas Cc: iedowse@FreeBSD.org, bug-followup@freebsd.org Subject: Re: gnu/13427: gdb reports wrong info Date: Thu, 31 Jan 2002 12:09:59 +0200 On Tue, 22 Jan 2002 06:15:03 +0200, Giorgos Keramidas wrote: > > Does this problem still exist in more recent FreeBSD releases? > > Yes, on -CURRENT built on Jan 12 (I 've been lazy updating my CURRENT > box) and on a fresh installation of 4.4-RELEASE I did this afternoon, > the bug is still there. The information printed for the current stack > frame by gdb(1) is wrong, in programs compiled with -ggdb. > > I'm trying to find out why this happens on my machine, and I've > contacted Rexpixel (who frequents that > IRC channel) with today's tests and results. > > Can we leave this open for a while? The PR doesn't need to remain open if it's the same problem as PR 24132, which is open and assigned to a willling GDB maintainer. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:10:16 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 790D837B404 for ; Thu, 31 Jan 2002 02:10:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAA7h73896; Thu, 31 Jan 2002 02:10:07 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 02:10:07 -0800 (PST) Message-Id: <200201311010.g0VAA7h73896@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/34032 (was Re: port fails on one machine, not others) Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34032; it has been noted by GNATS. From: Sheldon Hearn To: "Dan Langille" Cc: bug-followup@freebsd.org, cjc@FreeBSD.org Subject: Re: bin/34032 (was Re: port fails on one machine, not others) Date: Thu, 31 Jan 2002 12:12:12 +0200 On Wed, 30 Jan 2002 06:50:02 PST, "Dan Langille" wrote: > > I think this is BSD make's friendly way of telling you that > > SENDMAIL_VERSION is not defined. There's a patch I wrote to make (1 line > > change) that *may* fix this. See bin/34032. > > > > Please followup to bin/43032 if this patch works for your problem. Thank > > you. > > Yes, that does fix it. I will submit a patch for security/drweb-sendmail Crist, are you going to commit these patches to make(1)? The poor beast is currently without a maintainer. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:20: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D8EA637B405 for ; Thu, 31 Jan 2002 02:20:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAK0s75509; Thu, 31 Jan 2002 02:20:00 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EF0E437B400 for ; Thu, 31 Jan 2002 02:12:30 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VACUS74363; Thu, 31 Jan 2002 02:12:30 -0800 (PST) (envelope-from nobody) Message-Id: <200201311012.g0VACUS74363@freefall.freebsd.org> Date: Thu, 31 Jan 2002 02:12:30 -0800 (PST) From: Matt Sykes To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: misc/34480: system hangs after killing xinit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34480 >Category: misc >Synopsis: system hangs after killing xinit >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 02:20:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Matt Sykes >Release: 4.5-stable >Organization: >Environment: FreeBSD xerxes 4.5-STABLE FreeBSD 4.5-STABLE #0: Wed Jan 30 23:28:22 GMT 2002 P2B-D Dual PentiumIII 550MHZ 512M RAM Matrox MGA Millenium SB Live! 3Com900 latest XFree86-4 from ports (XFree-4.1.0_12) latest XFree86-libraries from ports (XFree86-libraries-4.1.0_1) >Description: After killing xinit, switching back to your X console will leave you with a hung system. Keyboard is unresponsive, so you can't type into any xterms which happen to be open and you can't switch back to a text console. The mouse works. Why would I kill xinit? I have no idea. >How-To-Repeat: 1. startx 2. Ctl+Alt+F2 (some open console) 3. killall xinit 4. Ctl+Alt+F1 (back to your X console) 5. keyboard hung! 6. reluctantly power off your computer and hope for the best >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:21:30 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1A6DB37B404; Thu, 31 Jan 2002 02:21:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VACjT74395; Thu, 31 Jan 2002 02:12:45 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 02:12:45 -0800 (PST) From: Message-Id: <200201311012.g0VACjT74395@freefall.freebsd.org> To: dmorriso@hes.hmc.psu.edu, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: i386/33195: User Configuration transfer problem during install Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: User Configuration transfer problem during install State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 02:11:55 PST 2002 State-Changed-Why: Please see the Handbook for information on the difference between 5.0-CURRENT and 4.x-RELEASE / 4.x-STABLE. As an aside, this sounds a lot like a broken CD / CD image. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33195 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:31:40 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4097A37B400; Thu, 31 Jan 2002 02:31:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAQvX76631; Thu, 31 Jan 2002 02:26:57 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 02:26:57 -0800 (PST) From: Message-Id: <200201311026.g0VAQvX76631@freefall.freebsd.org> To: dwchoe@naver.com, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/30781: msgrcv call blocks other pthread's jobs Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: msgrcv call blocks other pthread's jobs State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 02:26:40 PST 2002 State-Changed-Why: Duplicate of kern/30781. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=30781 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:31:41 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6CE1D37B41A; Thu, 31 Jan 2002 02:31:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAOD476138; Thu, 31 Jan 2002 02:24:13 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 02:24:13 -0800 (PST) From: Message-Id: <200201311024.g0VAOD476138@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-ports@FreeBSD.org Subject: Re: ports/34480: system hangs after killing xinit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: system hangs after killing xinit Responsible-Changed-From-To: freebsd-bugs->freebsd-ports Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 02:23:55 PST 2002 Responsible-Changed-Why: Mis-filed PR. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34480 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:31:35 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A539D37B419; Thu, 31 Jan 2002 02:31:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VARmS76910; Thu, 31 Jan 2002 02:27:48 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 02:27:48 -0800 (PST) From: Message-Id: <200201311027.g0VARmS76910@freefall.freebsd.org> To: wilco.oelen@cmg.nl, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/21783: When msgrcv() blocks, it blocks ALL threads in multi-threaded application Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: When msgrcv() blocks, it blocks ALL threads in multi-threaded application State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 02:27:04 PST 2002 State-Changed-Why: This will be addressed in 5.0-RELEASE later this year, with the advent of KSEs. For now, the suggested work-around is to use linuxthreads. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21783 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:33:19 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from tao.org.uk (genius.tao.org.uk [212.135.162.51]) by hub.freebsd.org (Postfix) with ESMTP id 28A1637B416; Thu, 31 Jan 2002 02:33:13 -0800 (PST) Received: by tao.org.uk (Postfix, from userid 100) id CBB2232B; Thu, 31 Jan 2002 10:33:08 +0000 (GMT) Date: Thu, 31 Jan 2002 10:33:08 +0000 From: Josef Karthauser To: Bruce Evans Cc: sheldonh@FreeBSD.ORG, rkw@Dataplex.Net, freebsd-bugs@FreeBSD.ORG Subject: Re: conf/6346: Kernel version strings need to relate to the source not the build Message-ID: <20020131103308.B77899@genius.tao.org.uk> References: <20020130174141.C43943@genius.tao.org.uk> <20020131065411.Q55810-100000@gamplex.bde.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="1LKvkjL3sHcu1TtY" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020131065411.Q55810-100000@gamplex.bde.org>; from bde@zeta.org.au on Thu, Jan 31, 2002 at 06:58:10AM +1100 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --1LKvkjL3sHcu1TtY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 31, 2002 at 06:58:10AM +1100, Bruce Evans wrote: > On Wed, 30 Jan 2002, Josef Karthauser wrote: >=20 > > On Wed, Jan 30, 2002 at 05:40:41PM +0000, Josef Karthauser wrote: > > > Technically we could use the date in the latest $FreeBSD$ tag of the > > > source code, and then put this into vers.c at kernel build time. > > > > > > The following patch would do it. [patch cut] > That slows it down enough to be annoying. Also, the path shouldn't be > absolute. Yes, the path shouldn't be absolute I agree. With respect to time, we should have it switched on in /etc/make.conf if we don't want to use it. For most people, who don't rebuild their kernels 15 times a day (like me sometimes) there's a trade off between having a slightly longer kernel build vs having a date in the output of uname that is meaningful for support purposes. Joe --1LKvkjL3sHcu1TtY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxZHWQACgkQXVIcjOaxUBbkAACfeyd6Jdg97QZ4AQPj9RNZSp6Z GxcAmgIlqYUPYaeYpgkW9xnRBfRSgU5D =hINZ -----END PGP SIGNATURE----- --1LKvkjL3sHcu1TtY-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:41:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1BA9C37B41D; Thu, 31 Jan 2002 02:41:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAW1277615; Thu, 31 Jan 2002 02:32:01 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 02:32:01 -0800 (PST) From: Message-Id: <200201311032.g0VAW1277615@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, sound@FreeBSD.org Subject: Re: kern/34120: optimized fm801 pcm driver Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: optimized fm801 pcm driver Responsible-Changed-From-To: freebsd-bugs->sound Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 02:31:50 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34120 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:41:34 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B61E337B41E; Thu, 31 Jan 2002 02:41:30 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAWuA77843; Thu, 31 Jan 2002 02:32:56 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 02:32:56 -0800 (PST) From: Message-Id: <200201311032.g0VAWuA77843@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, green@FreeBSD.org Subject: Re: misc/33523: XV application cannnot be transfered through ssh for FreeBSD4.4. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: XV application cannnot be transfered through ssh for FreeBSD4.4. Responsible-Changed-From-To: freebsd-bugs->green Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 02:32:44 PST 2002 Responsible-Changed-Why: Over to OpenSSH maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33523 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 2:50:12 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0297337B404 for ; Thu, 31 Jan 2002 02:50:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VAo3B80568; Thu, 31 Jan 2002 02:50:03 -0800 (PST) (envelope-from gnats) Received: from enigma.x-telecom.net (enigma.x-telecom.net [80.70.64.51]) by hub.freebsd.org (Postfix) with ESMTP id 4338E37B402 for ; Thu, 31 Jan 2002 02:45:41 -0800 (PST) Received: from root by enigma.x-telecom.net with local (Exim 3.34 #1) id 16WEik-0000vy-00 for FreeBSD-gnats-submit@freebsd.org; Thu, 31 Jan 2002 12:45:34 +0200 Message-Id: Date: Thu, 31 Jan 2002 12:45:34 +0200 From: Olexander Kunytsa Reply-To: Olexander Kunytsa To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: kern/34481: Add support of Daisy Technology PhotoClip USB camera Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34481 >Category: kern >Synopsis: Add support of Daisy Technology PhotoClip USB camera >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 02:50:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Olexander Kunytsa >Release: FreeBSD 5.0-CURRENT i386 >Organization: XTC >Environment: System: FreeBSD enigma.x-telecom.net 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Thu Jan 31 10:25:38 EET 2002 root@enigma.x-telecom.net:/usr/obj/usr/src/sys/CURRENT i386 Also it works under STABLE >Description: Adding support of PhotoClip USB Camera (http://www.myphotoclip.com) - Vendor&Device IDs for USB product, - quirk for SCSI CAM, as well as it based on my quirk for Diva Mp3 player (PR:kern/33638), device of the same company (inspite of theirs' different vendor IDs) >How-To-Repeat: Plug the device into usb port, U'll see it is attached by usbd, but trying to read from you will see: umass0: Phase Error, residue = 0 umass0: BBB reset failed, STALLED umass0: Phase Error, residue = 0 umass0: BBB reset failed, STALLED umass0: Phase Error, residue = 0 umass0: BBB reset failed, STALLED umass0: Phase Error, residue = 0 umass0: BBB reset failed, STALLED >Fix: Apply this patch: --- sys/dev/usb/usbdevs.old Thu Jan 31 10:12:14 2002 +++ sys/dev/usb/usbdevs Thu Jan 31 10:12:23 2002 @@ -325,6 +325,7 @@ vendor ENTREGA 0x1645 Entrega vendor ACTIONTEC 0x1668 Actiontec Electronics, Inc. vendor DLINK 0x2001 D-Link Corp +vendor DAISY 0x3579 Daisy Technology vendor INTEL 0x8086 Intel vendor HP2 0xf003 Hewlett-Packard @@ -490,6 +491,9 @@ product DLINK DSB650TX 0x4002 10/100 ethernet adapter product DLINK DSB650TX_PNA 0x4003 1/10/100 ethernet adapter product DLINK DSB650 0xABC1 10/100 ethernet adapter + +/* Daisy Technology products */ +product DAISY DMC 0x6901 PhotoClip Camera /* Dallas Semiconductor products */ product DALLAS J6502 0x4201 J-6502 speakers --- sys/dev/usb/usbdevs.h.old Thu Jan 31 10:12:10 2002 +++ sys/dev/usb/usbdevs.h Thu Jan 31 10:12:27 2002 @@ -332,6 +332,7 @@ #define USB_VENDOR_ENTREGA 0x1645 /* Entrega */ #define USB_VENDOR_ACTIONTEC 0x1668 /* Actiontec Electronics, Inc. */ #define USB_VENDOR_DLINK 0x2001 /* D-Link Corp */ +#define USB_VENDOR_DAISY 0x3579 /* Daisy Technology */ #define USB_VENDOR_INTEL 0x8086 /* Intel */ #define USB_VENDOR_HP2 0xf003 /* Hewlett-Packard */ @@ -497,6 +498,9 @@ #define USB_PRODUCT_DLINK_DSB650TX 0x4002 /* 10/100 ethernet adapter */ #define USB_PRODUCT_DLINK_DSB650TX_PNA 0x4003 /* 1/10/100 ethernet adapter */ #define USB_PRODUCT_DLINK_DSB650 0xABC1 /* 10/100 ethernet adapter */ + +/* Daisy Technology products */ +#define USB_PRODUCT_DAISY_DMC 0x6901 /* PhotoClip Camera */ /* Dallas Semiconductor products */ #define USB_PRODUCT_DALLAS_J6502 0x4201 /* J-6502 speakers */ --- sys/dev/usb/usbdevs_data.h.old Thu Jan 31 10:12:06 2002 +++ sys/dev/usb/usbdevs_data.h Thu Jan 31 10:12:27 2002 @@ -532,6 +532,12 @@ "10/100 ethernet adapter", }, { + USB_VENDOR_DAISY, USB_PRODUCT_DAISY_DMC, + 0, + "Daisy Technology", + "PhotoClip Camera", + }, + { USB_VENDOR_DALLAS, USB_PRODUCT_DALLAS_J6502, 0, "Dallas Semiconductor", @@ -3835,6 +3841,12 @@ USB_VENDOR_DLINK, 0, USB_KNOWNDEV_NOPROD, "D-Link Corp", + NULL, + }, + { + USB_VENDOR_DAISY, 0, + USB_KNOWNDEV_NOPROD, + "Daisy Technology", NULL, }, { --- sys/cam/scsi/scsi_da.c.old Thu Jan 31 10:17:28 2002 +++ sys/cam/scsi/scsi_da.c Mon Jan 28 09:18:50 2002 @@ -354,6 +354,13 @@ */ {T_DIRECT, SIP_MEDIA_REMOVABLE, "DIVA USB", "Media Reader","*"}, /*quirks*/ DA_Q_NO_6_BYTE + }, + { + /* + * Daisy Technology PhotoClip USB Camera + */ + {T_DIRECT, SIP_MEDIA_REMOVABLE, "Digital", "World DMC","*"}, + /*quirks*/ DA_Q_NO_6_BYTE } }; >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 3:30:15 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9884E37B402 for ; Thu, 31 Jan 2002 03:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VBU2A91169; Thu, 31 Jan 2002 03:30:02 -0800 (PST) (envelope-from gnats) Received: from memphis.mephi.ru (memphis.mephi.ru [194.67.67.234]) by hub.freebsd.org (Postfix) with ESMTP id 04BAB37B402 for ; Thu, 31 Jan 2002 03:26:29 -0800 (PST) Received: (from timon@localhost) by memphis.mephi.ru (8.11.6/8.11.3) id g0VBQNp55541; Thu, 31 Jan 2002 14:26:23 +0300 (MSK) (envelope-from timon) Message-Id: <200201311126.g0VBQNp55541@memphis.mephi.ru> Date: Thu, 31 Jan 2002 14:26:23 +0300 (MSK) From: "Artem 'Zazoobr' Ignatjev" Reply-To: "Artem 'Zazoobr' Ignatjev" To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34483 >Category: bin >Synopsis: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 03:30:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Artem 'Zazoobr' Ignatjev >Release: FreeBSD 4.4-RELEASE i386 >Organization: Moscow Engineering-Physical Institute (MEPhI) >Environment: System: FreeBSD memphis.mephi.ru 4.4-RELEASE FreeBSD 4.4-RELEASE #3: Sun Nov 18 00:46:03 MSK 2001 root@:/usr/src/sys/compile/LOCAL i386 >Description: amd(4) is a daemon which automatically mounts filesystems whenever a file or directory within that filesystem is accessed. The 'program' filesystem type (type:=program) allows a program to be run whenever a mount or unmount of filesystem is requested. However, the following code from contrib/amd/amd/amfs_program.c (from /usr/src/ hierarchy) makes that somewhat tricky: $Id: amfs_program.c,v 1.5 1999/09/30 21:01:30 ezk Exp $ (line 116) static int amfs_program_exec(char *info) { char **xivec; int error; /* * Split copy of command info string */ info = strdup(info); if (info == 0) return ENOBUFS; xivec = strsplit(info, ' ', '\''); /* * Put stdout to stderr */ /* ... skip ... */ (line 156) if (xivec[0] == 0 || xivec[1] == 0) { errno = EINVAL; plog(XLOG_USER, "1st/2nd args missing to (un)mount program"); } else { (void) execv(xivec[0], xivec + 1); } Notice the line in `else' clause: it calls program xivec[0], giving it arguments (INCLUDING argv[0] which supposed to be program name) since xivec[1], of course, this don't works, and called program `looses' its first argument. Also, no docs from contrib/amd/doc, written in tex/texi are neither formatted nor installed in /usr/share ierarchy ( I was unsuccessful trying to find formatted docs, at least) >How-To-Repeat: To check that, try adding this line to your amd.map: test type:=program;mount:="/usr/bin/logger request to mount ${path}";unmount:="/usr/bin/logger trying to unmount ${path}" then reload map using killall (as root) killall -1 amd and then try to chdir to the 'test' directory in toplevel directory for amd (/mnt in my case) cd /mnt/test This will cause amd(8) to try mount the "test" directory by calling the ${mount} program, which is supposed to be `/usr/bin/logger request to mount /mnt/test', where "/mnt/test" is the value of ${path} variable, but will fail, since execv(2) will look as follows: execv("/usr/bin/logger", {"request", "to", "mount", "/mnt/test"}) and program is expected to be run by execv("/usr/bin/logger", {"/usr/bin/logger", "request", "to", "mount", "/mnt/test"}) >Fix: --- contrib/amd/amd/amfs_program.c.orig +++ contrib/amd/amd/amfs_program.c @@ -155,11 +155,11 @@ if (xivec[0] == 0 || xivec[1] == 0) { errno = EINVAL; plog(XLOG_USER, "1st/2nd args missing to (un)mount program"); } else { - (void) execv(xivec[0], xivec + 1); + (void) execv(xivec[0], xivec); } /* * Save error number */ >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 3:43:53 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mail20.jump.net (mail20.jump.net [206.196.91.20]) by hub.freebsd.org (Postfix) with ESMTP id 9793137B405; Thu, 31 Jan 2002 03:43:48 -0800 (PST) Received: from Powerbook.Dataplex.Net (cust-92-208.customer.jump.net [207.8.92.208]) by mail20.jump.net (8.11.6/) with ESMTP id g0VBhjA21041; Thu, 31 Jan 2002 05:43:45 -0600 (CST) Date: Thu, 31 Jan 2002 05:43:45 -0600 Subject: Re: conf/6346: Kernel version strings need to relate to the source not the build Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v480) Cc: joe@tao.org.uk, sheldonh@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG, bde@zeta.org.au To: "."@babolo.ru From: Richard Wackerbarth In-Reply-To: <200201310401.HAA01299@aaz.links.ru> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.480) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wednesday, January 30, 2002, at 10:01 PM, "."@babolo.ru wrote: > Richard Wackerbarth writes: >> On Wednesday, January 30, 2002, at 06:26 PM, "."@babolo.ru wrote: >> >>> Richard Wackerbarth writes: >>>> It can also be done by playing games on a special file in the master >>>> cvs archive (but not the copies thereof) >>> Exactly. >>> What about do >>> date +'#define LAST_MOD "%Y-%m-%d %H:%M:%S"' > /path/last_mod_date.h >>> on any CVS tree update? > Sorry, commit > >>> And #include >> >> That won't work. It produces the time of the cvs checkout/update and >> not >> the time of the source modification. >> That is little better than the time of the compile that we have now. > I think about commit time (my mistake, not checkout) > But I understand, it is slightly complex to generate > last_mod_date.h,v then last_mod_date.h, > but there no need in tags in it, so it can be whole > overwritten by every commit Rather than computing the source date from the sources as Joe's algorithm does, you could compute that result at commit time and commit that time to the master cvs tree. The problem with that approach is that such a file would grow at an unacceptable rate. Your suggestion to simplify if to the extreme doesn't work either. Consider what happens if I check out any version other than the "HEAD". By your approach, I would get a recent time stamp and not the one which reflects the true age of the sources that I am using. Now, I do think your idea has some merit. For example, we could override the checkout/update procedure for this special file to produce a time stamp when checking out the head of a branch and to produce some other identifier when another tag is used. Other approaches which approximate the true source time stamp can also be considered. It might be reasonable to trade time granularity for accuracy. For example, you might update the source time stamp only once a day. That leaves some uncertainty in the result (Was that Thursday before xxx was corrected, or after? However, it would still be clear that it was before Saturday's change.) As Joe notes in another message, having the option to suppress the recalculation might be a good approach. Power users who are most impacted by the added complexity of the build time probably don't need the same level of source identification. Another approach is to integrate the searching with the build process. Instead of examining each source file directly, you can partition the files into subsets and compute a time stamp for each subset. The global time stamp can then be computed by examining only the limited number of collective time stamps. Modification of a file would trigger the computation of the time stamp for its subset, and hence the global time stamp, but not involve the other subsets. -- Richard Wackerbarth The Digital Dataplex (512) 346-5772 8801 Camelia Ln rkw@dataplex.net Austin, TX 78759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 3:50:10 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D3E3037B400 for ; Thu, 31 Jan 2002 03:50:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VBo5N93890; Thu, 31 Jan 2002 03:50:05 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 03:50:05 -0800 (PST) Message-Id: <200201311150.g0VBo5N93890@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Peter Pentchev Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Reply-To: Peter Pentchev Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34483; it has been noted by GNATS. From: Peter Pentchev To: Artem 'Zazoobr' Ignatjev Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Date: Thu, 31 Jan 2002 13:48:18 +0200 And just as a minor followup to my comments in the open->feedback state change, I have checked the amd sources and the same bug is present in the most recent version, am-utils-6.0.7. G'luck, Peter -- No language can express every thought unambiguously, least of all this one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 3:51:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1F72837B400; Thu, 31 Jan 2002 03:51:28 -0800 (PST) Received: (from roam@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VBijd93137; Thu, 31 Jan 2002 03:44:45 -0800 (PST) (envelope-from roam) Date: Thu, 31 Jan 2002 03:44:45 -0800 (PST) From: Message-Id: <200201311144.g0VBijd93137@freefall.freebsd.org> To: timon@memphis.mephi.ru, roam@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map State-Changed-From-To: open->feedback State-Changed-By: roam State-Changed-When: Thu Jan 31 03:35:28 PST 2002 State-Changed-Why: amd is contributed software, as witnessed by the sources' location in the contrib/ section of the FreeBSD source tree. As per the FreeBSD policy regarding contributed software, and as per the specific instructions in the src/contrib/amd/FREEBSD-upgrade file, local changes should be kept down to a minumum, and all proposed changes should be sent to the amd maintainers at for inclusion in a future release. Thus, the changes would be cleanly imported into FreeBSD at the import of the next release, and there would be no conflicts in future imports. Could you verify if the change you are proposing (which looks fine to me personally, and therefore should also look fine to the amd maintainers) would not be accepted by the amd developers, so it can be cleanly imported into FreeBSD? If it is, and if it is accepted exactly as in your patch, it would even be possible to commit it to FreeBSD before the next import, as it will be cleanly "swallowed" at import time. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34483 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 4:30: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8AD5037B402 for ; Thu, 31 Jan 2002 04:30:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VCU4O11014; Thu, 31 Jan 2002 04:30:04 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 04:30:04 -0800 (PST) Message-Id: <200201311230.g0VCU4O11014@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/26510: panic with >4GB RAM Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/26510; it has been noted by GNATS. From: Sheldon Hearn To: "Hiten Pandya" Cc: bug-followup@freebsd.org Subject: Re: kern/26510: panic with >4GB RAM Date: Thu, 31 Jan 2002 14:31:20 +0200 On Mon, 21 Jan 2002 07:40:02 PST, "Hiten Pandya" wrote: > Basically, this issue comes up, because of the Intel's 4 Gigabytes > Virtual Address (VA) space limitation. This causes a hang in the > FreeBSD's KVA mapping system. A patch for this was posted by Matt > Dillon on the freebsd-current mailing list, as well -hackers. Could you post message IDs? I can't find the Patch from Matt that you're talking about. Also, if the patch hasn't been committed yet, surely these PRs should remain open and be assigned to him? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 4:30:13 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C072937B400 for ; Thu, 31 Jan 2002 04:30:06 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VCU6Q11021; Thu, 31 Jan 2002 04:30:06 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 04:30:06 -0800 (PST) Message-Id: <200201311230.g0VCU6Q11021@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/23411: SMP Kernel Freezes Machines on Dual Processor TYAN Tiger Motherboard System. Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/23411; it has been noted by GNATS. From: Sheldon Hearn To: "Hiten Pandya" Cc: bug-followup@freebsd.org Subject: Re: kern/23411: SMP Kernel Freezes Machines on Dual Processor TYAN Tiger Motherboard System. Date: Thu, 31 Jan 2002 14:32:40 +0200 On Mon, 21 Jan 2002 07:10:02 PST, "Hiten Pandya" wrote: > According to the kernel config file you submitted, it seems that there > is a minute un-noticeable error (to my eyes anyway): > > 01: machine i386 > 02: # cpu I386_CPU > 03: # cpu I486_CPU > 04: cpu I586_CPU > 05: cpu I686_CPU > > If you notice, on line 04 and 05, you can only have one type of > processor I beleive. According to the way SMP works, on intel, > you can't mix and match CPU types. I don't think this is true. Just take a look at GENERIC. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 4:59:24 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id CE7A437B404; Thu, 31 Jan 2002 04:59:20 -0800 (PST) Received: from pool0005.cvx22-bradley.dialup.earthlink.net ([209.179.198.5] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WGna-0003r7-00; Thu, 31 Jan 2002 04:58:42 -0800 Message-ID: <3C593F22.977C00FD@mindspring.com> Date: Thu, 31 Jan 2002 04:57:06 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Culver Cc: David Malone , "Cameron, Frank" , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: <20020130161320.K18721-100000@alpha.yumyumyum.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Kenneth Culver wrote: > Actually FreeBSD does make use of them, but in a way that doesn't cause a > problem. There's actually a seperate TLB bug, but FreeBSD doesn't trigger that one, either (Linux can tickle it, when there are certain specific circumstances met). $10,000, and I'll tell you how to fix it. 8-) 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 5:11:30 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3DDC037B402; Thu, 31 Jan 2002 05:11:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VD7Ir22366; Thu, 31 Jan 2002 05:07:18 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 05:07:18 -0800 (PST) From: Message-Id: <200201311307.g0VD7Ir22366@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, n_hibma@FreeBSD.org Subject: Re: kern/31659: USB controller driver will die after some hours/heavy load. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: USB controller driver will die after some hours/heavy load. Responsible-Changed-From-To: freebsd-bugs->n_hibma Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 05:06:51 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31659 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 5:50:59 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9D10637B41B for ; Thu, 31 Jan 2002 05:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VDo1J38438; Thu, 31 Jan 2002 05:50:01 -0800 (PST) (envelope-from gnats) Received: from domu.oav.net (domu.oav.net [195.154.210.133]) by hub.freebsd.org (Postfix) with ESMTP id 0097B37B404 for ; Thu, 31 Jan 2002 05:48:43 -0800 (PST) Received: from kiwi.adsl.isdnet.net (kiwi.adsl.isdnet.net [195.154.177.33]) by domu.oav.net (New World Mailer from the Space) with ESMTP id A161C1C731 for ; Thu, 31 Jan 2002 14:48:41 +0100 (CET) (envelope-from kiwi@kiwi.home.oav.net) Received: from kiwi.home.oav.net (kiwi.home.oav.net [192.168.255.11]) by kiwi.adsl.isdnet.net (Postfix) with ESMTP id 71F6CD342 for ; Thu, 31 Jan 2002 13:47:13 +0100 (CET) Received: (from root@localhost) by kiwi.home.oav.net (8.11.6/8.11.6) id g0VDmfQ01021; Thu, 31 Jan 2002 14:48:41 +0100 (CET) (envelope-from kiwi) Message-Id: <200201311348.g0VDmfQ01021@kiwi.home.oav.net> Date: Thu, 31 Jan 2002 14:48:41 +0100 (CET) From: Xavier Beaudouin To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: kern/34487: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34487 >Category: kern >Synopsis: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 05:50:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Xavier Beaudouin >Release: FreeBSD 4.5-STABLE i386 >Organization: The Caudium Group >Environment: System: FreeBSD kiwi.home.oav.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Thu Jan 31 02:57:49 CET 2002 root@kiwi.home.oav.net:/usr/src/sys/compile/KIWI i386 (This was used to send-pr, but here is the description of the machine) ASUS P2B-DS motherboard, with 2 PII-400 (512k - ECC L2 cache), 512M memory Nic : Intel Interexpress, video card cirrus logic, and scsi card adaptec aic onboard. >Description: Using CDROM images or floppy images from FreeBSD 4.0, 4.1, 4.2 or 4.3, the system will install sligtly without any locks up. But starting with FreeBSD 4.4 or 4.5, the kernel will lock itself (waiting maybe for something it cannot found) just after unsuccesfull probing of ppc0 port. I've tryed numerous configuration : swaping from SCSI to IDE, configure the machine with MPS 1.4 (on bios) enabled or disable, with only one CPU... Note that recent linux version, openbsd, windows, sco or solaris OS works very well on this mobo... >How-To-Repeat: Use CDROM image or floppy installation image, an asus P2B-DS and try to install on it a FreeBSD 4.4 or 4.5 >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6: 1:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 510EA37B402; Thu, 31 Jan 2002 06:01:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VE0GH40475; Thu, 31 Jan 2002 06:00:16 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 06:00:16 -0800 (PST) From: Message-Id: <200201311400.g0VE0GH40475@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, sheldonh@FreeBSD.org Subject: Re: bin/3170: vi freaks and dump core if user doesn't exist Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: vi freaks and dump core if user doesn't exist Responsible-Changed-From-To: freebsd-bugs->sheldonh Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 05:59:18 PST 2002 Responsible-Changed-Why: I'll tke this one, now that Alex has shown us a patch from the maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3170 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6: 1:32 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id F3BBC37B416; Thu, 31 Jan 2002 06:01:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VDwcT40072; Thu, 31 Jan 2002 05:58:38 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 05:58:38 -0800 (PST) From: Message-Id: <200201311358.g0VDwcT40072@freefall.freebsd.org> To: alexs@snark.ratmir.ru, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, sheldonh@FreeBSD.org Subject: Re: bin/26869: vi(1) crashes in viewing a file with long lines Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: vi(1) crashes in viewing a file with long lines State-Changed-From-To: feedback->analyzed State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 05:57:51 PST 2002 State-Changed-Why: Committed in -CURRENT, with plans to MFC to -STABLE in a month. Responsible-Changed-From-To: freebsd-bugs->sheldonh Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 05:57:51 PST 2002 Responsible-Changed-Why: I have to remember to MFC this. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=26869 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:10: 7 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7862337B416 for ; Thu, 31 Jan 2002 06:10:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEA0b45993; Thu, 31 Jan 2002 06:10:00 -0800 (PST) (envelope-from gnats) Received: from xeon.unixathome.org (CPE00C0DFB00A2B.cpe.net.cable.rogers.com [24.102.95.54]) by hub.freebsd.org (Postfix) with ESMTP id 1ED0437B404 for ; Thu, 31 Jan 2002 06:06:39 -0800 (PST) Received: (from dan@localhost) by xeon.unixathome.org (8.11.6/8.11.6) id g0VE6cU02541; Thu, 31 Jan 2002 09:06:38 -0500 (EST) (envelope-from dan) Message-Id: <200201311406.g0VE6cU02541@xeon.unixathome.org> Date: Thu, 31 Jan 2002 09:06:38 -0500 (EST) From: Dan Langille Reply-To: Dan Langille To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: bin/34489: tail cores if you press control-\ Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34489 >Category: bin >Synopsis: tail cores if you press control-\ >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 06:10:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Dan Langille >Release: FreeBSD 4.5-STABLE i386 >Organization: The FreeBSD Diary >Environment: System: FreeBSD xeon.unixathome.org 4.5-STABLE FreeBSD 4.5-STABLE #4: Mon Jan 28 22:31:03 EST 2002 root@xeon.unixathome.org:/usr/obj/usr/src/sys/XEON i386 >Description: tail will core if you press control-\ while it is running. >How-To-Repeat: tail -f /var/log/messages press control \ yes, that's the command used to terminate xtail.. >Fix: sorry, haven't looked yet. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:12: 7 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from lists.unixathome.org (lists.unixathome.org [210.48.103.158]) by hub.freebsd.org (Postfix) with ESMTP id 54DFA37B416; Thu, 31 Jan 2002 06:12:03 -0800 (PST) Received: from wocker (lists.unixathome.org [210.48.103.158]) by lists.unixathome.org (8.11.6/8.11.6) with ESMTP id g0VEC0q31504; Fri, 1 Feb 2002 03:12:00 +1300 (NZDT) (envelope-from dan@lists.unixathome.org) Message-Id: <200201311412.g0VEC0q31504@lists.unixathome.org> From: "Dan Langille" Organization: DVL Software Limited To: gnats-admin@FreeBSD.org, freebsd-bugs@FreeBSD.org Date: Thu, 31 Jan 2002 09:11:58 -0500 MIME-Version: 1.0 Subject: Re: bin/34489: tail cores if you press control-\ Reply-To: dan@langille.org In-reply-to: <200201311410.g0VEA0l45989@freefall.freebsd.org> References: Your message of Thu, 31 Jan 2002 09:06:38 -0500 (EST) <200201311406.g0VE6cU02541@xeon.unixathome.org> X-mailer: Pegasus Mail for Windows (v4.01) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 31 Jan 2002 at 6:10, gnats-admin@FreeBSD.org wrote: > http://www.freebsd.org/cgi/query-pr.cgi?pr=34489 > > >Category: bin > >Responsible: freebsd-bugs > >Synopsis: tail cores if you press control-\ > >Arrival-Date: Thu Jan 31 06:10:00 PST 2002 Well, silly me, control-\ is supposed to do that. It is typically SIGQUIT, which is expected to generate a core. See action(2). Someone please close this PR. Thanks. -- Dan Langille The FreeBSD Diary - http://freebsddiary.org/ - practical examples To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:21:32 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 5AB2637B402; Thu, 31 Jan 2002 06:21:28 -0800 (PST) Received: (from tmm@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEJoi48026; Thu, 31 Jan 2002 06:19:50 -0800 (PST) (envelope-from tmm) Date: Thu, 31 Jan 2002 06:19:50 -0800 (PST) From: Message-Id: <200201311419.g0VEJoi48026@freefall.freebsd.org> To: dan@freebsddiary.org, tmm@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/34489: tail cores if you press control-\ Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: tail cores if you press control-\ State-Changed-From-To: open->closed State-Changed-By: tmm State-Changed-When: Thu Jan 31 06:18:26 PST 2002 State-Changed-Why: Closed at originator's request. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34489 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:21:35 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B5ADE37B416; Thu, 31 Jan 2002 06:21:28 -0800 (PST) Received: (from silby@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEKbv48153; Thu, 31 Jan 2002 06:20:37 -0800 (PST) (envelope-from silby) Date: Thu, 31 Jan 2002 06:20:37 -0800 (PST) From: Message-Id: <200201311420.g0VEKbv48153@freefall.freebsd.org> To: steve@watt.com, silby@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/33709: VXLOCK interlock avoided coming out Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: VXLOCK interlock avoided coming out State-Changed-From-To: open->closed State-Changed-By: silby State-Changed-When: Thu Jan 31 06:18:13 PST 2002 State-Changed-Why: Matt Dillon recently removed this error message; it's more of a rare occurance than a problem now. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33709 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:40: 5 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 51A6137B402 for ; Thu, 31 Jan 2002 06:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEe2a80357; Thu, 31 Jan 2002 06:40:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 06:40:02 -0800 (PST) Message-Id: <200201311440.g0VEe2a80357@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/34487: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/34487; it has been noted by GNATS. From: Sheldon Hearn To: Xavier Beaudouin Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/34487: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard Date: Thu, 31 Jan 2002 16:38:57 +0200 On Thu, 31 Jan 2002 14:48:41 +0100, Xavier Beaudouin wrote: > But starting with FreeBSD 4.4 or 4.5, the kernel will lock itself (waiting > maybe for something it cannot found) just after unsuccesfull probing of ppc0 > port. Can you use boot -v to provide more detail on exactly where the lockup occurs? Note the following open PRs relating to ASUS motherboards: kern/25909 kern/28418 kern/31233 See also PR misc/33398, which suggests toggling the "Plug'n'Play OS" option in the BIOS. Also, PR kern/30715 suggests that a bug tickled by the use of PCI slot #4 on P3B boards was resolved in 4.5-RELEASE. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:41:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6259537B402; Thu, 31 Jan 2002 06:41:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEcZZ73067; Thu, 31 Jan 2002 06:38:35 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 06:38:35 -0800 (PST) From: Message-Id: <200201311438.g0VEcZZ73067@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, bde@FreeBSD.org Subject: Re: kern/34470: Modem gets sio1 interrupt-level buffer overflows' Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Modem gets sio1 interrupt-level buffer overflows' Responsible-Changed-From-To: freebsd-bugs->bde Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 06:38:23 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34470 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:41:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C2DCB37B416; Thu, 31 Jan 2002 06:41:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEbYn68435; Thu, 31 Jan 2002 06:37:34 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 06:37:34 -0800 (PST) From: Message-Id: <200201311437.g0VEbYn68435@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, joe@FreeBSD.org Subject: Re: kern/34481: Add support of Daisy Technology PhotoClip USB camera Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Add support of Daisy Technology PhotoClip USB camera Responsible-Changed-From-To: freebsd-bugs->joe Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 06:37:19 PST 2002 Responsible-Changed-Why: Joe usually adds new IDs. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34481 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:51:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6497537B400; Thu, 31 Jan 2002 06:51:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEjmX17294; Thu, 31 Jan 2002 06:45:48 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 06:45:48 -0800 (PST) From: Message-Id: <200201311445.g0VEjmX17294@freefall.freebsd.org> To: jan@caustic.org, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: i386/34405: -CURRENT fatal trap during boot. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: -CURRENT fatal trap during boot. State-Changed-From-To: open->feedback State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 06:45:33 PST 2002 State-Changed-Why: More detail on the panic has been promised. :-) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34405 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:51:35 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B976837B404; Thu, 31 Jan 2002 06:51:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEl4722616; Thu, 31 Jan 2002 06:47:04 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 06:47:04 -0800 (PST) From: Message-Id: <200201311447.g0VEl4722616@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, green@FreeBSD.org Subject: Re: misc/34401: ssh & kerberos IV don't work together Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: ssh & kerberos IV don't work together Responsible-Changed-From-To: freebsd-bugs->green Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 06:46:51 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34401 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 6:51:35 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 58AD537B402; Thu, 31 Jan 2002 06:51:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEgf298052; Thu, 31 Jan 2002 06:42:41 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 06:42:41 -0800 (PST) From: Message-Id: <200201311442.g0VEgf298052@freefall.freebsd.org> To: anders.larsson@marratech.com, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/34447: DLink DFE 500 rev E1 + dhclient dc0 crashes system Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: DLink DFE 500 rev E1 + dhclient dc0 crashes system State-Changed-From-To: open->feedback State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 06:39:35 PST 2002 State-Changed-Why: Search the mailing list archives for support responses from Bill Paul and you'll see why I haven't assigned this PR to the maintainer yet. Before we hand this over to Paul, please provide a lot more detail on what you mean by "the machine crashes". If you mean that the machine panics, then please follow the advice given at the following web page to provide more detail: http://www.freebsd.org/FAQ/advanced.html#KERNEL-PANIC-TROUBLESHOOTING You should probably also show us the kernel probe messages for the cards, with this command: dmesg | grep ^dc[01] Please copy your feedback to , using the subject line of this message. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34447 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7: 0:24 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 819BB37B41D for ; Thu, 31 Jan 2002 07:00:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VF07892291; Thu, 31 Jan 2002 07:00:07 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 07:00:07 -0800 (PST) Message-Id: <200201311500.g0VF07892291@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/34373: SMP lockup somewhat similar to bug #33986, unless vmware is running... Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/34373; it has been noted by GNATS. From: Sheldon Hearn To: Jesse McConnell Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/34373: SMP lockup somewhat similar to bug #33986, unless vmware is running... Date: Thu, 31 Jan 2002 17:01:28 +0200 On Mon, 28 Jan 2002 07:38:38 PST, Jesse McConnell wrote: > >Number: 34373 > >Category: kern > >Synopsis: SMP lockup somewhat similar to bug #33986, unless vmware is running... 1) You say your lockup is similar to i386/33986. Does that mean you don't get it if you remove audio support from your kernel? 2) Do you see the same problem with a more sane value for NMBCLUSTERS, like say 18432? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7: 1:32 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 74E4D37B405; Thu, 31 Jan 2002 07:01:28 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VEqk462992; Thu, 31 Jan 2002 06:52:46 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 06:52:46 -0800 (PST) From: Message-Id: <200201311452.g0VEqk462992@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, peter@FreeBSD.org Subject: Re: bin/34394: tgetent returns wrong value in libtermcap Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: tgetent returns wrong value in libtermcap Responsible-Changed-From-To: freebsd-bugs->peter Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 06:52:34 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34394 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:10: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8D4EA37B405 for ; Thu, 31 Jan 2002 07:10:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VFA4897951; Thu, 31 Jan 2002 07:10:04 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 07:10:04 -0800 (PST) Message-Id: <200201311510.g0VFA4897951@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/12281: active-filter option in pppd doesn't stop reset of idle timer Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/12281; it has been noted by GNATS. From: Sheldon Hearn To: iedowse@FreeBSD.org Cc: bug-followup@freebsd.org Subject: Re: kern/12281: active-filter option in pppd doesn't stop reset of idle timer Date: Thu, 31 Jan 2002 17:12:13 +0200 On Sun, 20 Jan 2002 16:47:39 PST, Tim Moore wrote: > I don't use pppd anymore and don't have a current copy of the sources > checked out, so unfortunately I can't comment. So does this get closed or assigned to Peter? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:11:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 13B7B37B416; Thu, 31 Jan 2002 07:11:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VF1q192753; Thu, 31 Jan 2002 07:01:52 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 07:01:52 -0800 (PST) From: Message-Id: <200201311501.g0VF1q192753@freefall.freebsd.org> To: ran@styx.aic.net, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/7410: [PATCH] driver for arlan-655 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] driver for arlan-655 State-Changed-From-To: feedback->closed State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 07:00:28 PST 2002 State-Changed-Why: Originator no longer has access to this hardware. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=7410 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:11:38 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 71E4C37B405; Thu, 31 Jan 2002 07:11:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VF50I93537; Thu, 31 Jan 2002 07:05:00 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 07:05:00 -0800 (PST) From: Message-Id: <200201311505.g0VF50I93537@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, obrien@FreeBSD.org Subject: Re: gnu/34102: Linker doesn't search /usr/local/lib Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Linker doesn't search /usr/local/lib Responsible-Changed-From-To: freebsd-bugs->obrien Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 07:04:39 PST 2002 Responsible-Changed-Why: This decision lies with the binutils maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34102 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:11:39 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8D47237B400; Thu, 31 Jan 2002 07:11:34 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VF85b97677; Thu, 31 Jan 2002 07:08:05 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 07:08:05 -0800 (PST) From: Message-Id: <200201311508.g0VF85b97677@freefall.freebsd.org> To: isupov@moonhe.jinr.ru, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, dfr@FreeBSD.org Subject: Re: bin/12545: kldload(8) should be more sensitive to errors in *_module_handler(..., MOD_LOAD, ...) Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: kldload(8) should be more sensitive to errors in *_module_handler(..., MOD_LOAD, ...) State-Changed-From-To: feedback->open State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 07:07:22 PST 2002 State-Changed-Why: Doug, are you still looking after kld* utilities? Responsible-Changed-From-To: freebsd-bugs->dfr Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 07:07:22 PST 2002 Responsible-Changed-Why: Feedback acquired. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=12545 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:20: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D1C8F37B402 for ; Thu, 31 Jan 2002 07:20:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VFK3C99850; Thu, 31 Jan 2002 07:20:03 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 07:20:03 -0800 (PST) Message-Id: <200201311520.g0VFK3C99850@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/12244: realpath() fails when there is no permission to read the WD Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/12244; it has been noted by GNATS. From: Sheldon Hearn To: "Jose M. Alcaide" Cc: iedowse@FreeBSD.org, bug-followup@freebsd.org Subject: Re: bin/12244: realpath() fails when there is no permission to read the WD Date: Thu, 31 Jan 2002 17:13:11 +0200 On Mon, 21 Jan 2002 02:15:34 +0100, "Jose M. Alcaide" wrote: > Yes, it is. Realpath(3) continues using open()/fchdir() for > saving/restoring the current directory. I think that the getwd()/chdir() > method should be used as fallback. Could you submit a patch for that? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:20:13 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 50A6E37B405 for ; Thu, 31 Jan 2002 07:20:07 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VFK7r99894; Thu, 31 Jan 2002 07:20:07 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 07:20:07 -0800 (PST) Message-Id: <200201311520.g0VFK7r99894@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: kern/11966: TCP copies send and receive socket buffer sizes from routing information even when user applications set them Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/11966; it has been noted by GNATS. From: Sheldon Hearn To: Ruslan Ermilov Cc: bug-followup@freebsd.org Subject: Re: kern/11966: TCP copies send and receive socket buffer sizes from routing information even when user applications set them Date: Thu, 31 Jan 2002 17:14:10 +0200 On Thu, 24 Jan 2002 05:00:02 PST, Ruslan Ermilov wrote: > Yes, and I think this patch (sitting in my RELENG_4 tree for over > a year now, and I now almost forgot what it's about) should fix it: You want to commit your patch to tcp_input.c yourself, or shall I assign this PR to jlemon? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:31:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9493D37B404; Thu, 31 Jan 2002 07:31:29 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VFSCA01453; Thu, 31 Jan 2002 07:28:12 -0800 (PST) (envelope-from sheldonh) Date: Thu, 31 Jan 2002 07:28:12 -0800 (PST) From: Message-Id: <200201311528.g0VFSCA01453@freefall.freebsd.org> To: aron@cs.rice.edu, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, ru@FreeBSD.org Subject: Re: kern/11966: TCP copies send and receive socket buffer sizes from routing information even when user applications set them Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: TCP copies send and receive socket buffer sizes from routing information even when user applications set them State-Changed-From-To: feedback->open State-Changed-By: sheldonh State-Changed-When: Thu Jan 31 07:27:40 PST 2002 State-Changed-Why: Ruslan will commit his patch when he has time. Responsible-Changed-From-To: freebsd-bugs->ru Responsible-Changed-By: sheldonh Responsible-Changed-When: Thu Jan 31 07:27:40 PST 2002 Responsible-Changed-Why: Ruslan will commit his patch when he has time. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=11966 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:42:13 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with SMTP id 3B28337B41B for ; Thu, 31 Jan 2002 07:42:06 -0800 (PST) Received: (qmail 21846 invoked by uid 1001); 31 Jan 2002 15:41:31 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Jan 2002 15:41:31 -0000 Date: Thu, 31 Jan 2002 10:41:31 -0500 (EST) From: Kenneth Culver To: Terry Lambert Cc: David Malone , "Cameron, Frank" , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug In-Reply-To: <3C593F22.977C00FD@mindspring.com> Message-ID: <20020131103927.A21783-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > There's actually a seperate TLB bug, but FreeBSD doesn't > trigger that one, either (Linux can tickle it, when there > are certain specific circumstances met). > Well, I think I know what you're talking about, linux allocates agpgart memory without setting a "non-cacheable" bit, and then the agp card writes to that memory, but the cpu cached it already, which makes the cache wrong or something like that, and causes the crashes/hangs. I know this is a greatly simplified version of the real problem, but I think this is a linux bug not necesarily an amd bug. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:44:32 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from pogo.caustic.org (caustic.org [64.163.147.186]) by hub.freebsd.org (Postfix) with ESMTP id 4965E37B400; Thu, 31 Jan 2002 07:44:27 -0800 (PST) Received: from localhost (jan@localhost) by pogo.caustic.org (8.11.6/8.11.6) with ESMTP id g0VFiQ807374; Thu, 31 Jan 2002 07:44:27 -0800 (PST) (envelope-from jan@caustic.org) Date: Thu, 31 Jan 2002 07:44:26 -0800 (PST) From: "f.johan.beisser" X-X-Sender: jan@localhost To: sheldonh@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: i386/34405: -CURRENT fatal trap during boot. In-Reply-To: <200201311445.g0VEjmX17294@freefall.freebsd.org> Message-ID: <20020131074322.T4132-100000@localhost> X-Ignore: This statement isn't supposed to be read by you X-TO-THE-FBI-CIA-AND-NSA: HI! HOW YA DOIN? MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 31 Jan 2002 sheldonh@FreeBSD.org wrote: > Synopsis: -CURRENT fatal trap during boot. > > State-Changed-From-To: open->feedback > State-Changed-By: sheldonh > State-Changed-When: Thu Jan 31 06:45:33 PST 2002 > State-Changed-Why: > More detail on the panic has been promised. :-) > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34405 more is coming. haven't had a chance to hook the laptop to my workstation and get the full trace and ps info via the serial port. busy guy, and all that.. ;) -------/ f. johan beisser /--------------------------------------+ http://caustic.org/~jan jan@caustic.org "John Ashcroft is really just the reanimated corpse of J. Edgar Hoover." -- Tim Triche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 7:50:54 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from server5.ctc.com (server5.ctc.com [147.160.136.36]) by hub.freebsd.org (Postfix) with ESMTP id 5864F37B405; Thu, 31 Jan 2002 07:50:31 -0800 (PST) Received: from server6.ctc.com (stonewall.ctc.com [147.160.136.10]) by server5.ctc.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0VFoUi06482; Thu, 31 Jan 2002 10:50:30 -0500 Received: from nsc-mail1.nsc.ctc.com (nsc-mail1.nsc.ctc.com [147.160.138.14]) by server6.ctc.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id g0VFoUp26715; Thu, 31 Jan 2002 10:50:30 -0500 Received: by nsc-mail1.nsc.ctc.com with Internet Mail Service (5.5.2653.19) id ; Thu, 31 Jan 2002 10:50:45 -0500 Message-ID: <7925FCEF327F984DB5885285256F0D3AC9446F@nsc-mail1.nsc.ctc.com> From: "Cameron, Frank" To: "'Kenneth Culver'" , Terry Lambert Cc: David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: RE: AMD AGP Bug Date: Thu, 31 Jan 2002 10:50:45 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org From what was posted on the linux-kernel list the problem is the OS doing the wrong thing not the hardware. I originally asked the question (albeit not worded as clearly as I should have) because if Microsoft and Linux programmers made the same mistake, might FreeBSD have also. > -----Original Message----- > From: Kenneth Culver [mailto:culverk@yumyumyum.org] > Sent: Thursday, January 31, 2002 10:42 AM > To: Terry Lambert > Cc: David Malone; Cameron, Frank; 'freebsd-bugs@freebsd.org'; > 'freebsd-current@freebsd.org' > Subject: Re: AMD AGP Bug > > > > There's actually a seperate TLB bug, but FreeBSD doesn't > > trigger that one, either (Linux can tickle it, when there > > are certain specific circumstances met). > > > Well, I think I know what you're talking about, linux > allocates agpgart > memory without setting a "non-cacheable" bit, and then the > agp card writes > to that memory, but the cpu cached it already, which makes > the cache wrong > or something like that, and causes the crashes/hangs. I know this is a > greatly simplified version of the real problem, but I think this is a > linux bug not necesarily an amd bug. > > Ken > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 8: 0:36 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2EF5237B42F for ; Thu, 31 Jan 2002 08:00:11 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VG0Bx06514; Thu, 31 Jan 2002 08:00:11 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 08:00:11 -0800 (PST) Message-Id: <200201311600.g0VG0Bx06514@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Alexey V. Neyman" Subject: Re: misc/33736: Scroll-lock on the console prevents shutdown Reply-To: "Alexey V. Neyman" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR misc/33736; it has been noted by GNATS. From: "Alexey V. Neyman" To: "Ted Mittelstaedt" , bug-followup@FreeBSD.org Cc: Subject: Re: misc/33736: Scroll-lock on the console prevents shutdown Date: Thu, 31 Jan 2002 18:53:57 +0300 Just verified, the problem persists as of -stable cvsupped yesterday. -- <-------------------------> ) May the Sun and Water ( Regards, Alexey V. Neyman ) always fall upon you! ( mailto:alex.neyman@auriga.ru <-------------------------> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 8:15:55 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 6F52237B405; Thu, 31 Jan 2002 08:15:48 -0800 (PST) Received: from [62.49.251.130] (helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 16WJsI-000NZV-0X; Thu, 31 Jan 2002 16:15:46 +0000 Received: from herring (herring [10.0.0.2]) by herring.nlsystems.com (8.11.2/8.11.2) with ESMTP id g0VGEU908285; Thu, 31 Jan 2002 16:14:30 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 31 Jan 2002 16:14:30 +0000 (GMT) From: Doug Rabson To: Cc: , , Subject: Re: bin/12545: kldload(8) should be more sensitive to errors in *_module_handler(..., MOD_LOAD, ...) In-Reply-To: <200201311508.g0VF85b97677@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 31 Jan 2002 sheldonh@FreeBSD.org wrote: > Doug, are you still looking after kld* utilities? Not really. Peter was the most recent person to maintain this stuff but these days, I don't think anyone 'owns' it. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 9:30:10 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EBFBA37B405 for ; Thu, 31 Jan 2002 09:30:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VHU0i27187; Thu, 31 Jan 2002 09:30:00 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3C35F37B405 for ; Thu, 31 Jan 2002 09:22:16 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VHMGo25888; Thu, 31 Jan 2002 09:22:16 -0800 (PST) (envelope-from nobody) Message-Id: <200201311722.g0VHMGo25888@freefall.freebsd.org> Date: Thu, 31 Jan 2002 09:22:16 -0800 (PST) From: Dale Sleeper To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: conf/34494: usb configuration problem - usb does not work Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34494 >Category: conf >Synopsis: usb configuration problem - usb does not work >Confidential: no >Severity: non-critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: wish >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 09:30:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Dale Sleeper >Release: FreeBSD 4.4-Release >Organization: Self >Environment: >Description: When I try to use a usb mouse or game controller, I plug in the device a few seconds later the system displays this message: "problem with usbh0 diabling port 1". The system tells me at boot what kind of usb I have on my laptop, which is Intel. But when I try to use it the port gets disabled. I can't figure out how to fix this problem. Please help? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 10:52:34 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with SMTP id 2AD6A37B416 for ; Thu, 31 Jan 2002 10:52:14 -0800 (PST) Received: (qmail 22586 invoked by uid 1001); 31 Jan 2002 18:51:37 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 31 Jan 2002 18:51:37 -0000 Date: Thu, 31 Jan 2002 13:51:37 -0500 (EST) From: Kenneth Culver To: "Cameron, Frank" Cc: Terry Lambert , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: RE: AMD AGP Bug In-Reply-To: <7925FCEF327F984DB5885285256F0D3AC9446F@nsc-mail1.nsc.ctc.com> Message-ID: <20020131135127.V22577-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Yeah, that's what I saw on linux-kernel... Ken On Thu, 31 Jan 2002, Cameron, Frank wrote: > From what was posted on the linux-kernel list the problem is the OS > doing the wrong thing not the hardware. I originally asked the > question (albeit not worded as clearly as I should have) because if > Microsoft and Linux programmers made the same mistake, might > FreeBSD have also. > > > -----Original Message----- > > From: Kenneth Culver [mailto:culverk@yumyumyum.org] > > Sent: Thursday, January 31, 2002 10:42 AM > > To: Terry Lambert > > Cc: David Malone; Cameron, Frank; 'freebsd-bugs@freebsd.org'; > > 'freebsd-current@freebsd.org' > > Subject: Re: AMD AGP Bug > > > > > > > There's actually a seperate TLB bug, but FreeBSD doesn't > > > trigger that one, either (Linux can tickle it, when there > > > are certain specific circumstances met). > > > > > Well, I think I know what you're talking about, linux > > allocates agpgart > > memory without setting a "non-cacheable" bit, and then the > > agp card writes > > to that memory, but the cpu cached it already, which makes > > the cache wrong > > or something like that, and causes the crashes/hangs. I know this is a > > greatly simplified version of the real problem, but I think this is a > > linux bug not necesarily an amd bug. > > > > Ken > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 11:40: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7AE8637B416 for ; Thu, 31 Jan 2002 11:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VJe2g56995; Thu, 31 Jan 2002 11:40:02 -0800 (PST) (envelope-from gnats) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 5A10B37B404 for ; Thu, 31 Jan 2002 11:34:55 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g0VJYs904520; Thu, 31 Jan 2002 20:34:54 +0100 (CET) (envelope-from wkb) Message-Id: <200201311934.g0VJYs904520@freebie.xs4all.nl> Date: Thu, 31 Jan 2002 20:34:54 +0100 (CET) From: wilko@FreeBSD.org Reply-To: wilko@FreeBSD.org To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.2 Subject: bin/34497: calendar(1) does not understand calendars Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34497 >Category: bin >Synopsis: calendar(1) does not understand calendars >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 11:40:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: Wilko Bulte >Release: FreeBSD 4-STABLE i386 >Organization: Private FreeBSD site - The Netherlands >Environment: FreeBSD freebie.xs4all.nl 4.5-STABLE FreeBSD 4.5-STABLE #5: Wed Jan 30 22:12:43 CET 2002 root@freebie.xs4all.nl:/usr/obj/usr/src/sys/FREEBIE i386 >Description: calendar(1) does not understand calendars, has 33 days in January for example. >How-To-Repeat: Given the following calendar file: Thursday BAR Friday FOO Saturday DUH running calendar displays: Jan 31* BAR Jan 32* FOO Jan 33* DUH When run on Thu Jan 31 20:32:12 CET 2002 January with 33 days appears slightly odd. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 12: 0:12 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8F8AA37B405 for ; Thu, 31 Jan 2002 12:00:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VK04l60144; Thu, 31 Jan 2002 12:00:04 -0800 (PST) (envelope-from gnats) Received: from moose.wakeful.net (moose.ne.mediaone.net [24.147.191.79]) by hub.freebsd.org (Postfix) with ESMTP id B024837B417 for ; Thu, 31 Jan 2002 11:50:14 -0800 (PST) Received: (from ira@localhost) by moose.wakeful.net (8.11.4/8.11.4) id g0VJkYq60200; Thu, 31 Jan 2002 14:46:34 -0500 (EST) (envelope-from ira) Message-Id: <200201311946.g0VJkYq60200@moose.wakeful.net> Date: Thu, 31 Jan 2002 14:46:34 -0500 (EST) From: "Ira L. Cooper" Reply-To: ira@wakeful.net To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: bin/34498: Error in vi manpage. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34498 >Category: bin >Synopsis: Error in vi manpage. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 12:00:04 PST 2002 >Closed-Date: >Last-Modified: >Originator: Ira L. Cooper >Release: FreeBSD 4.3-STABLE i386 >Organization: >Environment: System: FreeBSD star.wakeful.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #1: Mon Jan 7 22:10:35 EST 2002 root@star.wakeful.net:/usr/obj/home/ira/4.X-STABLE/src/sys/STAR i386 >Description: The following is in error on the FreeBSD manpage for vi. [count] ~ motion Reverse the case of the characters in a text region specified by the count and motion. >How-To-Repeat: Either: man vi or edit a file in vi and try 2~j >Fix: Remove the offending text. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 12:10:22 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 77AFC37B402 for ; Thu, 31 Jan 2002 12:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VKA2i65339; Thu, 31 Jan 2002 12:10:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 12:10:02 -0800 (PST) Message-Id: <200201312010.g0VKA2i65339@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Brooks Davis Subject: Re: bin/34498: Error in vi manpage. Reply-To: Brooks Davis Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34498; it has been noted by GNATS. From: Brooks Davis To: "Ira L. Cooper" Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/34498: Error in vi manpage. Date: Thu, 31 Jan 2002 12:03:54 -0800 On Thu, Jan 31, 2002 at 02:46:34PM -0500, Ira L. Cooper wrote: > > System: FreeBSD star.wakeful.net 4.5-PRERELEASE FreeBSD 4.5-PRERELEASE #1: Mon Jan 7 22:10:35 EST 2002 root@star.wakeful.net:/usr/obj/home/ira/4.X-STABLE/src/sys/STAR i386 > >Description: > The following is in error on the FreeBSD manpage for vi. > > [count] ~ motion > Reverse the case of the characters in a text region > specified by the count and motion. > > >How-To-Repeat: > Either: man vi > > or edit a file in vi and try 2~j > > >Fix: > > Remove the offending text. The only thing that's wrong is the "motion" part. ~ works and it does take a count. -- Brooks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 12:30:38 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3114837B404 for ; Thu, 31 Jan 2002 12:30:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VKU3P71443; Thu, 31 Jan 2002 12:30:03 -0800 (PST) (envelope-from gnats) Received: from eubie.lbl.gov (eubie.lbl.gov [131.243.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 6D6D637B400 for ; Thu, 31 Jan 2002 12:23:40 -0800 (PST) Received: (from jin@localhost) by eubie.lbl.gov (8.11.6/8.11.6) id g0VKNex00336; Thu, 31 Jan 2002 12:23:40 -0800 (PST) (envelope-from jin) Message-Id: <200201312023.g0VKNex00336@eubie.lbl.gov> Date: Thu, 31 Jan 2002 12:23:40 -0800 (PST) From: Jin.Guojun@eubie.lbl.gov Reply-To: j_guojun@lbl.gov To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: bin/34502: ssh can crash the 4.5 system Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34502 >Category: bin >Synopsis: ssh can crash the 4.5 system >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 12:30:03 PST 2002 >Closed-Date: >Last-Modified: >Originator: Jin Guojun >Release: FreeBSD 4.5-RELEASE i386 >Organization: >Environment: System: FreeBSD 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Wed Jan 30 09:39:25 PST 2002 OpenSSH_2.9 FreeBSD localisations 20011202 >Description: Problem 1: ssh localhost cause system panic. A local user can use it to crash all 4.5 systems. Problem 2: does not work for protocol 2. After rename authorized_keys to x.authorized_keys (i.e., disable protocol 1), then ssh will ask password instead of passphase: % ls ~/.ssh -rw------- 1 jin advdev 607 Jan 31 12:10 authorized_keys2 -rw------- 1 jin advdev 668 Jan 31 12:08 id_dsa -rw-r--r-- 1 jin advdev 607 Jan 31 12:08 id_dsa.pub -rw------- 1 jin advdev 533 Jan 11 21:24 identity -rw-r--r-- 1 jin advdev 337 Jan 11 21:24 identity.pub -rw------- 1 jin advdev 512 Jan 31 11:43 random_seed -rw------- 1 jin advdev 1687 Aug 27 08:59 x.authorized_keys % ssh peer jin@peer.lbl.gov's password: >How-To-Repeat: Do as described in Description section. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 12:40:24 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BEC6537B41E for ; Thu, 31 Jan 2002 12:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VKe2n74484; Thu, 31 Jan 2002 12:40:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 12:40:02 -0800 (PST) Message-Id: <200201312040.g0VKe2n74484@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Jin Guojun[ITG]" Subject: Re: bin/30993: xxgdb cannot open source file Reply-To: "Jin Guojun[ITG]" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/30993; it has been noted by GNATS. From: "Jin Guojun[ITG]" To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: bin/30993: xxgdb cannot open source file Date: Thu, 31 Jan 2002 12:36:03 -0800 This problem still exists in 4.5-RELEASE. Ian has provided some solution to this bug, I wonder if is this acceptable one or is there a better solution? If there is no other better solution to this problem, can we just use this solution for now? -Jin -------- original discussion ------------- From: Ian Dowse To: Jin Guojun Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/30993: xxgdb cannot open source file Date: Wed, 24 Oct 2001 13:00:59 +0100 In message <3BD616EC.40F97564@lbl.gov>, Jin Guojun writes: >789 XtSetValues(sourceWindow, args, n); >(gdb) s >Warning: Cannot open file /tmp/x.c; Resource temporarily unavailable Something within the X code must be interpreting a zero return from open() as a failure - I've seen this with xxgdb, but rather than digging into the X code I just changed xxgdb to not leave file descriptors 0 and 1 closed. A patch is below. Ian --- orig/calldbx.c Wed Oct 24 12:38:41 2001 +++ calldbx.c Wed Oct 24 12:56:18 2001 @@ -311,6 +311,11 @@ */ close(0); close(1); + if (open("/dev/null", O_RDONLY) < 0 || + open("/dev/null", O_WRONLY) < 0) { + perror("/dev/null"); + exit(1); + } #ifdef _POSIX_SOURCE fcntl(master, F_SETFL, O_NONBLOCK); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 13: 0:14 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D0EE737B404 for ; Thu, 31 Jan 2002 13:00:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VL02N77438; Thu, 31 Jan 2002 13:00:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 13:00:02 -0800 (PST) Message-Id: <200201312100.g0VL02N77438@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: parv Subject: Re: bin/34502: ssh can crash the 4.5 system Reply-To: parv Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34502; it has been noted by GNATS. From: parv To: j_guojun@lbl.gov Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/34502: ssh can crash the 4.5 system Date: Thu, 31 Jan 2002 15:58:25 -0500 in message <200201312023.g0VKNex00336@eubie.lbl.gov>, wrote Jin.Guojun@eubie.lbl.gov thusly... > > System: FreeBSD 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Wed Jan 30 09:39:25 PST 2002 > > OpenSSH_2.9 FreeBSD localisations 20011202 > > >Description: > Problem 1: > ssh localhost > cause system panic. A local user can use it to crash all 4.5 systems. i just tried "ssh localhost" w/o any problems on 4.5-release 2002.01.24.19.00.47 utc. > Problem 2: > > does not work for protocol 2. After rename authorized_keys to > x.authorized_keys (i.e., disable protocol 1), then ssh will ask > password instead of passphase: isn't that the way ssh supposed to work: in absence of keys ask the password? - parv -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 13:16:22 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 7834E37B419; Thu, 31 Jan 2002 13:15:49 -0800 (PST) Received: from [192.168.1.129] (212.129.9.202) by mail.libertysurf.net (5.1.070) id 3C50CBD40014F3FB; Thu, 31 Jan 2002 22:14:59 +0100 Date: Wed, 30 Jan 2002 23:14:48 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Kenneth Culver Cc: "Cameron, Frank" , Terry Lambert , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: RE: AMD AGP Bug In-Reply-To: <20020131135127.V22577-100000@alpha.yumyumyum.org> Message-ID: <20020130225003.C2570-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 31 Jan 2002, Kenneth Culver wrote: > Yeah, that's what I saw on linux-kernel... You probably didn't see the whole story or just did a too selective reading. You should re-read, in my opinion, since you may have just missed the important part. What I understood is that the Athlon allocates cache lines for speculative writes (if write may hit cachable) and such cache lines are flushed to memory even if the write does not happen. As a result, numerous useless writes to memory may happen under any OS. This does not cause visible issue for memory that is required to be cache coherent. Just AGP accesses are not required to be snooped by cache for performance concerns and as memory given to AGP is intended to contain data as textures that should not need tight synchronisation with CPU. Indeed Linux has cached mapping to AGP memory and this could be avoided. Nevertheless, only strange issues like the AMD AGP bug we are talking about could turn this into a real problem. Linux can be fixed, but the useless writes of the existing Athlons from the very fast cache to the relatively very slow memory cannot. And all Athlon users may well pay this penalty under any OS... unless we want to disable caching. :) Btw, I have 2 Athlon 1.2GHz machines that work just fine and fast for me. G=E9rard. > Ken > > On Thu, 31 Jan 2002, Cameron, Frank wrote: > > > From what was posted on the linux-kernel list the problem is the OS > > doing the wrong thing not the hardware. I originally asked the > > question (albeit not worded as clearly as I should have) because if > > Microsoft and Linux programmers made the same mistake, might > > FreeBSD have also. > > > > > -----Original Message----- > > > From: Kenneth Culver [mailto:culverk@yumyumyum.org] > > > Sent: Thursday, January 31, 2002 10:42 AM > > > To: Terry Lambert > > > Cc: David Malone; Cameron, Frank; 'freebsd-bugs@freebsd.org'; > > > 'freebsd-current@freebsd.org' > > > Subject: Re: AMD AGP Bug > > > > > > > > > > There's actually a seperate TLB bug, but FreeBSD doesn't > > > > trigger that one, either (Linux can tickle it, when there > > > > are certain specific circumstances met). > > > > > > > Well, I think I know what you're talking about, linux > > > allocates agpgart > > > memory without setting a "non-cacheable" bit, and then the > > > agp card writes > > > to that memory, but the cpu cached it already, which makes > > > the cache wrong > > > or something like that, and causes the crashes/hangs. I know this is = a > > > greatly simplified version of the real problem, but I think this is a > > > linux bug not necesarily an amd bug. > > > > > > Ken > > > > > > > > > > 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 From owner-freebsd-bugs Thu Jan 31 13:21:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8D90E37B405; Thu, 31 Jan 2002 13:21:29 -0800 (PST) Received: (from brooks@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VLGxS89908; Thu, 31 Jan 2002 13:16:59 -0800 (PST) (envelope-from brooks) Date: Thu, 31 Jan 2002 13:16:59 -0800 (PST) From: Message-Id: <200201312116.g0VLGxS89908@freefall.freebsd.org> To: ira@wakeful.net, brooks@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/34498: Error in vi manpage. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Error in vi manpage. State-Changed-From-To: open->suspended State-Changed-By: brooks State-Changed-When: Thu Jan 31 13:15:07 PST 2002 State-Changed-Why: The submitter will submit the change to the nvi maintainer to be merged when the corrected version appears in a release. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34498 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 13:30:50 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BA0A237B419 for ; Thu, 31 Jan 2002 13:30:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VLU2d96837; Thu, 31 Jan 2002 13:30:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 13:30:02 -0800 (PST) Message-Id: <200201312130.g0VLU2d96837@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Taylor Subject: Re: bin/34497: calendar(1) does not understand calendars Reply-To: David Taylor Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34497; it has been noted by GNATS. From: David Taylor To: wilko@FreeBSD.org Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: bin/34497: calendar(1) does not understand calendars Date: Thu, 31 Jan 2002 21:24:00 +0000 --cNdxnHkX5QqsyA0e Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, 31 Jan 2002, wilko@FreeBSD.org wrote: >=20 > >Number: 34497 > >Category: bin > >Synopsis: calendar(1) does not understand calendars >=20 > >Description: >=20 > calendar(1) does not understand calendars, has 33 days in=20 > January for example. >=20 > >How-To-Repeat: >=20 > Given the following calendar file: >=20 > Thursday BAR > Friday FOO > Saturday DUH >=20 > running calendar displays: >=20 > Jan 31* BAR > Jan 32* FOO > Jan 33* DUH >=20 > When run on Thu Jan 31 20:32:12 CET 2002 >=20 > January with 33 days appears slightly odd. >=20 Yeah, it does. For some reason, I was bored and decided to look at the source to see if I could fix it. I regret that move now :) First thing I noticed was the code for the -a option (to run as root, and loop through every user's calendar: while ((pw =3D getpwent()) !=3D NULL) { (void)setegid(pw->pw_gid); (void)initgroups(pw->pw_name, pw->pw_gid); (void)seteuid(pw->pw_uid); if (!chdir(pw->pw_dir)) cal(); (void)seteuid(0); } Which helpfully casts the return value of setegid()/seteuid()/etc to (void) and ignores it, so if there _is_ an error, it will just read the user-definable calendar file (which can include arbitrary files) as root... not sure that's a good idea. I was going to submit a patch for that along with a fix for the original problem, until I decided there was no way I was fixing the original problem. The code is rather weird and obfusciated, but I managed to create a fix for the specific problem reported, but that doesn't stop '2002-01-33' being misinterpreted, along with other problems that cropped up.... The easiest way I can see to fix it (instead of adding yet more horrible code to an already messy program) would be to change the design from: for each entry in calendar file: Assign date to entry. If date is within user-specified range of dates to display: Display date endif loop (which currently results in assigning 'Jan 32' to 'Friday', and also means if you have something to do every Thursday (e.g. clean car, or something), and ask for every entry for the next 60 days, you will only get one 'clean car' entry, instead of 8 or 9) to for each date in user-specified range: for each entry in calendar file: if entry could represent current date: Display date endif loop loop Thus, you'd have the date 'Feb 01' and the entry 'Thursday', and just have to check if 'Feb 01' is 'Thursday'. However, I don't have enough time to write a calendar(1) replacement from scratch.. Personally, if I was a committer, I'd rip calendar(1) out of the cvs repo. :) [although that may explain why i'm not a committer :)]. Is there a similar program anywhere in /usr/ports? I can see various replacements for cal(1), and a few programs that appear to be X-versions of calendar(1), but nothing that claims to be a better console version of calendar(1). Bah. --=20 David Taylor davidt@yadt.co.uk "The future just ain't what it used to be" --cNdxnHkX5QqsyA0e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8WbXvfIqKXSsJ/xERAnv/AJ9LiGkUiKRSdEvfPMgfepdt64TGdACfa7oG UzHO9enfjAXK5fTfz4SLFFQ= =+sv/ -----END PGP SIGNATURE----- --cNdxnHkX5QqsyA0e-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 13:40:16 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8A6F937B404 for ; Thu, 31 Jan 2002 13:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VLe2V98483; Thu, 31 Jan 2002 13:40:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 13:40:02 -0800 (PST) Message-Id: <200201312140.g0VLe2V98483@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Jin Guojun[ITG]" Subject: Re: bin/34502: ssh can crash the 4.5 system Reply-To: "Jin Guojun[ITG]" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34502; it has been noted by GNATS. From: "Jin Guojun[ITG]" To: parv Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/34502: ssh can crash the 4.5 system Date: Thu, 31 Jan 2002 13:31:50 -0800 parv wrote: > > in message <200201312023.g0VKNex00336@eubie.lbl.gov>, > wrote Jin.Guojun@eubie.lbl.gov thusly... > > > > System: FreeBSD 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Wed Jan 30 09:39:25 PST 2002 > > > > OpenSSH_2.9 FreeBSD localisations 20011202 > > > > >Description: > > Problem 1: > > ssh localhost > > cause system panic. A local user can use it to crash all 4.5 systems. > > i just tried "ssh localhost" w/o any problems on 4.5-release > 2002.01.24.19.00.47 utc. # ssh -v localhost OpenSSH_2.9 FreeBSD localisations 20011202, SSH protocols 1.5/2.0, OpenSSL 0x0090601f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 0 geteuid 0 anon 1 debug1: Connecting to localhost [::1] port 22. debug1: temporarily_use_uid: 0/0 (e=0) debug1: restore_uid debug1: temporarily_use_uid: 0/0 (e=0) ---- crashing Read from remote host peer.lbl.gov: Connection reset by peer Connection to peer.lbl.gov closed. This time I tried as a root who has no ssh set up at all. So, I do not think this is related to .ssh/ set up. I have tried on three machines: Dual 200Mhz Pentium 500Mhz Celeron 700MHz AMD > > > Problem 2: > > > > does not work for protocol 2. After rename authorized_keys to > > x.authorized_keys (i.e., disable protocol 1), then ssh will ask > > password instead of passphase: > > isn't that the way ssh supposed to work: in absence of keys ask the > password? The authorized_keys2 is there (not missing). Below is the manual page: ... SSH protocol version 2 When a user connects using the protocol version 2 different authentica- tion methods are available: At first, the client attempts to authenticate using the public key method. If this method fails password authentica- tion is tried. The public key method is similar to RSA authentication described in the previous section except that the DSA algorithm is used instead of the patented RSA algorithm. The client uses his private DSA key $HOME/.ssh/id_dsa to sign the session identifier and sends the result to the server. The server checks whether the matching public key is listed in $HOME/.ssh/authorized_keys2 and grants access if both the key is found and the signature is correct. The session identifier is derived from a shared Diffie-Hellman value and is only known to the client and the serv- er. If public key authentication fails or is not available a password can be sent encrypted to the remote host for proving the user's identity. This protocol 2 implementation does not yet support Kerberos or OPIE authenti- cation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 14:20:11 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6408337B404 for ; Thu, 31 Jan 2002 14:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VMK1110548; Thu, 31 Jan 2002 14:20:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3B49A37B402 for ; Thu, 31 Jan 2002 14:10:49 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VMAnd07288; Thu, 31 Jan 2002 14:10:49 -0800 (PST) (envelope-from nobody) Message-Id: <200201312210.g0VMAnd07288@freefall.freebsd.org> Date: Thu, 31 Jan 2002 14:10:49 -0800 (PST) From: Hendrik Scholz To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: bin/34507: systerm doesn't permit local login because two pam modules are missing after upgrading to -CURRENT Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34507 >Category: bin >Synopsis: systerm doesn't permit local login because two pam modules are missing after upgrading to -CURRENT >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 14:20:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Hendrik Scholz >Release: 5.0-CURRENT >Organization: NetUSE AG >Environment: FreeBSD deimos.lan.raisdorf.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Jan 31 2 3:01:59 CET 2002 hscholz@deimos.lan.raisdorf.net:/usr/src/sys/i386/compile/D EIMOS5 i386 >Description: I upgraded from 4.5-RELEASE to 4.5-STABLE and then to 5.0-CURRENT. After doing installworld, mergemaster and rebooting the system doesn't allow local login anymore. It keeps saying that it cannot dlopen /usr/lib/pam_login_access.so. If that one is available the system lacks /usr/lib/pam_lastlog.so. >How-To-Repeat: Upgrade to -current from -stable. Simply try to login. >Fix: The pam_login_access und pam_lastlog modules seem to be not compiled. /usr/src/lib/libpam/modules/Makefile doesn't show them. By adding two SUBDIR+= lines to the Makefile and running make && make install the system runs well again. --- Makefile.orig Thu Jan 31 23:57:18 2002 +++ Makefile Thu Jan 31 23:57:52 2002 @@ -32,6 +32,8 @@ .if defined(MAKE_KERBEROS5) && !defined(NOCRYPT) && !defined(NO_OPENSSL) SUBDIR+= pam_krb5 .endif +SUBDIR+= pam_lastlog +SUBDIR+= pam_login_access SUBDIR+= pam_nologin SUBDIR+= pam_opie SUBDIR+= pam_opieaccess >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 14:50: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1FE4237B439 for ; Thu, 31 Jan 2002 14:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VMo1H16019; Thu, 31 Jan 2002 14:50:01 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 14:50:01 -0800 (PST) Message-Id: <200201312250.g0VMo1H16019@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Bill Fumerola Subject: Re: bin/34502: ssh can crash the 4.5 system Reply-To: Bill Fumerola Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34502; it has been noted by GNATS. From: Bill Fumerola To: j_guojun@lbl.gov Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/34502: ssh can crash the 4.5 system Date: Thu, 31 Jan 2002 14:47:17 -0800 On Thu, Jan 31, 2002 at 12:23:40PM -0800, Jin.Guojun@eubie.lbl.gov wrote: > >Description: > Problem 1: > ssh localhost > cause system panic. A local user can use it to crash all 4.5 systems. obviously this doesn't happen for everyone. if a machine crashes, it has a crashdump. there is ample documentation in the handbook on how to retrieve this crashdump. more likely then not, ssh has nothing to do with your machine crashing and its just tickling another bug in the system. we don't know which one though, because you didn't include a crashdump traceback. -- - bill fumerola / fumerola@yahoo-inc.com / billf@FreeBSD.org / billf@mu.org - my anger management counselor can beat up your self-affirmation therapist How-To-Not-Repeat: [ref4-billf] /home/billf > uname -a FreeBSD ref4.freebsd.org 4.5-STABLE FreeBSD 4.5-STABLE #0: Tue Jan 29 18:18:29 PST 2002 cshumway@ref4.freebsd.org:/local0/scratch/obj/usr/src/sys/REF4 i386 [ref4-billf] /home/billf > ssh localhost billf@localhost's password: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 15:20:11 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id BE29E37B400 for ; Thu, 31 Jan 2002 15:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g0VNK1f36014; Thu, 31 Jan 2002 15:20:01 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 15:20:01 -0800 (PST) Message-Id: <200201312320.g0VNK1f36014@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Xavier Beaudouin Subject: Re: kern/34487: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard Reply-To: Xavier Beaudouin Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/34487; it has been noted by GNATS. From: Xavier Beaudouin To: Sheldon Hearn Cc: Subject: Re: kern/34487: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard Date: Thu, 31 Jan 2002 23:17:06 +0100 (CET) Le Thu, 31 Jan 2002, Sheldon Hearn a écrit : > On Thu, 31 Jan 2002 14:48:41 +0100, Xavier Beaudouin wrote: > > > But starting with FreeBSD 4.4 or 4.5, the kernel will lock itself (waiting > > maybe for something it cannot found) just after unsuccesfull probing of ppc0 > > port. > > Can you use boot -v to provide more detail on exactly where the lockup > occurs? Yes sure (using FreeBSD 4.5-RELEASE) floppies : [...] ppc0: parallel port found at 0x378 ppc0: using extended I/O range ppc0: SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus0 bpf0: lp0 attached ed0 failed to probe at port 0x280-0x29f iomem 0xd8000 irq 10 on isa0 fe0 failed to probe at port 0x300-0x31f on isa0 ie0 failed to probe at port 0x300 iomem 0xd0000 irq 10 on isa0 lnc0 failed to probe at port 0x280 irq 10 drq 0 on isa0 cs0 failed to probe at port 0x300-0x31f on isa0 sn0 failed to probe at port 0x300-0x30f irq 10 on isa0 isa_probe_children: probing PnP devices [ Sometimes the kernel locks a this point even if PNP OS is enabled or disabled in the bios... Sometimes it continue and locks on ahc0 card just after "Waiting 15 seconds for SCIS devices to settle" ] > Note the following open PRs relating to ASUS motherboards: > > kern/25909 > kern/28418 > kern/31233 > > See also PR misc/33398, which suggests toggling the "Plug'n'Play OS" > option in the BIOS. > > Also, PR kern/30715 suggests that a bug tickled by the use of PCI slot > #4 on P3B boards was resolved in 4.5-RELEASE. Tryed what thoses PR suggests... but they didn't help me... ;( Thanks again, Don't hesitate to ask me more question and/or tests about the p2b-ds... :) /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. For mail address, please check header of this mails. Spams are not accepted. Caudium: http://caudium.net/, CAMAS webmail: http://camas.caudium.net/ [ Little fortune now ] Those who don't understand UNIX are doomed to reinvent it, poorly. --Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 15:23:34 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from postfix1-2.free.fr (postfix1-2.free.fr [213.228.0.130]) by hub.freebsd.org (Postfix) with ESMTP id 5978D37B4A2; Thu, 31 Jan 2002 15:23:18 -0800 (PST) Received: from online.fr (nas-cbv-3-138-100.dial.proxad.net [62.147.138.100]) by postfix1-2.free.fr (Postfix) with ESMTP id 62DFBAB446; Fri, 1 Feb 2002 00:23:16 +0100 (CET) Message-ID: <3C59D340.E7DC6257@online.fr> Date: Fri, 01 Feb 2002 00:29:04 +0100 From: Thao et Hubert Tournier Organization: Maison X-Mailer: Mozilla 4.78 [en] (Win98; U) X-Accept-Language: fr,en MIME-Version: 1.0 To: sheldonh@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: i386/25889: FDISK lost a partition ! References: <200201301358.g0UDwFp47424@freefall.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, sheldonh@FreeBSD.org wrote: > > Synopsis: FDISK lost a partition ! > > State-Changed-From-To: open->feedback > State-Changed-By: sheldonh > State-Changed-When: Wed Jan 30 05:57:41 PST 2002 > State-Changed-Why: > Anyone able to reproduce this on recent FreeBSD installations? > > http://www.FreeBSD.org/cgi/query-pr.cgi?pr=25889 It's nice to hear from you. I never encountered this problem again (I will have a new chance this week-end during a 4.4R to 4.5R upgrade. This time I will make a backup before :-)). Anyway, I recovered nearly all of my data on the lost partition, although something else had been screwed (maybe in the partition boot sector) apart from the partition entry. I still think that having Fdisk modify only partition entries which have changed would be the way to go. Just my 2c. Have a nice day ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 15:51:33 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mailhost.alphaconcept.fr (host.97.81.23.62.rev.coltfrance.com [62.23.81.97]) by hub.freebsd.org (Postfix) with ESMTP id 3E2EA37B416; Thu, 31 Jan 2002 15:49:04 -0800 (PST) Received: from cfn.ist.utl.pt (NS [210.111.140.195]) by mailhost.alphaconcept.fr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id Z019N5T9; Fri, 1 Feb 2002 00:44:43 +0100 To: From: "Cheech" Subject: Don't Bogart That Joint... 23908 Date: Thu, 31 Jan 2002 03:46:10 -2000 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <20020131234904.3E2EA37B416@hub.freebsd.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Now Offering for your "Sensitive" Delight ... NEW & IMPROVED *** KATHMANDU 2 *** Thanks to recent dramatic advances in the laboratorial processes for the extraction of botanical/herbal alkaloids and glycocides, we are now able to offer what has already been the most incredibly potent marijuana/cannabis alternative available on the planet .... KATHMANDU TEMPLE KIFF!!! It is NEW, IMPROVED and 20 times more stokin'-tokin' potent in its formulation. KATHMANDU 2 ... a viripotent cannabis alternative for blissful regressions of vexatious depressions... * BURNS AND SMOKES EASIER! * TOKES DEEPER! * TASTES SWEETER! * LASTS LONGER! Kathmandu Temple Kiff is a proprietary; Nepalese, sensitive, pipe-smoking/stoking substance. Kathmandu Temple Kiff is indeed the most substantial marijuana/cannabis alternative on the planet. Absolutely Legal! Marvelously Potent! Kathmandu Temple Kiff possesses all of the positive virtues fine ganja/cannabis without any of the negatives. An amalgamation of high concentrates of rare euphoric herbas, Kathmandu is offered in a solid jigget/bar format and is actually more UPLIFTING & POISED than cannabis / marijuana while rendering Euphoria, Happiness, Mood-Enhancement, Stress/Depression Relief and promoting contemplativeness, creativity, better sleep, lucid dreaming ... and enhancing the sexual experience!!! Kathmandu Temple Kiff is simply the best and just a little pinch/snippet of the Kathmandu goes a long, "sensitive" way. Just 4 or 5 draws of the pipe ... (an herb pipe included with each package of Kathmandu Temple Kiff). PLEASE NOTE: Although no botanical factor in Kathmandu Temple Kiff is illegal or considered to be harmful by regulatory agencies and no tobacco is included therein, it is the policy of our company that Kathmandu Temple Kiff may not be offered or sold to any person that has not attained at least 21 years of age. So power-smokin potent is our new formulation, that much to our delight and actually even to our amazement, we have even be able to establish a very happy clientele within the hard core stoner market. Here is what our customers are saying about Kathmandu Temple Kiff: "Thank you so much for the Temple Kiff. It is everything you guys claim, and then some! I was a bit skeptical when I read your description of its effects, but there is literally no exaggeration in your advertisements. How nice that this is legal! It tastes great and feels great too! I am so glad I took a chance and ordered. Blessings to all of you." -- Frankie R. "I'm a man of my 40's and I really know my stuff. I don't drink or do illegal drugs anymore and have found a much more spiritual path. I used to have to take Valium in the past. Not anymore with the Temple Kiff. It really amazes me how this stuff tastes exactly like the lebanese red and blond hash I used to smoke in the 70's and it has a much more pleasurable effect. I am very satisfied with this product. I like it a lot and will be a customer for life for sure. Whoever makes this stuff is an ARTIST at it. Who would have thought?! Folks, this is the real stuff! Look no further!!" -- A.J. ************************************************************ Our other fine herbal, botanical products include the following: 1. Sweet Vjestika Aphrodisia Drops (tm); An erotic aphrodisia; sexual intensifier / enhancer liquid amalgamated extract for MEN and WOMEN. 2. "Seventh Heaven" Prosaka Tablets (tm); a botanical alternative to pharmaceutical medications for calm, balance, serenity and joyful living... 3. "Seventh Heaven" Gentle Ferocity Tablets (tm); a most efficacious, non-caffeine, non-ephedrine, non-MaHuang botanical energizer and cutting-edge appetite suppressant... 4. Extreme Martial Arts Botanical Remedies; Equivalence Tablets & Dragon Wing Remedy Spray ... pain management that works to alleviate pain even for arthritis and fibromyalgia sufferers... ********************************************* Sweet Vjestika Aphrodisia Drops (tm) inspires and enhances: * Penile & clitoral sensitivity * Sensitivity to touch * Desire to touch and be touched * Fantasy, lust, rapture, erogenous sensitivity ... * Prolongs and intensifies foreplay, orgasm & climax ********************************************* "Seventh Heaven" Prosaka Tablets ... Entirely natural, proprietary, botanical prescription comprised of uncommon Asian Herbs for Calm, Balance, Serenity and Joyful Living. "Seventh Heaven" Prosaka is indeed a most extraordinary, viripotent, calming, centering, mood-enhancing, holistically-formulated, exotic herbaceous alternative to pharmaceutical medications for depression, anxiety, stress, insomnia, etc. NO side effects! NO dependency! Vivaciously Mellow! ********************************************** "Seventh Heaven" Gentle Ferocity Tablets (tm) ... a non-caffeine, non-ephedrine, non-ephedra, non-MaHuang; viripotent, herbaceous prescription for the dynamic energization of body, mind and spirit. This Gentle Ferocity Formulation is amalgamated in accordance with the fundamental Taoist herbal principle of botanical interactiveness and precursorship which in essence is a molecular equation of the relevant botanical/herbal alkaloids and glycosides interacting with one another to prolificate molecular communion and thereby to achieve demonstrative herbal efficaciousness without negative implication to any aspect of human composition. These Gentle Ferocity Cordial Tablets are incredulously and thoroughly effective. Enjoy! For those of you who seek to achieve most demonstrative/non-invasive/non-prohibitive appetite suppression without the negative implications of ongoing usage of MaHuang Herb, Ephedra/Ephedrine or Caffeine as are so magnaminously utilized in a multitude of herbal "diet aids" entitled as "Thermogenics" ... this is ABSOLUTELY the herbal agenda/product for you!! Entirely Natural! Increases Energy! Increases Metabolism! Decreases Appetite! *********************************************** Extreme Martial Arts Botanical Remedies Eastern culture has long had a treatment for bone, muscle, tendon, ligament, sinew and joint distress, traumas, afflictions and constrictions. We are pleased to offer Equivalence Tablets & Dragon Wing Remedy Spray (Hei Ping Shun) (Hei Long Chibang) PLEASE NOTE: While it is true that all physiological traumas and injuries are unique and that no product can arbitrarily eliminate all of the pain and discomfort in all people all of the time, the combination of Equivalence Tablets (Hei Ping Shun) and Dragon Wing Remedy (Hei Long Chibang) remedial botanicals does guarantee to at the least: 1. Significantly reduce discomfort and pain! (In many instances most, if not all, traumas and distress can be eliminated!) 2. Significantly increase mobility and strength ratio. (Please remember also the significance of proper diet, excercise, rest and prayer.) Equivalence Tablets & Dragon Wing Spray Remedials are comprised of entirely natural botanical factors. While Equivalence Tablets (Hei Ping Shun) and Dragon Wing Remedy Spray (Hei Long Chibang) are extremely effective individually, they are utilized to maximum advantage when used in conjunction with one another. ======================================================== PRICING INFORMATION: 1. SEVENTH HEAVEN KATHMANDU TEMPLE KIFF (tm) One .75 oz. jigget/bar $65.00 One 2.0 oz. jigget/bar $115.00 (Free Capillaris Herba with 2.0 oz. bar. Refer to Capillaris paragraph at end of text) 2. SWEET VJESTIKA APHRODISIA DROPS (tm) One 1.0 oz. bottle $90.00 Two 1.0 oz. bottles $140.00 3. SEVENTH HEAVEN PROSAKA (tm) One 100 tablet tin $40.00 Three 100 tablet tins $105.00 Six 100 tablet tins $185.00 4. SEVENTH HEAVEN GENTLE FEROCITY (tm) One 300 tablet jar $130.00 5. Equivalence Tablets - Each bottle contains 90 - 500mg tablets. ** 3-pack (270 tablets) $83.00 ** 6-pack (540 tablets) $126.00 (save $40.00) ** 9-pack (810 tablets) $159.00 (save $90.00) ** 12-pack (1,080 tablets) $192.00 (save $140.00) 6. Dragon Wing Spray Remedy - Each spray bottle contains 4 liquid oz. ** 3-pack (3 - 4 oz. bottles) $83.00 ** 6-pack (6 - 4 oz. bottles) $126.00 (save $40.00) ** 9-pack (9 - 4 oz. bottles) $159.00 (save $90.00) ** 12-pack (12 - 4 oz. bottles) $192.00 (save $140.00) 7. Dynamic Duo Introductory Offers ** 3-pack Equivalence Tabs & 3-pack Dragon Wing $126.00 (save $40.00) ** 6-pack Equivalence Tabs & 3-pack Dragon Wing $159.00 (save $50.00) ** 9-pack Equivalence Tabs & 6-pack Dragon Wing $215.00 (save $70.00) ** 12-pack Equivalence Tabs & 9-pack Dragon Wing $271.00 (save $80.00) 8. SWEET APHRODISIA INTRO COMBINATION OFFER Includes one, 2.0 oz. jigget/bar of Kathmandu Temple Kiff & one, 1 oz. bottle of Sweet Vjestika Aphrodisia Drops. For $150.00 (Reg. $205.00 Save $55) (Free Capillaris Herba with this intro offer. Refer to Capillaris paragraph at end of text) 9. BODY, MIND, SPIRIT "HEAVENLY" INTRO COMBINATION OFFER Includes one, 2.0 oz. jigget/bar of Kathmandu Temple Kiff & 1 tin (100 tablets) of Seventh Heaven Prosaka. For $125.00 (Reg. $155.00 Save $30) (Free Capillaris Herba with this intro offer. Refer to Capillaris paragraph at end of text) 10. "PURE ENERGY" INTRO COMBINATION OFFER Includes one, 2.0 oz. jigget/bar of Kathmandu Temple Kiff & 1 jar (300 tablets) of Seventh Heaven Gentle Ferocity. For $170.00 (Reg. $245.00 Save $75) (Free Capillaris Herba with this intro offer Refer to Capillaris paragraph at end of text) 11. "SENSITIVE" PREFERENTIAL INTRO COMBINATION OFFER Includes one, 2.0 oz. jigget/bar of Kathmandu Temple Kiff & 1 tin (100 tablets) of Seventh Heaven Prosaka & 1 jar (300 tablets) of Seventh Heaven Gentle Ferocity For $200.00 (Reg. $285.00 Save $85) (Free Capillaris Herba with this intro offer Refer to Capillaris paragraph at end of text.) 12. ULTIMATE HERBACEOUSNESS INTRO COMBINATION OFFER Includes one - 2.0 oz. jigget / bar of Kathmandu Temple Kiff, one - 1 oz. bottle of Sweet Vjestika Aphrodisia Drops, one - 100 tablet tin of Prosaka, and one - 300 count jar of Gentle Ferocity for a deep discounted Retail Price of $260.00 (Reg. $375.00 Save $115) (Free Capillaris Herba with this intro offer Refer to Capillaris paragraph at end of text.) SPECIAL OFFER: For a limited time only, you will receive a FREE personal brass hookah with the Ultimate Herbaceous Intro Offer as our gift to you. This hookah has a retail value of $25.00. ************************************************** ORDERING INFORMATION: For your convenience, you can call us direct with your orders or questions. Call 1-623-974-2295 Monday - Friday -- 10:30 AM to 7:00 PM (Mountain Time) Saturday -- 11:00 AM to 3:00 PM (Mountain Time) For all domestic orders, add $5.00 shipping & handling (shipped U.S. Priority Mail). Add $20.00 for International orders. ************************************************** SPECIAL DISCOUNT & GIFT Call now and receive a FREE botanical gift! With every order for a 2.0 oz. jigget / bar of Kathmandu Temple Kiff or one of our four (4) Intro Combination Offers, we will include as our free gift to you ... a 2.0 oz. package of our ever so sedate, sensitive Asian import, loose-leaf Capillaris Herba for "happy" smoking or brewing ... (a $65.00 retail value). ==================================================== To remove your address from our list, click "Reply" in your email software and type "Remove" in the subject field, then send. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 16:10: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0912337B402 for ; Thu, 31 Jan 2002 16:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g110A2g56788; Thu, 31 Jan 2002 16:10:02 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 16:10:02 -0800 (PST) Message-Id: <200202010010.g110A2g56788@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Hiten Pandya Subject: re: kern/34487: ASUS P2B-DS Problem Reply-To: Hiten Pandya Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/34487; it has been noted by GNATS. From: Hiten Pandya To: freebsd-gnats-submit@FreeBSD.org Cc: kiwi@caudium.net Subject: re: kern/34487: ASUS P2B-DS Problem Date: Fri, 1 Feb 2002 00:04:54 +0000 OK, The following might not help and it does sound stupid :) but I used to get this kind of problem with 4.4, but it wasn't related to FreeBSD. First of all, if you haven't, I suggest that you download the firmware updates. The below URL should help. It is located at the bottom of the page. http://www.asus.com.tw/download/mbdriver/slot1-440bx.htm Also have a look at the below URL, which contains some more fixes for your particular BIOS. Look for the P2B-DS Motherboard, which is somewhere down the page: http://www.abios.com/asus/asus-440bx.html Does your PNP Scan become slow, before this problem, as in, do you get time stops between the PNP Scan. But, putting this in a nutshell, I know that this problem is not related to FreeBSD, though I may be wrong. :) Regards, - Hiten Pandya - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 16:19:48 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id A1E5637B404; Thu, 31 Jan 2002 16:19:40 -0800 (PST) Received: from pool0167.cvx40-bradley.dialup.earthlink.net ([216.244.42.167] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WRQN-00068q-00; Thu, 31 Jan 2002 16:19:27 -0800 Message-ID: <3C59DF0A.8F850B66@mindspring.com> Date: Thu, 31 Jan 2002 16:19:22 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kenneth Culver Cc: David Malone , "Cameron, Frank" , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: <20020131103927.A21783-100000@alpha.yumyumyum.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Kenneth Culver wrote: > > There's actually a seperate TLB bug, but FreeBSD doesn't > > trigger that one, either (Linux can tickle it, when there > > are certain specific circumstances met). > > Well, I think I know what you're talking about, linux allocates agpgart > memory without setting a "non-cacheable" bit, and then the agp card writes > to that memory, but the cpu cached it already, which makes the cache wrong > or something like that, and causes the crashes/hangs. I know this is a > greatly simplified version of the real problem, but I think this is a > linux bug not necesarily an amd bug. No, you are describing the coherency bug in the chipset used for the AGP with AMD processors, which should enforce a coherency cycle, and cache invalidation for AGP based writes of the shared memory region. They are treating it as if it were non-cacheable dual ported SDRAM. There *really* is a bug in P4 and above and in late model AMD chips with 4M pages. It is very easy to reproduce with a few small kernel modifications (to actively use 4M pages) and 256M-512M of RAM. I'll characterize it further and provide the software workaround, for $10,000. It's about 16 machine instructions, if you write it out as code. Meanwhile, Linux and Windows can keep turning off the PSE, and losing 4-14% of their performance, depending on their application. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 16:25: 7 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 0D3B937B400; Thu, 31 Jan 2002 16:25:04 -0800 (PST) Received: from pool0167.cvx40-bradley.dialup.earthlink.net ([216.244.42.167] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WRVd-0000VZ-00; Thu, 31 Jan 2002 16:24:54 -0800 Message-ID: <3C59E050.6564C115@mindspring.com> Date: Thu, 31 Jan 2002 16:24:48 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Cameron, Frank" Cc: 'Kenneth Culver' , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: <7925FCEF327F984DB5885285256F0D3AC9446F@nsc-mail1.nsc.ctc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Cameron, Frank" wrote: > From what was posted on the linux-kernel list the problem is the OS > doing the wrong thing not the hardware. I originally asked the > question (albeit not worded as clearly as I should have) because if > Microsoft and Linux programmers made the same mistake, might > FreeBSD have also. No. FreeBSD does not make active use of 4M pages for anything other than the initial kernel text and data, which is obvious, if you look at /sys/i386/machdep.c. For Linux and Windows, the obvious thing is to not map the memory into an aperture marked cacheable and in a 4M page; it's a coding problem with the use of 4M pages, when memory in them is allocated to AGP. This still doesn't get around the other bug, which happens if you use 4M pages certain obviously useful ways, without waving a dead chicken over certain things. 8-). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 17:20: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id ADA8B37B416 for ; Thu, 31 Jan 2002 17:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g111K1F71283; Thu, 31 Jan 2002 17:20:01 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 17:20:01 -0800 (PST) Message-Id: <200202010120.g111K1F71283@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mike Makonnen Subject: Re: bin/34497: calendar(1) does not understand calendars Reply-To: Mike Makonnen Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34497; it has been noted by GNATS. From: Mike Makonnen To: David Taylor Cc: bug-followup@freebsd.org Subject: Re: bin/34497: calendar(1) does not understand calendars Date: Thu, 31 Jan 2002 17:14:48 -0800 On Thu, 31 Jan 2002 13:30:02 -0800 (PST) David Taylor wrote: > The code is rather weird and obfusciated, but I managed to create a fix > for the specific problem reported, but that doesn't stop '2002-01-33' > being misinterpreted, along with other problems that cropped up.... Hah! That's an understatement! Calendar(1) could be used as a prime example of how *not* to write code. > > However, I don't have enough time to write a calendar(1) replacement from > scratch.. There's also a few other bugs in the code that I have come accross (i.e. - it can't handle 'the first Thursday of every month') and which I thought about fixing, but I've been putting it off because of the time it would take. I'm in agreement with you: any way you look at it the *only* solution IMO is to rewrite the damned thing. Now that I know others would be interested in getting it fixed I'm willing to go ahead and do that if a committer is willing to take a look at my code. cheers, mike makonnen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 17:20:21 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EC2E437B400 for ; Thu, 31 Jan 2002 17:20:05 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g111K5e71306; Thu, 31 Jan 2002 17:20:05 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 17:20:05 -0800 (PST) Message-Id: <200202010120.g111K5e71306@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Xavier Beaudouin Subject: re: kern/34487: ASUS P2B-DS Problem Reply-To: Xavier Beaudouin Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/34487; it has been noted by GNATS. From: Xavier Beaudouin To: Hiten Pandya Cc: Subject: re: kern/34487: ASUS P2B-DS Problem Date: Fri, 1 Feb 2002 01:14:56 +0100 (CET) Hi Hiten, > > OK, The following might not help and it does sound stupid :) but I used > to get this kind of problem with 4.4, but it wasn't related to FreeBSD. > > First of all, if you haven't, I suggest that you download the firmware > updates. The below URL should help. It is located at the bottom of the > page. > > http://www.asus.com.tw/download/mbdriver/slot1-440bx.htm > > Also have a look at the below URL, which contains some more fixes for > your particular BIOS. Look for the P2B-DS Motherboard, which is somewhere > down the page: > > http://www.abios.com/asus/asus-440bx.html Ok I did some hunting.... and found BIOS release 1013 that does update the Adaptec BIOS... (I was using 1012B from a previous update 3 days ago because I was suspecting something like this...). So now with BIOS 1013 the install boot disk boots and install :) Great :) > Does your PNP Scan become slow, before this problem, as in, do you > get time stops between the PNP Scan. > > But, putting this in a nutshell, I know that this problem is not > related to FreeBSD, though I may be wrong. :) > Yes you are totaly right... I just didn't notice this update :) Thanks for the support :) You are were very helpfull :) Sincerly, /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. For mail address, please check header of this mails. Spams are not accepted. Caudium: http://caudium.net/, CAMAS webmail: http://camas.caudium.net/ [ Little fortune now ] Those who don't understand UNIX are doomed to reinvent it, poorly. --Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 17:23:52 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with SMTP id A9A4137B402 for ; Thu, 31 Jan 2002 17:23:42 -0800 (PST) Received: (qmail 219 invoked by uid 1001); 1 Feb 2002 01:23:41 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Feb 2002 01:23:41 -0000 Date: Thu, 31 Jan 2002 20:23:41 -0500 (EST) From: Kenneth Culver To: =?ISO-8859-1?Q?G=E9rard_Roudier?= Cc: "Cameron, Frank" , Terry Lambert , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: RE: AMD AGP Bug In-Reply-To: <20020130225003.C2570-100000@gerard> Message-ID: <20020131202226.L209-100000@alpha.yumyumyum.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm thinking you may have misunderstood, the people at amd themselves said this wasn't an amd bug... why would you write from cache to memory, I think it's the other way around, stuff getting written to cache from memory... (being retrieved by the cpu) I'll have to read the article again to be sure since it was a week ago when I read it. Ken On Wed, 30 Jan 2002, [ISO-8859-1] G=E9rard Roudier wrote: > > > On Thu, 31 Jan 2002, Kenneth Culver wrote: > > > Yeah, that's what I saw on linux-kernel... > > You probably didn't see the whole story or just did a too selective > reading. You should re-read, in my opinion, since you may have just misse= d > the important part. > > What I understood is that the Athlon allocates cache lines for speculativ= e > writes (if write may hit cachable) and such cache lines are flushed to > memory even if the write does not happen. As a result, numerous useless > writes to memory may happen under any OS. > > This does not cause visible issue for memory that is required to be cache > coherent. Just AGP accesses are not required to be snooped by cache for > performance concerns and as memory given to AGP is intended to contain > data as textures that should not need tight synchronisation with CPU. > > Indeed Linux has cached mapping to AGP memory and this could be avoided. > Nevertheless, only strange issues like the AMD AGP bug we are talking > about could turn this into a real problem. > > Linux can be fixed, but the useless writes of the existing Athlons from > the very fast cache to the relatively very slow memory cannot. And all > Athlon users may well pay this penalty under any OS... unless we want to > disable caching. :) > > Btw, I have 2 Athlon 1.2GHz machines that work just fine and fast for me. > > G=E9rard. > > > > Ken > > > > On Thu, 31 Jan 2002, Cameron, Frank wrote: > > > > > From what was posted on the linux-kernel list the problem is the OS > > > doing the wrong thing not the hardware. I originally asked the > > > question (albeit not worded as clearly as I should have) because if > > > Microsoft and Linux programmers made the same mistake, might > > > FreeBSD have also. > > > > > > > -----Original Message----- > > > > From: Kenneth Culver [mailto:culverk@yumyumyum.org] > > > > Sent: Thursday, January 31, 2002 10:42 AM > > > > To: Terry Lambert > > > > Cc: David Malone; Cameron, Frank; 'freebsd-bugs@freebsd.org'; > > > > 'freebsd-current@freebsd.org' > > > > Subject: Re: AMD AGP Bug > > > > > > > > > > > > > There's actually a seperate TLB bug, but FreeBSD doesn't > > > > > trigger that one, either (Linux can tickle it, when there > > > > > are certain specific circumstances met). > > > > > > > > > Well, I think I know what you're talking about, linux > > > > allocates agpgart > > > > memory without setting a "non-cacheable" bit, and then the > > > > agp card writes > > > > to that memory, but the cpu cached it already, which makes > > > > the cache wrong > > > > or something like that, and causes the crashes/hangs. I know this i= s a > > > > greatly simplified version of the real problem, but I think this is= a > > > > linux bug not necesarily an amd bug. > > > > > > > > Ken > > > > > > > > > > > > > > > > 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-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 18:10: 8 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1C06D37B405 for ; Thu, 31 Jan 2002 18:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g112A3t87375; Thu, 31 Jan 2002 18:10:03 -0800 (PST) (envelope-from gnats) Date: Thu, 31 Jan 2002 18:10:03 -0800 (PST) Message-Id: <200202010210.g112A3t87375@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Jin Guojun[ITG]" Subject: Re: bin/34502: ssh can crash the 4.5 system Reply-To: "Jin Guojun[ITG]" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34502; it has been noted by GNATS. From: "Jin Guojun[ITG]" To: Bill Fumerola Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/34502: ssh can crash the 4.5 system Date: Thu, 31 Jan 2002 18:00:48 -0800 Bill Fumerola wrote: > > On Thu, Jan 31, 2002 at 12:23:40PM -0800, Jin.Guojun@eubie.lbl.gov wrote: > > > >Description: > > Problem 1: > > ssh localhost > > cause system panic. A local user can use it to crash all 4.5 systems. > > obviously this doesn't happen for everyone. if a machine crashes, it has > a crashdump. there is ample documentation in the handbook on how to > retrieve this crashdump. more likely then not, ssh has nothing to do > with your machine crashing and its just tickling another bug in the > system. we don't know which one though, because you didn't include a > crashdump traceback. This is odd. The dump reports panic somewhere in tcp_input(). So, I recompiled all tcp_*.o with -g option (not entire kernel), then problem goes away. A couple of things I encounted during the installation was some /dev/md0 errors related to two things: (1) when entired a wrong DNS IP, after system hanging for a while, typed in a correct IP, the system did not accept the new one and keep hanging. Hit ^C to restart the installation over, then saw a /dev/md0 error. (2) when read mfsroot, I saw /dev/md0 errors. This type error may cause installation failure. However, I have no idea what really caused /dev/md0 errors. The source I download was a few of hours prior to the 4.5-RELEASE stably released to ftp.freebsd.org. I will try to download the 4.5 source again and reinstall some systems to see if problem still persists. -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 18:17:57 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 0DE3937B404; Thu, 31 Jan 2002 18:17:49 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020201021748.OHHG10199.rwcrmhc53.attbi.com@peter3.wemm.org>; Fri, 1 Feb 2002 02:17:48 +0000 Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id g112Hls57876; Thu, 31 Jan 2002 18:17:47 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id A50863809; Thu, 31 Jan 2002 18:17:47 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: "Cameron, Frank" , "'Kenneth Culver'" , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug In-Reply-To: <3C59E050.6564C115@mindspring.com> Date: Thu, 31 Jan 2002 18:17:47 -0800 From: Peter Wemm Message-Id: <20020201021747.A50863809@overcee.wemm.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > "Cameron, Frank" wrote: > > From what was posted on the linux-kernel list the problem is the OS > > doing the wrong thing not the hardware. I originally asked the > > question (albeit not worded as clearly as I should have) because if > > Microsoft and Linux programmers made the same mistake, might > > FreeBSD have also. > > No. FreeBSD does not make active use of 4M pages for anything > other than the initial kernel text and data, which is obvious, > if you look at /sys/i386/machdep.c. Actually, it is obvious if you actually do look at the pmap.c that we *do* use 4MB pages for device mappings. /* * This code maps large physical mmap regions into the * processor address space. Note that some shortcuts * are taken, but the code works. */ if (pseflag && (object->type == OBJT_DEVICE) && ((addr & (NBPDR - 1)) == 0) && ((size & (NBPDR - 1)) == 0)) { ... for(i = 0; i < npdes; i++) { pmap->pm_pdir[ptepindex] = ptepa | PG_U | PG_RW | PG_V | PG_PS; ptepa += NBPDR; ptepindex += 1; } ... Even doing a simple grep for the 4MB page flag (PG_PS) and using a little initiative would have shown this. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 18:21:21 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 309B637B405; Thu, 31 Jan 2002 18:21:13 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020201022112.QWFR26243.rwcrmhc51.attbi.com@peter3.wemm.org>; Fri, 1 Feb 2002 02:21:12 +0000 Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id g112LCs57915; Thu, 31 Jan 2002 18:21:12 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id 227833809; Thu, 31 Jan 2002 18:21:12 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Kenneth Culver Cc: "Cameron, Frank" , Terry Lambert , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug In-Reply-To: <20020131135127.V22577-100000@alpha.yumyumyum.org> Date: Thu, 31 Jan 2002 18:21:12 -0800 From: Peter Wemm Message-Id: <20020201022112.227833809@overcee.wemm.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Kenneth Culver wrote: > Yeah, that's what I saw on linux-kernel... > > Ken We need to use the PAT cpu_features feature. This gives us 8 page attribute modes instead of simple no-cache / writethrough flags. We can (and must) control more carefully the speculative hardware prefetch, for example. I've been thinking about this with the pmap revamp that I'm working on. It may solve the athlon problems too. > On Thu, 31 Jan 2002, Cameron, Frank wrote: > > > From what was posted on the linux-kernel list the problem is the OS > > doing the wrong thing not the hardware. I originally asked the > > question (albeit not worded as clearly as I should have) because if > > Microsoft and Linux programmers made the same mistake, might > > FreeBSD have also. > > > > > -----Original Message----- > > > From: Kenneth Culver [mailto:culverk@yumyumyum.org] > > > Sent: Thursday, January 31, 2002 10:42 AM > > > To: Terry Lambert > > > Cc: David Malone; Cameron, Frank; 'freebsd-bugs@freebsd.org'; > > > 'freebsd-current@freebsd.org' > > > Subject: Re: AMD AGP Bug > > > > > > > > > > There's actually a seperate TLB bug, but FreeBSD doesn't > > > > trigger that one, either (Linux can tickle it, when there > > > > are certain specific circumstances met). > > > > > > > Well, I think I know what you're talking about, linux > > > allocates agpgart > > > memory without setting a "non-cacheable" bit, and then the > > > agp card writes > > > to that memory, but the cpu cached it already, which makes > > > the cache wrong > > > or something like that, and causes the crashes/hangs. I know this is a > > > greatly simplified version of the real problem, but I think this is a > > > linux bug not necesarily an amd bug. > > > > > > Ken > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message > Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 18:31:34 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 26E2037B417; Thu, 31 Jan 2002 18:31:30 -0800 (PST) Received: (from archie@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g112O7F89238; Thu, 31 Jan 2002 18:24:07 -0800 (PST) (envelope-from archie) Date: Thu, 31 Jan 2002 18:24:07 -0800 (PST) From: Message-Id: <200202010224.g112O7F89238@freefall.freebsd.org> To: richard@xebeo.com, archie@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/29150: Incomplete cleanup in the netgraph bridge shutdown function Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Incomplete cleanup in the netgraph bridge shutdown function State-Changed-From-To: open->closed State-Changed-By: archie State-Changed-When: Thu Jan 31 18:23:24 PST 2002 State-Changed-Why: Fixed in revisions 1.12 (-current) and 1.1.2.4 (-stable). http://www.FreeBSD.org/cgi/query-pr.cgi?pr=29150 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 19:23:49 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 3691437B404; Thu, 31 Jan 2002 19:23:46 -0800 (PST) Received: from pool0289.cvx40-bradley.dialup.earthlink.net ([216.244.43.34] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WUId-0006Re-00; Thu, 31 Jan 2002 19:23:39 -0800 Message-ID: <3C5A09F1.CD638C3E@mindspring.com> Date: Thu, 31 Jan 2002 19:22:25 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Kenneth Culver , "Cameron, Frank" , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: <20020201022112.227833809@overcee.wemm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Peter Wemm wrote: > We need to use the PAT cpu_features feature. This gives us 8 page attribute > modes instead of simple no-cache / writethrough flags. We can (and must) > control more carefully the speculative hardware prefetch, for example. > > I've been thinking about this with the pmap revamp that I'm working on. > It may solve the athlon problems too. This sounds cool. Do you have references to the page attribute stuff? The books I have here don't discuss it; the only thing I see are 3 bits (9,10,11) that are "available" in the PDE and PTE? -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 19:24: 8 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 0A01337B405; Thu, 31 Jan 2002 19:23:50 -0800 (PST) Received: from pool0289.cvx40-bradley.dialup.earthlink.net ([216.244.43.34] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WUIZ-0006Ei-00; Thu, 31 Jan 2002 19:23:36 -0800 Message-ID: <3C5A07AE.FE08CC34@mindspring.com> Date: Thu, 31 Jan 2002 19:12:46 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: "Cameron, Frank" , 'Kenneth Culver' , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: <20020201021747.A50863809@overcee.wemm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Peter Wemm wrote: > > No. FreeBSD does not make active use of 4M pages for anything > > other than the initial kernel text and data, which is obvious, > > if you look at /sys/i386/machdep.c. > > Actually, it is obvious if you actually do look at the pmap.c that we *do* > use 4MB pages for device mappings. The "active use" I was referring to was kernel space, and this sets PG_U, so there are not fault handler invocations on attempts to write the pages. This code also does not set the PG_G bit, like Linux does. This code has a requirement that the address mapping occur on a 4M boundary, and that it be an even multiple of 4M. My reading of the AGPGART kernel module indicates to me that this code is not triggered in normal use. Correct me if my interpretation here is wrong (I'd like to know *how*; the default aperture appears to be 1M, unless it is overridden, and the alignment isn't on the right boundary). In any case, let's say that it gets invoked on the AGP hardware, and establishes a 4M mapping on FreeBSD, as well. I think the Linux problem has more to do with having *both* 4K and 4M mappings to the same physical memory area at the same time. FreeBSD avoids doing this to active pages; the initial setup replaces the PDE and "loses" the 4K worth of 4K mapping tables, and the later code that you reference doesn't replace any existing entries. It's accidental, but still, it should mean that FreeBSD is not succeptible to the problem. The real hint in characterizing the problem is to ask "why does it happen with 4M pages, but doesn't also happen with 4K pages?". This indicates that the problem is really a TLB problem, and therefore a real processor problem: the problem should happen no matter what, if it's a problem with writing to mapped memory use by the AGP not giving an invalidation signal to the CPU on writes, rather than a problem in the CPUs handling of 4M page invalidation itself, a problem that does not exist in the 4K invalidation case. Unfortuantely, I would need to upgrade both my FreeBSD and my XFree86 to try this with the AGP on my AMD box (it has a 0x7121 ID, and so can't GARTIOCINFO correctly) to be able to even try to repeat the problem, and Fry's does not appear to be selling FreeBSD CDROM sets any more, even with the books attached. 8-(. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 19:49:48 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id AD9BC37B419; Thu, 31 Jan 2002 19:49:39 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.4/8.11.4) id g113nP293173; Thu, 31 Jan 2002 19:49:25 -0800 (PST) (envelope-from sgk) Date: Thu, 31 Jan 2002 19:49:24 -0800 From: Steve Kargl To: Terry Lambert Cc: Peter Wemm , Kenneth Culver , "Cameron, Frank" , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug Message-ID: <20020131194924.A93144@troutmask.apl.washington.edu> References: <20020201022112.227833809@overcee.wemm.org> <3C5A09F1.CD638C3E@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C5A09F1.CD638C3E@mindspring.com>; from tlambert2@mindspring.com on Thu, Jan 31, 2002 at 07:22:25PM -0800 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jan 31, 2002 at 07:22:25PM -0800, Terry Lambert wrote: > Peter Wemm wrote: > > We need to use the PAT cpu_features feature. This gives us 8 page attribute > > modes instead of simple no-cache / writethrough flags. We can (and must) > > control more carefully the speculative hardware prefetch, for example. > > > > I've been thinking about this with the pmap revamp that I'm working on. > > It may solve the athlon problems too. > > This sounds cool. > > Do you have references to the page attribute stuff? The > books I have here don't discuss it; the only thing I see > are 3 bits (9,10,11) that are "available" in the PDE and > PTE? > Well, twice in this thread you've offered info for $10000. I'm sure Peter can reciprocate with the info you seek for a similar price. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 20:42:54 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by hub.freebsd.org (Postfix) with ESMTP id 080BA37B404; Thu, 31 Jan 2002 20:42:49 -0800 (PST) Received: from aldan.algebra.com (localhost [127.0.0.1]) by aldan.algebra.com (8.11.6/8.11.5) with ESMTP id g114fnQ27638; Thu, 31 Jan 2002 23:41:51 -0500 (EST) (envelope-from mi@aldan.algebra.com) Message-Id: <200202010441.g114fnQ27638@aldan.algebra.com> Date: Thu, 31 Jan 2002 23:41:46 -0500 (EST) From: Mikhail Teterin Subject: Re: bin/14448: ftp-client may not recognize failure, report erroneous stats To: iedowse@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <200201212126.g0LLQDI31167@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 21 Jan, iedowse@FreeBSD.org wrote: No, now the reporting is correct: /tmp: write failed, file system is full ftp: local: 4.5-mini.iso: No space left on device 16% |********** | 28513 KB 23.56 KB/s 1:45:18 ETA 451 Transfer aborted. Broken pipe 29197472 bytes received in 20:11 (23.52 KB/s) -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 23:21:35 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EAA2E37B402; Thu, 31 Jan 2002 23:21:29 -0800 (PST) Received: (from dinoex@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g117Hv343942; Thu, 31 Jan 2002 23:17:57 -0800 (PST) (envelope-from dinoex) Date: Thu, 31 Jan 2002 23:17:57 -0800 (PST) From: Message-Id: <200202010717.g117Hv343942@freefall.freebsd.org> To: dinoex@FreeBSD.org, freebsd-bugs@FreeBSD.org, dinoex@FreeBSD.org Subject: Re: gnu/21128: a proposed patch for uucp package Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: a proposed patch for uucp package Responsible-Changed-From-To: freebsd-bugs->dinoex Responsible-Changed-By: dinoex Responsible-Changed-When: Thu Jan 31 23:17:21 PST 2002 Responsible-Changed-Why: I will look into thios. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=21128 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 23:21:36 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id EB2FD37B404; Thu, 31 Jan 2002 23:21:30 -0800 (PST) Received: (from dinoex@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g117FXu43576; Thu, 31 Jan 2002 23:15:33 -0800 (PST) (envelope-from dinoex) Date: Thu, 31 Jan 2002 23:15:33 -0800 (PST) From: Message-Id: <200202010715.g117FXu43576@freefall.freebsd.org> To: dinoex@FreeBSD.org, freebsd-bugs@FreeBSD.org, dinoex@FreeBSD.org Subject: Re: misc/3225: [PATCH] uucpd.c should normalize host names as login does Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: [PATCH] uucpd.c should normalize host names as login does Responsible-Changed-From-To: freebsd-bugs->dinoex Responsible-Changed-By: dinoex Responsible-Changed-When: Thu Jan 31 23:15:08 PST 2002 Responsible-Changed-Why: Now part of ports, I will look into this http://www.FreeBSD.org/cgi/query-pr.cgi?pr=3225 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 23:21:37 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8529A37B416; Thu, 31 Jan 2002 23:21:31 -0800 (PST) Received: (from dinoex@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g117H5r43798; Thu, 31 Jan 2002 23:17:05 -0800 (PST) (envelope-from dinoex) Date: Thu, 31 Jan 2002 23:17:05 -0800 (PST) From: Message-Id: <200202010717.g117H5r43798@freefall.freebsd.org> To: dinoex@FreeBSD.org, freebsd-bugs@FreeBSD.org, dinoex@FreeBSD.org Subject: Re: conf/16536: size of /var/spool/uucp/Log, a UUCP logfile, grows forever Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: size of /var/spool/uucp/Log, a UUCP logfile, grows forever Responsible-Changed-From-To: freebsd-bugs->dinoex Responsible-Changed-By: dinoex Responsible-Changed-When: Thu Jan 31 23:16:06 PST 2002 Responsible-Changed-Why: Now part of ports, I will look into this. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=16536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 23:40:17 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 39E2837B417 for ; Thu, 31 Jan 2002 23:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g117e1f49002; Thu, 31 Jan 2002 23:40:01 -0800 (PST) (envelope-from gnats) Received: from ms1.nttdata.co.jp (ms1.nttdata.co.jp [163.135.193.232]) by hub.freebsd.org (Postfix) with ESMTP id ED7BA37B402 for ; Thu, 31 Jan 2002 23:33:58 -0800 (PST) Received: from mail0.nttdata.co.jp ([163.135.10.20]) by ms1.nttdata.co.jp (8.9.3/3.7W-NTTDATA-TOP-11/07/01) with ESMTP id QAA29629 for ; Fri, 1 Feb 2002 16:33:45 +0900 (JST) Received: from norisuke.sc.biz.nttdata.co.jp (localhost [127.0.0.1]) by mail0.nttdata.co.jp (8.9.3/3.7W-NTTDmx/01110714) with ESMTP id QAA03452 for ; Fri, 1 Feb 2002 16:30:51 +0900 (JST) Received: by norisuke.sc.biz.nttdata.co.jp (Postfix, from userid 0) id 2698A15B80; Fri, 1 Feb 2002 16:33:56 +0900 (JST) Received: from taiko.sc.biz.nttdata.co.jp (localhost [127.0.0.1]) by norisuke.sc.biz.nttdata.co.jp (Postfix) with ESMTP id B8AD733EA9; Fri, 1 Feb 2002 16:33:55 +0900 (JST) Received: from namihei.sc.biz.nttdata.co.jp (namihei.sc.biz.nttdata.co.jp [10.41.133.36]) by taiko.sc.biz.nttdata.co.jp (8.12.1/8.12.1/taiko-20011211) with ESMTP id g117Xs0m006213; Fri, 1 Feb 2002 16:33:55 +0900 (JST) Received: from classic.sc.biz.nttdata.co.jp (classic.sc.biz.nttdata.co.jp [10.41.132.81]) by namihei.sc.biz.nttdata.co.jp (Postfix) with ESMTP id AC78E2F8CE; Fri, 1 Feb 2002 16:33:54 +0900 (JST) Received: (from joshua@localhost) by classic.sc.biz.nttdata.co.jp (8.11.6/8.11.6) id g117XrI01476; Fri, 1 Feb 2002 16:33:53 +0900 (JST) (envelope-from joshua) Message-Id: <200202010733.g117XrI01476@classic.sc.biz.nttdata.co.jp> Date: Fri, 1 Feb 2002 16:33:53 +0900 (JST) From: SHIMIZU Yoshiaki Reply-To: SHIMIZU Yoshiaki To: FreeBSD-gnats-submit@freebsd.org Cc: shimizuysa@nttdata.co.jp X-Send-Pr-Version: 3.113 Subject: bin/34519: pkg_check(8) does not return exit code >0 if verifing in case of PKG_UNSIGNED or PKG_SIGUNKNOWN Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34519 >Category: bin >Synopsis: pkg_check(8) does not return exit code >0 if verifing in case of PKG_UNSIGNED or PKG_SIGUNKNOWN >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jan 31 23:40:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: SHIMIZU Yoshiaki >Release: FreeBSD 4.5-STABLE i386 >Organization: NTT Data CORPORATION >Environment: System: FreeBSD classic.sc.biz.nttdata.co.jp 4.5-STABLE FreeBSD 4.5-STABLE #0: Thu Jan 31 16:31:05 JST 2002 joshua@classic.sc.biz.nttdata.co.jp:/usr/obj/usr/src/sys/CLASSIC i386 >Description: DIAGNOSTICS of pkg_check(8) manpage says : pkg_sign and pkg_check return with an exit code >0 if anything went wrong for any file. For pkg_check, this usually indicates that the package is not signed, or that the signature is forged. However, when verifying non-signed or non-gziped file (both PKG_UNSIGNED case), pkg_check(8) returns exit code =0 with warnning message. I use only `-t x509' option-type, but Maybe using `-t sha-1' option-type `PKG_UNKNOWN' case is looks same. It's makes problem, when detecting package integrity mismatch in shell-scripts. >How-To-Repeat: # pkg_check -t x509 -k VALID_CRT PKG_UNSIGNED.tar.gz File UNSIGNED.tar.gz is not a signed gzip file # echo $? 0 >Fix: /* $FreeBSD: src/usr.sbin/pkg_install/sign/main.c,v 1.1.2.1 2001/03/05 03:43:53 wes Exp $ */ ====== --- src/usr.sbin/pkg_install/sign/main.c.orig Mon Mar 5 12:43:53 2001 +++ src/usr.sbin/pkg_install/sign/main.c Tue Jan 29 20:30:00 2002 @@ -83,7 +83,7 @@ } result = check_signature(file, userid, envp, filename); if (fclose(file) == 0) { - if (result == PKG_BADSIG || result == PKG_SIGERROR) + if (result == PKG_BADSIG || result == PKG_UNSIGNED || result == PKG_SIGERROR || result == PKG_UNKNOWN) return 0; else return 1; >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Thu Jan 31 23:45:46 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from scaup.prod.itd.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by hub.freebsd.org (Postfix) with ESMTP id 98D3937B41C; Thu, 31 Jan 2002 23:45:28 -0800 (PST) Received: from pool0004.cvx22-bradley.dialup.earthlink.net ([209.179.198.4] helo=mindspring.com) by scaup.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WYNj-0007ml-00; Thu, 31 Jan 2002 23:45:12 -0800 Message-ID: <3C5A477E.73E85017@mindspring.com> Date: Thu, 31 Jan 2002 23:45:02 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Steve Kargl Cc: Peter Wemm , Kenneth Culver , "Cameron, Frank" , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: <20020201022112.227833809@overcee.wemm.org> <3C5A09F1.CD638C3E@mindspring.com> <20020131194924.A93144@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Steve Kargl wrote: > > This sounds cool. > > > > Do you have references to the page attribute stuff? The > > books I have here don't discuss it; the only thing I see > > are 3 bits (9,10,11) that are "available" in the PDE and > > PTE? > > > > Well, twice in this thread you've offered info for > $10000. I'm sure Peter can reciprocate with the > info you seek for a similar price. 8-). The info I offered is unrelated to FreeBSD. It lets the Linux people and the Windows people turn the PSE back on. They can afford it where FreeBSD can't. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 0: 0:21 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6FC5137B41A for ; Fri, 1 Feb 2002 00:00:08 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11808752133; Fri, 1 Feb 2002 00:00:08 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 3DB3B37B400 for ; Thu, 31 Jan 2002 23:59:54 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g117xsh52079; Thu, 31 Jan 2002 23:59:54 -0800 (PST) (envelope-from nobody) Message-Id: <200202010759.g117xsh52079@freefall.freebsd.org> Date: Thu, 31 Jan 2002 23:59:54 -0800 (PST) From: Andryan To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: i386/34521: Upgrade problem Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34521 >Category: i386 >Synopsis: Upgrade problem >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 01 00:00:03 PST 2002 >Closed-Date: >Last-Modified: >Originator: Andryan >Release: FreeBSD 4.2-RELEASE >Organization: Alternative Web Services >Environment: >Description: I have done cvsup, make buildworld, make kernel, make installworld and mergemaster (using the "upgrade from src" reference from the handbook). I rebooted it, it went back online (box is remote box) and pingable. Once I attempt a connection to ANY open port to the box, the ping stops and start giving RTOs, the box is not running firewall nor NAT. I asked the hosting company to boot with generic kernel and scanned the syslog. Nothing useful there and I found out that everytime I attempted a connection to ANY open port, it will reboot. I tried doing the make buildkernel with my own conf and GENERIC, both resulted the same. I had to do make installworld in multiuser mode b/c I don't have physical access to the box. More info, the box specs: AMD Duron 600MHz 128MB RAM Intel Express Pro 10/100 >How-To-Repeat: Upgrade FreeBSD 4.2 RELEASE using cvsup and make buildworld, buildkernel, installkernel, installworld and do mergemaster. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 0:14:55 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 5C08A37B6C6; Fri, 1 Feb 2002 00:06:03 -0800 (PST) Received: from pool0004.cvx22-bradley.dialup.earthlink.net ([209.179.198.4] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WYgW-0002Y9-00; Fri, 01 Feb 2002 00:04:37 -0800 Message-ID: <3C5A4C0C.16F8426E@mindspring.com> Date: Fri, 01 Feb 2002 00:04:28 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Glendon Gross Cc: Steve Kargl , Peter Wemm , Kenneth Culver , "Cameron, Frank" , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Glendon Gross wrote: > That's right, guys! This is FreeBSD after all... so Mr. Lambert is > entitled to charge 10K for that bugfix code if he wants. In fact he is > "Free" to do so. But it's a little pricy for me, although perhaps not for > AMD if it means they can fix their cache-paging problems! It cost me two weeks to figure out, and both Intel and AMD wanted to charge me $$$ to file a problem report. I once fixed a Borland library problem which was pretty serious: it would effect all programs that did string manipulation, and linked the standard library, instead of using the compiler generated inlines. They wanted to charge me to file a bug report, too, so I demanded that they agree to send me a T-shirt before I would tell them the fix. As far as I know, they still have the bug. Microsoft also charged me to report a bug in the removable media driver in Windows 95/98 (you can't safely page to it because it fails to propagate some writes it's supposed to propagate, so you can'tt safely install Windows on a JAZ or Syquest cartridge, because paging fails). I made them admit the problem, and they credited the incident report after they admitted it was their issue, but it still started my 90 day support clock, so that it wasn't there when I needed it, later. Since it's not a FreeBSD problem, you'll forgive me if I find it funny that Linux and Windows disables the PSE to work around some problems. It's not that hard to understand or work around, if you know where to look, and knowing where to look is what will cost them. The *other* AMD problem, with AGP and 4K and 4M pages that point to the same memory could arguably be a chipset or a software problem (depending on whether or not the chipset vendor has documented the behaviour before people were let loose to write the software -- errata: the difference between a software problem and a software workaround to a hardware problem). It's already documented how to work around that one; I'm sure a fix is pending for Linux, and Windows will probably leave PSE off until they can figure out a way to update everyone. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 0:34:30 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id B419A37B405; Fri, 1 Feb 2002 00:34:22 -0800 (PST) Received: from peter3.wemm.org ([12.232.27.13]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020201083418.UGYE3578.rwcrmhc52.attbi.com@peter3.wemm.org>; Fri, 1 Feb 2002 08:34:18 +0000 Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id g118YIs58956; Fri, 1 Feb 2002 00:34:18 -0800 (PST) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (Postfix) with ESMTP id C3FFC3809; Fri, 1 Feb 2002 00:34:17 -0800 (PST) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Terry Lambert Cc: Glendon Gross , Steve Kargl , Kenneth Culver , "Cameron, Frank" , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug In-Reply-To: <3C5A4C0C.16F8426E@mindspring.com> Date: Fri, 01 Feb 2002 00:34:17 -0800 From: Peter Wemm Message-Id: <20020201083417.C3FFC3809@overcee.wemm.org> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Terry Lambert wrote: > Glendon Gross wrote: > > That's right, guys! This is FreeBSD after all... so Mr. Lambert is > > entitled to charge 10K for that bugfix code if he wants. In fact he is > > "Free" to do so. But it's a little pricy for me, although perhaps not for > > AMD if it means they can fix their cache-paging problems! > > It cost me two weeks to figure out, and both Intel and AMD > wanted to charge me $$$ to file a problem report. [..] > Since it's not a FreeBSD problem, you'll forgive me if I > find it funny that Linux and Windows disables the PSE to work > around some problems. It's not that hard to understand or > work around, if you know where to look, and knowing where to > look is what will cost them. [..] > The *other* AMD problem, with AGP and 4K and 4M pages that > point to the same memory could arguably be a chipset or a > software problem (depending on whether or not the chipset > vendor has documented the behaviour before people were let > loose to write the software -- errata: the difference > between a software problem and a software workaround to a > hardware problem). It's already documented how to work > around that one; I'm sure a fix is pending for Linux, and > Windows will probably leave PSE off until they can figure > out a way to update everyone. I'm a little confused as to which bugs are which that we're talking about now. Which is the one that you're trying to sell the info for? The issues that I know about: - interactions between PG_G, CR4_PGE, 4M and 4K pages and TLB flushing (potentially cross platform issue due to boot time quirks).. I think we have a workaround for this in our code already, but I have a better complete fix for it in a pending change that I'm working on. - AMD invlpg vs 4MB page bug (AMD bug). If you invlpg using an address in the upper 2MB of a 4MB page, the 4MB tlb may not be flushed (we dont suffer from this (I think) because we do some very suboptimal things with 4MB pages), versus doing an invlpg at the base address of the 4MB mapping. - AMD write cache allocation due to speculative writes being cancelled and then written back later vs no cache snooping on AGP regions. I'm somewhat perplexed about this issue, there's lots of conflicting info going around, a good deal of it which does not make much sense [to me :-)]. I really dont see what PSE has to do with this for several reasons.. if the page/ region is cacheable, why does a 4MB vs 4K page make any difference? cacheable vs no-cache-snooping is a recipe for disaster.. why would 4K pages on a non-coherent region be safer? Or is the problem that write allocation happens on uncacheable/non-write-back regions in 4MB pages? Or something else? - hardware prefetch (newer AMD cpus, pentium 4, 0.13 micron pentium3's) related problems. (can be solved with PAT and/or MSRR programming). I'm just trying to figure out if there's something I'm missing. I know we do some very dubious things with PG_G at bootup. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 1:50: 4 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9C27E37B402 for ; Fri, 1 Feb 2002 01:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g119o1981156; Fri, 1 Feb 2002 01:50:01 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Feb 2002 01:50:01 -0800 (PST) Message-Id: <200202010950.g119o1981156@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Hiten Pandya Subject: re: kern/34487: ASUS P2B-DS Problem (Close Request) Reply-To: Hiten Pandya Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/34487; it has been noted by GNATS. From: Hiten Pandya To: bug-followup@FreeBSD.org Cc: kiwi@caudium.net Subject: re: kern/34487: ASUS P2B-DS Problem (Close Request) Date: Fri, 1 Feb 2002 09:47:01 +0000 Hi, As agreed above, by the originator, the problem/issue is resolved, and all neccessary *new* firmware updates were applied. If the originator agrees, this PR can be successfully closed, and I will take the point to document this problem in the Handbook, as my next patch to the FreeBSD-Doc list. This also suggests that we put up a "Troubleshooting" section in the installation chapter of the handbook. This goes to murray and the -doc team ;) Thanks, Regards, - Hiten Pandya - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3: 5:15 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id D6D0D37B400; Fri, 1 Feb 2002 03:05:12 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16WbYC-000OpJ-00; Fri, 01 Feb 2002 13:08:12 +0200 From: Sheldon Hearn To: brooks@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/34498: Error in vi manpage. In-reply-to: Your message of "Thu, 31 Jan 2002 13:16:59 PST." <200201312116.g0VLGxS89908@freefall.freebsd.org> Date: Fri, 01 Feb 2002 13:08:12 +0200 Message-ID: <95436.1012561692@axl.seasidesoftware.co.za> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 31 Jan 2002 13:16:59 PST, brooks@FreeBSD.org wrote: > State-Changed-From-To: open->suspended > State-Changed-By: brooks > State-Changed-When: Thu Jan 31 13:15:07 PST 2002 > State-Changed-Why: > The submitter will submit the change to the nvi maintainer to be merged > when the corrected version appears in a release. You can assign all nvi-related PRs to me, if you like. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3: 6:48 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 92E0437B400 for ; Fri, 1 Feb 2002 03:06:45 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16WbZX-000OqQ-00; Fri, 01 Feb 2002 13:09:35 +0200 From: Sheldon Hearn To: Hiten Pandya Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/34487: ASUS P2B-DS Problem (Close Request) In-reply-to: Your message of "Fri, 01 Feb 2002 01:50:01 PST." <200202010950.g119o1981156@freefall.freebsd.org> Date: Fri, 01 Feb 2002 13:09:35 +0200 Message-ID: <95505.1012561775@axl.seasidesoftware.co.za> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 01 Feb 2002 01:50:01 PST, Hiten Pandya wrote: > This also suggests that we put up a "Troubleshooting" section > in the installation chapter of the handbook. This goes to > murray and the -doc team ;) Wouldn't this fit better in the Troubleshooting section of the FAQ? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3:11:38 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E0DE537B426; Fri, 1 Feb 2002 03:11:32 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11B8kq01590; Fri, 1 Feb 2002 03:08:46 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 03:08:46 -0800 (PST) From: Message-Id: <200202011108.g11B8kq01590@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-doc@freebsd.org Subject: Re: docs/34487: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: FreeBSD >= 4.4 cannot boot / install on ASUS P2B-DS Motherboard Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: sheldonh Responsible-Changed-When: Fri Feb 1 03:08:03 PST 2002 Responsible-Changed-Why: Hiten is going to come up with a Handbook / FAQ entry for this. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34487 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3:11:38 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4DCB337B41A; Fri, 1 Feb 2002 03:11:32 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11BA1c01843; Fri, 1 Feb 2002 03:10:01 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 03:10:01 -0800 (PST) From: Message-Id: <200202011110.g11BA1c01843@freefall.freebsd.org> To: mi@aldan.algebra.com, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/14448: ftp-client may not recognize failure, report erroneous stats Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: ftp-client may not recognize failure, report erroneous stats State-Changed-From-To: feedback->closed State-Changed-By: sheldonh State-Changed-When: Fri Feb 1 03:09:37 PST 2002 State-Changed-Why: Originator confirms that the problem is solved in a later release. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14448 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3:18:52 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 5B9BB37B402 for ; Fri, 1 Feb 2002 03:18:34 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16Wbkp-000OvL-00; Fri, 01 Feb 2002 13:21:15 +0200 From: Sheldon Hearn To: David Taylor Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/34497: calendar(1) does not understand calendars In-reply-to: Your message of "Thu, 31 Jan 2002 13:30:02 PST." <200201312130.g0VLU2d96837@freefall.freebsd.org> Date: Fri, 01 Feb 2002 13:21:15 +0200 Message-ID: <95810.1012562475@axl.seasidesoftware.co.za> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 31 Jan 2002 13:30:02 PST, David Taylor wrote: > I was going to submit a patch for that along with a fix for the original > problem, until I decided there was no way I was fixing the original > problem. Can you check out the NetBSD and OpenBSD repos and see whether they have a solution? Often, we can just borrow code from those projects, where some problems get fixed long before they're even noticed in FreeBSD. Poor man's access to the NetBSD and OpenBSD repos is available at http://cvsweb.freebsd.org/, by selecting alternative repos. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3:21:35 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 51DF737B419; Fri, 1 Feb 2002 03:21:30 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11BCIm02179; Fri, 1 Feb 2002 03:12:18 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 03:12:18 -0800 (PST) From: Message-Id: <200202011112.g11BCIm02179@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, imp@FreeBSD.org Subject: Re: conf/33395: better way to use more than one pccard network cards Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: better way to use more than one pccard network cards Responsible-Changed-From-To: freebsd-bugs->imp Responsible-Changed-By: sheldonh Responsible-Changed-When: Fri Feb 1 03:12:02 PST 2002 Responsible-Changed-Why: Over to pccard maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33395 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3:22: 4 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from web21106.mail.yahoo.com (web21106.mail.yahoo.com [216.136.227.108]) by hub.freebsd.org (Postfix) with SMTP id 0167037B400 for ; Fri, 1 Feb 2002 03:22:01 -0800 (PST) Message-ID: <20020201112200.33875.qmail@web21106.mail.yahoo.com> Received: from [62.254.0.4] by web21106.mail.yahoo.com via HTTP; Fri, 01 Feb 2002 03:22:00 PST Date: Fri, 1 Feb 2002 03:22:00 -0800 (PST) From: Hiten Pandya Subject: Re: kern/34487: ASUS P2B-DS Problem (Close Request) To: Sheldon Hearn Cc: freebsd-bugs@FreeBSD.org In-Reply-To: <95505.1012561775@axl.seasidesoftware.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Wouldn't this fit better in the Troubleshooting > section of the FAQ? Hmm, It would fit better in the FAQ, but I h've seen people who resort to the Handbook when they encounter installation or other problems. And also, I don't see any good reason why it also shouldn't be documented in the FAQ as well. :) I will need to make a new for this, which should be sometime soon this weekend, and produce a diff. Suggestions, Regards, - Hiten Pandya - __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3:29:12 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za [196.31.7.201]) by hub.freebsd.org (Postfix) with ESMTP id 9972737B402 for ; Fri, 1 Feb 2002 03:28:51 -0800 (PST) Received: from sheldonh (helo=axl.seasidesoftware.co.za) by axl.seasidesoftware.co.za with local-esmtp (Exim 3.33 #1) id 16Wbuw-000OyF-00; Fri, 01 Feb 2002 13:31:42 +0200 From: Sheldon Hearn To: Hiten Pandya Cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/34487: ASUS P2B-DS Problem (Close Request) In-reply-to: Your message of "Fri, 01 Feb 2002 03:22:00 PST." <20020201112200.33875.qmail@web21106.mail.yahoo.com> Date: Fri, 01 Feb 2002 13:31:42 +0200 Message-ID: <95990.1012563102@axl.seasidesoftware.co.za> Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 01 Feb 2002 03:22:00 PST, Hiten Pandya wrote: > Hmm, It would fit better in the FAQ, but I h've seen > people who resort to the Handbook when they encounter > installation or other problems. Ah, then perhaps that's another issue to be addressed. I think the Handbook should be the canonical resource that offers, for any given issue, the information most folks are going to need. Cases like the one in this PR, where a common but silly mistake or known-flakey hardware cause problems, should be documented in the FAQ. Sections of the Handbook that have handed over documentation of such cases to the FAQ, should refer to the FAQ. That's how I see it. So I think this particular case should be documented in the Troubleshooting or Installation section of the FAQ, and the Installation section of the Handbook should refer to the FAQ for "more information on common problems encountered during installation". I'm not a -doc god, so it'd probably be worth checking that this world view is congruent with the direction the -doc project is heading in. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 3:42:38 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from web21106.mail.yahoo.com (web21106.mail.yahoo.com [216.136.227.108]) by hub.freebsd.org (Postfix) with SMTP id 1F9FB37B400 for ; Fri, 1 Feb 2002 03:42:33 -0800 (PST) Message-ID: <20020201114232.39894.qmail@web21106.mail.yahoo.com> Received: from [62.254.0.4] by web21106.mail.yahoo.com via HTTP; Fri, 01 Feb 2002 03:42:32 PST Date: Fri, 1 Feb 2002 03:42:32 -0800 (PST) From: Hiten Pandya Subject: Re: kern/34487: ASUS P2B-DS Problem (Close Request) To: Sheldon Hearn Cc: freebsd-bugs@FreeBSD.org, freebsd-doc@FreeBSD.org In-Reply-To: <95990.1012563102@axl.seasidesoftware.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hi Sheldon, > Ah, then perhaps that's another issue to be > addressed. > > I think the Handbook should be the canonical > resource that offers, for > any given issue, the information most folks are > going to need. indeed ;) > Cases like the one in this PR, where a common but > silly mistake or > known-flakey hardware cause problems, should be > documented in the FAQ. True, the reason I am saying about the handbook, is because it is available in bookstores, and people feel that their problems will be solved if they read off from the hard copy.. well.. most :) But FAQ is also neccessary > So I think this particular case should be documented > in the > Troubleshooting or Installation section of the FAQ, > and the Installation > section of the Handbook should refer to the FAQ for > "more information on > common problems encountered during installation". OK, for that, I have already made a diff for the Installation chapter of the Handbook. The diff is sent as a Problem Report docs/34524. The FAQ entry is going to be sent as a followup to the above mentioned PR. :) [ I've also CC'ed this copy to freebsd-doc ] Regards, - Hiten Pandya - __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 4: 4:41 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from avocet.prod.itd.earthlink.net (avocet.mail.pas.earthlink.net [207.217.120.50]) by hub.freebsd.org (Postfix) with ESMTP id 51A6A37B400; Fri, 1 Feb 2002 04:04:38 -0800 (PST) Received: from pool0081.cvx40-bradley.dialup.earthlink.net ([216.244.42.81] helo=mindspring.com) by avocet.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16WcQg-0005ko-00; Fri, 01 Feb 2002 04:04:31 -0800 Message-ID: <3C5A8448.2C49BDEF@mindspring.com> Date: Fri, 01 Feb 2002 04:04:24 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Peter Wemm Cc: Glendon Gross , Steve Kargl , Kenneth Culver , "Cameron, Frank" , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug References: <20020201083417.C3FFC3809@overcee.wemm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Peter Wemm wrote: > I'm a little confused as to which bugs are which that we're talking > about now. Which is the one that you're trying to sell the info for? I'm not really trying to sell the fix; it's that I'm not willing to give it away when it's no benefit to do so; I'd need a bribe. Kind of like Kirk and Soft Updates. 8-). I was aware of all but the "recent" AMD problem, but it's pretty obvious in retrospect (Alfred had the idea of putting a fast network interface in an AGP slot some time back, and I looked at AGP a little back then). I can tell you how to cause the problem I'm talking about, off list, if you're willing to laugh along and keep quiet (I have dibs on the bribe 8-)). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 4:21:32 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 68DBA37B400; Fri, 1 Feb 2002 04:21:30 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11CEDG24566; Fri, 1 Feb 2002 04:14:13 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 04:14:13 -0800 (PST) From: Message-Id: <200202011214.g11CEDG24566@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, n_hibma@FreeBSD.org Subject: Re: conf/34494: usb configuration problem - usb does not work Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: usb configuration problem - usb does not work Responsible-Changed-From-To: freebsd-bugs->n_hibma Responsible-Changed-By: sheldonh Responsible-Changed-When: Fri Feb 1 04:13:58 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34494 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 4:33:39 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 02D3437B417; Fri, 1 Feb 2002 04:33:37 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11CXBm28100; Fri, 1 Feb 2002 04:33:11 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 04:33:11 -0800 (PST) From: Message-Id: <200202011233.g11CXBm28100@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, ru@FreeBSD.org Subject: Re: misc/6612: bsd.man.mk can't handle man pages with ":"s Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: bsd.man.mk can't handle man pages with ":"s Responsible-Changed-From-To: freebsd-bugs->ru Responsible-Changed-By: sheldonh Responsible-Changed-When: Fri Feb 1 04:32:56 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6612 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 5: 6:57 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from bambino.amt.ru (bambino.amt.ru [212.111.64.24]) by hub.freebsd.org (Postfix) with SMTP id BBD5637B417 for ; Fri, 1 Feb 2002 05:06:46 -0800 (PST) Received: (from root@localhost) by bambino.amt.ru (8.11.6/8.11.6) id g11D6iC09524 for freebsd-bugs@FreeBSD.org.KAV; Fri, 1 Feb 2002 16:06:44 +0300 Received: from bakhtin.amt.ru (bakhtin.amt.ru [10.0.0.172]) by bambino.amt.ru (8.11.6/8.11.6) with ESMTP id g11D6iY09516; Fri, 1 Feb 2002 16:06:44 +0300 Received: (from bakhtin@localhost) by bakhtin.amt.ru (8.11.6/8.11.6) id g11D6iV51811; Fri, 1 Feb 2002 16:06:44 +0300 (MSK) (envelope-from bakhtin@amt.ru) X-Authentication-Warning: bakhtin.amt.ru: bakhtin set sender to bakhtin@amt.ru using -f X-Comment-To: iedowse@FreeBSD.org To: iedowse@FreeBSD.org Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/25474: dump can't close fifo pipe correctly References: <200111211843.fALIhFl64754@freefall.freebsd.org> Organization: AMT Group From: Alex Bakhtin Date: 01 Feb 2002 16:06:44 +0300 In-Reply-To: <200111211843.fALIhFl64754@freefall.freebsd.org> Message-ID: <81sn8l8i6z.fsf@bakhtin.amt.ru> Lines: 7 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, Have you got the requested patch? -- Best regards, Alex Bakhtin, CCIE #8439 AMT Group, Cisco Systems Gold Partner, http://www.amt.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 5:40: 7 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 80C7237B400 for ; Fri, 1 Feb 2002 05:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11De2R49460; Fri, 1 Feb 2002 05:40:02 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Feb 2002 05:40:02 -0800 (PST) Message-Id: <200202011340.g11De2R49460@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: i386/34521: Upgrade problem Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR i386/34521; it has been noted by GNATS. From: David Malone To: Andryan Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: i386/34521: Upgrade problem Date: Fri, 1 Feb 2002 13:30:18 +0000 On Thu, Jan 31, 2002 at 11:59:54PM -0800, Andryan wrote: > I have done cvsup, make buildworld, make kernel, make installworld and mergemaster (using the "upgrade from src" reference from the handbook). I rebooted it, it went back online (box is remote box) and pingable. Once I attempt a connection to ANY open port to the box, the ping stops and start giving RTOs, the box is not running firewall nor NAT. I asked the hosting company to boot with generic kernel and scanned the syslog. Nothing useful there and I found out that everytime I attempted a connection to A NY open port, it will reboot. I tried doing the make buildkernel with my own conf and GENERIC, both resulted the same. Is it possible that you have old kernel modules left around? What way did you build the kernel? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 5:51:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8CFBD37B400; Fri, 1 Feb 2002 05:51:30 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11Dkvw55884; Fri, 1 Feb 2002 05:46:57 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 05:46:57 -0800 (PST) From: Message-Id: <200202011346.g11Dkvw55884@freefall.freebsd.org> To: sheldonh@FreeBSD.org, ru@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: misc/6612: bsd.man.mk can't handle man pages with ":"s Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: bsd.man.mk can't handle man pages with ":"s Responsible-Changed-From-To: ru->freebsd-bugs Responsible-Changed-By: sheldonh Responsible-Changed-When: Fri Feb 1 05:46:36 PST 2002 Responsible-Changed-Why: The man maintainer says this is a make(1) issue. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=6612 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 6:50:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9B3BA37B400 for ; Fri, 1 Feb 2002 06:50:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11Eo2v45439; Fri, 1 Feb 2002 06:50:02 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Feb 2002 06:50:02 -0800 (PST) Message-Id: <200202011450.g11Eo2v45439@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Niels Piersma" Subject: Re: bin/34158: High NATD cpu usage Reply-To: "Niels Piersma" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34158; it has been noted by GNATS. From: "Niels Piersma" To: , Cc: Subject: Re: bin/34158: High NATD cpu usage Date: Fri, 1 Feb 2002 15:47:24 +0100 This is a multi-part message in MIME format. ------=_NextPart_000_0006_01C1AB37.C14CA060 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Here a screen shot of TOP, with some high(er) cpu usage. =20 last pid: 35819; load averages: 0.08, 0.04, 0.00 up 12+03:18:02 15:40:05 28 processes: 3 running, 25 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 15M Active, 12M Inact, 13M Wired, 568K Cache, 14M Buf, 18M Free Swap: 256M Total, 16K Used, 256M Free =F21;34H 0.08, 0.04, 0.00 PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 33734 root 28 0 492K 244K RUN 13:07 5.08% 5.08% natd 203 root 2 0 2500K 1676K select 0:47 0.00% 0.00% sendmail 269 root 2 0 1980K 1168K select 0:45 0.00% 0.00% nmbd 258 root 2 0 1876K 972K select 0:34 0.00% 0.00% mpd 241 root 4 0 2524K 2044K bpf 0:33 0.00% 0.00% arpwatch 173 root 2 0 2392K 1768K select 0:07 0.00% 0.00% named 195 root 10 0 968K 640K nanslp 0:05 0.00% 0.00% cron 169 root 2 0 936K 572K select 0:05 0.00% 0.00% syslogd 253 root 2 0 1064K 672K select 0:04 0.00% 0.00% dhcpd 198 root 2 0 2548K 1300K select 0:02 0.00% 0.00% sshd 200 root 2 0 904K 520K select 0:02 0.00% 0.00% usbd 267 root 2 0 2512K 1204K select 0:01 0.00% 0.00% smbd 193 root 2 0 1052K 696K select 0:01 0.00% 0.00% inetd 271 root -6 0 1940K 1044K piperd 0:00 0.00% 0.00% nmbd 35816 niels 28 0 1896K 960K RUN 0:00 0.00% 0.00% top 35813 root 28 0 2300K 1312K RUN 0:00 0.00% 0.00% telnetd =20 This is only 5% but results in very slow ssh and telnet connections. =20 Niels ------=_NextPart_000_0006_01C1AB37.C14CA060 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Here a screen shot of TOP, = with some high(er) cpu usage.

 

last= pid: 35819;=A0 load averages:=A0 = 0.08,=A0 0.04,=A0 0.00=A0=A0 up = 12+03:18:02=A0 = 15:40:05

28 processes:=A0 3 running, 25 = sleeping

CPU states:=A0 0.0% user,=A0 0.0% nice,=A0 0.0% system,=A0 0.0% interrupt,=A0 100% = idle

Mem<= /span>: 15M Active, 12M Inact, 13M Wired, = 568K Cache, 14M Buf, 18M = Free

Swap: 256M Total, 16K Used, = 256M Free

=F21;34H 0.08,=A0 0.04,=A0 0.00

=A0 PID USERNAME PRI NICE=A0 SIZE=A0=A0=A0 = RES = STATE=A0=A0=A0 TIME=A0=A0 WCPU=A0=A0=A0 CPU COMMAND

33734 root=A0=A0=A0=A0=A0 28=A0=A0 0=A0=A0 492K=A0=A0 244K RUN=A0=A0=A0=A0 = 13:07=A0 5.08%=A0 5.08% natd

=A0 203 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0 2500K=A0 1676K select=A0=A0 0:47=A0 0.00%=A0 0.00% sendmail

=A0 269 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0 1980K=A0 1168K select=A0=A0 0:45=A0 0.00%=A0 0.00% nmbd

=A0 258 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0 1876K=A0=A0 972K select=A0=A0 0:34=A0 0.00%=A0 0.00% mpd

=A0 241 = root=A0=A0=A0=A0=A0=A0 4=A0=A0 0=A0 2524K=A0 2044K bpf=A0=A0=A0=A0=A0 0:33=A0 0.00%=A0 0.00% arpwatch

=A0 173 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0 2392K=A0 1768K select=A0=A0 0:07=A0 0.00%=A0 0.00% named

=A0 195 = root=A0=A0=A0=A0=A0 10=A0=A0 0=A0=A0 968K=A0=A0 640K nanslp=A0=A0 0:05=A0 0.00%=A0 0.00% cron

=A0 169 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0=A0 936K=A0=A0 572K select=A0=A0 0:05=A0 0.00%=A0 0.00% syslogd

=A0 253 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0 1064K=A0=A0 672K select=A0=A0 0:04 =A00.00%=A0 0.00% dhcpd

=A0 198 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0 2548K=A0 1300K select=A0=A0 0:02=A0 0.00%=A0 0.00% sshd

=A0 200 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0=A0 904K=A0=A0 520K select=A0=A0 0:02=A0 0.00%=A0 0.00% usbd

=A0 267 = root=A0=A0=A0=A0=A0=A0 2=A0=A0 0=A0 2512K=A0 1204K select=A0=A0 0:01=A0 0.00%=A0 0.00% smbd

=A0 = 193 root=A0=A0=A0=A0=A0=A0 = 2=A0=A0 0=A0 1052K=A0=A0 696K select=A0=A0 = 0:01=A0 0.00%=A0 0.00% inetd

=A0 271 root=A0=A0=A0=A0=A0 = -6=A0=A0 0=A0 1940K=A0 1044K piperd=A0=A0 0:00=A0 0.00%=A0 0.00% nmbd

35816 niels=A0=A0=A0=A0 28=A0=A0 0=A0 = 1896K=A0=A0 960K RUN=A0=A0=A0=A0=A0 0:00=A0 0.00%=A0 0.00% = top

35813 root=A0=A0=A0=A0=A0 28=A0=A0 0=A0 = 2300K=A0 1312K RUN=A0=A0=A0=A0=A0 0:00=A0 0.00%=A0 0.00% telnetd

 

This is only 5% but results = in very slow ssh and = telnet connections.

 

Niels=

------=_NextPart_000_0006_01C1AB37.C14CA060-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 6:51:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1709F37B405; Fri, 1 Feb 2002 06:51:31 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11EjE921783; Fri, 1 Feb 2002 06:45:14 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 06:45:14 -0800 (PST) From: Message-Id: <200202011445.g11EjE921783@freefall.freebsd.org> To: pantzer@ludd.luth.se, sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/34117: ftpd enters endless sendfile loop Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: ftpd enters endless sendfile loop State-Changed-From-To: open->closed State-Changed-By: sheldonh State-Changed-When: Fri Feb 1 06:44:50 PST 2002 State-Changed-Why: Duplicate of bin/33770. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34117 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 7: 1:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A845337B402; Fri, 1 Feb 2002 07:01:30 -0800 (PST) Received: (from sheldonh@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11F05K93061; Fri, 1 Feb 2002 07:00:05 -0800 (PST) (envelope-from sheldonh) Date: Fri, 1 Feb 2002 07:00:05 -0800 (PST) From: Message-Id: <200202011500.g11F05K93061@freefall.freebsd.org> To: sheldonh@FreeBSD.org, freebsd-bugs@FreeBSD.org, yokota@FreeBSD.org Subject: Re: misc/33736: Scroll-lock on the console prevents shutdown Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Scroll-lock on the console prevents shutdown Responsible-Changed-From-To: freebsd-bugs->yokota Responsible-Changed-By: sheldonh Responsible-Changed-When: Fri Feb 1 06:59:51 PST 2002 Responsible-Changed-Why: Over to maintainer. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=33736 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 7:40:14 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DDA6F37B402 for ; Fri, 1 Feb 2002 07:40:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11Fe4G17209; Fri, 1 Feb 2002 07:40:04 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Feb 2002 07:40:04 -0800 (PST) Message-Id: <200202011540.g11Fe4G17209@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Andryan" Subject: Re: i386/34521: Upgrade problem Reply-To: "Andryan" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR i386/34521; it has been noted by GNATS. From: "Andryan" To: "David Malone" Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: i386/34521: Upgrade problem Date: Fri, 1 Feb 2002 22:35:43 +0700 I used make buildkernel and installkernel. I think it should automatically override all modules =/ ----- Original Message ----- From: "David Malone" To: "Andryan" Cc: Sent: Friday, February 01, 2002 20:30 Subject: Re: i386/34521: Upgrade problem > On Thu, Jan 31, 2002 at 11:59:54PM -0800, Andryan wrote: > > I have done cvsup, make buildworld, make kernel, make installworld and mergemaster (using the "upgrade from src" reference from the handbook). I rebooted it, it went back online (box is remote box) and pingable. Once I attempt a connection to ANY open port to the box, the ping stops and start giving RTOs, the box is not running firewall nor NAT. I asked the hosting company to boot with generic kernel and scanned the syslog. Nothing useful there and I found out that everytime I attempted a connection to ANY open port, it will reboot. I tried doing the make buildkernel with my own conf and GENERIC, both resulted the same. > > Is it possible that you have old kernel modules left around? > What way did you build the kernel? > > David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 8:21:22 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.yadt.co.uk (yadt.demon.co.uk [158.152.4.134]) by hub.freebsd.org (Postfix) with SMTP id B6FB137B402 for ; Fri, 1 Feb 2002 08:21:08 -0800 (PST) Received: (qmail 57416 invoked from network); 1 Feb 2002 16:20:59 -0000 Received: from unknown (HELO mail.gattaca.yadt.co.uk) (qmailr@10.0.0.2) by yadt.demon.co.uk with SMTP; 1 Feb 2002 16:20:59 -0000 Received: (qmail 47140 invoked by uid 1000); 1 Feb 2002 16:20:58 -0000 Date: Fri, 1 Feb 2002 16:20:58 +0000 From: David Taylor To: Sheldon Hearn Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/34497: calendar(1) does not understand calendars Message-ID: <20020201162058.GA46152@gattaca.yadt.co.uk> Mail-Followup-To: Sheldon Hearn , freebsd-bugs@FreeBSD.org References: <200201312130.g0VLU2d96837@freefall.freebsd.org> <95810.1012562475@axl.seasidesoftware.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <95810.1012562475@axl.seasidesoftware.co.za> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 01 Feb 2002, Sheldon Hearn wrote: > > > On Thu, 31 Jan 2002 13:30:02 PST, David Taylor wrote: > > > I was going to submit a patch for that along with a fix for the original > > problem, until I decided there was no way I was fixing the original > > problem. > > Can you check out the NetBSD and OpenBSD repos and see whether they have > a solution? Often, we can just borrow code from those projects, where > some problems get fixed long before they're even noticed in FreeBSD. OpenBSD does appear to have a fix for that problem (almost identical to my fix, in fact). There are a lot of changes (including addition of various comments explaining some of the weirder things the code is doing, which is nice) which would probably be useful. They've also changed the way -A/-B is handled internally (-B 3 and -A 2 is converted to -A 5, but the time is moved back 3 days), which helps simplify everything a lot. I've no idea if it comes close to fixing all the bugs, however. NetBSD didn't merge the change (from FreeBSD, apparantly) which split calendar.c into calendar.c/day.c/io.c, etc, but have commmited some cleanups (which introduced a minor memory leak: blank lines are never freed -- any idea where to report that?). They don't _seem_ to have fixed -- David Taylor davidt@yadt.co.uk "The future just ain't what it used to be" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 8:41:34 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D362C37B400; Fri, 1 Feb 2002 08:41:30 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11GcRh29432; Fri, 1 Feb 2002 08:38:27 -0800 (PST) (envelope-from dwmalone) Date: Fri, 1 Feb 2002 08:38:27 -0800 (PST) From: Message-Id: <200202011638.g11GcRh29432@freefall.freebsd.org> To: andryan@softhome.net, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: i386/34521: Upgrade problem Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Upgrade problem State-Changed-From-To: open->feedback State-Changed-By: dwmalone State-Changed-When: Fri Feb 1 08:37:14 PST 2002 State-Changed-Why: We think we may have tracked this to an out-of-date trafcount module, but we're not sure. Waiting to see if disabling trafcount helps. (http://sourceforge.net/projects/trafcount) http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34521 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 11:10:10 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 129A237B417 for ; Fri, 1 Feb 2002 11:10:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11JA1l63736; Fri, 1 Feb 2002 11:10:01 -0800 (PST) (envelope-from gnats) Received: from relay3-gui.server.ntli.net (relay3-gui.server.ntli.net [194.168.4.200]) by hub.freebsd.org (Postfix) with ESMTP id 057FA37B402 for ; Fri, 1 Feb 2002 11:06:29 -0800 (PST) Received: from pc4-card4-0-cust162.cdf.cable.ntl.com ([80.4.14.162] helo=rhadamanth.private.submonkey.net ident=mailnull) by relay3-gui.server.ntli.net with esmtp (Exim 3.03 #2) id 16Wj11-0001Uy-00 for FreeBSD-gnats-submit@freebsd.org; Fri, 01 Feb 2002 19:06:27 +0000 Received: from setantae by rhadamanth.private.submonkey.net with local (Exim 3.34 #1) id 16Wj10-0001Ff-00 for FreeBSD-gnats-submit@freebsd.org; Fri, 01 Feb 2002 19:06:26 +0000 Message-Id: Date: Fri, 01 Feb 2002 19:06:26 +0000 From: Ceri Reply-To: Ceri To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: conf/34535: mailnull and smmsp should be in /etc/ftpusers Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34535 >Category: conf >Synopsis: mailnull and smmsp should be in /etc/ftpusers >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Fri Feb 01 11:10:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Ceri >Release: FreeBSD 4.5-STABLE i386 >Organization: >Environment: System: FreeBSD rhadamanth.private.submonkey.net 4.5-STABLE FreeBSD 4.5-STABLE #0: Tue Jan 29 12:54:04 GMT 2002 root@rhadamanth.private.submonkey.net:/usr/obj/usr/src/sys/RHADAMANTH i386 >Description: mailnull and smmsp are system accounts and so should be listed in /etc/ftpusers Ceri >How-To-Repeat: cat /etc/ftpusers >Fix: --- src/etc/ftpusers.old Fri Feb 1 19:03:51 2002 +++ src/etc/ftpusers Fri Feb 1 19:04:09 2002 @@ -17,3 +17,5 @@ xten pop nobody +mailnull +smmsp >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 11:21:51 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 26AAB37B431 for ; Fri, 1 Feb 2002 11:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11JK1465701; Fri, 1 Feb 2002 11:20:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6676837B400 for ; Fri, 1 Feb 2002 11:14:19 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11JEJF64299; Fri, 1 Feb 2002 11:14:19 -0800 (PST) (envelope-from nobody) Message-Id: <200202011914.g11JEJF64299@freefall.freebsd.org> Date: Fri, 1 Feb 2002 11:14:19 -0800 (PST) From: Yixin To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: i386/34536: accept() blocks other threads Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34536 >Category: i386 >Synopsis: accept() blocks other threads >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 01 11:20:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Yixin >Release: 4.4 >Organization: SLMsoft >Environment: FreeBSD freebsd.slm.com 4.4-RELEASE FreeBSD 4.4-RELEASE #3: Wed Jan 30 13:38:55 EST 2002 root@freebsd.slm.com:/usr/src/sys/compile/MYKERNEL i386 >Description: I created a simple program: main thread listens to a port, and child threads serve the requests. If main thread uses accept() to wait for request, the new thread can not get scheduled. But if main thread uses select() to wait for request, it works fine. >How-To-Repeat: /* This is just a test program * Compile: * cc -o thread thread.c -pthread * Test: * ./thread 90 * telnet localhost 90 */ #include #include #include #include #include #include #include #include #include #include #include #include #include #include #include void * srv(void *arg){ int fd=(int)arg; char buff[100]; int count; struct sockaddr_in saddr, daddr; int length; syslog(LOG_NOTICE, "Begin to read"); count=read(fd, buff, 10); close(fd); syslog(LOG_NOTICE, "Begin to exit"); } main(int argc, char *argv[]){ int sock, newsock, length, port,pid, i; struct sockaddr_in addr, daddr; pthread_t ptid; pthread_attr_t tattr; if(argc==1) { printf("Usage:\n %s Port\n", argv[0]); exit(1); } port=atoi(argv[1]); if(port==0){ printf("Illegal Port:%s\n", argv[1]); exit(1); } sock=socket(AF_INET, SOCK_STREAM,0); if(sock < 0){ perror("Opening stream socket"); exit(1); } bzero(&addr, sizeof(addr)); addr.sin_family=AF_INET; addr.sin_addr.s_addr = htonl(INADDR_ANY); addr.sin_port = htons(port); if(bind(sock, (struct sockaddr *)&addr, sizeof addr) == -1){ perror("Binding stream socket"); exit(1); }; bzero(&addr, sizeof(addr)); i = sizeof(addr); if(getsockname(sock, (struct sockaddr *)&addr, &i) < 0){ perror("getsockname"); exit(1); } if(listen(sock, 5) == -1){ perror("Listening stream socket"); exit(1); }; if(fork()){ sleep(2); exit(0); } pthread_attr_init(&tattr); pthread_attr_setdetachstate(&tattr, PTHREAD_CREATE_DETACHED); pthread_attr_setscope(&tattr, PTHREAD_SCOPE_SYSTEM); setsid(); #define USE_POLL #ifdef USE_POLL { fd_set fdset; struct timeval timeout; while(1){ FD_ZERO(&fdset); FD_SET(sock, &fdset); timeout.tv_usec = 0; timeout.tv_sec = 10; i=select(sock+1, &fdset, NULL, NULL, &timeout); if(i==0) continue; else if(i < 0){ syslog(LOG_NOTICE, "select: %m"); continue; }; length = sizeof(daddr); newsock=accept(sock, (struct sockaddr *)&daddr, &length); if(newsock < 0){ syslog(LOG_NOTICE, "accept: %m"); continue; } if(pthread_create(&ptid, &tattr, srv, (void *)newsock)){ syslog(LOG_NOTICE, "pthread_create() failed: %m"); close(newsock); } } } #else while((newsock=accept(sock, (struct sockaddr *)&daddr, (length=sizeof daddr, &length))) != -1){ syslog(LOG_NOTICE, "Main Thread is going to start a new thread"); if(pthread_create(&ptid, &tattr, srv, (void *)newsock)){ syslog(LOG_NOTICE, "pthread_create() failed: %m"); close(newsock); } } #endif /* never reached */ close(sock); } >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 11:30:17 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id B714937B41B for ; Fri, 1 Feb 2002 11:30:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11JU0I67222; Fri, 1 Feb 2002 11:30:00 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id C372737B417 for ; Fri, 1 Feb 2002 11:20:31 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11JKV065788; Fri, 1 Feb 2002 11:20:31 -0800 (PST) (envelope-from nobody) Message-Id: <200202011920.g11JKV065788@freefall.freebsd.org> Date: Fri, 1 Feb 2002 11:20:31 -0800 (PST) From: Yixin Pan To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: i386/34537: The second NIC card could not get configured correctly Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34537 >Category: i386 >Synopsis: The second NIC card could not get configured correctly >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 01 11:30:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Yixin Pan >Release: 4.4 & 4.5 >Organization: SLMsoft >Environment: FreeBSD freebsd.slm.com 4.4-RELEASE FreeBSD 4.4-RELEASE #3: Wed Jan 30 13:38:55 EST 2002 root@freebsd.slm.com:/usr/src/sys/compile/MYKERNEL i386 >Description: My machine has 2 network cards. I configured these 2 network cards with 2 different IP address during the initial installation. These 2 NIC's IP addresses are the same after rebooting. >How-To-Repeat: Do a initial installation to a machine with 2 NICs >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 11:50: 6 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id ACBB837B405 for ; Fri, 1 Feb 2002 11:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11Jo1c71985; Fri, 1 Feb 2002 11:50:01 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Feb 2002 11:50:01 -0800 (PST) Message-Id: <200202011950.g11Jo1c71985@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Dave Zarzycki Subject: Re: kern/29741: ptrace(pid);ptrace(ppid) makes pid and ppid unkillable Reply-To: Dave Zarzycki Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/29741; it has been noted by GNATS. From: Dave Zarzycki To: "Tim J. Robbins" Cc: freebsd-gnats-submit@FreeBSD.org, Dave Zarzycki Subject: Re: kern/29741: ptrace(pid);ptrace(ppid) makes pid and ppid unkillable Date: Fri, 1 Feb 2002 11:41:41 -0800 (PST) On Sun, 27 Jan 2002, Tim J. Robbins wrote: > I can reproduce this problem with 4.5-RC. The problem seems to be that > ptrace() allows a process to attach to its owner. I've attached a patch > for both RELENG_4 and -CURRENT that seems to correct the problem. When > I try to reproduce it now: The patch doesn't solve the gdb -> gdb -> gdb -> grandparent-pid... davez -- Dave Zarzycki Darwin & Mac OS X Apple Computer, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 11:51:33 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 2395337B41B; Fri, 1 Feb 2002 11:51:31 -0800 (PST) Received: (from keramida@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11JibW70891; Fri, 1 Feb 2002 11:44:37 -0800 (PST) (envelope-from keramida) Date: Fri, 1 Feb 2002 11:44:37 -0800 (PST) From: Message-Id: <200202011944.g11JibW70891@freefall.freebsd.org> To: yxpan@yahoo.com, keramida@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: i386/34537: The second NIC card could not get configured correctly Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: The second NIC card could not get configured correctly State-Changed-From-To: open->feedback State-Changed-By: keramida State-Changed-When: Fri Feb 1 11:41:39 PST 2002 State-Changed-Why: You haven't provided enough information for anyone to debug your problem. Please do tell us more about your hardware & configuration. + What ouput does dmesg give in this system? + What types of NICs your system has? (This can be ommitted if you post dmesg output, and the types are included in that output). + Exactly what did you do to configure your NICs with an address? + What is the output of /sbin/ifconfig *after* you have configured the NICs and restarted your system or run /etc/netstart? http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34537 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 11:51:39 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 1CADF37B43A; Fri, 1 Feb 2002 11:51:35 -0800 (PST) Received: from [192.168.1.129] (212.129.46.20) by mail.libertysurf.net (5.1.053) id 3C5A05630002895A; Fri, 1 Feb 2002 20:50:43 +0100 Date: Thu, 31 Jan 2002 21:50:52 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Terry Lambert Cc: "Cameron, Frank" , 'Kenneth Culver' , David Malone , "'freebsd-bugs@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: Re: AMD AGP Bug In-Reply-To: <3C59E050.6564C115@mindspring.com> Message-ID: <20020131214744.Y1769-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 31 Jan 2002, Terry Lambert wrote: > "Cameron, Frank" wrote: > > From what was posted on the linux-kernel list the problem is the OS > > doing the wrong thing not the hardware. I originally asked the > > question (albeit not worded as clearly as I should have) because if > > Microsoft and Linux programmers made the same mistake, might > > FreeBSD have also. > > No. FreeBSD does not make active use of 4M pages for anything > other than the initial kernel text and data, which is obvious, > if you look at /sys/i386/machdep.c. > > For Linux and Windows, the obvious thing is to not map the > memory into an aperture marked cacheable and in a 4M page; > it's a coding problem with the use of 4M pages, when memory > in them is allocated to AGP. > > This still doesn't get around the other bug, which happens > if you use 4M pages certain obviously useful ways, without > waving a dead chicken over certain things. 8-). This one is not $10,000 but $0, since it has already been suggested.:-) G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 12:20:10 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9AD7537B402 for ; Fri, 1 Feb 2002 12:20:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11KK1o86116; Fri, 1 Feb 2002 12:20:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8023237B41B for ; Fri, 1 Feb 2002 12:14:33 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11KEXw80582; Fri, 1 Feb 2002 12:14:33 -0800 (PST) (envelope-from nobody) Message-Id: <200202012014.g11KEXw80582@freefall.freebsd.org> Date: Fri, 1 Feb 2002 12:14:33 -0800 (PST) From: Frank Dabek To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: gnu/34538: mp_set_memory_functions not extern "C"'d in gmp.h Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34538 >Category: gnu >Synopsis: mp_set_memory_functions not extern "C"'d in gmp.h >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 01 12:20:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Frank Dabek >Release: 4.5 stable >Organization: LCS >Environment: uname -a FreeBSD supervised-residence.lcs.mit.edu 4.5-RELEASE FreeBSD 4.5-RELEASE #1: Thu Jan 31 13:36:23 EST 2002 rtm@frenulum.lcs.mit.edu:/usr/src/sys/compile/PDOS-UNI i386 >Description: At line 171 (or so) in /usr/include/gmp.h, void mp_set_memory_functions _PROTO ((void *(*) (size_t), void *(*) (void *, size_t, size_t), void (*) (void *, size_t))); is not included in the extern "C" { declaration of line 177 (or so) This makes it impossible to link C++ programs which use this function. >How-To-Repeat: use mp_set_memory_functions in a C++ program and link it against libgmp.a. The linker will report mp_set_memory_functions as an unresolved symbol (since C++ is mangling its name) >Fix: move mp_set_memory_functions into the extern "C" >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 13:17:48 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from tomts9-srv.bellnexxia.net (tomts9.bellnexxia.net [209.226.175.53]) by hub.freebsd.org (Postfix) with ESMTP id 222DD37B400 for ; Fri, 1 Feb 2002 13:17:38 -0800 (PST) Received: from on.aibn.com ([64.228.43.80]) by tomts9-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20020201211737.CUUT23714.tomts9-srv.bellnexxia.net@on.aibn.com> for ; Fri, 1 Feb 2002 16:17:37 -0500 Message-ID: <220342-22002251223648310@on.aibn.com> X-EM-Version: 6, 0, 1, 0 X-EM-Registration: #00F06206106618006920 X-Priority: 3 Reply-To: infosource@on.aibn.com Organization: InfoSource From: "Barbara Caldwell" To: "freebsd-bugs@freebsd.org" Subject: The United States Healthcare Directory Date: Fri, 1 Feb 2002 16:36:48 -0600 MIME-Version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If this information is not relevant to you or your organization,=20 please accept our apologies for taking your time=2E We are publishers of specialized reports and directories=20 dealing with public affairs=2E Our new directory,=20 "The United States Healthcare Directory" covers=20 hospitals, nursing homes, government departments, etc=2E =20 It is used by corporations, associations and governments=20 and is available at a cost of $195=2E If you are interested=20 in receiving this directory, please provide us with=20 your mailing address=2E Please visit our website, www=2Enational-directories=2Ecom,=20 for information on our other directories and reports=2E=20 Thank you for your consideration=2E =20 Please Note: If you do not respond to this message,=20 you will be taken off our list automatically=2E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 14:40:24 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6066E37B41A for ; Fri, 1 Feb 2002 14:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11Me2f26417; Fri, 1 Feb 2002 14:40:02 -0800 (PST) (envelope-from gnats) Received: from kevinday.com (dsl092-133-149.chi1.dsl.speakeasy.net [66.92.133.149]) by hub.freebsd.org (Postfix) with ESMTP id 3410537B405 for ; Fri, 1 Feb 2002 14:31:44 -0800 (PST) Received: (from root@localhost) by gw.kevinday.com (8.11.6/8.11.6) id g11NRFu02041; Fri, 1 Feb 2002 17:27:15 -0600 (CST) (envelope-from toasty) Message-Id: <200202012327.g11NRFu02041@gw.kevinday.com> Date: Fri, 1 Feb 2002 17:27:15 -0600 (CST) From: toasty Reply-To: toasty To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: bin/34539: [PATCH] fsck(8) doesn't account for negative values in some signed fields Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34539 >Category: bin >Synopsis: [PATCH] fsck(8) doesn't account for negative values in some signed fields >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 01 14:40:02 PST 2002 >Closed-Date: >Last-Modified: >Originator: toasty >Release: FreeBSD 4.4-RELEASE i386 >Organization: DragonData >Environment: System: FreeBSD gw.kevinday.com 4.4-RELEASE FreeBSD 4.4-RELEASE #4: Thu Jan 17 23:34:34 CST 2002 toasty@gw.kevinday.com:/usr/src/sys/compile/GW i386 >Description: In fs.h: /* * Cylinder group block for a file system. */ struct cg { ... int32_t cg_rotor; /* position of last used block */ int32_t cg_frotor; /* position of last used frag */ int32_t cg_irotor; /* position of last used inode */ ... } these are signed fields, but fsck never checks for negative values. We had a system crash, and come back with negative values in a few irotor fields on a FS. Fsck says the FS was fine, but the kernel crashed every time that CG was used. I discussed this with a few people. I originally suggested changing this to an unsigned value, but it was pointed out that NetBSD tried this and it ended up being quite a bit of work. My patch below checks for negative numbers, and corrects them. >How-To-Repeat: >Fix: --- pass5.c.orig Fri Feb 1 17:16:48 2002 +++ pass5.c Fri Feb 1 17:18:19 2002 @@ -195,15 +195,15 @@ newcg->cg_cs.cs_nffree = 0; newcg->cg_cs.cs_nbfree = 0; newcg->cg_cs.cs_nifree = fs->fs_ipg; - if (cg->cg_rotor < newcg->cg_ndblk) + if ((cg->cg_rotor < newcg->cg_ndblk) && (cg->cg_rotor > 0)) newcg->cg_rotor = cg->cg_rotor; else newcg->cg_rotor = 0; - if (cg->cg_frotor < newcg->cg_ndblk) + if ((cg->cg_frotor < newcg->cg_ndblk) && (cg->cg_frotor > 0)) newcg->cg_frotor = cg->cg_frotor; else newcg->cg_frotor = 0; - if (cg->cg_irotor < newcg->cg_niblk) + if ((cg->cg_irotor < newcg->cg_niblk) && (cg->cg_irotor > 0)) newcg->cg_irotor = cg->cg_irotor; else newcg->cg_irotor = 0; >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 14:50: 5 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7F2CB37B402 for ; Fri, 1 Feb 2002 14:50:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g11Mo1x27393; Fri, 1 Feb 2002 14:50:01 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Feb 2002 14:50:01 -0800 (PST) Message-Id: <200202012250.g11Mo1x27393@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Juha Ylitalo Subject: Re: kern/31460: ATAPI CD-ROM makes system reboot with DVD movie. Reply-To: Juha Ylitalo Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/31460; it has been noted by GNATS. From: Juha Ylitalo To: bug-followup@freebsd.org Cc: Nate Eldredge Subject: Re: kern/31460: ATAPI CD-ROM makes system reboot with DVD movie. Date: 02 Feb 2002 00:40:58 +0200 It seems that this PR can really be closed as something that got fixed into 4.5-RELEASE. I just experimented things (with different DVD, but ...) and even though I am still able to crash my system with mplayer, it now manages to get disc information correctly and play some of it, xine is not able to crash my system at all and with ogle, which gives me best results on DVD player, all my problems looks like something that is ogle related. -- Juha Ylitalo juha.ylitalo@iki.fi "Some tools are used, because its policy, others because they are good." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 17: 0:47 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E9E4C37B419 for ; Fri, 1 Feb 2002 17:00:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12100p53252; Fri, 1 Feb 2002 17:00:00 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A323737B402 for ; Fri, 1 Feb 2002 16:52:25 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g120qPS52461; Fri, 1 Feb 2002 16:52:25 -0800 (PST) (envelope-from nobody) Message-Id: <200202020052.g120qPS52461@freefall.freebsd.org> Date: Fri, 1 Feb 2002 16:52:25 -0800 (PST) From: "Marcus L. Reid" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/34544: Kernel crash on fclose() of /dev/kbd1 when USB keyboard is detached while file is open. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34544 >Category: kern >Synopsis: Kernel crash on fclose() of /dev/kbd1 when USB keyboard is detached while file is open. >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 01 17:00:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Marcus L. Reid >Release: 4.5-RELEASE >Organization: Gampro >Environment: FreeBSD zork.punq.net 4.5-RELEASE FreeBSD 4.5-RELEASE #0: Fri Feb 1 16:06:37 PST 2002 root@zork.punq.net:/usr/obj/home/archive/releases/RELENG_4_5/src/sys/ZORK i386 >Description: When a USB keyboard is detached while a process has /dev/kbd1 open, the machine crashes hard when the process tries to fclose() the file. >How-To-Repeat: int main(void) { FILE *fp; /* USB keyboard is attached. */ fp = fopen("/dev/kbd1", "r"); if(fp) { printf("Unplug the keyboard in the next 10 seconds.\n"); sleep(10); } else { fprintf(stderr, "Couldn't open /dev/kbd1\n"); exit(1); } /* USB keyboard is detached by now. */ fclose(fp); /* Boom. */ exit(0); } >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 17:21:43 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A4B9037B405; Fri, 1 Feb 2002 17:21:31 -0800 (PST) Received: (from bmah@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g121Dh758493; Fri, 1 Feb 2002 17:13:43 -0800 (PST) (envelope-from bmah) Date: Fri, 1 Feb 2002 17:13:43 -0800 (PST) From: Message-Id: <200202020113.g121Dh758493@freefall.freebsd.org> To: juha.o.ylitalo@nokia.com, bmah@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/31460: ATAPI CD-ROM makes system reboot with DVD movie. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: ATAPI CD-ROM makes system reboot with DVD movie. State-Changed-From-To: feedback->closed State-Changed-By: bmah State-Changed-When: Fri Feb 1 17:13:02 PST 2002 State-Changed-Why: Submitter says this PR can be closed. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=31460 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Fri Feb 1 19:20:12 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7239837B417 for ; Fri, 1 Feb 2002 19:20:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g123K2G84892; Fri, 1 Feb 2002 19:20:02 -0800 (PST) (envelope-from gnats) Date: Fri, 1 Feb 2002 19:20:02 -0800 (PST) Message-Id: <200202020320.g123K2G84892@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Jed Clear Subject: Re: i386/30860: While install after "Mounting root from ufs:/dev/md0c" hang's and wont continiue Reply-To: Jed Clear Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR i386/30860; it has been noted by GNATS. From: Jed Clear To: freebsd-gnats-submit@FreeBSD.org, dubstar911@lycos.de Cc: Subject: Re: i386/30860: While install after "Mounting root from ufs:/dev/md0c" hang's and wont continiue Date: Fri, 01 Feb 2002 22:13:15 -0500 Why did this PR go to "feedback"? Near as I can tell the originator claims the suggestion didn't solve his original problem. If this PR is now tracking why an IRQ must be assigned for USB, is a costly[1] HW workaround to something that crept into 4.4 considered a solution? Is there a different PR for IRQ/USB issue? I was initially trying to see if this was fixed in 4.5. Thanks, -Jed [1]Costly (adj.): something that wastes an ISA IRQ to no apparent purpose -Murphy's Unabridged Dictionary of Computer Terms. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 1:41:34 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 91DE337B402; Sat, 2 Feb 2002 01:41:32 -0800 (PST) Received: (from dwmalone@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g129Wqf54456; Sat, 2 Feb 2002 01:32:52 -0800 (PST) (envelope-from dwmalone) Date: Sat, 2 Feb 2002 01:32:52 -0800 (PST) From: Message-Id: <200202020932.g129Wqf54456@freefall.freebsd.org> To: andryan@softhome.net, dwmalone@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: i386/34521: Upgrade problem Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: Upgrade problem State-Changed-From-To: feedback->closed State-Changed-By: dwmalone State-Changed-When: Sat Feb 2 01:32:22 PST 2002 State-Changed-Why: It was an out of date trafcount module. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34521 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 2:40: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 81DFF37B405 for ; Sat, 2 Feb 2002 02:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12Ae2h65743; Sat, 2 Feb 2002 02:40:02 -0800 (PST) (envelope-from gnats) Date: Sat, 2 Feb 2002 02:40:02 -0800 (PST) Message-Id: <200202021040.g12Ae2h65743@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Artem 'Zazoobr' Ignatjev" Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Reply-To: "Artem 'Zazoobr' Ignatjev" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34483; it has been noted by GNATS. From: "Artem 'Zazoobr' Ignatjev" To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Date: Sat, 2 Feb 2002 13:38:28 +0300 (MSK) Hi. Here is reply from author, Erez Zadok (from amd-dev mailing list): > From ezk@shekel.mcl.cs.columbia.edu Sat Feb 2 07:11:08 2002 > Date: Fri, 1 Feb 2002 23:11:02 -0500 (EST) > From: Erez Zadok > To: "Artem 'Zazoobr' Ignatjev" > Cc: amd-dev@cs.columbia.edu > Subject: Re: wrong execv() call for ${mount} and ${unmount} if mount type:=program in amd.map > I don't think that's a bug. The mount:= variable in amd requires special > syntax that's a little different than an argv[] list. If the command to > mount something is, say, "mount /this /here", then you have to specify the > map entry as > > type:=program;mount:="/etc/mount mount /this /here" > > IOW, you also list the program name's full path (here etc/mount) in the list > of args to the program type's mount:= variable. > > That has been the syntax for amd's program type since the beginning. It's a > source of unfortunate confusion to programmers who are used to think that > it's just an argv[] list. It's not. > Erez. But I still think, that in case of hardlinks, this patch will work, and all man have to do is to write the correct path in map; in other cases there could be no possibility to mount filesystem "by hands", without writing shell script/tiny program, which will call exec...() on one path, giving argv[0] with other prog's name. Wishes & regards, Artem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 7:10: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 761DD37B402 for ; Sat, 2 Feb 2002 07:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12FA2n72257; Sat, 2 Feb 2002 07:10:02 -0800 (PST) (envelope-from gnats) Date: Sat, 2 Feb 2002 07:10:02 -0800 (PST) Message-Id: <200202021510.g12FA2n72257@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Peter Pentchev Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Reply-To: Peter Pentchev Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34483; it has been noted by GNATS. From: Peter Pentchev To: Artem 'Zazoobr' Ignatjev Cc: bug-followup@FreeBSD.org Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Date: Sat, 2 Feb 2002 17:00:18 +0200 On Sat, Feb 02, 2002 at 02:40:02AM -0800, Artem 'Zazoobr' Ignatjev wrote: > Hi. > Here is reply from author, Erez Zadok (from amd-dev mailing list): > [snip] > > type:=program;mount:="/etc/mount mount /this /here" [snip] > > It's a > > source of unfortunate confusion to programmers who are used to think that > > it's just an argv[] list. It's not. > > But I still think, that in case of hardlinks, this patch will work, and all man have to do > is to write the correct path in map; in other cases there could be no possibility to mount > filesystem "by hands", without writing shell script/tiny program, which will call exec...() on > one path, giving argv[0] with other prog's name. Actually, I now believe Erez to be correct - I no longer think this is a bug. What he is trying to say is that you should provide argv[0] along with the other arguments, *after* the path to the program. This allows you to execute a program, giving it an argv[0] different from the filename of the executable file - exactly the same way that inetd.conf's syntax allows you to do the same. This is done to minimize the need for hardlinks, as you say; even without a hardlink, you are able to invoke, say, /sbin/mount as either 'mount' or 'mount_ffs' or 'mount_msdosfs' or whatever else you like. Just take a look at inetd.conf: it will illustrate this perfectly: ftp stream tcp nowait root /usr/libexec/ftpd ftpd -l This is equivalent to amd's syntax of: type:=program;mount:="/usr/libexec/ftpd ftpd -l" IOW, invoke the program executable file /usr/libexec/ftpd, and pass it an argv[] list of argv[0]="ftpd", argv[1]="-l", argv[2]=NULL. If you do not wish to invoke programs with names other than their executable files' names, you just have to provide the program name twice, as in: type:=program;mount:="mount mount blah" ..though this is both unusable and insecure (think PATH). In an ideal case, you would provide a full path to the executable and just a name for the program, as in: type:=program;mount:="/sbin/mount mount blah" Can you provide an example of an executable/program name, which can NOT be handled by this scheme? If not, I think this PR should be closed.. Still, thanks for your effort to improve FreeBSD by filing a report on what you believed was a genuine problem! G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@FreeBSD.org Hey, out there - is it *you* reading me, or is it someone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 7:20:14 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0CFF037B417 for ; Sat, 2 Feb 2002 07:20:04 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12FK3n73297; Sat, 2 Feb 2002 07:20:04 -0800 (PST) (envelope-from gnats) Date: Sat, 2 Feb 2002 07:20:04 -0800 (PST) Message-Id: <200202021520.g12FK3n73297@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Peter Pentchev Subject: Re: i386/34536: accept() blocks other threads Reply-To: Peter Pentchev Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR i386/34536; it has been noted by GNATS. From: Peter Pentchev To: Yixin Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: i386/34536: accept() blocks other threads Date: Sat, 2 Feb 2002 17:09:39 +0200 On Fri, Feb 01, 2002 at 11:14:19AM -0800, Yixin wrote: > > >Number: 34536 > >Category: i386 > >Synopsis: accept() blocks other threads > >Description: > I created a simple program: main thread listens to a port, and child > threads serve the requests. If main thread uses accept() to wait for > request, the new thread can not get scheduled. But if main thread uses > select() to wait for request, it works fine. I do not really think this should be considered a problem - accept(2) is a blocking call by default, its manual page does not anywhere document that it has special handling for the threads case. Since currently FreeBSD executes all threads in the context of a single process, a blocking syscall from one thread would certainly block all the others. You can either wait for the new threads and KSE implementation in FreeBSD 5.0, or work around this by using non-blocking sockets and select()'ing on them, as I can see you already do. Another possibility would be to install the linuxthreads port, which simulates the Linux way of handling threads as separate processes. However, I personally would recommend using a non-blocking socket and select() on it. G'luck, Peter -- Peter Pentchev roam@ringlet.net roam@FreeBSD.org This sentence was in the past tense. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 7:40: 6 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id A5A3D37B400 for ; Sat, 2 Feb 2002 07:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12Fe2175061; Sat, 2 Feb 2002 07:40:02 -0800 (PST) (envelope-from gnats) Date: Sat, 2 Feb 2002 07:40:02 -0800 (PST) Message-Id: <200202021540.g12Fe2175061@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Artem 'Zazoobr' Ignatjev" Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Reply-To: "Artem 'Zazoobr' Ignatjev" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/34483; it has been noted by GNATS. From: "Artem 'Zazoobr' Ignatjev" To: roam@ringlet.net, timon@memphis.mephi.ru Cc: bug-followup@FreeBSD.org Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Date: Sat, 2 Feb 2002 18:36:55 +0300 (MSK) > From roam@straylight.ringlet.net Sat Feb 2 18:21:17 2002 > Date: Sat, 2 Feb 2002 17:00:18 +0200 > From: Peter Pentchev > To: "Artem 'Zazoobr' Ignatjev" > Cc: bug-followup@FreeBSD.org > Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map > > Actually, I now believe Erez to be correct - I no longer think this is a bug. > What he is trying to say is that you should provide argv[0] along with > the other arguments, *after* the path to the program. This allows you > to execute a program, giving it an argv[0] different from the filename > of the executable file - exactly the same way that inetd.conf's syntax > allows you to do the same. This is done to minimize the need for > hardlinks, as you say; even without a hardlink, you are able to invoke, > say, /sbin/mount as either 'mount' or 'mount_ffs' or 'mount_msdosfs' or > whatever else you like. Yeah, I found description of this in _info am-utils_... So this pr should be closed, or something To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 8: 1:34 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0DAA337B404; Sat, 2 Feb 2002 08:01:33 -0800 (PST) Received: (from roam@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12FwYE76605; Sat, 2 Feb 2002 07:58:34 -0800 (PST) (envelope-from roam) Date: Sat, 2 Feb 2002 07:58:34 -0800 (PST) From: Message-Id: <200202021558.g12FwYE76605@freefall.freebsd.org> To: timon@memphis.mephi.ru, roam@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: bin/34483: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: wrong execv() call in amd for ${mount} and ${unmount} if mount type:=program in amd.map State-Changed-From-To: feedback->closed State-Changed-By: roam State-Changed-When: Sat Feb 2 07:55:39 PST 2002 State-Changed-Why: The originator agrees that the amd syntax allows both the executable image name and the argv[0] array to be specified unambiguously. Still, thank you for reporting what you considered a genuine problem! http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34483 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 8:11:34 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0ED5937B400; Sat, 2 Feb 2002 08:11:33 -0800 (PST) Received: (from roam@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12G4Fc77225; Sat, 2 Feb 2002 08:04:15 -0800 (PST) (envelope-from roam) Date: Sat, 2 Feb 2002 08:04:15 -0800 (PST) From: Message-Id: <200202021604.g12G4Fc77225@freefall.freebsd.org> To: yxpan@yahoo.com, roam@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: i386/34536: accept() blocks other threads Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: accept() blocks other threads State-Changed-From-To: open->closed State-Changed-By: roam State-Changed-When: Sat Feb 2 07:59:14 PST 2002 State-Changed-Why: accept(2) is documented as a blocking syscall. In FreeBSD's current threads implementation, blocking syscalls block the whole process - all of its threads. The possible ways around that are: using the linuxthreads port, waiting for FreeBSD 5.0's KSE's, or using non-blocking sockets and select(2) as described in the PR. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 10:41:35 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 6158037B400; Sat, 2 Feb 2002 10:41:33 -0800 (PST) Received: (from matusita@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12IaN409383; Sat, 2 Feb 2002 10:36:23 -0800 (PST) (envelope-from matusita) Date: Sat, 2 Feb 2002 10:36:23 -0800 (PST) From: Message-Id: <200202021836.g12IaN409383@freefall.freebsd.org> To: hendrik@scholz.net, matusita@FreeBSD.org, freebsd-bugs@FreeBSD.org, des@FreeBSD.org Subject: Re: bin/34507: systerm doesn't permit local login because two pam modules are missing after upgrading to -CURRENT Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: systerm doesn't permit local login because two pam modules are missing after upgrading to -CURRENT State-Changed-From-To: open->analyzed State-Changed-By: matusita State-Changed-When: Sat Feb 2 10:32:23 PST 2002 State-Changed-Why: It seems that it is the same change of src/lib/libpam/modules/Makefile rev 1.17. If yes, this PR can be closed. But I do not close this PR, leaving the decision to PAM maintainer. Responsible-Changed-From-To: freebsd-bugs->des Responsible-Changed-By: matusita Responsible-Changed-When: Sat Feb 2 10:32:23 PST 2002 Responsible-Changed-Why: des is working on PAM area. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=34507 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 13:10:19 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7A04237B417 for ; Sat, 2 Feb 2002 13:10:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g12LA2944227; Sat, 2 Feb 2002 13:10:02 -0800 (PST) (envelope-from gnats) Date: Sat, 2 Feb 2002 13:10:02 -0800 (PST) Message-Id: <200202022110.g12LA2944227@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Archie Cobbs Subject: Re: kern/31586: netgraph bridges cause connectivity probs from bridge Reply-To: Archie Cobbs Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/31586; it has been noted by GNATS. From: Archie Cobbs To: freebsd-gnats-submit@FreeBSD.org, michaelb@thus.net Cc: Subject: Re: kern/31586: netgraph bridges cause connectivity probs from bridge Date: Sat, 02 Feb 2002 12:47:36 -0800 I think the problem is the delayed checksum support added to FreeBSD. The delayed checksum code makes the (reasonable) assumption in ip_output() that a packet routed to a specific interface will actually be transmitted by the hardware associated with that interface. This is not necessarily true when netgraph is being used. The solution would be to modify ng_ether() to compute on-demand any delayed checksums for packets leaving the 'lower' hook when that hook is attached to another node. I'll try to work on this soon. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 14: 7:48 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id BC37837B402; Sat, 2 Feb 2002 14:07:43 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 2 Feb 2002 22:07:42 +0000 (GMT) Date: Sat, 2 Feb 2002 22:07:42 +0000 From: David Malone To: roam@FreeBSD.org Cc: yxpan@yahoo.com, freebsd-bugs@FreeBSD.org Subject: Re: i386/34536: accept() blocks other threads Message-ID: <20020202220742.GA14170@walton.maths.tcd.ie> References: <200202021604.g12G4Fc77225@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200202021604.g12G4Fc77225@freefall.freebsd.org> User-Agent: Mutt/1.3.25i Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, Feb 02, 2002 at 08:04:15AM -0800, roam@FreeBSD.org wrote: > Synopsis: accept() blocks other threads > > State-Changed-From-To: open->closed > State-Changed-By: roam > State-Changed-When: Sat Feb 2 07:59:14 PST 2002 > State-Changed-Why: > accept(2) is documented as a blocking syscall. In FreeBSD's current > threads implementation, blocking syscalls block the whole process - all > of its threads. The possible ways around that are: using the > linuxthreads port, waiting for FreeBSD 5.0's KSE's, or using > non-blocking sockets and select(2) as described in the PR. Surely this can't be a valid explaination for the problem? Syscalls like select, wait4 and read are documented to block, but libc_r provides magic versions which only block the current thread. I note a version of accept is included in libc_r. I'd guess that one of the following has happened: 1) the POSIX threads spec says that accept should block, 2) there is a bug in the libc_r version of accept, 3) there is a bug in the code using accept. I honestly don't know much about POSIX threads, but I'd guess that (3) is a possibility 'cos sockets are created in the example code before the threads system is initialised, which might mean that the socket is getting created with incorrect settings of some sort. (I do note that Sheldon closed a PR recently with a similar reason, but the function in question was msgrcv(3), which might be hard to produce a non-blocking version of within libc_r because I don't think you can poll(2) on message queue and I think libc_r uses poll to do things in a non-blocking way.) If I'm miles off here, please correct me... David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 14:15:43 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by hub.freebsd.org (Postfix) with ESMTP id 5257F37B416; Sat, 2 Feb 2002 14:15:36 -0800 (PST) Received: from news1.macomnet.ru (news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.3/8.11.3) with ESMTP id g12MFPO6040486; Sun, 3 Feb 2002 01:15:26 +0300 (MSK) Date: Sun, 3 Feb 2002 01:15:23 +0300 (MSK) From: Maxim Konovalov To: David Malone Cc: roam@FreeBSD.ORG, , Subject: Re: i386/34536: accept() blocks other threads In-Reply-To: <20020202220742.GA14170@walton.maths.tcd.ie> Message-ID: <20020203011345.G59736-100000@news1.macomnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 22:07-0000, Feb 2, 2002, David Malone wrote: > On Sat, Feb 02, 2002 at 08:04:15AM -0800, roam@FreeBSD.org wrote: > > Synopsis: accept() blocks other threads > > > > State-Changed-From-To: open->closed > > State-Changed-By: roam > > State-Changed-When: Sat Feb 2 07:59:14 PST 2002 > > State-Changed-Why: > > accept(2) is documented as a blocking syscall. In FreeBSD's current > > threads implementation, blocking syscalls block the whole process - all > > of its threads. The possible ways around that are: using the > > linuxthreads port, waiting for FreeBSD 5.0's KSE's, or using > > non-blocking sockets and select(2) as described in the PR. > > Surely this can't be a valid explaination for the problem? Syscalls > like select, wait4 and read are documented to block, but libc_r > provides magic versions which only block the current thread. I note > a version of accept is included in libc_r. I'd guess that one of > the following has happened: > > 1) the POSIX threads spec says that accept should block, > 2) there is a bug in the libc_r version of accept, > 3) there is a bug in the code using accept. > > I honestly don't know much about POSIX threads, but I'd guess that > (3) is a possibility 'cos sockets are created in the example code > before the threads system is initialised, which might mean that the > socket is getting created with incorrect settings of some sort. > > (I do note that Sheldon closed a PR recently with a similar reason, > but the function in question was msgrcv(3), which might be hard to > produce a non-blocking version of within libc_r because I don't > think you can poll(2) on message queue and I think libc_r uses poll > to do things in a non-blocking way.) > > If I'm miles off here, please correct me... I believe you are correct, David, and we have to reopen this PR. -- Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer phone: +7 (095) 796-9079, mailto: maxim@macomnet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 18:30: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 912E737B417 for ; Sat, 2 Feb 2002 18:30:00 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g132U0o01745; Sat, 2 Feb 2002 18:30:00 -0800 (PST) (envelope-from gnats) Received: from maynard.mail.mindspring.net (maynard.mail.mindspring.net [207.69.200.243]) by hub.freebsd.org (Postfix) with ESMTP id 6F85A37B416 for ; Sat, 2 Feb 2002 18:26:04 -0800 (PST) Received: from bstnma1-ar1-4-62-117-088.elnk.dsl.gtei.net ([4.62.117.88] helo=polkan2.dyndns.org) by maynard.mail.mindspring.net with esmtp (Exim 3.33 #1) id 16XCLz-0005sv-00 for FreeBSD-gnats-submit@freebsd.org; Sat, 02 Feb 2002 21:26:03 -0500 Received: (from meshko@localhost) by polkan2.dyndns.org (8.11.6/8.11.6) id g132Qxd00808; Sat, 2 Feb 2002 21:26:59 -0500 (EST) (envelope-from meshko) Message-Id: <200202030226.g132Qxd00808@polkan2.dyndns.org> Date: Sat, 2 Feb 2002 21:26:59 -0500 (EST) From: Mikhail Kruk Reply-To: Mikhail Kruk To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: misc/34568: turning printer on and off hangs the computer Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34568 >Category: misc >Synopsis: turning printer on and off hangs the computer >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 02 18:30:00 PST 2002 >Closed-Date: >Last-Modified: >Originator: Mikhail Kruk >Release: FreeBSD 4.5-STABLE i386 >Organization: Mikhail Kruk >Environment: System: FreeBSD polkan2.dyndns.org 4.5-STABLE FreeBSD 4.5-STABLE #0: Wed Jan 30 21:40:19 EST 2002 meshko@polkan2.dyndns.org:/usr/src/sys/compile/FBPK2 i386 >Description: I've tried printing a pdf file. I have apsfilter installed. The printer (HP Deskjet) made a couple of weird sounds and started blinking the out of paper light. I turned it off and on. Light blinking again. lprm the job -- still blinking. Turn off and on a couple of times -- and computer is hanging. Reproduced twice now. Printing worked fine before upgrade to 4.5 (from 4.4) I've had similar problem before I beleive. It was caused by some sort of apsfilter misconfiguration. So looks like there is some problem lurking around in the parallel port driver code... >How-To-Repeat: I don't think it's easy to reproduce that. Required some kind of weird apsfilter problem which makes printer go crazy and do something bad to the os. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message From owner-freebsd-bugs Sat Feb 2 19:41:31 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8141C37B975 for ; Sat, 2 Feb 2002 19:40:01 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g133e1412369; Sat, 2 Feb 2002 19:40:01 -0800 (PST) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 7C0D637B9A0 for ; Sat, 2 Feb 2002 19:39:14 -0800 (PST) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g133dEt12290; Sat, 2 Feb 2002 19:39:14 -0800 (PST) (envelope-from nobody) Message-Id: <200202030339.g133dEt12290@freefall.freebsd.org> Date: Sat, 2 Feb 2002 19:39:14 -0800 (PST) From: Ming Zhang To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: kern/34569: kernel panic. Related to softupdate Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 34569 >Category: kern >Synopsis: kernel panic. Related to softupdate >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Feb 02 19:40:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Ming Zhang >Release: FreeBSD 4.5-RC >Organization: >Environment: shell# uname -a FreeBSD shell.unixbox.com 4.5-RC FreeBSD 4.5-RC #5: Thu Jan 24 15:57:55 PST 2002 ming@shell.unixbox.com:/usr/src/sys/compile/unixbox i386 >Description: Here is what I see in the log after the machine crashed: Feb 2 19:26:59 shell /kernel: /dev/ad2s1f: UNEXPECTED SOFT UPDATE INCONSISTENCY ; RUN fsck MANUALLY. Feb 2 19:26:59 shell /kernel: THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCON SISTENCY: Feb 2 19:26:59 shell /kernel: Feb 2 19:26:59 shell /kernel: /dev/ad2s1f (/var) Feb 2 19:26:59 shell /kernel: Automatic file system check failed... help! Feb 2 19:26:59 shell /kernel: Enter full pathname of shell or RETURN for /bin/s h: here is the gdb backtrace of the core: gdb -k kernel.33 ming GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... IdlePTD at phsyical address 0x002c3000 initial pcb at physical address 0x002457a0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x28 fault code = supervisor read, page not present instruction pointer = 0x8:0xc019c9f9 stack pointer = 0x10:0xc0226444 frame pointer = 0x10:0xc0226460 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault Uptime: 8d21h41m40s dumping to dev #ad/0x20001, offset 1656001 dump ata0: resetting devices .. done 191 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 0xc01485c2 in dumpsys () (kgdb) bt #0 0xc01485c2 in dumpsys () #1 0xc01483d7 in boot () #2 0xc01487b8 in poweroff_wait () #3 0xc01f5d0a in trap_fatal () #4 0xc01f59dd in trap_pfault () #5 0xc01f55c7 in trap () #6 0xc01a87dc in acquire_lock () #7 0xc01ac840 in softdep_update_inodeblock () #8 0xc01a78f5 in ffs_update () #9 0xc01b12e5 in ffs_fsync () #10 0xc01afbbf in ffs_sync () #11 0xc0178537 in sync () #12 0xc014818a in boot () #13 0xc01487b8 in poweroff_wait () #14 0xc01f5d0a in trap_fatal () #15 0xc01f59dd in trap_pfault () #16 0xc01f55c7 in trap () #17 0xc019c9f9 in syncache_socket () #18 0xc019cb40 in syncache_expand () #19 0xc019867c in tcp_input () #20 0xc0194863 in ip_input () #21 0xc01948c3 in ipintr () >How-To-Repeat: Don't know how >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message