Hi All,
Today, after upgrading an HP Proliant DL380 G6 to 8.3-STABLE we had the
following panic few minutes after going to multiuser mode:
http://193.194.156.21/bce_crash.jpg
dmesg from 8.3-STABLE kernel (Note the link up/down events):
...
Sep 3 14:19:54 m kernel: bce0: mem 0xf400-0xf5
On 03/09/2012 11:10, Krassimir Slavchev wrote:
> Hi All,
>
> Today, after upgrading an HP Proliant DL380 G6 to 8.3-STABLE we had the
> following panic few minutes after going to multiuser mode:
>
> http://193.194.156.21/bce_crash.jpg
>
here are crashing all amd64 8.3 machines with panic on curr
On 6/25/12 1:21 PM, Herbert Poeckl wrote:
> We are getting access denied error on our debian clients when mounting
> nfsv4 network drives with kerberos 5 authentication.
>
> What is wired about this, is that it works with one server, but not with
> a second server.
[..]
For the records:
The prob
I have kern.maxswzone default (32m), and now start to see this message:
warning: total configured swap (1048576 pages) exceeds maximum recommended
amount (995904 pages).
warning: increase kern.maxswzone or reduce amount of swap.
As I read somewhere 32m of maxswzone is enough up to 7Gb of swap,
No idea anybody why this bug happens? Patches?
On 08/29/2012 10:22 PM, Giulio Ferro wrote:
On 08/28/2012 11:12 AM, Damien Fleuriot wrote:
Hi Giulio,
Just to clear things up:
igb0: 192.168.9.60/24
lagg0: 192.168.12.21/24
Yes.
Actually I notice now that the lagg0 address is different from
Increasing it even up to 64m does not help at all.
Solved by reducing swap partition size to the recommended amount (swapoff,
gpart resize, reboot)
On Mon, Sep 03, 2012 at 09:34:08PM +0400, Andrey Chernov wrote:
> I have kern.maxswzone default (32m), and now start to see this message:
>
> warni
Herbert Poeckl wrote:
> On 6/25/12 1:21 PM, Herbert Poeckl wrote:
> > We are getting access denied error on our debian clients when
> > mounting
> > nfsv4 network drives with kerberos 5 authentication.
> >
> > What is wired about this, is that it works with one server, but not
> > with
> > a second
Hi,
On fre, aug 24, 2012 at 10:52:48am -0700, YongHyeon PYUN wrote:
>>
>> During boot I get:
>>
>> pcib3: at device 2.0 on pci0
>> pci3: on pcib3
>> pci0:3:0:0: failed to read VPD data.
>> bge0: mem
>> 0xf6bf-0xf6bf0xf6be-0xf6be,0xf6bd-0xf6bd irq 32
>> at device 0.0 on