From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 31 00:09:32 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF2C116A412 for ; Sun, 31 Dec 2006 00:09:32 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: from seaholm.caamora.com.au (seaholm.caamora.com.au [203.7.226.5]) by mx1.freebsd.org (Postfix) with ESMTP id 59EEC13C465 for ; Sun, 31 Dec 2006 00:09:29 +0000 (UTC) (envelope-from jon@seaholm.caamora.com.au) Received: (from jon@localhost) by seaholm.caamora.com.au (8.11.1/8.11.1) id kBUNwqU23632; Sun, 31 Dec 2006 10:58:52 +1100 (EST) Message-ID: <20061231105852.59380@caamora.com.au> Date: Sun, 31 Dec 2006 10:58:52 +1100 From: jonathan michaels To: freebsd-hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organisation: Caamora, PO Box 144, Rosebery NSW 1445 Australia Subject: some advice please --- amd semperon v opteron for dns/mail/nfs freebsd server X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2006 00:09:33 -0000 greetings all and best wishes for the coming new year. i'm about to setup a webserver on the freebsd system here, currently we are running several intel 386dx33 with co-processors 8-16 mb dram and an intel 486dx33 and a i486dx50 (16-32 mb dram) all are running scsi ontop of adaptec aha-1542b hostadapters, supporting between several 2-3x250 mb, 4x350 mb and several 3x1 gb. all have a scsi2 1x500 mb operating system dedicated spindle for the basic system software and for /, /etc, /var, /var/tmp, fs) media. christmas saw a compaq proliant 5500 (2xPIII 550/100 L2 1mb Xeon cpu, 5x9g1 gb scsi3 ultra drives and a SMART-2/P raid controller and 1g25 ecc/edo dimms i think) i also have several dec alpha server 2000 model 500's ( a pedestal with 2 cpu and 512 mb dram wuth a scsi raid cage (16 slots but only 6x3g5 scsi2 ultra drives) the other 2000.500 is a rack case sans its case, the 6 foot case was too much to lug and did't fit, wasnt wirth the effort for one 2 unit host, in hindsight (wonderfull this hindsight thing, isn't it???) it would have given me a tidy place for the proliant to live as well and make for easy transport around teh floor here, grrr, silly me o'h ell thats life. anyway, i'm looking to replace both/one of teh dec alphas with a more curently supported architecture thats likely to offer simialr performance and clean architecture, sorry that my world view. i've decided that the amd mob would be teh best of all possible worlds as candide would opine .. and give me a suitable 64 bit platform into teh future. my only difficulty is that i do not understand what are the differences between the two amd offerings, that is between teh opteron and teh semperon .. currently i don't need 'bleeding edge, blazingly fast i.e. inflated go fast because it s bigger numbers .. just reliable relatively cool (stable operating tempreatures) and long term reliability. what sort of motherboards would work best with freebsd, what if any gotchas are thier with the semperon and or teh opteron and which would be the best to use in a medium workload, relatively slow local network with a 50 percent of lits loading coming from internet network over teh (choke/throttle point) dialup via a permanent pppd connection running at 56/33k6 kilo bits its a reliable analogue modem thats been connected to the service providor's network for some 10 years now. stories, recomendations, suggestions would be much appreciated. as i said i do not understand what teh real difference is between the semperon/opteron and its for networking environment that its going to be going into, perhaps at some latter point in time another machine will be added to act as a cad/graphic arts/multimedia/graphical workstation ergo its floating point operations will be critical and need to be at least up in teh dec alpha processor class. i saw a dec alpha kitted out as a cad station a long time ago and compared to a motorola mc68060 something like that the axp chip put up a good showing and i was smitten .. the intel jobs were left in teh dust, didn't have a chance. oh well that was then and this is now. much appreciation for al the support we have goten from the freebsd support team over the years (we started back in v2.0.5-release, and are still going) thank you for all your tireless support. much gracious regards jonathan -- ================================================================ powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system ==== === appropriate solution in an inappropriate world === ==== From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 31 16:47:09 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A84C16A47B for ; Sun, 31 Dec 2006 16:47:09 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by mx1.freebsd.org (Postfix) with ESMTP id 3C86D13C459 for ; Sun, 31 Dec 2006 16:47:09 +0000 (UTC) (envelope-from gkontos.mail@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so5161113wxc for ; Sun, 31 Dec 2006 08:47:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=GPNJ9Abz5r/urQ8SdV+IziQZS2va8j9Ki16JvPvLcwkklF1QbrjTL0IqA/kSwhxY3Diyq/o90qLJP70XBgsmiGo83zzv+QH6pSBpxa/omZJ2oQJb23AGChSJr0aevKFpBOYdknlhH5qpMQzvjaYENzrgLnh/1O8oTeco6L+L4d8= Received: by 10.70.116.1 with SMTP id o1mr33276223wxc.1167581972943; Sun, 31 Dec 2006 08:19:32 -0800 (PST) Received: by 10.70.56.14 with HTTP; Sun, 31 Dec 2006 08:19:32 -0800 (PST) Message-ID: Date: Sun, 31 Dec 2006 18:19:32 +0200 From: "George Kontostanos" To: freebsd-hardware@freebsd.org In-Reply-To: <20061122001356.1841b243.ariff@FreeBSD.org> MIME-Version: 1.0 References: <20061122001356.1841b243.ariff@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Sound Problem or IRQ mixup? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2006 16:47:09 -0000 Any chance that Intel HDA will be part of 6.2 release? It is still missing in 6.2 RC2. The patch works though. Regards, George On 11/21/06, Ariff Abdullah wrote: > > On Tue, 21 Nov 2006 16:34:53 +0200 > "George Kontostanos" wrote: > > Hello everybody, > > I have a problem with my soundcard detection. The system is running > > on a ASUS P5B mobo on an Intel Core2Duo Processor at 2.4G with 2 > > Gigs of Ram. > > > [...] > > none0@pci0:27:0: class=0x040300 card=0x81ec1043 > > chip=0x284b8086 rev=0x02 hdr=0x00 > ^^^^^^^^^^ > > vendor = 'Intel Corporation' > > class = multimedia > > Intel HDA. Either apply patch from http://people.freebsd.org/~ariff/ , > or for your own convenience, grab binary kernel modules from > http://people.freebsd.org/~ariff/lowlatency/ . > > > > -- > Ariff Abdullah > FreeBSD > > ... Recording in stereo is obviously too advanced > and confusing for us idiot ***** users :P ........ > > > From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 24 12:37:24 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D26C816A40F for ; Sun, 24 Dec 2006 12:37:24 +0000 (UTC) (envelope-from ogautherot@vtr.net) Received: from vtr.cl (mail-b-out.cgp.vtr.net [200.83.2.215]) by mx1.freebsd.org (Postfix) with ESMTP id 1D22513C463 for ; Sun, 24 Dec 2006 12:37:23 +0000 (UTC) (envelope-from ogautherot@vtr.net) Received: from [192.168.5.4] (HELO av3.vtr.cl) by fe1.vtr.cl (CommuniGate Pro SMTP 5.0.12) with ESMTP id 52832503 for freebsd-hardware@freebsd.org; Sun, 24 Dec 2006 08:37:15 -0300 X-ASG-Debug-ID: 1166960233-013a00700024-e7p9Ku X-Barracuda-URL: http://192.168.5.4:8000/cgi-bin/mark.cgi X-Barracuda-Connect: mxfe4.cgp.vtr.net[192.168.6.5] X-Barracuda-Start-Time: 1166960233 Received: from vtr.cl (mxfe4.cgp.vtr.net [192.168.6.5]) by av3.vtr.cl (Spam Firewall) with ESMTP id 5D6A03AC723 for ; Sun, 24 Dec 2006 08:37:13 -0300 (CLST) Received: by fe4.vtr.cl (CommuniGate Pro PIPE 5.0.12) with PIPE id 53375777; Sun, 24 Dec 2006 08:37:13 -0300 X-NHContentFiltered: yes Received: from [200.120.119.5] (account ogautherot@vtr.net HELO olivier-bb) by fe4.vtr.cl (CommuniGate Pro SMTP 5.0.12) with ESMTPA id 53375661 for freebsd-hardware@freebsd.org; Sun, 24 Dec 2006 08:36:45 -0300 From: Olivier Gautherot To: freebsd-hardware@freebsd.org X-ASG-Orig-Subj: Re: memory holes Date: Sun, 24 Dec 2006 08:36:10 -0300 User-Agent: KMail/1.9.1 References: <458D36E4.9000900@dnainternet.net> <458D67CC.1050102@dnainternet.net> In-Reply-To: <458D67CC.1050102@dnainternet.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612240836.11747.ogautherot@vtr.net> X-Barracuda-Virus-Scanned: by Barracuda3 at vtr.cl X-Barracuda-Spam-Score: 0.50 X-Barracuda-Spam-Status: No, SCORE=0.50 using global scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=BSF_SC0_SA085, BSF_SC0_SA085b X-Barracuda-Spam-Report: Code version 3.1, rules version 3.1.4275 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.40 BSF_SC0_SA085b URI: Custom Rule SA085b 0.10 BSF_SC0_SA085 URI: Custom Rule SA085 Subject: Re: memory holes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: olivier@gautherot.net List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Dec 2006 12:37:25 -0000 Hi Erik! Mixing memory modules with different speeds is generally a dangerous thing to do. I would strongly recommend you match them all. The fact that your 384MB configuration worked is in no way a garantee that the 512MB config you describe should work (I would even say that it is a miracle that it ever worked in the first place). The problems you describe with the various *BSD sound very much like soft errors - which may happen with out-of-spec bus frequency. Merry Christmas Olivier On Saturday 23 December 2006 14:30, Erik Udo wrote: > OK. I've tested OpenBSD and NetBSD. > > Both find 512MB of ram, but.. > NetBSD crashes after boot stage when it starts to load the kernel. > (thanks NetBSD team for not building the kernel image with debugging > symbols, but you did build it with DDB) > > OpenBSD finds 512MB of ram too, but... > it wont find my hard disk, even thought it has wd0 as a hard disk in dmesh. > > To add to my previous post, i tested with 128MB PC100 + 32MB PC100. Both > memory modules was found by FreeBSD and put to use. > > Which leads me to the conclusion: Why can't FreeBSD use PC133 memory > when OpenBSD can? Did someone forget to port drivers for memory modules? :P > > Erik Udo wrote: > > I upgraded my hardware and software yesturday, and for some reason, > > FreeBSD only 'detects' 128MB of the memory, when the BIOS is clearly > > seeing 512MB. OpenBSD also finds 512MB of memory. > > > > So i added one 128MB ECC memory. There was one 128MB PC100 and 256MB > > PC133 memory before, and it worked fine on 6.2-PRERELASE. > > > > Now that i upgraded to 6.2-RC1, from 6.2-PRERELEASE and added the 128MB > > memory to the 384MB i had, the kernel started giving me this error on > > the first line of the kernel output: > > "Too many holes in the physical address space, giving up" > > > > Now, i searched google for anything, and found this earlier thread: > > http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg01624.html > > > > I also found this: > > http://lists.freebsd.org/pipermail/freebsd-hackers/2005-October/013932.ht > >ml > > > > Like the previous post says, the memory was found after the increased > > PHYSMAP_SIZE. I increased mine to 2*32, later 2*128. It didn't work. > > > > Also someone told me to add this line to the kernel config: > > options MAXMEM=524288 > > > > That didn't work either. > > > > I also tried to toggle all the bios settings on the computer, i even > > upgraded the bios. Nothing. > > > > Now i found out that OpenBSD sees 512MB of memory, so there must be some > > kind of trick to make FreeBSD recognize that memory too. > > > > Here is some output of my verbose boot: > > > > with 512MB: > > real memory = 134234112 (128 MB) > > Physical memory chunk(s): > > 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) > > 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) > > 0x0000000000c25000 - 0x0000000007d82fff, 118874112 bytes (29022 pages) > > avail memory = 121798656 (116 MB) > > > > Anyone have any ideas? > > > > Thanks, > > Erik > > _______________________________________________ > > freebsd-hardware@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > > To unsubscribe, send any mail to > > "freebsd-hardware-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" -- Olivier Gautherot Email: olivier@gautherot.net LinkedIn: http://www.linkedin.com/in/ogautherot MSN: ogautherot@hotmail.com From owner-freebsd-hardware@FreeBSD.ORG Sun Dec 24 12:58:06 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7CFA516A407 for ; Sun, 24 Dec 2006 12:58:06 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from isolokki.dnainternet.net (isolokki.dnainternet.net [212.149.75.39]) by mx1.freebsd.org (Postfix) with ESMTP id 08CDA13C46F for ; Sun, 24 Dec 2006 12:58:05 +0000 (UTC) (envelope-from erik.u@dnainternet.net) Received: from [192.168.1.11] (host-212-149-186-30.kpylaajakaista.net [212.149.186.30]) by isolokki.dnainternet.net (Postfix) with ESMTP id 05929D9EF; Sun, 24 Dec 2006 14:58:03 +0200 (EET) Message-ID: <458E795B.9020805@dnainternet.net> Date: Sun, 24 Dec 2006 14:58:03 +0200 From: Erik Udo User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: olivier@gautherot.net References: <458D36E4.9000900@dnainternet.net> <458D67CC.1050102@dnainternet.net> <200612240836.11747.ogautherot@vtr.net> In-Reply-To: <200612240836.11747.ogautherot@vtr.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: memory holes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Dec 2006 12:58:06 -0000 Yes, i got it working after having two memoy modules that match in bus speed. But, i was wondering how BIOS had 512MB of ram. Shouldn't the speed and stuff be invisible to the OS? Or did i have bad memory? Olivier Gautherot wrote: > Hi Erik! > > Mixing memory modules with different speeds is generally a dangerous thing to > do. I would strongly recommend you match them all. The fact that your 384MB > configuration worked is in no way a garantee that the 512MB config you > describe should work (I would even say that it is a miracle that it ever > worked in the first place). The problems you describe with the various *BSD > sound very much like soft errors - which may happen with out-of-spec bus > frequency. > > Merry Christmas > Olivier > > On Saturday 23 December 2006 14:30, Erik Udo wrote: >> OK. I've tested OpenBSD and NetBSD. >> >> Both find 512MB of ram, but.. >> NetBSD crashes after boot stage when it starts to load the kernel. >> (thanks NetBSD team for not building the kernel image with debugging >> symbols, but you did build it with DDB) >> >> OpenBSD finds 512MB of ram too, but... >> it wont find my hard disk, even thought it has wd0 as a hard disk in dmesh. >> >> To add to my previous post, i tested with 128MB PC100 + 32MB PC100. Both >> memory modules was found by FreeBSD and put to use. >> >> Which leads me to the conclusion: Why can't FreeBSD use PC133 memory >> when OpenBSD can? Did someone forget to port drivers for memory modules? :P >> >> Erik Udo wrote: >>> I upgraded my hardware and software yesturday, and for some reason, >>> FreeBSD only 'detects' 128MB of the memory, when the BIOS is clearly >>> seeing 512MB. OpenBSD also finds 512MB of memory. >>> >>> So i added one 128MB ECC memory. There was one 128MB PC100 and 256MB >>> PC133 memory before, and it worked fine on 6.2-PRERELASE. >>> >>> Now that i upgraded to 6.2-RC1, from 6.2-PRERELEASE and added the 128MB >>> memory to the 384MB i had, the kernel started giving me this error on >>> the first line of the kernel output: >>> "Too many holes in the physical address space, giving up" >>> >>> Now, i searched google for anything, and found this earlier thread: >>> http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg01624.html >>> >>> I also found this: >>> http://lists.freebsd.org/pipermail/freebsd-hackers/2005-October/013932.ht >>> ml >>> >>> Like the previous post says, the memory was found after the increased >>> PHYSMAP_SIZE. I increased mine to 2*32, later 2*128. It didn't work. >>> >>> Also someone told me to add this line to the kernel config: >>> options MAXMEM=524288 >>> >>> That didn't work either. >>> >>> I also tried to toggle all the bios settings on the computer, i even >>> upgraded the bios. Nothing. >>> >>> Now i found out that OpenBSD sees 512MB of memory, so there must be some >>> kind of trick to make FreeBSD recognize that memory too. >>> >>> Here is some output of my verbose boot: >>> >>> with 512MB: >>> real memory = 134234112 (128 MB) >>> Physical memory chunk(s): >>> 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) >>> 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) >>> 0x0000000000c25000 - 0x0000000007d82fff, 118874112 bytes (29022 pages) >>> avail memory = 121798656 (116 MB) >>> >>> Anyone have any ideas? >>> >>> Thanks, >>> Erik >>> _______________________________________________ >>> freebsd-hardware@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>> To unsubscribe, send any mail to >>> "freebsd-hardware-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 26 11:13:41 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AB2DE16A407 for ; Tue, 26 Dec 2006 11:13:41 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from talk.nabble.com (www.nabble.com [72.21.53.35]) by mx1.freebsd.org (Postfix) with ESMTP id 8FCC613C489 for ; Tue, 26 Dec 2006 11:13:41 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Gz9wq-0000ia-Mv for freebsd-hardware@freebsd.org; Tue, 26 Dec 2006 02:54:20 -0800 Message-ID: <8052383.post@talk.nabble.com> Date: Tue, 26 Dec 2006 02:54:20 -0800 (PST) From: freebsd To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: arun_sridhar2@yahoo.co.in Subject: freebsd - boot error X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Dec 2006 11:13:41 -0000 I am working in freebsd 6.0 unix system. Currently I am installing apache and php. Now I am not able to boot it normally. When I boot unix it automatically enters into the single user mode The error is 'ad0: FAILURE - READ_DMA status=51 error=40 LBA=7509039' CANNOT READ BLK: UNEXPECTED SOFT UPDATE INCONSISTENCY Note: I got this second time. First I reinstalled freebsd to rectify, but I dont want to do this again because I went through long into it I searched some sites which asked me to use fsck but in vein Please help me regards Arun -- View this message in context: http://www.nabble.com/freebsd---boot-error-tf2881914.html#a8052383 Sent from the freebsd-hardware mailing list archive at Nabble.com. From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 26 11:58:06 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E983D16A403 for ; Tue, 26 Dec 2006 11:58:06 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from auriate.fluffles.net (cust.95.160.adsl.cistron.nl [195.64.95.160]) by mx1.freebsd.org (Postfix) with ESMTP id A40D613C480 for ; Tue, 26 Dec 2006 11:58:06 +0000 (UTC) (envelope-from etc@fluffles.net) Received: from destiny ([10.0.0.21]) by auriate.fluffles.net with esmtpa (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GzAW1-000N8t-LG for freebsd-hardware@freebsd.org; Tue, 26 Dec 2006 12:30:41 +0100 Message-ID: <459107F2.2060903@fluffles.net> Date: Tue, 26 Dec 2006 12:30:58 +0100 From: Fluffles User-Agent: Thunderbird 1.5.0.8 (X11/20061114) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <8052383.post@talk.nabble.com> In-Reply-To: <8052383.post@talk.nabble.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: freebsd - boot error X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Dec 2006 11:58:07 -0000 freebsd wrote: > I am working in freebsd 6.0 unix system. Currently I am installing apache and > php. Now I am not able to boot it normally. When I boot unix it > automatically enters into the single user mode > The error is > 'ad0: FAILURE - READ_DMA status=51 error=40 > LBA=7509039' > CANNOT READ BLK: > UNEXPECTED SOFT UPDATE INCONSISTENCY > > Note: I got this second time. First I reinstalled freebsd to rectify, but I > dont want to do this again because I went through long into it > > I searched some sites which asked me to use fsck but in vein > Please help me > > regards > Arun > You hard drive contains bad sectors - sector 7509039. Solution: replace the disk, and recover as soon as possible any valuable information on the disk. - Veronica From owner-freebsd-hardware@FreeBSD.ORG Tue Dec 26 15:18:23 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A43816A492 for ; Tue, 26 Dec 2006 15:18:23 +0000 (UTC) (envelope-from kuzma.wm@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.233]) by mx1.freebsd.org (Postfix) with ESMTP id F0EFF13C473 for ; Tue, 26 Dec 2006 15:18:22 +0000 (UTC) (envelope-from kuzma.wm@gmail.com) Received: by nz-out-0506.google.com with SMTP id i11so1667658nzh for ; Tue, 26 Dec 2006 07:18:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=M5bMy99/4kUkIh5zWbTXcUXNTjCTTVUALQljWY12YWpcEeNiQJmLZsAxDqmv4u6xvqIQtBvBlcseg7Hte3k4MS58l6yYPhTSIq2DjeuUuyP2jIIlLRyWS0Sq6wesM7icutYvz8pDGBP4DnD7z2FXbAivj50tNSQJGJCj7cn2Gu0= Received: by 10.65.219.17 with SMTP id w17mr17913670qbq.1167144576053; Tue, 26 Dec 2006 06:49:36 -0800 (PST) Received: by 10.65.182.3 with HTTP; Tue, 26 Dec 2006 06:49:36 -0800 (PST) Message-ID: Date: Tue, 26 Dec 2006 16:49:36 +0200 From: "Ivan Kuznetsov" To: freebsd-hardware@freebsd.org, freebsd-drivers@freebsd.org, freebsd-questions@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: Subject: USB Modem at "HTC Wizard" aka "Qtek 9100" pda phone X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Dec 2006 15:18:23 -0000 I have some problems using my pda phone as usb-modem for my PC with FreeBSD 6.1-RELEASE At first I loaded: [kuzma@zealot] /home/kuzma # kldload umodem [kuzma@zealot] /home/kuzma # kldload ucom Then I activated "Modem Link" at my pda-device. According to all documentation that I founded during hours of "googling", after reconnection of my pda-device it should be smth like "ucom0" or "umodem0". But it still "ugen0". Has anybody noticed this problem and can help to solve it? Here is some information I've collected: ------------------------------------------------------------- [kuzma@zealot] /home/kuzma # usbdevs addr 1: UHCI root hub, Intel addr 2: Generic Serial, HTC addr 1: UHCI root hub, Intel ------------------------------------------------------------- [kuzma@zealot] /home/kuzma # dmesg | grep HTC ugen0: HTC Generic RNDIS, rev 2.00/0.00, addr 2 ugen0: HTC Generic Serial, rev 2.00/0.90, addr 2 ------------------------------------------------------------- [kuzma@zealot] /home/kuzma # ll /dev/u ugen0% ugen0.1% ugen0.2% ugen0.3% urandom@ usb% usb0% usb1% ------------------------------------------------------------- [kuzma@zealot] /home/kuzma # ll /dev/tty ttyd0% ttyd1.init% ttyp2% ttyp6% ttyv1% ttyv5% ttyv9% ttyvd% ttyd0.init% ttyd1.lock% ttyp3% ttyp7% ttyv2% ttyv6% ttyva% ttyve% ttyd0.lock% ttyp0% ttyp4% ttyp8% ttyv3% ttyv7% ttyvb% ttyvf% ttyd1% ttyp1% ttyp5% ttyv0% ttyv4% ttyv8% ttyvc% ------------------------------------------------------------- [kuzma@zealot] /home/kuzma # ps -ax | grep /usr/libexec/getty 713 ?? I 0:00,41 /usr/libexec/getty Pc ttyv10 714 ?? I 0:00,28 /usr/libexec/getty Pc ttyv11 715 ?? I 0:00,45 /usr/libexec/getty Pc ttyv12 716 ?? I 0:00,38 /usr/libexec/getty Pc ttyv13 705 v1 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv1 706 v2 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv2 707 v3 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv3 708 v4 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv4 709 v5 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv5 710 v6 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv6 711 v7 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv7 712 v9 IWs+ 0:00,00 /usr/libexec/getty Pc ttyv9 45318 p8 DL+ 0:00,00 grep /usr/libexec/getty ------------------------------------------------------------- -- ______________________________ Yours sincerely, Kuzma aka WildSurfer mailto: kuzma.wm@gmail.com From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 28 01:22:16 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 63C7C16A407 for ; Thu, 28 Dec 2006 01:22:16 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 909D913C466 for ; Thu, 28 Dec 2006 01:22:15 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kBS0hFdm059827; Wed, 27 Dec 2006 19:43:17 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Wed, 27 Dec 2006 19:42:53 -0500 User-Agent: KMail/1.9.4 References: <458D36E4.9000900@dnainternet.net> <200612240836.11747.ogautherot@vtr.net> <458E795B.9020805@dnainternet.net> In-Reply-To: <458E795B.9020805@dnainternet.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612271942.53932.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Wed, 27 Dec 2006 19:43:18 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2386/Wed Dec 27 13:32:31 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Erik Udo , olivier@gautherot.net Subject: Re: memory holes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 01:22:16 -0000 On Sunday 24 December 2006 07:58, Erik Udo wrote: > Yes, i got it working after having two memoy modules that match in bus > speed. > > But, i was wondering how BIOS had 512MB of ram. Shouldn't the speed and > stuff be invisible to the OS? Or did i have bad memory? It is invisible, but the memory may not have worked, and FreeBSD does a few simple memory tests on almost all the memory before it uses it, so FreeBSD may have just ignored the memory that didn't work. > Olivier Gautherot wrote: > > Hi Erik! > > > > Mixing memory modules with different speeds is generally a dangerous thing to > > do. I would strongly recommend you match them all. The fact that your 384MB > > configuration worked is in no way a garantee that the 512MB config you > > describe should work (I would even say that it is a miracle that it ever > > worked in the first place). The problems you describe with the various *BSD > > sound very much like soft errors - which may happen with out-of-spec bus > > frequency. > > > > Merry Christmas > > Olivier > > > > On Saturday 23 December 2006 14:30, Erik Udo wrote: > >> OK. I've tested OpenBSD and NetBSD. > >> > >> Both find 512MB of ram, but.. > >> NetBSD crashes after boot stage when it starts to load the kernel. > >> (thanks NetBSD team for not building the kernel image with debugging > >> symbols, but you did build it with DDB) > >> > >> OpenBSD finds 512MB of ram too, but... > >> it wont find my hard disk, even thought it has wd0 as a hard disk in dmesh. > >> > >> To add to my previous post, i tested with 128MB PC100 + 32MB PC100. Both > >> memory modules was found by FreeBSD and put to use. > >> > >> Which leads me to the conclusion: Why can't FreeBSD use PC133 memory > >> when OpenBSD can? Did someone forget to port drivers for memory modules? :P > >> > >> Erik Udo wrote: > >>> I upgraded my hardware and software yesturday, and for some reason, > >>> FreeBSD only 'detects' 128MB of the memory, when the BIOS is clearly > >>> seeing 512MB. OpenBSD also finds 512MB of memory. > >>> > >>> So i added one 128MB ECC memory. There was one 128MB PC100 and 256MB > >>> PC133 memory before, and it worked fine on 6.2-PRERELASE. > >>> > >>> Now that i upgraded to 6.2-RC1, from 6.2-PRERELEASE and added the 128MB > >>> memory to the 384MB i had, the kernel started giving me this error on > >>> the first line of the kernel output: > >>> "Too many holes in the physical address space, giving up" > >>> > >>> Now, i searched google for anything, and found this earlier thread: > >>> http://www.mail-archive.com/freebsd-hardware@freebsd.org/msg01624.html > >>> > >>> I also found this: > >>> http://lists.freebsd.org/pipermail/freebsd-hackers/2005-October/013932.ht > >>> ml > >>> > >>> Like the previous post says, the memory was found after the increased > >>> PHYSMAP_SIZE. I increased mine to 2*32, later 2*128. It didn't work. > >>> > >>> Also someone told me to add this line to the kernel config: > >>> options MAXMEM=524288 > >>> > >>> That didn't work either. > >>> > >>> I also tried to toggle all the bios settings on the computer, i even > >>> upgraded the bios. Nothing. > >>> > >>> Now i found out that OpenBSD sees 512MB of memory, so there must be some > >>> kind of trick to make FreeBSD recognize that memory too. > >>> > >>> Here is some output of my verbose boot: > >>> > >>> with 512MB: > >>> real memory = 134234112 (128 MB) > >>> Physical memory chunk(s): > >>> 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) > >>> 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) > >>> 0x0000000000c25000 - 0x0000000007d82fff, 118874112 bytes (29022 pages) > >>> avail memory = 121798656 (116 MB) > >>> > >>> Anyone have any ideas? > >>> > >>> Thanks, > >>> Erik > >>> _______________________________________________ > >>> freebsd-hardware@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >>> To unsubscribe, send any mail to > >>> "freebsd-hardware-unsubscribe@freebsd.org" > >> _______________________________________________ > >> freebsd-hardware@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >> To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 28 01:22:17 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3947616A40F for ; Thu, 28 Dec 2006 01:22:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id A11BB13C46D for ; Thu, 28 Dec 2006 01:22:16 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kBS0hFdl059827; Wed, 27 Dec 2006 19:43:16 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Wed, 27 Dec 2006 19:39:59 -0500 User-Agent: KMail/1.9.4 References: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> <4586e047.0c5f3bc7.600b.ffff85e7SMTPIN_ADDED@mx.google.com> <72c3a9570612190702j55d98b48s64a471e0923c786b@mail.gmail.com> In-Reply-To: <72c3a9570612190702j55d98b48s64a471e0923c786b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612271939.59771.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Wed, 27 Dec 2006 19:43:16 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2386/Wed Dec 27 13:32:31 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Sergey Lyubka Subject: Re: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 01:22:17 -0000 On Tuesday 19 December 2006 10:02, Sergey Lyubka wrote: > I figured out, that the APIC is responsible for that. If APIC is > turned off, then the box boots fine (although it cannot see more that > 1 CPU). Here is the dmesg with APIC disabled: > > Copyright (c) 1992-2006 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 is a registered trademark of The FreeBSD Foundation. > FreeBSD 6.2-PRERELEASE #1: Tue Dec 19 14:29:09 GMT 2006 > devnull@valenok.netfort-iss.com:/usr/var/tmp/devnull/obj/usr/src/sys/MANAGER > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2995.51-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 > Features=0xbfebfbff > Features2=0xe4bd,> > AMD Features=0x20100000 > AMD Features2=0x1 > Cores per package: 2 > Logical CPUs per core: 2 > real memory = 1073381376 (1023 MB) > avail memory = 999518208 (953 MB) > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci5: on pcib1 > pcib2: at device 0.0 on pci5 > pci6: on pcib2 > pcib3: at device 0.0 on pci6 > pci7: on pcib3 > pcib4: at device 1.0 on pci6 > pci9: on pcib4 > pcib5: at device 0.3 on pci5 > pci10: on pcib5 > pcib6: at device 3.0 on pci0 > pci1: on pcib6 > pcib7: at device 0.0 on pci1 > pci2: on pcib7 > mpt0: port 0xec00-0xecff mem > 0xfddfc000-0xfddfffff,0xfdde0000-0xfddeffff irq 6 at device 8.0 on > pci2 > mpt0: [GIANT-LOCKED] > mpt0: MPI Version=1.5.12.0 > mpt0: mpt_cam_event: 0x16 > mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). > mpt0: mpt_cam_event: 0x12 > mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). > pcib8: at device 4.0 on pci0 > pci11: on pcib8 > bge0: mem > 0xfd8f0000-0xfd8fffff irq 6 at device 0.0 on pci11 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:10:18:19:68:ae > pcib9: at device 5.0 on pci0 > pci12: on pcib9 > pcib10: at device 6.0 on pci0 > pci13: on pcib10 > pcib11: at device 7.0 on pci0 > pci14: on pcib11 > pcib12: at device 28.0 on pci0 > pci3: on pcib12 > uhci0: port 0xcce0-0xccff irq 11 at > device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xccc0-0xccdf irq 10 at > device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xcca0-0xccbf irq 11 at > device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > pci0: at device 29.7 (no driver attached) > pcib13: at device 30.0 on pci0 > pci15: on pcib13 > pci15: at device 13.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on > pci0 > ata0: on atapci0 > ata1: on atapci0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > orm0: at iomem 0xc0000-0xc8fff,0xec000-0xeffff on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > uhub3: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 2 > uhub3: 4 ports with 4 removable, self powered > ukbd0: Dell Dell USB Keyboard, rev 1.10/3.01, addr 3, iclass 3/1 > kbd1 at ukbd0 > Timecounter "TSC" frequency 2995514748 Hz quality 800 > Timecounters tick every 1.000 msec > mpt0: mpt_cam_event: 0x16 > mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). > acd0: CDROM at ata0-master UDMA33 > ses0 at mpt0 bus 0 target 8 lun 0 > ses0: Fixed Enclosure Services SCSI-5 device > ses0: 300.000MB/s transfers > ses0: SCSI-3 SES Device > da0 at mpt0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 300.000MB/s transfers, Tagged Queueing Enabled > da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) > Trying to mount root from ufs:/dev/md0 > bge0: link state changed to UP > > > However, with APIC turned on, the boot stops here: > > Timecounters tick every 1.000 msec > mpt0: mpt_cam_event: 0x16 > mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). > acd0: CDROM at ata0-master UDMA33 > <---- hang ---> > > > It looks like it stopped on ses0 detection. The hang is nasty: event > the powercycle button didn't work, I had to unplug the power led and > plug it again. Any ideas ? Please advise. Please provide a verbose dmesg with APIC enabled (looks like you aren't getting interrupts on mpt0) as well as the output from mptable. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 28 13:50:05 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CEE7016A407 for ; Thu, 28 Dec 2006 13:50:05 +0000 (UTC) (envelope-from valenok@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 46A2213C47A for ; Thu, 28 Dec 2006 13:50:05 +0000 (UTC) (envelope-from valenok@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so5170821nfc for ; Thu, 28 Dec 2006 05:50:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hzbB9jkKpZImBoLUbdv19dfnzqko43qI7llttszwysk6hs9GxPqK6ohybR5tTTRyPm/X6rlyi9E8ti0pECFgDboe6JZ1flzoq6ZQP5eGZG00fM+fxiaainCzJgAjhw2f8Z8D5HQTk4fwM9EkZEAk8RGm/IcC6g3mVmBgYznHQLk= Received: by 10.49.55.18 with SMTP id h18mr6620324nfk.1167313804330; Thu, 28 Dec 2006 05:50:04 -0800 (PST) Received: by 10.48.48.17 with HTTP; Thu, 28 Dec 2006 05:50:03 -0800 (PST) Message-ID: <72c3a9570612280550uac9f932k2dc6cf4ab92ac8eb@mail.gmail.com> Date: Thu, 28 Dec 2006 13:50:03 +0000 From: "Sergey Lyubka" To: "John Baldwin" In-Reply-To: <72c3a9570612280527s5e586b52hf76bd52132d93235@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> <4586e047.0c5f3bc7.600b.ffff85e7SMTPIN_ADDED@mx.google.com> <72c3a9570612190702j55d98b48s64a471e0923c786b@mail.gmail.com> <200612271939.59771.jhb@freebsd.org> <72c3a9570612280527s5e586b52hf76bd52132d93235@mail.gmail.com> Cc: freebsd-hardware@freebsd.org Subject: Re: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 13:50:05 -0000 This is the successful boot with all CPU features enabled in the BIOS. Copyright (c) 1992-2006 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RC1 #0: Thu Nov 16 05:12:08 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2995.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff Features2=0xe4bd,> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 real memory = 1073381376 (1023 MB) avail memory = 1041211392 (992 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 64 != expected base 24 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 64-87 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci5: on pcib1 pcib2: at device 0.0 on pci5 pci6: on pcib2 pcib3: at device 0.0 on pci6 pci7: on pcib3 pcib4: at device 1.0 on pci6 pci9: on pcib4 pcib5: at device 0.3 on pci5 pci10: on pcib5 pcib6: at device 3.0 on pci0 pci1: on pcib6 pcib7: at device 0.0 on pci1 pci2: on pcib7 mpt0: port 0xec00-0xecff mem 0xfddfc000-0xfddfffff,0xfdde0000-0xfddeffff irq 64 at device 8.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.12.0 mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). pcib8: at device 4.0 on pci0 pci11: on pcib8 bge0: mem 0xfd8f0000-0xfd8fffff irq 16 at device 0.0 on pci11 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:10:18:19:68:ae pcib9: at device 5.0 on pci0 pci12: on pcib9 pcib10: at device 6.0 on pci0 pci13: on pcib10 pcib11: at device 7.0 on pci0 pci14: on pcib11 pcib12: at device 28.0 on pci0 pci3: on pcib12 uhci0: port 0xcce0-0xccff irq 21 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xccc0-0xccdf irq 20 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xcca0-0xccbf irq 21 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfdf00000-0xfdf003ff irq 21 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 2 uhub4: multiple transaction translators uhub4: 4 ports with 4 removable, self powered ukbd0: Dell Dell USB Keyboard, rev 1.10/3.01, addr 3, iclass 3/1 kbd2 at ukbd0 pcib13: at device 30.0 on pci0 pci15: on pcib13 pci15: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc8fff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 ses0 at mpt0 bus 0 target 8 lun 0 ses0: Fixed Enclosure Services SCSI-5 device ses0: 300.000MB/s transfers ses0: SCSI-3 SES Device SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #4 Launched! SMP: AP CPU #6 Launched! da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Trying to mount root from ufs:/dev/da0s1a bge0: link state changed to UP From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 28 13:54:51 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01ED316A415 for ; Thu, 28 Dec 2006 13:54:51 +0000 (UTC) (envelope-from valenok@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 4EBF813C46E for ; Thu, 28 Dec 2006 13:54:50 +0000 (UTC) (envelope-from valenok@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so5171958nfc for ; Thu, 28 Dec 2006 05:54:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DIyhgsaK6mPDkZ/UspAPB/duety5OlkTAHsk/rAPUWnCWtza6DSFSD2oD1EQrjbE5Vd+XBc6sUznGStFoAjAdjQbgzNSbj1ewmMKQWAUyrukt5nu3CHctJIPmj3nXM9ks40pM84h+SubFno+vt60Uk787kYYqU911zo0oiHDCT8= Received: by 10.49.80.12 with SMTP id h12mr1170027nfl.1167312474975; Thu, 28 Dec 2006 05:27:54 -0800 (PST) Received: by 10.48.48.17 with HTTP; Thu, 28 Dec 2006 05:27:54 -0800 (PST) Message-ID: <72c3a9570612280527s5e586b52hf76bd52132d93235@mail.gmail.com> Date: Thu, 28 Dec 2006 13:27:54 +0000 From: "Sergey Lyubka" To: "John Baldwin" In-Reply-To: <200612271939.59771.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> <4586e047.0c5f3bc7.600b.ffff85e7SMTPIN_ADDED@mx.google.com> <72c3a9570612190702j55d98b48s64a471e0923c786b@mail.gmail.com> <200612271939.59771.jhb@freebsd.org> Cc: freebsd-hardware@freebsd.org Subject: Re: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 13:54:51 -0000 Right, here is the dmesg where hang did not happen (usually happens though): Copyright (c) 1992-2006 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RC1 #0: Thu Nov 16 05:12:08 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2995.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 Features=0xbfebfbff Features2=0xe4bd,> AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Logical CPUs per core: 2 real memory = 1073381376 (1023 MB) avail memory = 1041211392 (992 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic1: WARNING: intbase 64 != expected base 24 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 64-87 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci5: on pcib1 pcib2: at device 0.0 on pci5 pci6: on pcib2 pcib3: at device 0.0 on pci6 pci7: on pcib3 pcib4: at device 1.0 on pci6 pci9: on pcib4 pcib5: at device 0.3 on pci5 pci10: on pcib5 pcib6: at device 3.0 on pci0 pci1: on pcib6 pcib7: at device 0.0 on pci1 pci2: on pcib7 mpt0: port 0xec00-0xecff mem 0xfddfc000-0xfddfffff,0xfdde0000-0xfddeffff irq 64 at device 8.0 on pci2 mpt0: [GIANT-LOCKED] mpt0: MPI Version=1.5.12.0 mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). mpt0: mpt_cam_event: 0x12 mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). mpt0: mpt_cam_event: 0x16 mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). pcib8: at device 4.0 on pci0 pci11: on pcib8 bge0: mem 0xfd8f0000-0xfd8fffff irq 16 at device 0.0 on pci11 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:10:18:19:68:ae pcib9: at device 5.0 on pci0 pci12: on pcib9 pcib10: at device 6.0 on pci0 pci13: on pcib10 pcib11: at device 7.0 on pci0 pci14: on pcib11 pcib12: at device 28.0 on pci0 pci3: on pcib12 uhci0: port 0xcce0-0xccff irq 21 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xccc0-0xccdf irq 20 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xcca0-0xccbf irq 21 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xfdf00000-0xfdf003ff irq 21 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered uhub4: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 2 uhub4: multiple transaction translators uhub4: 4 ports with 4 removable, self powered ukbd0: Dell Dell USB Keyboard, rev 1.10/3.01, addr 3, iclass 3/1 kbd2 at ukbd0 pcib13: at device 30.0 on pci0 pci15: on pcib13 pci15: at device 13.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 0 not in bitmap of probed irqs 0 sio0: port may not be enabled pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc8fff,0xec000-0xeffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master UDMA33 ses0 at mpt0 bus 0 target 8 lun 0 ses0: Fixed Enclosure Services SCSI-5 device ses0: 300.000MB/s transfers ses0: SCSI-3 SES Device SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 300.000MB/s transfers, Tagged Queueing Enabled da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) Trying to mount root from ufs:/dev/da0s1a bge0: link state changed to UP This time `sysctl hw.ncpu` shows 4. This is because I have disabled CPU features (hardware prefetch, virtualization, logical processor, etc). If these features enabled, hw.ncpu is 8. The box is 2 x Xeon Dell 1950. From owner-freebsd-hardware@FreeBSD.ORG Thu Dec 28 14:22:17 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87BA516A416 for ; Thu, 28 Dec 2006 14:22:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 321D713C470 for ; Thu, 28 Dec 2006 14:22:16 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kBSDu5rO065301; Thu, 28 Dec 2006 08:56:05 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Sergey Lyubka" Date: Thu, 28 Dec 2006 08:56:01 -0500 User-Agent: KMail/1.9.4 References: <72c3a9570612180904t6dba47das5ea0cbcc34cd2b4b@mail.gmail.com> <200612271939.59771.jhb@freebsd.org> <72c3a9570612280527s5e586b52hf76bd52132d93235@mail.gmail.com> In-Reply-To: <72c3a9570612280527s5e586b52hf76bd52132d93235@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612280856.01539.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Thu, 28 Dec 2006 08:56:05 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2386/Wed Dec 27 13:32:31 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-hardware@freebsd.org Subject: Re: Dell Poweredge 1950, boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Dec 2006 14:22:17 -0000 On Thursday 28 December 2006 08:27, Sergey Lyubka wrote: > Right, here is the dmesg where hang did not happen (usually happens though): Can you use a serial console to get the 'boot -v' dmesg when the hang does occur? Also, when the hang occurs, can you break into ddb and run 'show intrcnt'? > Copyright (c) 1992-2006 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 is a registered trademark of The FreeBSD Foundation. > FreeBSD 6.2-RC1 #0: Thu Nov 16 05:12:08 UTC 2006 > root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2995.51-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf64 Stepping = 4 > Features=0xbfebfbff > Features2=0xe4bd,> > AMD Features=0x20100000 > AMD Features2=0x1 > Cores per package: 2 > Logical CPUs per core: 2 > real memory = 1073381376 (1023 MB) > avail memory = 1041211392 (992 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 2 > cpu2 (AP): APIC ID: 4 > cpu3 (AP): APIC ID: 6 > ioapic0: Changing APIC ID to 8 > ioapic1: Changing APIC ID to 9 > ioapic1: WARNING: intbase 64 != expected base 24 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 64-87 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 2.0 on pci0 > pci5: on pcib1 > pcib2: at device 0.0 on pci5 > pci6: on pcib2 > pcib3: at device 0.0 on pci6 > pci7: on pcib3 > pcib4: at device 1.0 on pci6 > pci9: on pcib4 > pcib5: at device 0.3 on pci5 > pci10: on pcib5 > pcib6: at device 3.0 on pci0 > pci1: on pcib6 > pcib7: at device 0.0 on pci1 > pci2: on pcib7 > mpt0: port 0xec00-0xecff mem > 0xfddfc000-0xfddfffff,0xfdde0000-0xfddeffff irq 64 at device 8.0 on > pci2 > mpt0: [GIANT-LOCKED] > mpt0: MPI Version=1.5.12.0 > mpt0: mpt_cam_event: 0x16 > mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). > mpt0: mpt_cam_event: 0x12 > mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required). > mpt0: mpt_cam_event: 0x16 > mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required). > pcib8: at device 4.0 on pci0 > pci11: on pcib8 > bge0: mem > 0xfd8f0000-0xfd8fffff irq 16 at device 0.0 on pci11 > miibus0: on bge0 > brgphy0: on miibus0 > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, > 1000baseTX-FDX, auto > bge0: Ethernet address: 00:10:18:19:68:ae > pcib9: at device 5.0 on pci0 > pci12: on pcib9 > pcib10: at device 6.0 on pci0 > pci13: on pcib10 > pcib11: at device 7.0 on pci0 > pci14: on pcib11 > pcib12: at device 28.0 on pci0 > pci3: on pcib12 > uhci0: port 0xcce0-0xccff irq 21 at > device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0xccc0-0xccdf irq 20 at > device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0xcca0-0xccbf irq 21 at > device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > ehci0: mem 0xfdf00000-0xfdf003ff > irq 21 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub3: 6 ports with 6 removable, self powered > uhub4: vendor 0x04b4 product 0x6560, class 9/0, rev 2.00/0.0b, addr 2 > uhub4: multiple transaction translators > uhub4: 4 ports with 4 removable, self powered > ukbd0: Dell Dell USB Keyboard, rev 1.10/3.01, addr 3, iclass 3/1 > kbd2 at ukbd0 > pcib13: at device 30.0 on pci0 > pci15: on pcib13 > pci15: at device 13.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on > pci0 > ata0: on atapci0 > ata1: on atapci0 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0: configured irq 0 not in bitmap of probed irqs 0 > sio0: port may not be enabled > pmtimer0 on isa0 > orm0: at iomem 0xc0000-0xc8fff,0xec000-0xeffff on isa0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > ppc0: parallel port not found. > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0: port may not be enabled > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio1: configured irq 3 not in bitmap of probed irqs 0 > sio1: port may not be enabled > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > acd0: CDROM at ata0-master UDMA33 > ses0 at mpt0 bus 0 target 8 lun 0 > ses0: Fixed Enclosure Services SCSI-5 device > ses0: 300.000MB/s transfers > ses0: SCSI-3 SES Device > SMP: AP CPU #1 Launched! > SMP: AP CPU #2 Launched! > SMP: AP CPU #3 Launched! > da0 at mpt0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 300.000MB/s transfers, Tagged Queueing Enabled > da0: 34732MB (71132959 512 byte sectors: 255H 63S/T 4427C) > Trying to mount root from ufs:/dev/da0s1a > bge0: link state changed to UP > > > This time `sysctl hw.ncpu` shows 4. This is because I have disabled > CPU features (hardware prefetch, virtualization, logical processor, > etc). If these features enabled, hw.ncpu is 8. The box is 2 x Xeon > Dell 1950. > -- John Baldwin