Bug#772134: Kernel 3.2.0-4 failed to resume link
Hi Hope you had chance to dive into problem? Regards Igor
Bug#772134: Kernel 3.2.0-4 failed to resume link
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 leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
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
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
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-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
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 completely at random. Kernels versions start from 2.6 up to 3.2. Is there any way to debug the problem? Regards Igor
Bug#772134: Kernel 3.2.0-4 failed to resume link
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 at random? That question has be seen. And this message shows that it is not ignored. I think #772134 could be an interresting problem and I know I have allready interresting problems :-) Groeten Geert Stappers -- Leven en laten leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
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
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 initiator gets it's IP configuration. > >> > > Statically written in /etc/network/interfaces. Kernel hasn't read that file yet when it is initailizing disks ... > > I should notice that systems that are affected has two or four interfaces > > in same network segment. > > > > iSCSI initiator has static IPs as well > E-mail this bugreport, not me. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
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 wrote: > 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 leven >
Bug#772134: Kernel 3.2.0-4 failed to resume link
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 leven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#772134: Kernel 3.2.0-4 failed to resume link
Hello Any feedback is appreciated. Thanks Regards Igor On Mon, Dec 8, 2014 at 10:10 AM, EpsiloN EpsiloN 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 Fri, Dec 5, 2014 at 2:06 PM, EpsiloN EpsiloN wrote: > >> Package: src:linux >> Version: kernel: 3.2.0-4-686-pae >> Severity: normal >> >> Dear Maintainers >> >> I have problem with some servers. This is what I see in log: >> >> [3.044812] ata1.01: failed to resume link (SControl 0) >> [3.055767] ata1.00: SATA link down (SStatus 0 SControl 300) >> [3.055786] ata1.01: SATA link down (SStatus 4 SControl 0) >> [3.055860] ata2.01: failed to resume link (SControl 0) >> [3.066813] ata2.00: SATA link down (SStatus 0 SControl 300) >> [3.066831] ata2.01: SATA link down (SStatus 4 SControl 0) >> [3.483734] PM: Starting manual resume from disk >> [3.483741] PM: Hibernation image partition 8:5 present >> [3.483743] PM: Looking for hibernation image. >> [3.483874] PM: Image not found (code -22) >> [3.483879] PM: Hibernation image not present or could not be loaded. >> [3.496745] EXT4-fs (sda1): INFO: recovery required on readonly >> filesystem >> [3.496751] EXT4-fs (sda1): write access will be enabled during >> recovery >> [3.729304] EXT4-fs (sda1): recovery complete >> [3.729411] EXT4-fs (sda1): mounted filesystem with ordered data mode. >> Opts: (null) >> >> The only way to bring server back is to use reset button. Keyboard is not >> responding and neither VGA monitor. Same issue on several HP DL servers. >> Starting from G6 to G8. >> >> I have attached the the bug report as well. This was an issue with the >> older kernel - Bug#612541. >> >> >> Regards >> Igor Maksimov >> > >
Bug#772134: Kernel 3.2.0-4 failed to resume link
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 wrote: > Package: src:linux > Version: kernel: 3.2.0-4-686-pae > Severity: normal > > Dear Maintainers > > I have problem with some servers. This is what I see in log: > > [3.044812] ata1.01: failed to resume link (SControl 0) > [3.055767] ata1.00: SATA link down (SStatus 0 SControl 300) > [3.055786] ata1.01: SATA link down (SStatus 4 SControl 0) > [3.055860] ata2.01: failed to resume link (SControl 0) > [3.066813] ata2.00: SATA link down (SStatus 0 SControl 300) > [3.066831] ata2.01: SATA link down (SStatus 4 SControl 0) > [3.483734] PM: Starting manual resume from disk > [3.483741] PM: Hibernation image partition 8:5 present > [3.483743] PM: Looking for hibernation image. > [3.483874] PM: Image not found (code -22) > [3.483879] PM: Hibernation image not present or could not be loaded. > [3.496745] EXT4-fs (sda1): INFO: recovery required on readonly > filesystem > [3.496751] EXT4-fs (sda1): write access will be enabled during recovery > [3.729304] EXT4-fs (sda1): recovery complete > [3.729411] EXT4-fs (sda1): mounted filesystem with ordered data mode. > Opts: (null) > > The only way to bring server back is to use reset button. Keyboard is not > responding and neither VGA monitor. Same issue on several HP DL servers. > Starting from G6 to G8. > > I have attached the the bug report as well. This was an issue with the > older kernel - Bug#612541. > > > Regards > Igor Maksimov >
