Hi,
I got the following OOPS on 2.6.32-41 (Linux version 2.6.32-5-amd64
(Debian 2.6.32-41) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian
4.3.5-4) ) #1 SMP Mon Jan 16 16:22:28 UTC 2012). The machine runs
Mysql, it's a dedicated database server with pretty high IO load.
The oops is hard to
On 03/09/12 15:57, Ben Hutchings wrote:
On Fri, 2012-03-09 at 13:30 +0100, Harald Dunkel wrote:
PS: I just noticed that severity is set to normal. Sorry
to say, but I disagree on the severity in this case. If our
production environment dies after 200 days uptime, then this
is fatal.
Why do
On Sun, 2012-03-11 at 18:20 +0100, Harald Dunkel wrote:
On 03/09/12 15:57, Ben Hutchings wrote:
On Fri, 2012-03-09 at 13:30 +0100, Harald Dunkel wrote:
PS: I just noticed that severity is set to normal. Sorry
to say, but I disagree on the severity in this case. If our
production
Is this bug still relevant for Squeeze's kernel 2.6.32-41 ?
Would you recommend to move to the debian-backports kernel
instead?
Any helpful comment would be highly appreciated.
Harri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
PS: I just noticed that severity is set to normal. Sorry
to say, but I disagree on the severity in this case. If our
production environment dies after 200 days uptime, then this
is fatal.
Would you mind to adjust the severity of this bug report?
Many thanx
Harri
--
To UNSUBSCRIBE, email to
On Fri, 2012-03-09 at 13:30 +0100, Harald Dunkel wrote:
PS: I just noticed that severity is set to normal. Sorry
to say, but I disagree on the severity in this case. If our
production environment dies after 200 days uptime, then this
is fatal.
Why do you say '200 days uptime'?
Would you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the screenshot has been taken from some out-of-band management (drac)
Unfortunatelly I do not have the ability to connect any serial line.. :(
Cheers
B
On 10.11.2011 00:08, Daniel Kahn Gillmor wrote:
Bjoern wrote:
I just wanted to ask if
Bjoern wrote:
I just wanted to ask if the attached kernel oops is also related to
this issue?
I can't tell from your attached png because not enough of the oops is
included.
It looks like that screenshot is from a virtual machine emulated VGA
console.
To catch future issues like this, I
8 matches
Mail list logo
