Hi,
do you still observe this behaviour? Which type of EC2 instances were
affected?
I tried to reproduce with kernel/tools from Dec 15 and did not manage to
crash the machine.
Jakub
On Sun, Dec 4, 2016 at 5:38 PM, Dimitry Andric wrote:
> On 04 Dec 2016, at 10:52, Hans Petter Selasky wrote:
>
See here:
https://lists.freebsd.org/pipermail/svn-src-head/2016-December/094657.html
and here:
https://lists.freebsd.org/pipermail/svn-src-head/2016-December/094695.html
I committed a fix on Dec 14, and MFCd it on Dec 18.
-Dimitry
> On 20 Dec 2016, at 11:54, Jakub Palider wrote:
>
> Hi,
>
>
Hello!
Some time ago new ACPI messages appeared on console and in /var/log/messages.
Like these:
ACPI Error: Needed type [Reference], found [Processor] 0xf800043b8980
(20161117/exresop-111)
ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName
unavailable] (20161117
On 12/19/16 22:42, Hiroki Sato wrote:
Michael Butler wrote
in :
im> On 12/19/16 12:12, Hiroki Sato wrote:
im> > Michael Butler wrote
im> > in :
im> >
im> > im> It appears that SVN r309925 and onward no longer opens a network
im> > im> socket unless the command-line explicitly contains "-b
Am Tue, 20 Dec 2016 18:09:20 +0300
Vladimir Zakharov schrieb:
> Hello!
>
> Some time ago new ACPI messages appeared on console and in /var/log/messages.
> Like
> these:
>
> ACPI Error: Needed type [Reference], found [Processor] 0xf800043b8980
> (20161117/exresop-111) ACPI Exception: AE_AML
Hi,
On 12/16/2016 16:20, John Baldwin wrote:
> On Thursday, December 15, 2016 03:57:58 PM Adrian Chadd wrote:
>> heh, an updated BIOS that solves the problem will solve the problem. :)
>>
>> I think you have enough information to provide to supermicro. Ie,
>> "SMAP says X, when physical memory pag
Anyone know how to kill firefox?
last pid: 69652; load averages: 0.49, 0.27, 0.24 up 1+02:40:06
13:16:02
126 processes: 1 running, 121 sleeping, 4 stopped
CPU: 0.8% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
Mem: 2049M Active, 3739M Inact, 496M Laundry, 1365M Wired, 78
On 12/20/2016 15:29, Steve Kargl wrote:
> Anyone know how to kill firefox?
>
> last pid: 69652; load averages: 0.49, 0.27, 0.24 up 1+02:40:06
> 13:16:02
> 126 processes: 1 running, 121 sleeping, 4 stopped
> CPU: 0.8% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle
> Mem: 20
Hi Everyone!
We had some progress with Wayland that we'd like to share.
Wayland (v1.12.0)
Working
Weston (v1.12.0)
Working (Porting WIP)
Weston-clients (installed with wayland/weston port)
Working
XWayland (run X11 apps in Wayland compositor)
Works (maximized window only) if started ma
On Tue, Dec 20, 2016 at 05:28:09PM -0600, Eric Badger wrote:
> On 12/20/2016 15:29, Steve Kargl wrote:
> > Anyone know how to kill firefox?
> >
> >
> > PID USERNAME PRI NICE SIZERES STATE C TIMEWCPU COMMAND
> > 63902 kargl 40 0 3157M 2302M STOP1 10:50 0.00%
> > fi
On Tue, Dec 20, 2016 at 05:28:09PM -0600, Eric Badger wrote:
> On 12/20/2016 15:29, Steve Kargl wrote:
> > Anyone know how to kill firefox?
> >
> Do you have output of procstat -k for all threads? I'd guess one thread
> is busy dumping core.
>
Seems that you're right. firefox finally dropped it
Can I bump this issue one more time?
On Sun, Dec 18, 2016, 18:38 Dave Cottlehuber wrote:
> On Sun, 18 Dec 2016, at 10:07, blubee blubeeme wrote:
> > Hi
> >
> > I am on a Macbook pro 11,3 and I wanted to start trying to help sort out
> > some problems that might be too small for the overall team
12 matches
Mail list logo