Bug#772134: Kernel 3.2.0-4 failed to resume link

2015-01-05 Thread EpsiloN EpsiloN
Hi Hope you had chance to dive into problem? Regards Igor

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-11 Thread EpsiloN EpsiloN
Hi Geert: do you have some plans investigate the problem more deeply? Regards Igor

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-11 Thread Geert Stappers
On Thu, Dec 11, 2014 at 03:31:38PM +0200, EpsiloN EpsiloN wrote: Geert: do you have some plans investigate the problem more deeply? As said in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772134#40 I have allready interresting problems :-) Groeten Geert Stappers -- Leven en laten

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread EpsiloN EpsiloN
Hello Any feedback is appreciated. Thanks Regards Igor On Mon, Dec 8, 2014 at 10:10 AM, EpsiloN EpsiloN eps@gmail.com wrote: Hi I have uploaded some core dump that I found on server. Here there are: http://www.megafileupload.com/en/file/586009/core-dumps-zip.html Regards Igor On

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread EpsiloN EpsiloN
Statically written in /etc/network/interfaces. I should notice that systems that are affected has two or four interfaces in same network segment. Regards Igor On Wed, Dec 10, 2014 at 12:47 PM, Geert Stappers stapp...@stappers.nl wrote: On Wed, Dec 10, 2014 at 10:40:40AM +0200, EpsiloN EpsiloN

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread Geert Stappers
On Wed, Dec 10, 2014 at 10:40:40AM +0200, EpsiloN EpsiloN wrote: Any feedback is appreciated. Information that I couldn't find at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772134 is where the iSCSI initiator gets it's IP configuration. Groeten Geert Stappers -- Leven en laten

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread Debian-kernel ML subscriber
On Wed, Dec 10, 2014 at 13:01 PM, EpsiloN EpsiloN wrote: On Wed, Dec 10, 2014 at 12:50 PM, EpsiloN EpsiloN wrote: On Wed, Dec 10, 2014 at 12:47 PM, Geert Stappers wrote: Information that I couldn't find at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772134 is where the iSCSI

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread EpsiloN EpsiloN
Any idea why kernel hasn't read the /etc/network/interfaces during disk initilization? And another question. Why does already working server hungs at random? Regards Igor

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread Geert Stappers
On Wed, Dec 10, 2014 at 01:53:13PM +0200, EpsiloN EpsiloN wrote: Any idea why kernel hasn't read the /etc/network/interfaces during disk initilization? That is called boot sequence. Disk (driver) initalisation needs to be done before a disk can be read. Why does already working server hungs

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread EpsiloN EpsiloN
Could you please paste part of the log, where you found problem with the boot sequence? By the way server hangs completely. So no output from monitor neither from magical keys. Also nothing special in core dumps. As I have written this problem happens on different models of ProLiant servers and

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread Geert Stappers
On Wed, Dec 10, 2014 at 03:14:16PM +0200, EpsiloN EpsiloN wrote: Is there any way to debug the problem? Advice: Analyze the core file(s) that where found -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-10 Thread EpsiloN EpsiloN
Latest hangs were without any core dumps, but I go through. Do you need any additional information? Regards Igor

Bug#772134: Kernel 3.2.0-4 failed to resume link

2014-12-08 Thread EpsiloN EpsiloN
Hi I have uploaded some core dump that I found on server. Here there are: http://www.megafileupload.com/en/file/586009/core-dumps-zip.html Regards Igor On Fri, Dec 5, 2014 at 2:06 PM, EpsiloN EpsiloN eps@gmail.com wrote: Package: src:linux Version: kernel: 3.2.0-4-686-pae Severity: