[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-security
Subject:    Re: [opensuse-security] Re: [security-announce] SUSE-SU-2012:0789-1: important: Security update for 
From:       Stefan Seyfried <stefan.seyfried () googlemail ! com>
Date:       2012-07-12 14:39:51
Message-ID: 4FFEE1B7.1070805 () message-id ! googlemail ! com
[Download RAW message or body]

Am 11.07.2012 22:15, schrieb Martin Konold:
> Am Mittwoch, 11. Juli 2012, 12:12:04 schrieb Marcus Meissner:
> 
> Hi,
> 
>> Did you report this in other channels, like our support team NTS?
> 
> Too bad that bug reports for kernel crashes for SLES get closed as invalid if 
> no seperate support contract is signed with Novell/Suse.com :-(
> 
> E.g. I have support contracts with HP

Well, then you probably need to report the kernel crash to HP.

> for SLES and and therefore cannot report 
> any kernel crashes via bnc. https://bugzilla.novell.com/show_bug.cgi?id=769292 
> (*)

Even if you have a support contract with SUSE / Novell you cannot enter
bugs against SLES usually. The workflow is different: you open a Service
Request with support, they then open the bug if necessary.

> This is imho an unfortunate policy as I am happily paying for SLES maintenance 
> but I am not entitled to even report a kernel crash.
> 
> In addition reporting via http://support.novell.com/additional/bugreport.html 
> is a black hole with a O_DIRECT to /dev/null.

http://www.novell.com/customercenter/, log in, on the left side "My
Support -> Service requests", then "Submit new SR".

Works almost every day for me, with timely response by the support team.

For my customer (with a slightly bigger support contract), I simply mail
or call my designated support engineer.

> P.S.: The above mentioned crash could just today be reproduced with the 3.0.36 
> SLES kernel  from monday but cannot be reported via proper channels even 
> though a kdump is available....

It can, via proper channel.

> (*) It is difficult to understand why I can report kernel crashes for opensuse 
> while I cannot for SLES11 even though I am paying for the later but not for 
> the former.

I report kernel crashes including crashdumps etc. for SLES almost every
week, so I cannot really see where the problem is.

-- 
Stefan Seyfried

"Dispatch war rocket Ajax to bring back his body!"
-- 
To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-security+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]