Re: APU.1C
On 2014-08-19, Stan Gammons sg063...@gmail.com wrote: Anyway. Did you have to sign a NDA to get the datasheet? I see on the RealTek website where they say it supports jumbo frames to 9K. Wonder if RealTek would answer some questions about the register config for jumbo frames? I just found it on google, didn't take long and it's easier now you have the strings from my previous mail to search for :) It's probably not too horrible to find in another OS's driver if there's one known to support it (as opposed to the vendor's own driver which was a right mess last time I looked). Probably easier than finding a vendor contact willing and able to give out information.
Re: APU.1C
On 08/20/14 17:24, Stuart Henderson wrote: On 2014-08-19, Stan Gammons sg063...@gmail.com wrote: Anyway. Did you have to sign a NDA to get the datasheet? I see on the RealTek website where they say it supports jumbo frames to 9K. Wonder if RealTek would answer some questions about the register config for jumbo frames? I just found it on google, didn't take long and it's easier now you have the strings from my previous mail to search for :) It's probably not too horrible to find in another OS's driver if there's one known to support it (as opposed to the vendor's own driver which was a right mess last time I looked). Probably easier than finding a vendor contact willing and able to give out information. Ok. I have another APU.1C that I can experiment with now. Guess I could try one of the other BSDs to see about jumbo frames and the link LED issue. Stan
APU.1C
Stan Gammons s_gammons at charter.net writes: On 07/29/14 04:01, Stuart Henderson wrote: That's to do with the traffic that the system is handling, you wouldn't normally expect to see all that much fragmented traffic. If there are lots of fragments, are you using pppoe? If so then make sure you either use 'scrub max-mss' or set suitable MTU on all machines on the lan. (In some cases you can use a larger MTU with pppoe RFC4638, but the re(4) driver doesn't yet support jumbo frames on the APU's nic so this won't be available to you). Are there other issues with the re(4) driver on the APU besides jumbo frames? The LED on the Ethernet ports on the one I have don't seem to be working right. At 100 meg the amber link LED is on, but at 1 gig the LED is off. I would have thought the green LED would be on for a 1 gig link. Other than that, I'm pretty pleased with how OpenBSD runs on it. From the datasheet, The RTL8111E supports customizable LED operation modes via IO register offset 18h~19h. I haven't spotted anything setting this in our driver so perhaps it's initialized to strange values by the BIOS. Standard behaviour is for the link led to blink when it has link at any speed, or when this LED is high for extended periods, it indicates that a link problem exists. The datasheet is also annoyingly silent about the register config for jumbo frames. I tried to reply to this email several days ago only to learn the entire subnet my ISP assigned DCHP IP address is on several of the IP blacklist. Anyway. Did you have to sign a NDA to get the datasheet? I see on the RealTek website where they say it supports jumbo frames to 9K. Wonder if RealTek would answer some questions about the register config for jumbo frames? There is a new version of BIOS for the APU. It's dated Jul 08, 2014. It doesn't solve the LED issue though. I don't recall seeing a link LED blink. All I've seen is amber, yellow, green or not lit. I've seen the activity LED blink at a constant rate when the NIC port was attached to a switch port that's configured as a trunk port. The pcengines support forum also has a link to the coreboot source code for the APU. It looks like it requires the Sage EDK to compile though. Bummer. I'm not that great a C programmer, so I guess it doesn't matter. Stan
Re: APU.1C was MinnowBoard MAX
Stan Gammons s_gammons at charter.net writes: On 07/29/14 04:01, Stuart Henderson wrote: That's to do with the traffic that the system is handling, you wouldn't normally expect to see all that much fragmented traffic. If there are lots of fragments, are you using pppoe? If so then make sure you either use 'scrub max-mss' or set suitable MTU on all machines on the lan. (In some cases you can use a larger MTU with pppoe RFC4638, but the re(4) driver doesn't yet support jumbo frames on the APU's nic so this won't be available to you). Are there other issues with the re(4) driver on the APU besides jumbo frames? The LED on the Ethernet ports on the one I have don't seem to be working right. At 100 meg the amber link LED is on, but at 1 gig the LED is off. I would have thought the green LED would be on for a 1 gig link. Other than that, I'm pretty pleased with how OpenBSD runs on it. From the datasheet, The RTL8111E supports customizable LED operation modes via IO register offset 18h~19h. I haven't spotted anything setting this in our driver so perhaps it's initialized to strange values by the BIOS. Standard behaviour is for the link led to blink when it has link at any speed, or when this LED is high for extended periods, it indicates that a link problem exists. The datasheet is also annoyingly silent about the register config for jumbo frames.
APU.1C was MinnowBoard MAX
On 07/29/14 04:01, Stuart Henderson wrote: That's to do with the traffic that the system is handling, you wouldn't normally expect to see all that much fragmented traffic. If there are lots of fragments, are you using pppoe? If so then make sure you either use 'scrub max-mss' or set suitable MTU on all machines on the lan. (In some cases you can use a larger MTU with pppoe RFC4638, but the re(4) driver doesn't yet support jumbo frames on the APU's nic so this won't be available to you). Are there other issues with the re(4) driver on the APU besides jumbo frames? The LED on the Ethernet ports on the one I have don't seem to be working right. At 100 meg the amber link LED is on, but at 1 gig the LED is off. I would have thought the green LED would be on for a 1 gig link. Other than that, I'm pretty pleased with how OpenBSD runs on it. Stan
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry
On 27.06.2014. 08:59, Mihai Popescu wrote: It think the designer wanted to keep the board compatible with the old case, or the other way around. To cool the CPU more one needs better pads ( i doubt there are much better, since the industry has standards) or adds a fan. Current situation is like this: \__/ - CPU - PAD == - Aluminium heatsink - PAD - CASE A better approach is a cast aluminium case, but this is too expensive. So one can do pressed steel sheet like this: \__/ - CPU - PAD . ../ \... - CASE ^^^ bend area This way, one pad and the extra aluminium heat spreader can be out of equation. Of course, and extra bending of the bottom sheet is needed. Maybe the price will go higher, maybe the CPU is too far and the bending distance I would try to replace the aluminium sheet with a copper one. It would be also good to make it thicker, in order to avoid thermal pads and use thermal paste instead (to additionally lower thermal resistance). Finally, increasing the area of this sheet would also help, preferably to cover the entire bottom of the box.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry
It think the designer wanted to keep the board compatible with the old case, or the other way around. To cool the CPU more one needs better pads ( i doubt there are much better, since the industry has standards) or adds a fan. Current situation is like this: \__/ - CPU - PAD == - Aluminium heatsink - PAD - CASE A better approach is a cast aluminium case, but this is too expensive. So one can do pressed steel sheet like this: \__/ - CPU - PAD . ../ \... - CASE ^^^ bend area This way, one pad and the extra aluminium heat spreader can be out of equation. Of course, and extra bending of the bottom sheet is needed. Maybe the price will go higher, maybe the CPU is too far and the bending distance is too much for the sheet. This is just the industry method, excuse my ASCII art, please.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry
One of the best pads around are Fujipoly [1] with thermal conductivity of 17 W/mK. These made a big difference on several laptop workstations that were having overheating issues. Some default pads are good enough, but in some cases thermal conductivity is a problem and you just need a better pad. [1] http://www.frozencpu.com/products/17499/thr-181/ On 06/27/2014 09:59 AM, Mihai Popescu wrote: It think the designer wanted to keep the board compatible with the old case, or the other way around. To cool the CPU more one needs better pads ( i doubt there are much better, since the industry has standards) or adds a fan. Current situation is like this: \__/ - CPU - PAD == - Aluminium heatsink - PAD - CASE A better approach is a cast aluminium case, but this is too expensive. So one can do pressed steel sheet like this: \__/ - CPU - PAD . ../ \... - CASE ^^^ bend area This way, one pad and the extra aluminium heat spreader can be out of equation. Of course, and extra bending of the bottom sheet is needed. Maybe the price will go higher, maybe the CPU is too far and the bending distance is too much for the sheet. This is just the industry method, excuse my ASCII art, please.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On Tue, Jun 24, 2014 at 4:23 PM, Chris Cappuccio ch...@nmedia.net wrote: Stuart Henderson [s...@spacehopper.org] wrote: On 2014-06-20, Roger Wiklund roger.wikl...@gmail.com wrote: On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Yes. Someone, make a better chassis for these, please...! A low rpm fan would be quite acceptable to me and I think would make a huge difference. You know thermal headroom is tight when the vendor goes as far as telling you to use a black chassis. Pascal Dornier says that consistent pressure between the CPU and heat spreader is critical. He also says the colored cases have better emissivity: http://pcengines.ch/apucool.htm Some emissivity tests: http://snap.fnal.gov/crshield/crs-mech/emissivity-eoi.html More cooling surface area here (but not colored): http://linitx.com/viewproduct.php?prodid=12745 would a bit of http://en.wikipedia.org/wiki/Thermal_grease help ? , air being approximately 8000 times less efficient at conducting heat than, for example, aluminum (a common heatsink material) -- - () ascii ribbon campaign - against html e-mail /\
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
sven falempin [sven.falem...@gmail.com] wrote: would a bit of http://en.wikipedia.org/wiki/Thermal_grease help ? , air being approximately 8000 times less efficient at conducting heat than, for example, aluminum (a common heatsink material) That's what the thermal pads are for. Going from 6W/mK to 17W/mK will conduct more heat to the sink, but the sink might need to be larger for some situations. Also even pressure around the pads is going to be critical as the box's designer says.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On Wed, Jun 25, 2014 at 9:51 AM, Chris Cappuccio ch...@nmedia.net wrote: sven falempin [sven.falem...@gmail.com] wrote: would a bit of http://en.wikipedia.org/wiki/Thermal_grease help ? , air being approximately 8000 times less efficient at conducting heat than, for example, aluminum (a common heatsink material) That's what the thermal pads are for. Going from 6W/mK to 17W/mK will conduct more heat to the sink, but the sink might need to be larger for some situations. Also even pressure around the pads is going to be critical as the box's designer says. Perhaps a stupid question, but what about grease or a pad between the sink and the case?
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
2014-06-25 22:25 GMT+02:00 noah pugsley noah.pugs...@gmail.com: On Wed, Jun 25, 2014 at 9:51 AM, Chris Cappuccio ch...@nmedia.net wrote: That's what the thermal pads are for. Going from 6W/mK to 17W/mK will conduct more heat to the sink, but the sink might need to be larger for some situations. Also even pressure around the pads is going to be critical as the box's designer says. Perhaps a stupid question, but what about grease or a pad between the sink and the case? You mean the thermal pads already deployed?
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On Wed, Jun 25, 2014 at 2:26 PM, Martin Schröder mar...@oneiros.de wrote: 2014-06-25 22:25 GMT+02:00 noah pugsley noah.pugs...@gmail.com: On Wed, Jun 25, 2014 at 9:51 AM, Chris Cappuccio ch...@nmedia.net wrote: That's what the thermal pads are for. Going from 6W/mK to 17W/mK will conduct more heat to the sink, but the sink might need to be larger for some situations. Also even pressure around the pads is going to be critical as the box's designer says. Perhaps a stupid question, but what about grease or a pad between the sink and the case? You mean the thermal pads already deployed? Yes. Either the pads if they are thin enough, or a dot of grease to fill in the air gaps between sink and case. But I don't have one of these so this is probably noise...
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On June 25, 2014 4:42:05 PM MDT, noah pugsley noah.pugs...@gmail.com wrote: On Wed, Jun 25, 2014 at 2:26 PM, Martin Schröder mar...@oneiros.de wrote: 2014-06-25 22:25 GMT+02:00 noah pugsley noah.pugs...@gmail.com: On Wed, Jun 25, 2014 at 9:51 AM, Chris Cappuccio ch...@nmedia.net wrote: That's what the thermal pads are for. Going from 6W/mK to 17W/mK will conduct more heat to the sink, but the sink might need to be larger for some situations. Also even pressure around the pads is going to be critical as the box's designer says. Perhaps a stupid question, but what about grease or a pad between the sink and the case? You mean the thermal pads already deployed? Yes. Either the pads if they are thin enough, or a dot of grease to fill in the air gaps between sink and case. But I don't have one of these so this is probably noise... Considering the way the heat spreader adheres to the bottom of the case (the adhesive basically _welds_ it on), I wouldn't think that there is much in the way of air gaps. But in my case, I guess because of how cool my basement is, heat isn't really a concern. Mike
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Stuart Henderson [s...@spacehopper.org] wrote: On 2014-06-20, Roger Wiklund roger.wikl...@gmail.com wrote: On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Yes. Someone, make a better chassis for these, please...! A low rpm fan would be quite acceptable to me and I think would make a huge difference. You know thermal headroom is tight when the vendor goes as far as telling you to use a black chassis. Pascal Dornier says that consistent pressure between the CPU and heat spreader is critical. He also says the colored cases have better emissivity: http://pcengines.ch/apucool.htm Some emissivity tests: http://snap.fnal.gov/crshield/crs-mech/emissivity-eoi.html More cooling surface area here (but not colored): http://linitx.com/viewproduct.php?prodid=12745
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On 2014-06-20, Roger Wiklund roger.wikl...@gmail.com wrote: On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Yes. Someone, make a better chassis for these, please...! A low rpm fan would be quite acceptable to me and I think would make a huge difference. You know thermal headroom is tight when the vendor goes as far as telling you to use a black chassis.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Sender: owner-m...@openbsd.org On-Behalf-Of: s...@spacehopper.org Subject: Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic Message-Id: slrnlqdavd.53v@naiad.spacehopper.org Recipient: adam.atkin...@damovo.com Received: from Mail2.damovo.com (109.204.121.44) by UK001B237.d.grp (10.8.1.9) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 22 Jun 2014 11:13:41 +0100 Received: from cluster-a.mailcontrol.com (85.115.52.190) by Mail2.damovo.com (109.204.121.44) with Microsoft SMTP Server (TLS) id 14.2.318.4; Sun, 22 Jun 2014 11:13:40 +0100 Received: from shear.ucar.edu (lists.openbsd.org [192.43.244.163]) by rly14a.srv.mailcontrol.com (MailControl) with ESMTP id s5MADbXr008083 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for adam.atkin...@damovo.com; Sun, 22 Jun 2014 11:13:39 +0100 Received: from openbsd.org (localhost [127.0.0.1]) by shear.ucar.edu (8.14.5/8.14.5) with ESMTP id s5MAMhHk024113 for adam.atkin...@damovo.com; Sun, 22 Jun 2014 04:22:44 -0600 (MDT) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by shear.ucar.edu (8.14.5/8.14.5) with ESMTP id s5MAMM74021087 for misc@openbsd.org; Sun, 22 Jun 2014 04:22:23 -0600 (MDT) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from goom-m...@m.gmane.org) id 1Wyekt-00080r-1O for misc@openbsd.org; Sun, 22 Jun 2014 12:12:11 +0200 Received: from naiad.spacehopper.org ([195.95.187.26]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for misc@openbsd.org; Sun, 22 Jun 2014 12:12:11 +0200 Received: from stu by naiad.spacehopper.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for misc@openbsd.org; Sun, 22 Jun 2014 12:12:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: misc@openbsd.org From: Stuart Henderson s...@spacehopper.org Subject: Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic Date: Sun, 22 Jun 2014 10:11:57 + Lines: 9 Message-ID: slrnlqdavd.53v@naiad.spacehopper.org References: 20140611040109.ga10...@ref.nmedia.net CAPHDuVPKWE7knccLeFB_zrVWenZy4TQbWhe8r35=k8rj+ds...@mail.gmail.com 20140612194920.gg18...@ref.nmedia.net CAC+aSK2UvSq9rURD3fGqO=wE6WtnbHG=adjgbr+szpyp4do...@mail.gmail.com X-Complaints-To: use...@ger.gmane.org X-Gmane-NNTP-Posting-Host: naiad.spacehopper.org User-Agent: slrn/1.0.1 (OpenBSD) List-Help: mailto:majord...@openbsd.org?body=help List-ID: misc.openbsd.org List-Owner: mailto:owner-m...@openbsd.org List-Post: mailto:misc@openbsd.org List-Subscribe: mailto:majord...@openbsd.org?body=sub%20misc List-Unsubscribe: mailto:majord...@openbsd.org?body=unsub%20misc X-Loop: misc@openbsd.org Precedence: list Sender: owner-m...@openbsd.org X-Mailcontrol-Inbound: 8gSgIv9v3sbRnxYICSb3h!uiaIa96vptNsOUTq2TeYo= X-Spam-Score: -0.653 X-Scanned-By: MailControl 28796.38 (www.mailcontrol.com) on 10.65.0.124 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Return-Path: owner-misc+M140772=adam.atkinson=damovo@openbsd.org X-MS-Exchange-Organization-OriginalArrivalTime: 22 Jun 2014 10:13:40.7970 (UTC) X-MS-Exchange-Organization-OriginalClientIPAddress: 85.115.52.190 X-MS-Exchange-Organization-OriginalServerIPAddress: 109.204.121.44 X-MS-Exchange-Organization-MessageDirectionality: Incoming X-MS-Exchange-Organization-Cross-Premises-Headers-Processed: Mail2.damovo.com X-MS-Exchange-Organization-PRD: openbsd.org Received-SPF: None (Mail2.damovo.com: owner-m...@openbsd.org does not designate permitted sender hosts) X-MS-Exchange-Organization-OriginalSize: 2847 X-MS-Exchange-Forest-MessageScope: ---- X-MS-Exchange-Organization-MessageScope: ---- X-MS-Exchange-Organization-HygienePolicy: Standard X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0 X-MS-Exchange-Organization-MessageLatencyInProgress: LSRV=Mail2.damovo.com:TOTAL=0;2014-06-22T10:13:40.999Z X-MS-Exchange-Forest-ArrivalHubServer: UK001B237.d.grp X-MS-Exchange-Organization-SenderIdResult: NONE X-MS-Exchange-Organization-AuthSource: Mail2.damovo.com X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-MessageLatency: SRV=Mail2.damovo.com:TOTAL=0 X-MS-Exchange-Organization-Recipient-Limit-Verified: True X-MS-Exchange-Forest-RulesExecuted: UK001B237 X-MS-Exchange-Organization-Rules-Execution-History: WW-SetDomainsAsNotJunk%%%DamovoUK-FaultEscalation%%%DamovoUK_AutoResponse%%%DE-UPSAlarmRule%%%BE-OutboundDisclaimer%%%WW-OutboundDisclaimer%%%UK-OutboundDisclaimer%%%IE-OutboundDisclaimer%%%DamovoUK_GFiRule%%%DE-Redirect_Techem%%%CH-SupportRule%%%UKScanToEmailBlockExternal On 2014-06-20, Roger Wiklund roger.wikl...@gmail.com wrote: On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Yes. Someone, make
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. On Thu, Jun 12, 2014 at 9:49 PM, Chris Cappuccio ch...@nmedia.net wrote: Happy to report that Plextor M6M (msata) passes all the tests so far, unlike msata Sandisk X110.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
That seems to be normal. Mine is currently 61.5 degrees and it's currently not under any load. Mine runs cooler if it's standing on its edge vertically, it just seems to help the airflow around the case at the expense of looking a bit odd. Regards - Nick On 20/06/2014 10:40, Roger Wiklund wrote: No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. On Thu, Jun 12, 2014 at 9:49 PM, Chris Cappuccio ch...@nmedia.net wrote: Happy to report that Plextor M6M (msata) passes all the tests so far, unlike msata Sandisk X110.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On Fri, Jun 20, 2014 at 11:40:02AM +0200, Roger Wiklund wrote: No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Same here: 70-75C, for a 0.2 average load. The case gets pretty hot, so I'm guessing I installed the heatsink correctly... Does anyone have (much) lower figures?
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On 20 June 2014, Zé Loff zel...@zeloff.org wrote: On Fri, Jun 20, 2014 at 11:40:02AM +0200, Roger Wiklund wrote: No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Same here: 70-75C, for a 0.2 average load. The case gets pretty hot, so I'm guessing I installed the heatsink correctly... The case itself is the sink. :) Does anyone have (much) lower figures? No, this seems to be common. I managed to lower the temperature a little by rising the case legs, so that there's better air circulation below it. Room temperature makes a big difference too. Regards, Liviu Daia
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Did some tests (cold Swedish midsummer around 12C outside) Bedroom floor near open window 1:48PM up 1:06, 1 user, load averages: 0.29, 0.17, 0.11 hw.sensors.km0.temp0=58.00 degC Kitchen countertop, no open windows 3:01PM up 1:09, 1 user, load averages: 0.11, 0.09, 0.08 hw.sensors.km0.temp0=64.25 degC Closed closet where I have my other server/networking stuff 4:14PM up 1:10, 1 user, load averages: 0.20, 0.11, 0.09 hw.sensors.km0.temp0=68.00 degC Max temp for the CPU is 90C http://www.amd.com/Documents/49282_G-Series_platform_brief.pdf On Fri, Jun 20, 2014 at 2:11 PM, Liviu Daia liviu.d...@gmail.com wrote: On 20 June 2014, Zé Loff zel...@zeloff.org wrote: On Fri, Jun 20, 2014 at 11:40:02AM +0200, Roger Wiklund wrote: No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Same here: 70-75C, for a 0.2 average load. The case gets pretty hot, so I'm guessing I installed the heatsink correctly... The case itself is the sink. :) Does anyone have (much) lower figures? No, this seems to be common. I managed to lower the temperature a little by rising the case legs, so that there's better air circulation below it. Room temperature makes a big difference too. Regards, Liviu Daia
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On 2014-06-20 04:14, Zé Loff wrote: On Fri, Jun 20, 2014 at 11:40:02AM +0200, Roger Wiklund wrote: No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Same here: 70-75C, for a 0.2 average load. The case gets pretty hot, so I'm guessing I installed the heatsink correctly... Does anyone have (much) lower figures? Mine sits in my basement on a shelf with the modem, switch, etc and it idles right around 57-58C, with an average load of around 0.2.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Roger Wiklund [roger.wikl...@gmail.com] wrote: No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. I have two DNS/NTP/DHCP servers running on APUs in a cooled datacenter environment. Unbound has caching turned up but the CPU usage is still tiny. (I don't think I'd see any difference with an ALIX vs the APU.) # sysctl hw.sensors hw.sensors.km0.temp0=59.50 degC # sysctl hw.sensors hw.sensors.km0.temp0=64.00 degC They both started up at 61.5 after 10 minutes or so. This is after several days. If you cover the top with more APUs it sits higher than 70. I bet if you put it upside down (where the heatsink joins the case would face up) then the temp will stay cooler. The heatsink pads that PC Engines ships to connect the CPU and chipset to the heatsink and case are rated at 6 W/mK. You could buy ones that are rated at 17 W/mK to get greater heat dissipation. http://173.254.28.23/~fujipoly/index.php?id=5 (I'm not sure that better pads are enough.) Chris
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry
I bet if you put it upside down (where the heatsink joins the case would face up) then the temp will stay cooler. Not by much. The heatsink pads that PC Engines ships to connect the CPU and chipset to the heatsink and case are rated at 6 W/mK. You could buy ones that are rated at 17 W/mK to get greater heat dissipation. http://173.254.28.23/~fujipoly/index.php?id=5 http://173.254.28.23/%7Efujipoly/index.php?id=5 (I'm not sure that better pads are enough.) The pads are rated for a specific thickness. If they thick, the data is going against you. If you need better cooling, the case needs aditional fins and it should be mechanical precise in order to be able to use thinner silk pads. In passive cooling, to get decent temperatures for the chip with a low surface heatsinks, 5 Watts is a real challenge (from my experience).
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On Fri, 20 Jun 2014 11:14:31 +0100, =?iso-8859-1?Q?Z=E9?= Loff wrote: On Fri, Jun 20, 2014 at 11:40:02AM +0200, Roger Wiklund wrote: No problems so far with Intel mSATA 525 30GB. On a side note I'm a bit worried about the CPU temperate, almost 70 degrees C during normal load. Same here: 70-75C, for a 0.2 average load. The case gets pretty hot, so I'm guessing I installed the heatsink correctly... Does anyone have (much) lower figures? 61.5C here at 0.14 load, but I flipped the case upside down so the heatsink faces upwards. Still gets up to 67C on a hot day.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On 2014-06-11, Chris Cappuccio ch...@nmedia.net wrote: SD on APU is USB, and it works fine, although my SD card to test is so pathetically slow that 'noatime' on fliesystem mounts makes a noticeable difference. It seems like every bit of disk activity big or small has some large waiting time with this random, old SD card. Same on a random new SD card. OpenBSD 5.5-current (GENERIC.MP) #85: Sun Apr 27 09:24:33 MDT 2014 t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2098511872 (2001MB) avail mem = 2033987584 (1939MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7e16d820 (6 entries) bios0: vendor coreboot version SageBios_PCEngines_APU-45 date 04/05/2014 bios0: PC Engines APU acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD G-T40E Processor, 1000.13 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD G-T40E Processor, 1000.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpiprt0 at acpi0: bus -1 (AGPB) acpiprt1 at acpi0: bus -1 (HDMI) acpiprt2 at acpi0: bus 1 (PBR4) acpiprt3 at acpi0: bus 2 (PBR5) acpiprt4 at acpi0: bus 3 (PBR6) acpiprt5 at acpi0: bus -1 (PBR7) acpiprt6 at acpi0: bus 5 (PE20) acpiprt7 at acpi0: bus -1 (PE21) acpiprt8 at acpi0: bus -1 (PE22) acpiprt9 at acpi0: bus -1 (PE23) acpiprt10 at acpi0: bus 0 (PCI0) acpiprt11 at acpi0: bus 4 (PIBR) acpicpu0 at acpi0: C2, PSS acpicpu1 at acpi0: C2, PSS acpibtn0 at acpi0: PWRB cpu0: 1000 MHz: speeds: 1000 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD AMD64 14h Host rev 0x00 ppb0 at pci0 dev 4 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:32:ff:b4 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 4 ppb1 at pci0 dev 5 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci2 at ppb1 bus 2 re1 at pci2 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:32:ff:b5 rgephy1 at re1 phy 7: RTL8169S/8110S PHY, rev. 4 ppb2 at pci0 dev 6 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci3 at ppb2 bus 3 re2 at pci3 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:32:ff:b6 rgephy2 at re2 phy 7: RTL8169S/8110S PHY, rev. 4 ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x40: apic 2 int 19, AHCI 1.2 scsibus1 at ahci0: 32 targets ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 2 int 18, version 1.0, legacy support ehci0 at pci0 dev 18 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 17 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1 ohci1 at pci0 dev 19 function 0 ATI SB700 USB rev 0x00: apic 2 int 18, version 1.0, legacy support ehci1 at pci0 dev 19 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 17 usb1 at ehci1: USB revision 2.0 uhub1 at usb1 ATI EHCI root hub rev 2.00/1.00 addr 1 piixpm0 at pci0 dev 20 function 0 ATI SBx00 SMBus rev 0x42: polling iic0 at piixpm0 pcib0 at pci0 dev 20 function 3 ATI SB700 ISA rev 0x40 ppb3 at pci0 dev 20 function 4 ATI SB600 PCI rev 0x40 pci4 at ppb3 bus 4 ohci2 at pci0 dev 20 function 5 ATI SB700 USB rev 0x00: apic 2 int 18, version 1.0, legacy support ppb4 at pci0 dev 21 function 0 ATI SB800 PCIE rev 0x00 pci5 at ppb4 bus 5 ohci3 at pci0 dev 22 function 0 ATI SB700 USB rev 0x00: apic 2 int 18, version 1.0, legacy support ehci2 at pci0 dev 22 function 2 ATI SB700 USB2 rev 0x00: apic 2
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Happy to report that Plextor M6M (msata) passes all the tests so far, unlike msata Sandisk X110.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Does an install on usb or sdcard medium work for you? Am 11.06.2014 06:01 schrieb Chris Cappuccio ch...@nmedia.net: Chris Cappuccio [ch...@nmedia.net] wrote: Mattieu Baptiste [mattie...@gmail.com] wrote: Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a ??crit : I know it???s no consolation to you but using a Kingston 30 GB mSATA from amazon works perfectly. The APU is on the May bios and I???ve had no issues. Didn???t the PCEngines mSATA drive have problems in general? There???s a mention on here about issues with the a version - is that yours? http://pcengines.ch/msata16b.htm Theoritically, I should have the new firmware (that's what told my vendor). But it seems there are still problems with these. Thanks for the tip concerning the Kingston drive. I've been using the Sandisk X110 msata. Borat says great success! As soon as I open my mouth # tar xzpf base55.tgz ahci0: log page read failed, slot 31 was still active. ahci0: stopping the port, softreset slot 31 was still active. tar: Failed write to file ./usr/lib/libedit.so.5.1: Input/output error gzip: stdin: crc error It's actually the Plextor M5M seems to be ok, that's what is in the box I've been using more. Ironically the buggy SuperSpeed thing from PC Engines stock is also reliable for me, albiet slow. Another problem I noticed with the X110 msata was the drive not saving all data on reboot. Like 'reboot' and low and behold, filesystem dirty! Christ
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Julian Andrej [j.and...@gmx.de] wrote: Does an install on usb or sdcard medium work for you? SD on APU is USB, and it works fine, although my SD card to test is so pathetically slow that 'noatime' on fliesystem mounts makes a noticeable difference. It seems like every bit of disk activity big or small has some large waiting time with this random, old SD card. Plextor M5M (msata) works fine so far. I have regular SATA X110 models that work on intel ahci, but the 32GB msatas are really funky on this amd ahci. Either I got a batch of bad ones or there are some workarounds necessary. Plextor M5M is already unavailable so I'm going to replace my bad X110s with M6M. A crapshoot. msata is just a smaller form factor for sata, so if sandisk's x110 part has a general compatibility issue, i'd imagine it would show up everywhere. Just to shut down the x110 msata properly, I have to do sync; sleep 1; sync; reboot
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Chris Cappuccio [ch...@nmedia.net] wrote: Mattieu Baptiste [mattie...@gmail.com] wrote: Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a ??crit : I know it???s no consolation to you but using a Kingston 30 GB mSATA from amazon works perfectly. The APU is on the May bios and I???ve had no issues. Didn???t the PCEngines mSATA drive have problems in general? There???s a mention on here about issues with the a version - is that yours? http://pcengines.ch/msata16b.htm Theoritically, I should have the new firmware (that's what told my vendor). But it seems there are still problems with these. Thanks for the tip concerning the Kingston drive. I've been using the Sandisk X110 msata. Borat says great success! As soon as I open my mouth # tar xzpf base55.tgz ahci0: log page read failed, slot 31 was still active. ahci0: stopping the port, softreset slot 31 was still active. tar: Failed write to file ./usr/lib/libedit.so.5.1: Input/output error gzip: stdin: crc error It's actually the Plextor M5M seems to be ok, that's what is in the box I've been using more. Ironically the buggy SuperSpeed thing from PC Engines stock is also reliable for me, albiet slow. Another problem I noticed with the X110 msata was the drive not saving all data on reboot. Like 'reboot' and low and behold, filesystem dirty! Christ
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a écrit : I know itâs no consolation to you but using a Kingston 30 GB mSATA from amazon works perfectly. The APU is on the May bios and Iâve had no issues. Didnât the PCEngines mSATA drive have problems in general? Thereâs a mention on here about issues with the a version - is that yours? http://pcengines.ch/msata16b.htm Theoritically, I should have the new firmware (that's what told my vendor). But it seems there are still problems with these. Thanks for the tip concerning the Kingston drive.
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Hi Matthieu, On 09.06.2014 19:30, Mattieu Baptiste wrote: Thanks for the tip concerning the Kingston drive. fwiw, I'm running april 5th firmware (I'm not aware of any may firmware, probably a confusion about date format, http://xkcd.com/1179/ ftw.) using a kingston SMS200S3/30G without any issues. hth andre
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On 9 June 2014, Mattieu Baptiste mattie...@gmail.com wrote: Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a ??crit : [...] Didn???t the PCEngines mSATA drive have problems in general? There???s a mention on here about issues with the a version - is that yours? http://pcengines.ch/msata16b.htm Theoritically, I should have the new firmware (that's what told my vendor). You do, according to the dmesg you posted in your first message. But it seems there are still problems with these. [...] This time it's the particular model of the disk shipped by PCEngines that has problems, not the firmware. A quick search reveals that many other people had to replace it with something else. Just make sure to search before you buy. Regards, Liviu Daia
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
Mattieu Baptiste [mattie...@gmail.com] wrote: Le 8 juin 2014 13:38, Nick Ryan n...@njryan.com a ??crit : I know it???s no consolation to you but using a Kingston 30 GB mSATA from amazon works perfectly. The APU is on the May bios and I???ve had no issues. Didn???t the PCEngines mSATA drive have problems in general? There???s a mention on here about issues with the a version - is that yours? http://pcengines.ch/msata16b.htm Theoritically, I should have the new firmware (that's what told my vendor). But it seems there are still problems with these. Thanks for the tip concerning the Kingston drive. I've been using the Sandisk X110 msata. Borat says great success!
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On 7 Jun 2014, at 23:35, Mattieu Baptiste mattie...@gmail.com wrote: On Sat, Jun 7, 2014 at 8:51 PM, JB M jbm.li...@gmail.com wrote: I'm having troubles installing OpenBSD 5.5 (amd64) on a mSATA SSD card ( http://pcengines.ch/msata16a.htm) PC Engines APU.1C device ( http://pcengines.ch/apu.htm) with the most recent BIOS version. I've made several attempts, using install55.fs copied to an SD card, with both 5.5-release and 5.5-current (June 6th snapshot). Most attempts have failed, either during the install (filesystem creation phase or during the sets extraction phase) or during the first boot after the initial install (case reported in this message). Same thing for me with : sd0 at scsibus1 targ 0 lun 0: ATA, SuperSSpeed mSAT, V462 SCSI3 0/direct fixed t10.ATA_SuperSSpeed_mSATA_SSD_16GB_YTAF140500376_ sd0: 15258MB, 512 bytes/sector, 31248704 sectors Installing on a USB drive solved the problem. I know it’s no consolation to you but using a Kingston 30 GB mSATA from amazon works perfectly. The APU is on the May bios and I’ve had no issues. Didn’t the PCEngines mSATA drive have problems in general? There’s a mention on here about issues with the a version - is that yours? http://pcengines.ch/msata16b.htm Regards - Nick OpenBSD 5.5-current (GENERIC.MP) #150: Mon May 26 11:50:31 MDT 2014 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2098520064 (2001MB) avail mem = 2033942528 (1939MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7e16d820 (6 entries) bios0: vendor coreboot version SageBios_PCEngines_APU-45 date 04/05/2014 bios0: PC Engines APU acpi0 at bios0: rev 0 acpi0: sleep states S0 S1 S3 S4 S5 acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PE20(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD G-T40E Processor, 1000.13 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu0: 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 199MHz cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD G-T40E Processor, 1000.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB 64b/line 16-way L2 cache cpu1: 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins acpiprt0 at acpi0: bus -1 (AGPB) acpiprt1 at acpi0: bus -1 (HDMI) acpiprt2 at acpi0: bus 1 (PBR4) acpiprt3 at acpi0: bus 2 (PBR5) acpiprt4 at acpi0: bus 3 (PBR6) acpiprt5 at acpi0: bus -1 (PBR7) acpiprt6 at acpi0: bus 5 (PE20) acpiprt7 at acpi0: bus -1 (PE21) acpiprt8 at acpi0: bus -1 (PE22) acpiprt9 at acpi0: bus -1 (PE23) acpiprt10 at acpi0: bus 0 (PCI0) acpiprt11 at acpi0: bus 4 (PIBR) acpicpu0 at acpi0: C2, PSS acpicpu1 at acpi0: C2, PSS acpibtn0 at acpi0: PWRB cpu0: 1000 MHz: speeds: 1000 800 MHz pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 AMD AMD64 14h Host rev 0x00 ppb0 at pci0 dev 4 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci1 at ppb0 bus 1 re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:33:06:c8 rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 4 ppb1 at pci0 dev 5 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci2 at ppb1 bus 2 re1 at pci2 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:33:06:c9 rgephy1 at re1 phy 7: RTL8169S/8110S PHY, rev. 4 ppb2 at pci0 dev 6 function 0 AMD AMD64 14h PCIE rev 0x00: msi pci3 at ppb2 bus 3 re2 at pci3 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E (0x2c00), msi, address 00:0d:b9:33:06:ca rgephy2 at re2 phy 7: RTL8169S/8110S PHY, rev. 4 ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x40: apic 2 int 19, AHCI 1.2 scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: ATA, KINGSTON SMS200S, 524A SCSI3 0/direct fixed naa.50026b724116179f sd0: 28626MB, 512 bytes/sector, 58626288
OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
I'm having troubles installing OpenBSD 5.5 (amd64) on a mSATA SSD card (
http://pcengines.ch/msata16a.htm) PC Engines APU.1C device (
http://pcengines.ch/apu.htm) with the most recent BIOS version.
I've made several attempts, using install55.fs copied to an SD card, with
both 5.5-release and 5.5-current (June 6th snapshot).
Most attempts have failed, either during the install (filesystem creation
phase or during the sets extraction phase) or during the first boot after
the initial install (case reported in this message).
I wonder if I have a faulty SSD unit.
In any case, here's my dmesg:
ddb{1} dmesg
OpenBSD 5.5 (GENERIC.MP) #315: Wed Mar 5 09:37:46 MST 2014
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 4245995520 (4049MB)
avail mem = 4124356608 (3933MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdf16d820 (6 entries)
bios0: vendor coreboot version SageBios_PCEngines_APU-45 date 04/05/2014
bios0: PC Engines APU
acpi0 at bios0: rev 0
acpi0: sleep states S0 S1 S3 S4 S5
acpi0: tables DSDT FACP SPCR HPET APIC HEST SSDT SSDT SSDT
acpi0: wakeup devices AGPB(S4) HDMI(S4) PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4)
PE2
0(S4) PE21(S4) PE22(S4) PE23(S4) PIBR(S4) UOH1(S3) UOH2(S3) UOH3(S3)
UOH4(S3) U
OH5(S3) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD G-T40E Processor, 1000.14 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,C
FLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LA
HF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 1
6-way L2 cache
cpu0: 8 4MB entries fully associative
cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 200MHz
cpu0: mwait min=64, max=64, C-substates=0.0.0.0.0, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD G-T40E Processor, 1000.00 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,C
FLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,SSSE3,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,LA
HF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,IBS,SKINIT,ITSC
cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 512KB
64b/line 1
6-way L2 cache
cpu1: 8 4MB entries fully associative
cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 21, 24 pins
acpiprt0 at acpi0: bus -1 (AGPB)
acpiprt1 at acpi0: bus -1 (HDMI)
acpiprt2 at acpi0: bus 1 (PBR4)
acpiprt3 at acpi0: bus 2 (PBR5)
acpiprt4 at acpi0: bus 3 (PBR6)
acpiprt5 at acpi0: bus -1 (PBR7)
acpiprt6 at acpi0: bus 5 (PE20)
acpiprt7 at acpi0: bus -1 (PE21)
acpiprt8 at acpi0: bus -1 (PE22)
acpiprt9 at acpi0: bus -1 (PE23)
acpiprt10 at acpi0: bus 0 (PCI0)
acpiprt11 at acpi0: bus 4 (PIBR)
acpicpu0 at acpi0: C2, PSS
acpicpu1 at acpi0: C2, PSS
acpibtn0 at acpi0: PWRB
cpu0: 1000 MHz: speeds: 1000 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 AMD AMD64 14h Host rev 0x00
ppb0 at pci0 dev 4 function 0 AMD AMD64 14h PCIE rev 0x00: msi
pci1 at ppb0 bus 1
re0 at pci1 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E
(0x2c00), m
si, address 00:0d:b9:33:98:cc
rgephy0 at re0 phy 7: RTL8169S/8110S PHY, rev. 4
ppb1 at pci0 dev 5 function 0 AMD AMD64 14h PCIE rev 0x00: msi
pci2 at ppb1 bus 2
re1 at pci2 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E
(0x2c00), m
si, address 00:0d:b9:33:98:cd
rgephy1 at re1 phy 7: RTL8169S/8110S PHY, rev. 4
ppb2 at pci0 dev 6 function 0 AMD AMD64 14h PCIE rev 0x00: msi
pci3 at ppb2 bus 3
re2 at pci3 dev 0 function 0 Realtek 8168 rev 0x06: RTL8168E/8111E
(0x2c00), m
si, address 00:0d:b9:33:98:ce
rgephy2 at re2 phy 7: RTL8169S/8110S PHY, rev. 4
ahci0 at pci0 dev 17 function 0 ATI SBx00 SATA rev 0x40: apic 2 int 19,
AHCI 1
.2
scsibus0 at ahci0: 32 targets
sd0 at scsibus0 targ 0 lun 0: ATA, SuperSSpeed mSAT, V462 SCSI3 0/direct
fixe
d t10.ATA_SuperSSpeed_mSATA_SSD_16GB_YTAF1405A_
sd0: 15258MB, 512 bytes/sector, 31248704 sectors
ohci0 at pci0 dev 18 function 0 ATI SB700 USB rev 0x00: apic 2 int 18,
versio
n 1.0, legacy support
ehci0 at pci0 dev 18 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 17
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 ATI EHCI root hub rev 2.00/1.00 addr 1
ohci1 at pci0 dev 19 function 0 ATI SB700 USB rev 0x00: apic 2 int 18,
versio
n 1.0, legacy support
ehci1 at pci0 dev 19 function 2 ATI SB700 USB2 rev 0x00: apic 2 int 17
usb1 at ehci1: USB revision 2.0
uhub1 at usb1 ATI EHCI root hub rev 2.0ev 20 function 0 ATI SBx00 SMBus
rev 0x42: polling
iic0 at piixpm0
pcib0 at pci0 dev 20
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On 2014-06-07 12:51, JB M wrote: I'm having troubles installing OpenBSD 5.5 (amd64) on a mSATA SSD card ( http://pcengines.ch/msata16a.htm) PC Engines APU.1C device ( http://pcengines.ch/apu.htm) with the most recent BIOS version. I've made several attempts, using install55.fs copied to an SD card, with both 5.5-release and 5.5-current (June 6th snapshot). Most attempts have failed, either during the install (filesystem creation phase or during the sets extraction phase) or during the first boot after the initial install (case reported in this message). I wonder if I have a faulty SSD unit. Does the mSATA drive have the new firmware, or is it one of the problem drives from earlier? If you have a null modem serial cable handy, you could try PXE booting and then installing the OS to the SD Card instead of the mSATA drive to at least rule out any other issues. Then try the same process and install to the mSATA card and see if you have the same problem again. Mike
Re: OpenBSD 5.5 on mSATA SSD unit in PC Engines APU.1C - bad dir ino 2 at offset 0: mangled entry kernel panic
On Sat, Jun 7, 2014 at 8:51 PM, JB M jbm.li...@gmail.com wrote: I'm having troubles installing OpenBSD 5.5 (amd64) on a mSATA SSD card ( http://pcengines.ch/msata16a.htm) PC Engines APU.1C device ( http://pcengines.ch/apu.htm) with the most recent BIOS version. I've made several attempts, using install55.fs copied to an SD card, with both 5.5-release and 5.5-current (June 6th snapshot). Most attempts have failed, either during the install (filesystem creation phase or during the sets extraction phase) or during the first boot after the initial install (case reported in this message). Same thing for me with : sd0 at scsibus1 targ 0 lun 0: ATA, SuperSSpeed mSAT, V462 SCSI3 0/direct fixed t10.ATA_SuperSSpeed_mSATA_SSD_16GB_YTAF140500376_ sd0: 15258MB, 512 bytes/sector, 31248704 sectors Installing on a USB drive solved the problem.
