From owner-freebsd-hardware Sun Aug 20 3:11:30 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by hub.freebsd.org (Postfix) with ESMTP id 5683537B43C for ; Sun, 20 Aug 2000 03:11:28 -0700 (PDT) Received: from execpc.com (d24.as5.appl.wi.voyager.net [169.207.124.152]) by mailgw00.execpc.com (8.9.1) id FAA17036; Sun, 20 Aug 2000 05:11:21 -0500 Message-ID: <399FAE84.7347B7C1@execpc.com> Date: Sun, 20 Aug 2000 05:10:12 -0500 From: Zach Johnson X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Boris Staeblow Cc: freebsd-hardware@freebsd.org Subject: Re: Can't load root fs with onboard ATA100 References: <20000817233758.1D1373E8E@dva.in-berlin.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>Is there anything at all that can be done about this? Or is the problem >>in the lack of ATA100 support and I should give up... (?!) > >Take the "ata-all.c" and "ata-dma.c" from -current in src/sys/dev/ata >and put them in your 4.1 tree, rebuild your kernel, reboot. Boris, thank you for your response. You have been the most helpful person yet. With your advice is definitely on the right track. Unfortunately, I cannot get my kernel to compile with those files from -current. I get compiler errors on ata-all.c if I use the config/make depend/make/make install method. I get strange errors if I try the make buildkernel KERNEL=MYKERNEL method. I tried copying all of the src/sys/dev/ata files from -current, but that doesn't fix things either. I had to add a file named bio.h to my source tree which was missing, this makes me wonder what other files from the -current tree I need. I want support for my ATA100 Hight Point Technologies HPT370 controller. The ATA code in -current provides that support. I need help importing the ATA code from -current into the 4.1-release tree so I compile a kernel. All help is appreciated! Thanks, Zach Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Aug 21 14:25:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id C062937B423; Mon, 21 Aug 2000 14:25:15 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id OAA14744; Mon, 21 Aug 2000 14:38:17 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008212138.OAA14744@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Cc: hardware@freebsd.org Subject: Updated driver for Mylex 160/170/352/2000/3000 controllers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Aug 2000 14:38:17 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The next BETA version of the 'mly' driver for Mylex's current family of PCI SCSI RAID controllers is now available from http://people.freebsd.org/~msmith/RAID/index.html#mylex. The major change in this version is the addition of status monitoring; the driver is now aware of the array status and will report drive status at attach time in the SCSI INQUIRY data, as well as logging status events. I don't have a 4.x system to test on at this stage, so I'm not trying to make the driver work on 4.x. Having said that, the issues involved in fixing it for 4.x are probably small, and if an interested user can provide me with a little assistance, I'm sure I can sort it out. Thanks as usual to Mylex for the hardware and data, and BSDi for funding this work. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Aug 21 21:47: 3 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp02.primenet.com (smtp02.primenet.com [206.165.6.132]) by hub.freebsd.org (Postfix) with ESMTP id B412A37B424 for ; Mon, 21 Aug 2000 21:47:00 -0700 (PDT) Received: (from daemon@localhost) by smtp02.primenet.com (8.9.3/8.9.3) id VAA07030 for ; Mon, 21 Aug 2000 21:44:52 -0700 (MST) Received: from king-gr.fhu.primenet.com(206.165.46.217), claiming to be "kinggr" via SMTP by smtp02.primenet.com, id smtpdAAADyaaQn; Mon Aug 21 21:44:44 2000 Message-ID: <014701c00bef$b01920e0$d92ea5ce@kinggr> From: "Rosemary & Gerald King" To: Subject: Linksys PCI 10/100 network card Date: Mon, 21 Aug 2000 21:16:02 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0144_01C00BB5.025B5520" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0144_01C00BB5.025B5520 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Has anyone gotten this card to work in Freebsd 3.2. I went to the = linksys site and pulled down some recommended kernel mods. The device-driver "pn" is not loaded = nor is the card identified by the PCI bus scan. I have three different systems all = running 3.2 exhibiting the same behaviour on two different cards. Any advice would be = appreciated. ------=_NextPart_000_0144_01C00BB5.025B5520 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 Has anyone gotten this card to work in Freebsd = 3.2.  I went to the linksys site and pulled
down some recommended kernel mods.  The = device-driver=20 "pn" is not loaded nor is the
card identified by the PCI bus scan.  I have = three=20 different systems all running 3.2 exhibiting
the same behaviour on two different cards.  Any = advice=20 would be appreciated.
------=_NextPart_000_0144_01C00BB5.025B5520-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Aug 22 9: 6:22 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from proxy.outblaze.com (proxy.outblaze.com [202.77.223.120]) by hub.freebsd.org (Postfix) with SMTP id 1831237B43E for ; Tue, 22 Aug 2000 09:06:19 -0700 (PDT) Received: (qmail 62826 invoked from network); 22 Aug 2000 16:06:16 -0000 Received: from unknown (HELO yusufg.portal2.com) (202.77.181.217) by proxy.outblaze.com with SMTP; 22 Aug 2000 16:06:16 -0000 Received: (qmail 28727 invoked by uid 500); 22 Aug 2000 16:06:15 -0000 Date: Wed, 23 Aug 2000 00:06:15 +0800 From: Yusuf Goolamabbas To: freebsd-hardware@freebsd.org Subject: RAID-0 over 2 disks or one single disk Message-ID: <20000823000615.A28706@outblaze.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am looking at setting up a relatively cheap/fast box and I wanted to know whether it makes more sense buying 2 15GB IBM 75GXP drives striped RAID-0 via a 3ware 6200 controller or just buy one 30GB IBM 75GXP The 15GB IBM 75GXP is approx $100 whereas the 30GB is approx $150. The 3ware should be approx be around $150. Would appreciate your thoughts on this ? Is there some cutover point at which RAID-0 gets better than a single drive ? Regards, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Aug 22 9:51:26 2000 Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 9B27437B423; Tue, 22 Aug 2000 09:51:23 -0700 (PDT) Subject: Re: Linksys PCI 10/100 network card In-Reply-To: <014701c00bef$b01920e0$d92ea5ce@kinggr> from Rosemary & Gerald King at "Aug 21, 2000 09:16:02 pm" To: king-gr@primenet.com (Rosemary & Gerald King) Date: Tue, 22 Aug 2000 09:51:23 -0700 (PDT) Cc: Freebsd-hardware@Freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20000822165123.9B27437B423@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Has anyone gotten this card to work in Freebsd 3.2. I went to the linksys site and pulled > down some recommended kernel mods. The device-driver "pn" is not loaded nor is the > card identified by the PCI bus scan. I have three different systems all running 3.2 exhibiting > the same behaviour on two different cards. Any advice would be appreciated. Unfortunately, you need to be a little more specific. LinkSys has had a bunch of 10/100 PCI cards on the market, several of which have the same product name. It's important to know which one you have. Here are the ones I know about: Really old LNE100TX ------------------- This has the 82c168 PNIC chipset on it and uses the PNIC's internal NWAY support, which is horribly broken. You can identify it by the presence of a relay on the board used for switching between 10 and 100Mbps modes, and the word PNIC on the controller chip in big letters. This board should work with the pn driver in 3.2. Not quite so old LNE100TX ------------------------- Uses the 82c169 PNIC chip and an external MII-compliant PHY. Since the external PHY provides the NWAY autonegotiation support, no relay is needed. Also works with the pn driver. LNE100TX version 2.0 -------------------- This card uses the 82c115 PNIC II chip with built-in NWAY. This card does not use the pn driver: it needs the mx driver. I don't know if the mx driver in 3.2 was modified to support this chip offhand. I think it may be in 3.3. LNE100TX version 4.0 and 4.1 ---------------------------- This card uses the ADMtek AN985 Centaur chipset, also with built-in NWAY. This chip was not supported in FreeBSD 3.2, but it is in 4.0 and later. All of these cards should work with the dc driver in FreeBSD 4.0 and up. The LNE100TX version 4.0/4.1 cards with the ADMtek chip are actually very good: they're fast, non-buggy and pretty cheap (I saw them at Fry's recently for $19.95). I tested one recently and was very pleased. I highly recommend them. Unfortunately, if you have this card, it won't work with 3.2 without a little bit of work. I do have a driver for FreeBSD 3.x at the following location: http://www.freebsd.org/~wpaul/ADMtek/3.0 I haven't tested this in a while, but it should work. What you need to do is this: - Download if_al.c and if_alreg.h from the URL above. - Copy them to /sys/pci on your system. - Edit /sys/conf/files and add the following line: pci/if_al.c optional al device-driver - Edit your kernel config file, e.g. /sys/i386/conf/GENERIC, and add the following line: device al0 - config and compile a new kernel Note that you must also have "controller pci0" in your kernel config as well since this is a PCI adapter. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Aug 22 10: 9:22 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 51FF337B42C for ; Tue, 22 Aug 2000 10:09:20 -0700 (PDT) Received: (from jin@localhost) by portnoy.lbl.gov (8.10.0/8.10.0) id e7MH9Js06003; Tue, 22 Aug 2000 10:09:19 -0700 (PDT) Date: Tue, 22 Aug 2000 10:09:19 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200008221709.e7MH9Js06003@portnoy.lbl.gov> To: freebsd-hardware@FreeBSD.ORG, yusufg@outblaze.com Subject: Re: RAID-0 over 2 disks or one single disk Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Yusuf Goolamabbas wrote: > Hi, I am looking at setting up a relatively cheap/fast box and I wanted > to know whether it makes more sense buying 2 15GB IBM 75GXP drives > striped RAID-0 via a 3ware 6200 controller or just buy one 30GB IBM > 75GXP > > The 15GB IBM 75GXP is approx $100 whereas the 30GB is approx $150. The > 3ware should be approx be around $150. Would appreciate your thoughts on > this ? Is there some cutover point at which RAID-0 gets better than a > single drive ? > > Regards, Yusuf Sounds like your configuration is $350 (2x15GB + 3ware) v.s. $150 (30GB) = 2.3, the throughput will be 170% v.s. 100% = 1.7 with same capacity. The ratio is not much different, but the absolute money value is. Unless you real care about the throughput, $350 can buy two 30GB that gives you 60GB + extra $50. Stripping on two disks is not very meaningful. For getting better throughput, you may think to use more disks for stripping. Otherwise, stay with a single disk, save money and energy. Just my thought, -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Aug 22 15: 2:20 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 2A4DB37B43C; Tue, 22 Aug 2000 15:02:15 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA22251; Tue, 22 Aug 2000 15:15:20 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008222215.PAA22251@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: hackers@freebsd.org Cc: hardware@freebsd.org Subject: Mylex driver, re-update Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Aug 2000 15:15:20 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After a pile more testing last night, I've updated the driver for the new Mylex controllers again. This code should now work correctly when loaded at boot time or statically compiled into the kernel, and as a bonus, it ought to work with 4.x systems as well. http://people.freebsd.org/~msmith/RAID/index.html#mylex As usual, success/failure reports would be greatly appreciated. Thanks! -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Aug 22 18:20:31 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 62BA337B440 for ; Tue, 22 Aug 2000 18:20:27 -0700 (PDT) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by smtp1.sentex.ca (8.11.0/8.11.0) with ESMTP id e7N1KQH08222; Tue, 22 Aug 2000 21:20:26 -0400 (EDT) Received: from chimp.simianscience.com (cage.simianscience.com [64.7.134.1]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id VAA29265; Tue, 22 Aug 2000 21:20:25 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: yusufg@outblaze.com Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: RAID-0 over 2 disks or one single disk Date: Wed, 23 Aug 2000 01:14:17 GMT Message-ID: <39a324ab.2551458@mail.sentex.net> References: In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22 Aug 2000 13:09:32 -0400, in sentex.lists.freebsd.hardware you wrote: >Yusuf Goolamabbas wrote: >> Hi, I am looking at setting up a relatively cheap/fast box and I wanted >> to know whether it makes more sense buying 2 15GB IBM 75GXP drives >> striped RAID-0 via a 3ware 6200 controller or just buy one 30GB IBM >> 75GXP >> >> The 15GB IBM 75GXP is approx $100 whereas the 30GB is approx $150. The >> 3ware should be approx be around $150. Would appreciate your thoughts on >> this ? Is there some cutover point at which RAID-0 gets better than a >> single drive ? >> >> Regards, Yusuf > >Sounds like your configuration is $350 (2x15GB + 3ware) v.s. $150 (30GB) = 2.3, >the throughput will be 170% v.s. 100% = 1.7 with same capacity. >The ratio is not much different, but the absolute money value is. > >Unless you real care about the throughput, $350 can buy two 30GB that gives >you 60GB + extra $50. Stripping on two disks is not very meaningful. > >For getting better throughput, you may think to use more disks for stripping. >Otherwise, stay with a single disk, save money and energy. You will see *some* improvement in disk access times. However, if your application is smart enough to make use of multiple disks as is (e.g. SQUID in my case) then you wont see too much difference to speak of. If you really need one big partition with good numbers, try with more than 2 disks. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada "Given enough time, 100 monkeys on 100 routers could setup a national IP network." (KDW2) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Aug 24 16: 1:51 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id F02F637B422; Thu, 24 Aug 2000 16:01:45 -0700 (PDT) Received: (from jin@localhost) by portnoy.lbl.gov (8.10.0/8.10.0) id e7ON1jX13791; Thu, 24 Aug 2000 16:01:45 -0700 (PDT) Date: Thu, 24 Aug 2000 16:01:45 -0700 (PDT) From: Jin Guojun (DSD staff) Message-Id: <200008242301.e7ON1jX13791@portnoy.lbl.gov> To: hardware@freebsd.org Subject: 370DLE motherboard Cc: smp@freebsd.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Was Subject: Intel 840 Chipset Discontinue > I was told by several of my distributors that all motherboards based off > of the Intel 840 chipset are being discontinued. That means the Supermicro > PIIDM3 and PIIIDME, and any other 840 board. > > Supermicro has two new boards, 370DL3 and 370DLE. Identical in specs to > the 840 boards, but using some kind of "ServerWork LE" chipset. However, I > have also been hearing bad news about these boards as well. > > Has anyone worked with these boards? Supermicro SAYS that they work fine > under Linux and Solaris. However, one of my distributors says thay they > are extremely touchy when it comes to memory. Only Registered PC133 ECC > memory will work. Just tested on Supermicro 370DLE motherboard and had problem with dual CPU. The system is configured with 1GB memory, Adaptec 3960D Ultra160 SCSI adapter, Intel Pro 10/100B/100+ NIC (fxp0), SysKonnect SK-9843 SX NIC (sk0). Running 4.1-RELEASE. The fxp0 is the primary network link, and the sk0 is a back-to-back connection to the other 370DLE (both are identical). With one CPU installed, the sk0 throughput is 900 Mbps. With two CPU installed, the sk0 throughput drops to 837 Mbps (non_SMP kernel). With two CPU installed + SMP kernel, the sk0 throughput drops to 770 Mbps. Case 1 and 3 are expected, however, the case 2 is NOT expected (non_SMP kernel). The dmesg shows some information about timer (8254) interrupt issue. APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IOAPIC #0 intpin 2 APIC_IO: routing 8254 via 8259 and IOAPIC #0 intpin 0 Waiting 7 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! Both machines have the same message. I wonder if the 4.1 does not recognize the board well, or there is something wrong with "ServerWork LE" chipset. Nothing affects the computation at all. So, the problem seems at interrupt somewhere when the second CPU is plugged in. Does any one have seen such behave? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Aug 24 20: 6:52 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 704EA37B423; Thu, 24 Aug 2000 20:06:47 -0700 (PDT) Received: from localhost (localhost.xtalwind.net [127.0.0.1]) by germanium.xtalwind.net (8.11.0/8.11.0) with ESMTP id e7P36jt98026; Thu, 24 Aug 2000 23:06:46 -0400 (EDT) Date: Thu, 24 Aug 2000 23:06:45 -0400 (EDT) From: jack To: Mike Smith Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: fxp, symbios, Intel MB problem In-Reply-To: <200008250232.TAA00816@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Today Mike Smith wrote: > The problem you're alluding to never manifested these symptoms. I couldn't recall the specifics, just the HW combination. > If you haven't resolved this already, try 'boot -v' and see if you get > any more verbose output (ie. so that we can for example tell if it's > still hung up in the fxp driver). It turned out to be an ne2000 compat. (ed driver) card that was also in the box. Since then I've come across two other ISA, ed driver, cards that won't work with 4.1 in boxes with two NICs. Thank you to who ever is responsible, I've wanted to get rid of those antiques for a while. :) If I get time I'll try them in my test box and see if I can narrow down the problem . -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Aug 24 23:48:14 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from synology.com (dns1.synology.com [202.173.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 2297437B42C for ; Thu, 24 Aug 2000 23:48:12 -0700 (PDT) Received: from derrenldev ([192.168.1.223]) by synology.com (8.9.3/8.9.3) with SMTP id OAA04863 for ; Fri, 25 Aug 2000 14:53:11 +0800 Reply-To: From: "Derren" To: Subject: Does FreeBSD support Promise Ultra ATA/100 Controller Card for PCI Date: Fri, 25 Aug 2000 14:48:04 +0800 Message-ID: <000001c00e60$6c1293e0$df01a8c0@derrenldev> MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: base64 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org RGVhciBhbGw6DQoNCkRvZXMgYW55IG9uZSBoYXZlIHRoZSBleHBlcmllbmNlIHdpdGggUHJvbWlz ZSBVbHRyYSBBVEEgY2FyZHM/DQpUaGUgUHJvbWlzZSBVbHRyYSBBVEEvNjYgY2FyZCB3b3JrcyB3 ZWxsIGluIEZyZWVCU0Qgc3lzdGVtLCBidXQgaXRzIFVsdHJhIEFUQS8xMDAgY2FyZCBkb2Vzbid0 Lg0KVGhlIEZyZWVCU0QgY2Fubm90IGRldGVjdCB0aGUgaGFyZCBkaXNrcyBhdHRhY2hlZCBvbiB0 aGUgVWx0cmEgQVRBLzEwMCBjYXJkLiANCkRvZXMgYW55IG9uZSBoYXZlIHRoZSBzb2x1dGlvbiBm b3IgdGhpcyBwcm9ibGVtPw0KDQpUaGFua3MgYSBsb3QNCg0KRGVycmVu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Aug 25 8:46:52 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from symbion.srrc.usda.gov (symbion.srrc.usda.gov [199.133.86.40]) by hub.freebsd.org (Postfix) with ESMTP id 66DCA37B422 for ; Fri, 25 Aug 2000 08:46:49 -0700 (PDT) Received: (from glenn@localhost) by symbion.srrc.usda.gov (8.9.3/8.9.3) id KAA52116 for hardware@freebsd.org; Fri, 25 Aug 2000 10:46:39 -0500 (CDT) (envelope-from glenn) From: Glenn Johnson Date: Fri, 25 Aug 2000 10:46:39 -0500 To: hardware@freebsd.org Subject: overheating AMD K6-2 400 Message-ID: <20000825104639.A51927@node1.cluster.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org About a year ago I purchased an AMD K6-2 400 MHz processor for my FreeBSD system at home. It had been working fine until recently. The last two months I have been seeing some rather strange problems like corrupted files from cvsup, bad dependencies from a buildworld even with a fresh object tree, and signals 4 and 10 during compilation. The last week I have had two spontaneous reboots which caused severe file system damage. I knew it was hardware trouble and I finally pinned it down to the CPU. The problems definitely start showing up after the CPU has warmed up a bit. It is obviously a thermal problem or at least temperature is a factor. I checked to make sure that the CPU fan was working and it is. I remembered people on the FreeBSD lists saying that they had to underclock there AMD K6-2s to get them stable so I clocked this one down to 350. The problems took a little longer to surface but still do. I should mention that the motherboard is a FIC VA503+ and the system had never been overclocked. I pulled the CPU out and put my old Cyrix 133 6x86-MX chip in. This is working fine but is slow of course. My questions are: Does it sound like the AMD chip is shot or can I try to enhance the cooling somehow and still use it? Or would I be better off getting another CPU? If I get another CPU should I get another AMD or should I go with one of the Cyrix MII models? I would want to put in a CPU that was at least 400 MHz. I know this is not specifically FreeBSD related but I have found that the people on the FreeBSD lists are the most knowledgeable. All responses are greatly appreciated. Thanks. -- Glenn Johnson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Aug 25 9: 8:55 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail2.aracnet.com (mail2.aracnet.com [216.99.193.35]) by hub.freebsd.org (Postfix) with ESMTP id 7765037B43E for ; Fri, 25 Aug 2000 09:08:54 -0700 (PDT) Received: from shell1.aracnet.com (shell1.aracnet.com [216.99.193.21]) by mail2.aracnet.com (8.9.3/8.9.3) with ESMTP id JAA26759; Fri, 25 Aug 2000 09:08:58 -0700 Received: by shell1.aracnet.com (8.9.3) id JAA27099; Fri, 25 Aug 2000 09:08:54 -0700 Date: Fri, 25 Aug 2000 09:08:54 -0700 (PDT) From: Rick Hamell To: Glenn Johnson Cc: hardware@FreeBSD.ORG Subject: Re: overheating AMD K6-2 400 In-Reply-To: <20000825104639.A51927@node1.cluster.srrc.usda.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > My questions are: Does it sound like the AMD chip is shot or can I try > to enhance the cooling somehow and still use it? Or would I be better > off getting another CPU? If I get another CPU should I get another AMD > or should I go with one of the Cyrix MII models? I would want to put in > a CPU that was at least 400 MHz. I'd still recommend getting a new CPU fan first, and make sure you have thermal grease on it. I've seen CPU fans that look like they're good but aren't going as fast as they use too... Rick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Aug 25 9:22:53 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 3433237B43C for ; Fri, 25 Aug 2000 09:22:51 -0700 (PDT) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id e7PGMVU18187; Fri, 25 Aug 2000 09:22:31 -0700 (PDT) Message-Id: <200008251622.e7PGMVU18187@ptavv.es.net> To: Glenn Johnson Cc: hardware@FreeBSD.ORG Subject: Re: overheating AMD K6-2 400 In-reply-to: Your message of "Fri, 25 Aug 2000 10:46:39 CDT." <20000825104639.A51927@node1.cluster.srrc.usda.gov> Date: Fri, 25 Aug 2000 09:22:31 -0700 From: "Kevin Oberman" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: Glenn Johnson > Date: Fri, 25 Aug 2000 10:46:39 -0500 > Sender: owner-freebsd-hardware@FreeBSD.ORG > > About a year ago I purchased an AMD K6-2 400 MHz processor for my > FreeBSD system at home. It had been working fine until recently. The > last two months I have been seeing some rather strange problems like > corrupted files from cvsup, bad dependencies from a buildworld even with > a fresh object tree, and signals 4 and 10 during compilation. The last > week I have had two spontaneous reboots which caused severe file system > damage. > > I knew it was hardware trouble and I finally pinned it down to the > CPU. The problems definitely start showing up after the CPU has warmed > up a bit. It is obviously a thermal problem or at least temperature is > a factor. I checked to make sure that the CPU fan was working and it > is. I remembered people on the FreeBSD lists saying that they had to > underclock there AMD K6-2s to get them stable so I clocked this one down > to 350. The problems took a little longer to surface but still do. I > should mention that the motherboard is a FIC VA503+ and the system had > never been overclocked. I pulled the CPU out and put my old Cyrix 133 > 6x86-MX chip in. This is working fine but is slow of course. > > My questions are: Does it sound like the AMD chip is shot or can I try > to enhance the cooling somehow and still use it? Or would I be better > off getting another CPU? If I get another CPU should I get another AMD > or should I go with one of the Cyrix MII models? I would want to put in > a CPU that was at least 400 MHz. No, it simply needs better cooling. My K6-III/450 was acting in a manner almost identical to yours. If you have a mobo that supports environmental monitoring, install healthd from the ports. You can use "healthd -d" to provide a running report on temperature. Mine would exceed 50 degrees C during a buildworld before it died and the temperature went up very quickly at some points. I have no doubt that gcc 2.95 hits the CPU much harder than 2.8 did. Also, the mobo monitors the temperature under the CPU while AMD specs a maximum temperature of 60 C on top of the chip. I suspect that the top get hotter than the bottom. I fixed the problem by spending $2 at Radio Shack for a little heat sink grease. Just unclipped the heat sink and spread a THIN layer of grease (just enough to have a layer of white) over the heat sink. Re-installed the heat sink and it ran like a champ. Buildworld ran without interruption or error for the first time since I upgraded to 4.0-Stable, and did so in a hot (29 C) room. Good luck! R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Aug 25 10:17:38 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from msgbas1tx.cos.agilent.com (msgbas1tx.cos.agilent.com [192.6.9.34]) by hub.freebsd.org (Postfix) with ESMTP id 63A3B37B424 for ; Fri, 25 Aug 2000 10:17:36 -0700 (PDT) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1tx.cos.agilent.com (Postfix) with ESMTP id C331027E; Fri, 25 Aug 2000 11:17:35 -0600 (MDT) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id 38724110; Fri, 25 Aug 2000 11:17:35 -0600 (MDT) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_18979)/8.9.3 SMKit7.0) with ESMTP id KAA15887; Fri, 25 Aug 2000 10:17:33 -0700 (PDT) Message-Id: <200008251717.KAA15887@mina.soco.agilent.com> To: "Kevin Oberman" Cc: Glenn Johnson , hardware@FreeBSD.ORG Subject: Re: overheating AMD K6-2 400 Reply-To: Darryl Okahata In-Reply-To: Your message of "Fri, 25 Aug 2000 09:22:31 PDT." <200008251622.e7PGMVU18187@ptavv.es.net> Mime-Version: 1.0 (generated by tm-edit 1.5) Content-Type: text/plain; charset=US-ASCII Date: Fri, 25 Aug 2000 10:17:33 -0700 From: Darryl Okahata Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kevin Oberman" wrote: > I fixed the problem by spending $2 at Radio Shack for a little heat > sink grease. Just unclipped the heat sink and spread a THIN layer of > grease (just enough to have a layer of white) over the heat > sink. Re-installed the heat sink and it ran like a champ. Buildworld > ran without interruption or error for the first time since I upgraded > to 4.0-Stable, and did so in a hot (29 C) room. Just being anal: for best heat conductivity, you want to spread a thin layer on *BOTH* the CPU and heat sink. Spreading a thin layer on just one is often enough, but placing a layer on both virtually guarantees the best heat conductivity. [ As Kevin said: you want a thin layer -- just enough to coat both sides. You don't want the grease "gooshing" out the sides (a tiny amount is OK, but, the less, the better). ] -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Aug 25 14:46:43 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by hub.freebsd.org (Postfix) with ESMTP id F32E537B424 for ; Fri, 25 Aug 2000 14:46:39 -0700 (PDT) Received: from asimov.phoenix.volant.org ([205.179.79.65]) by phoenix.volant.org with esmtp (Exim 1.92 #8) id 13SRJ9-0000dw-00; Fri, 25 Aug 2000 14:46:39 -0700 Received: from localhost (localhost [127.0.0.1]) by asimov.phoenix.volant.org (8.9.3+Sun/8.9.3) with SMTP id OAA14425; Fri, 25 Aug 2000 14:46:22 -0700 (PDT) From: patl@Phoenix.Volant.ORG Date: Fri, 25 Aug 2000 14:46:22 -0700 (PDT) Reply-To: patl@Phoenix.Volant.ORG Subject: Re: overheating AMD K6-2 400 To: Glenn Johnson Cc: hardware@freebsd.org In-Reply-To: <20000825104639.A51927@node1.cluster.srrc.usda.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Aug-00 at 08:46, Glenn Johnson (gjohnson@nola.srrc.usda.gov) wrote: > My questions are: Does it sound like the AMD chip is shot or can I try > to enhance the cooling somehow and still use it? Or would I be better > off getting another CPU? If I get another CPU should I get another AMD > or should I go with one of the Cyrix MII models? I would want to put in > a CPU that was at least 400 MHz. I'd replace the on-chip fan/heat sink; and make sure it made good contact via thermal grease. Then I'd add additional cooling to the case - probably one of the fan modules that fit in a PCI/ISA slot; and one that fits in a drive bay with a front-panel slot. (Assuming that you have both free.) The advantage of this is that even if you do wind up replacing the CPU, they are still helpful for the replacement system. I've been happy with my AMD based systems (ranging from a 133MHz 5x86 upgrade in a 486 socket to an Athlon 550); so I see no reason to change. Possibly someone with more in-depth knowlege of the heating characteristics of various chips might disagree. -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Aug 25 20:32:28 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from krell.webweaver.net (krell.webweaver.net [206.24.105.170]) by hub.freebsd.org (Postfix) with ESMTP id 799F937B43E for ; Fri, 25 Aug 2000 20:32:17 -0700 (PDT) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by krell.webweaver.net (Postfix) with ESMTP id D6B1820F04; Fri, 25 Aug 2000 20:26:53 -0700 (PDT) Content-Length: 2816 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000825104639.A51927@node1.cluster.srrc.usda.gov> Date: Fri, 25 Aug 2000 20:32:16 -0700 (PDT) From: "Nicole Harrington." To: Glenn Johnson Subject: RE: overheating AMD K6-2 400 Cc: hardware@freebsd.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If you are anywhere near a Fry's store, they have a very nice heat sink unit being sold for a Pent III or Zeon type of CPU, but it works fine for all socket 7 CPU's I have tried. It is huge... but very nice. It is gold, and round with the fan inside. I recommend it to anyone with heat problems on a socket 7. Also make sure your voltage setting is correct for that CPU. Nicole On 25-Aug-00 Glenn Johnson wrote: > About a year ago I purchased an AMD K6-2 400 MHz processor for my > FreeBSD system at home. It had been working fine until recently. The > last two months I have been seeing some rather strange problems like > corrupted files from cvsup, bad dependencies from a buildworld even with > a fresh object tree, and signals 4 and 10 during compilation. The last > week I have had two spontaneous reboots which caused severe file system > damage. > > I knew it was hardware trouble and I finally pinned it down to the > CPU. The problems definitely start showing up after the CPU has warmed > up a bit. It is obviously a thermal problem or at least temperature is > a factor. I checked to make sure that the CPU fan was working and it > is. I remembered people on the FreeBSD lists saying that they had to > underclock there AMD K6-2s to get them stable so I clocked this one down > to 350. The problems took a little longer to surface but still do. I > should mention that the motherboard is a FIC VA503+ and the system had > never been overclocked. I pulled the CPU out and put my old Cyrix 133 > 6x86-MX chip in. This is working fine but is slow of course. > > My questions are: Does it sound like the AMD chip is shot or can I try > to enhance the cooling somehow and still use it? Or would I be better > off getting another CPU? If I get another CPU should I get another AMD > or should I go with one of the Cyrix MII models? I would want to put in > a CPU that was at least 400 MHz. > > I know this is not specifically FreeBSD related but I have found that > the people on the FreeBSD lists are the most knowledgeable. All responses > are greatly appreciated. > > Thanks. > > -- > Glenn Johnson > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ // \\ ---------------------------(((---(((----------------------------------------- -- Powered by Coka-Cola and FreeBSD -- -- Strong enough for a man - But made for a Woman -- -- OWNED? MS: Who's Been In/Virused Your Computer Today? -- ------------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Aug 25 23:59:19 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-115.dsl.snfc21.pacbell.net [63.202.177.115]) by hub.freebsd.org (Postfix) with ESMTP id 4150F37B43E for ; Fri, 25 Aug 2000 23:59:16 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id TAA00816; Thu, 24 Aug 2000 19:32:35 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008250232.TAA00816@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: jack Cc: freebsd-hardware@freebsd.org Subject: Re: fxp, symbios, Intel MB problem In-reply-to: Your message of "Fri, 18 Aug 2000 01:03:49 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 24 Aug 2000 19:32:35 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Has this been resolved? I have an Intel mb with an EtherExpress > Pro 10/100B and and Diamond ?? with a symbios 875 chip that won't > boot from 4.1-RELEASE install floppies, it hangs right after > reporting the ethernet address of the EtherExpress. The problem you're alluding to never manifested these symptoms. If you haven't resolved this already, try 'boot -v' and see if you get any more verbose output (ie. so that we can for example tell if it's still hung up in the fxp driver). -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Aug 26 6:54:26 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.monmouth.com (mail.monmouth.com [209.191.58.1]) by hub.freebsd.org (Postfix) with ESMTP id 64B7837B423 for ; Sat, 26 Aug 2000 06:54:24 -0700 (PDT) Received: from monmouth.com (bg-tc-ppp925.monmouth.com [209.191.51.111]) by mail.monmouth.com (8.9.3/8.9.3) with ESMTP id JAA23220 for ; Sat, 26 Aug 2000 09:54:22 -0400 (EDT) Message-ID: <39A7CC09.69042B4@monmouth.com> Date: Sat, 26 Aug 2000 09:54:17 -0400 From: "W. Wilson" X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.16 i586) X-Accept-Language: en MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: USB Modem and 4.1R Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org USB Modem stalls when accessing Web sites. I am able to get the version of umodem.c in current to dial and connect. Once the ppp link is established I can ping and ftp but accessing http stalls. Has anyone else seen this problem when using a USB Modem with 4.1R? Thanks W To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Aug 26 8:24:12 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id 0531337B43C for ; Sat, 26 Aug 2000 08:24:10 -0700 (PDT) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id JAA12345 for ; Sat, 26 Aug 2000 09:25:58 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008261525.JAA12345@mail.fpsn.net> From: "Simon" To: "freebsd-hardware@freebsd.org" Date: Sat, 26 Aug 2000 11:27:17 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: What's this? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Can someone please help me identify the following message? I get it when my freebsd crashes and I have to do a cold- reboot. mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 instruction pointer = 0x8:0xc024d4e8 stack pointer = 0x10:0xdb3dcf20 frame pointer = 0x10:0xdb3dcfa0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = inerrupt enabled, IOPL = 0 current process = 55063 (httpd) interrupt mask = none <- SMP: XXX trap number = 29 panic: unknown/reserved trap mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 syncing disks... 868 860 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 giving up on 2 buffers Uptime: 23h16m47s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Grabbed mp lock for BSP Thank you very much in advance. -Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message