From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 01:51:30 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 300AA16A4CF; Sun, 21 Mar 2004 01:51:30 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E945143D1D; Sun, 21 Mar 2004 01:51:28 -0800 (PST) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i2L9pAGR066729; Sun, 21 Mar 2004 10:51:26 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <405D658E.6070607@DeepCore.dk> Date: Sun, 21 Mar 2004 10:51:10 +0100 From: =?KOI8-R?Q?S=3Fren_Schmidt?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20040126 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eugene Grosbein References: <40591EC9.B797F608@kuzbass.ru> <20040318101846.E62520@carver.gumbysoft.com> <405A55B1.2565B7AF@kuzbass.ru> <20040319160620.D72884@carver.gumbysoft.com> <405D493B.C1F9C21E@grosbein.pp.ru> In-Reply-To: <405D493B.C1F9C21E@grosbein.pp.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: Eugene Grosbein cc: stable@FreeBSD.ORG cc: bug-followup@FreeBSD.ORG cc: sos@FreeBSD.ORG Subject: Re: kern/60526: Post-PAE stable SMP machine freezes X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2004 09:51:30 -0000 Eugene Grosbein wrote: > Doug White wrote: > > >>Someone referred me to a EETimes article, and I have hundreds of Tyan >>S2510/S2518 boards I can reproduce the problem on under multiple operating >>systems. > > > I googled a little for ROSB4. > > Here http://www.ussg.iu.edu/hypermail/linux/kernel/0206.1/1212.html > I've found the next statement: > > >>The system will lock solid when both IDE channels are accessed, >>and either one is using DMA. Since I want DMA, I simply abandon the >>secondary channel. > > > Is it possible do such a thing using FreeBSD? > > Next, Linux seem to have a workarond(?) since 2002: > > http://www.ussg.iu.edu/hypermail/linux/kernel/0206.1/0996.html > > Soren, could you please look at this? That fix newer worked AFAIK, today linux just dont allow UDMA on the ROSB4 at all. There is no good SW fix, and its also not established that a HW fix exists as well, however I cannot reproduce the problem on my ASUS CUR-DLS engineering sample, but ASUS wont tell anything about it... -- -S?ren From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 07:34:16 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A302016A4CE for ; Sun, 21 Mar 2004 07:34:16 -0800 (PST) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2656B43D5F for ; Sun, 21 Mar 2004 07:34:16 -0800 (PST) (envelope-from stijn@pcwin002.win.tue.nl) Received: from pcwin002.win.tue.nl (orb_rules@localhost [127.0.0.1]) by pcwin002.win.tue.nl (8.12.11/8.12.11) with ESMTP id i2LFYZT7005743; Sun, 21 Mar 2004 16:34:35 +0100 (CET) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.12.11/8.12.11/Submit) id i2LFYZkw005742; Sun, 21 Mar 2004 16:34:35 +0100 (CET) (envelope-from stijn) Date: Sun, 21 Mar 2004 16:34:35 +0100 From: Stijn Hoop To: Barry Pederson Message-ID: <20040321153435.GA99333@pcwin002.win.tue.nl> References: <7670000.1079480581@palle.girgensohn.se> <13770000.1079537744@rambutan.pingpong.net> <40591A47.1C6617C7@kuzbass.ru> <33830000.1079712277@durian.pingpong.net> <20040319163201.GA16433@svzserv.kemerovo.su> <405B2D7A.5050309@barryp.org> <20040319195637.GA93135@pcwin002.win.tue.nl> <405BADFC.2020704@barryp.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <405BADFC.2020704@barryp.org> User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! cc: stable@freebsd.org Subject: Re: ATI Radeon 9600 SE & OpenGL? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2004 15:34:16 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Mar 19, 2004 at 08:35:40PM -0600, Barry Pederson wrote: > Thanks, having a known-working configuration to sure helps, but after=20 > taking your config and just reducing the "Modes" list in the "Screen"=20 > section to something my monitor can handle - I still get the same=20 > result, a hard hang with a black screen. Have you tried lowering the AGP rate in your BIOS (if that's possible)? Just a shot in the dark... --Stijn --=20 The right half of the brain controls the left half of the body. This means that only left handed people are in their right mind. --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAXbYLY3r/tLQmfWcRAt9GAJ4/FqwOZSRThdP58ksgiV3XPmYXKwCfcVwY TBsDOQhY169+hADXfve5wq8= =dqa3 -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 08:56:34 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75B5916A4CF for ; Sun, 21 Mar 2004 08:56:34 -0800 (PST) Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E06C43D31 for ; Sun, 21 Mar 2004 08:56:34 -0800 (PST) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32] ident=danny) by cs.huji.ac.il with esmtp id 1B56FT-000GRY-1q for freebsd-stable@freebsd.org; Sun, 21 Mar 2004 18:56:31 +0200 X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: freebsd-stable@freebsd.org In-Reply-To: Message from Danny Braniss of "Fri, 19 Mar 2004 19:55:20 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 2004 18:56:30 +0200 From: Danny Braniss Message-Id: Subject: Re: cancontrol not working X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2004 16:56:34 -0000 > hi, > with a quiet resent -stable, camcontrol is giving: > > dev# camcontrol devlist > camcontrol: error sending CAMIOCOMMAND ioctl: Invalid argument > > anybody else seeing this? else i guess something got screwed at this end > (not the first time :-) solved! the KERNCONF file had: options MAXDSIZ="((2*1024-1)*1024*1024)" # this solved thread problems reducing it further to MAXDSIZ="(2000*1024*1024)" solved it danny From owner-freebsd-stable@FreeBSD.ORG Sun Mar 21 10:00:42 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C4A916A4CE for ; Sun, 21 Mar 2004 10:00:42 -0800 (PST) Received: from smtp2.mc.surewest.net (smtp2.mc.surewest.net [66.60.130.51]) by mx1.FreeBSD.org (Postfix) with SMTP id B5A3543D3F for ; Sun, 21 Mar 2004 10:00:41 -0800 (PST) (envelope-from dislists@updegrove.net) Received: (qmail 6742 invoked from network); 21 Mar 2004 18:00:40 -0000 Received: from unknown (HELO updegrove.net) (64.30.97.117) by smtp2.mc.surewest.net with SMTP; 21 Mar 2004 18:00:40 -0000 Received: (qmail 33752 invoked by uid 98); 21 Mar 2004 18:00:43 -0000 Received: from dislists@updegrove.net by smeagol.purgatory by uid 1008 with qmail-scanner-1.20 Clear:RC:1(192.168.0.2):. Processed in 0.113529 secs); 21 Mar 2004 18:00:43 -0000 X-Qmail-Scanner-Mail-From: dislists@updegrove.net via smeagol.purgatory X-Qmail-Scanner: 1.20 (Clear:RC:1(192.168.0.2):. Processed in 0.113529 secs) Received: from unknown (HELO updegrove.net) (192.168.0.2) by updegrove.net with SMTP; 21 Mar 2004 18:00:42 -0000 Message-ID: <405DD931.9080303@updegrove.net> Date: Sun, 21 Mar 2004 10:04:33 -0800 From: Rick Updegrove User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <005401c3c575$674d4ab0$41c3c3cf@office.sihope.com> In-Reply-To: <005401c3c575$674d4ab0$41c3c3cf@office.sihope.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TST: smtp2.mc.surewest.net SNWK2 0.31-33 ip=64.30.97.117 Subject: Re: SMP forcing crash/reboot in 4.9-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2004 18:00:42 -0000 A 4.8-STABLE machine I have been running with no problems for over 130 days straight uptime is now having unexplained reboots. They are not every day, or predictable, but they are happening. It is a low traffic qmail-scanner machine (7k a day) and I upgraded due to http://www.freebsd.org/releases/4.9R/errata.html Now I am sort of wishing I did not : ) I lost all the uptime and now the unexplained rebooting... I hesitate reporting this because most people point their fingers at the hardware. I am tempted to abandon this machine for another but if anyone is interested in taking a look please advise. Currently, I don't have the ability to #/etc/rc.conf #rebooting dumpdev=YES savecore=YES dumpdir="/var/crash" Is there anything else I should do? Right now I do not have the ability to attach a serial console to the crashing system and set the system to serial console. And even if I did have physical access I am not sure how to do that exactly... Is there another way to accomplish the debugging of this? I have been running FreeBSD so long with no problems I am sort of rusty at tracking them down, especially the elusive ones. So please point me in the right direction. Thanks! Rick P.S. dmesg follows Copyright (c) 1992-2003 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.9-STABLE #0: Wed Mar 3 00:02:36 PST 2004 root@govmail.ca.gov:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (499.15-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387fbff real memory = 536870912 (524288K bytes) avail memory = 519507968 (507332K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard: 2 CPUs cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0329000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 14 entries at 0xc00fdee0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #0 intpin 19 -> irq 2 IOAPIC #0 intpin 17 -> irq 16 pci0: on pcib0 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xfcd0-0xfcdf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 2 Timecounter "PIIX" frequency 3579545 Hz chip1: port 0x2180-0x218f at device 4.3 on pci0 pcib1: at device 7.0 on pci0 IOAPIC #0 intpin 16 -> irq 17 pci1: on pcib1 ahc0: port 0xe800-0xe8ff mem 0xfebfe000-0xfebfefff irq 17 at device 4.0 on pci1 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs pci1: (vendor=0x1000, dev=0x000c) at 7.0 irq 18 amr0: mem 0xf0000000-0xf7ffffff irq 16 at device 7.1 on pci0 amr0: Firmware D.02.05, BIOS B.01.04, 16MB RAM pcib2: at device 8.0 on pci0 pci2: on pcib2 fxp0: port 0xdce0-0xdcff mem 0xfe900000-0xfe9fffff,0xefffe000-0xefffefff irq 16 at device 2.0 on pci2 fxp0: Ethernet address 00:90:27:b7:09:76 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: (vendor=0x103c, dev=0x10c1) at 11.0 pci0: at 13.0 orm0: