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

To: Geert Stappers <stappers@stappers.nl>
Cc: 772134@bugs.debian.org
Subject: Bug#772134: Kernel 3.2.0-4 failed to resume link
From: EpsiloN EpsiloN <eps.eps@gmail.com>
Date: Wed, 10 Dec 2014 12:50:05 +0200
Message-id: <[🔎] CABX0OXsuF9SvBGyGU2CzabNKTt-d5LsL2K-n-x9Mkws5PJOxVg@mail.gmail.com>
Reply-to: EpsiloN EpsiloN <eps.eps@gmail.com>, 772134@bugs.debian.org
In-reply-to: <[🔎] 20141210104745.GI9665@gpm.stappers.nl>
References: <[🔎] CABX0OXth34z0hWUWneujfa2LC4YZOnGdUwyNMtrnG+zFROXXOA@mail.gmail.com> <[🔎] CABX0OXskJwnKmadrnQSwmOL-hhRoy=yDq99Xrmv+DHOVxL2+Rw@mail.gmail.com> <[🔎] CABX0OXsB3FEUw3p8nwvPMKsB-rje+9X03RDe3wKyhmcyWoGE3g@mail.gmail.com> <[🔎] 20141210104745.GI9665@gpm.stappers.nl>

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 <stappers@stappers.nl> 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

Reply to:

References:
- Bug#772134: Kernel 3.2.0-4 failed to resume link
  - From: EpsiloN EpsiloN <eps.eps@gmail.com>
- Bug#772134: Kernel 3.2.0-4 failed to resume link
  - From: EpsiloN EpsiloN <eps.eps@gmail.com>
- Bug#772134: Kernel 3.2.0-4 failed to resume link
  - From: EpsiloN EpsiloN <eps.eps@gmail.com>
- Bug#772134: Kernel 3.2.0-4 failed to resume link
  - From: Geert Stappers <stappers@stappers.nl>

Prev by Date: Bug#772134: Kernel 3.2.0-4 failed to resume link
Next by Date: Re: Questions about adding new kernel configs to support omap5 devboard
Previous by thread: Bug#772134: Kernel 3.2.0-4 failed to resume link
Next by thread: Bug#772134: Kernel 3.2.0-4 failed to resume link
Index(es):
- Date
- Thread