freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
--
Andrew Boyerabo...@averesystems.com
___
freebsd-current@fr
On Apr 23, 2012, at 1:44 PM, Dimitry Andric wrote:
> On 2012-04-23 19:31, Andrew Boyer wrote:
>> Begin forwarded message:
>>
>>> From: Greg Bednarek
>>> Date: April 16, 2012 10:54:33 AM EDT
>>> To: freebsd-current@freebsd.org
>>
Begin forwarded message:
> From: Greg Bednarek
> Date: April 16, 2012 10:54:33 AM EDT
> To: freebsd-current@freebsd.org
> Cc: Andrew Boyer
> Subject: Memory leak in authunix_create_default()...
>
>
> Please see the attached patch for a proposed
MCA: Address 0xb43ca6240
> Mar 16 12:37:33 hostname kernel: MCA: Misc 0x4ac811164808
mcelog will help you figure out which DIMM is affected.
Also, if your server includes an IPMI controller, the BIOS should be set up to
log memory errors to the IPMI system event log (SEL). You can look
change that can be merge to older branches.
>
> Thanks,
>
> Doug A.
Does filt_liodetach() need the same treatment?
-Andrew
--
Andrew Boyerabo...@averesystems.com
___
freebsd-current@fre
On Dec 16, 2011, at 4:18 PM, John Baldwin wrote:
> On Friday, December 16, 2011 11:02:20 am Andrew Boyer wrote:
>>
>> On Dec 16, 2011, at 9:52 AM, Luigi Rizzo wrote:
>>
>>> On Thu, Dec 15, 2011 at 04:21:51PM -0500, Andrew Boyer wrote:
>>>> These two c
On Dec 16, 2011, at 9:52 AM, Luigi Rizzo wrote:
> On Thu, Dec 15, 2011 at 04:21:51PM -0500, Andrew Boyer wrote:
>> These two changes allow you to set PXE as the default MBR boot selection,
>> which enables you to write a 'reboot to the network' script. We've
til the BIOS screen comes up, hitting the
wrong button, etc. etc. On systems with a lot of memory the BIOS start times
are getting ridiculous.
-Andrew
> On Thu, Dec 15, 2011 at 1:21 PM, Andrew Boyer wrote:
>> These two changes allow you to set PXE as the default MBR boot selection
ndif /* SIO */
> +check_selection:
> cmpb $0x5,%al # F1..F6 or 1..6 ?
> #ifdef PXE /* enable PXE/INT18 using F6 */
> jne 1f;
> @@ -421,7 +422,6 @@
> #endif /* PXE */
> jae beep# Not in F1..F5, beep
>
>
, which needs to still be active
in case the dump hangs for other reasons. This is obviously not ideal but the
best solution I have right now. We also stop all of the network interfaces at
the beginning of boot().
--
Andrew Boyerabo...@averes
win
To do it this way (leave SMT enabled in the BIOS but disabled in the OS) makes
it easier to release a future upgrade to take advantage of those cores. Once
systems are distributed to customer sites it becomes very difficult to do BIOS
maintenance.
-Andrew
---------
On Sep 14, 2011, at 3:56 PM, Andriy Gapon wrote:
> on 14/09/2011 20:59 Andrew Boyer said the following:
>> When FreeBSD examines the CPU topology using CPUID leaf 11 in
>> topo_probe_0xb(), it never sets hyperthreading_cpus. At the end of
>> topo_probe_0x4() it set
system with two quad-core E5620 CPUs. The APIC IDs that
appear when SMT is enabled in the BIOS get marked AP/HT.
Do you agree?
Thanks,
Andrew
--
Andrew Boyerabo...@averesystems.com
___
freebsd
If malloc() fails in /sbin/sysctl, the error message is unhelpful. This patch
helps identify which sysctl entry is failing.
sysctl.diff
Description: Binary data
-Andrew
--
Andrew Boyerabo...@averesystems.com
_
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
--
Andrew Boyerabo...@aver
?
>
> Jack
>
>
> -Original Message-
> From: Andrew Boyer [mailto:abo...@averesystems.com]
> Sent: Wednesday, July 20, 2011 7:45 AM
> To: m...@freebsd.org
> Cc: freebsd-current@freebsd.org; Vogel, Jack
> Subject: [patch] Intel SATA controller hiccups, locking
>
> Hell
em.
Adding a mutex to a structure stored in ctlr->chipset_data makes the hiccups go
away; see the attached patch. Please advise if this is something you would
like to fix.
Thank you,
Andrew
ata_intel_sata.diff
Description: Binary data
---
d a place in the code that actually tries to stop
the other CPUs.
My question isn't about the initial panic (I was using the sysctl to provoke
one), but about the secondary panic.
This is on 8-core systems.
-Andrew
--
Andrew Boyerabo...@aver
___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
--
Andrew Boyerabo...@averesy
19 matches
Mail list logo
