public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: "Rabeda, Maciej" <maciej.rabeda@linux.intel.com>,
	Sivaraman Nainar <sivaramann@amiindia.co.in>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	Sean Brogan <sean.brogan@microsoft.com>
Cc: Santhosh Kumar V <santhoshkumarv@amiindia.co.in>
Subject: Re: [EXTERNAL] Re: [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019
Date: Tue, 2 Feb 2021 17:34:45 +0000	[thread overview]
Message-ID: <MWHPR21MB01890FF267BBD59DCA986850EFB59@MWHPR21MB0189.namprd21.prod.outlook.com> (raw)
In-Reply-To: <3cec943a-bae0-5e1b-2f69-3b8c1dda706e@linux.intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 2574 bytes --]

I’ll ask around, but I’m not aware of who off the top of my head.

- Bret

From: Rabeda, Maciej<mailto:maciej.rabeda@linux.intel.com>
Sent: Tuesday, February 2, 2021 5:53 AM
To: Sivaraman Nainar<mailto:sivaramann@amiindia.co.in>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>; Sean Brogan<mailto:sean.brogan@microsoft.com>
Cc: Santhosh Kumar V<mailto:santhoshkumarv@amiindia.co.in>
Subject: [EXTERNAL] Re: [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019

Siva,

I would try to bring it up with MSFT to see what might have caused that.

Bret, Sean,

Any ideas who could be the contact point from MSFT regarding iSCSI boot (and potential issues)?
Siva is observing some blue screens (see first email).

Thanks,
Maciej
On 02-Feb-21 12:55, Sivaraman Nainar wrote:
Hello Maciej:

The issue can be seen in edk2-stable201911 onwards. Haven’t  tested the earlier versions.

-Siva
From: Rabeda, Maciej [mailto:maciej.rabeda@linux.intel.com]
Sent: Tuesday, February 2, 2021 4:57 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Sivaraman Nainar
Cc: Santhosh Kumar V
Subject: Re: [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019

Hi Nainar,

Could you try to bisect the issue using older EDKII releases to see whether it reproduces there?

Thanks,
Maciej
On 01-Feb-21 12:57, Sivaraman Nainar wrote:
Hello Maciej:

Do we have any update on this Inquiry. IS this need to be checked in Network Pkg or we need to reach Microsoft.

The issue happening only with Windows OS especially 2019.

Thanks
Siva
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> [mailto:devel@edk2.groups.io] On Behalf Of Sivaraman Nainar
Sent: Monday, January 4, 2021 9:03 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Rabeda, Maciej; Santhosh Kumar V
Subject: [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019

Hello all:

When IPv6 based ISCSI boot performed with Windows 2019 as OS we are seeing the below error during Windows boots.  Out of 10  times 1 time it boots properly. Failure rate is 9/10.

Does anyone met this issue, Wth IPv4 based boot it always boots to OS.

[cid:part4.B513918F.60B3BF84@linux.intel.com]

-Siva
This e-mail is intended for the use of the addressee only and may contain privileged, confidential, or proprietary information that is exempt from disclosure under law. If you have received this message in error, please inform us promptly by reply e-mail, then delete the e-mail and destroy any printed copy. Thank you.





[-- Attachment #1.2: Type: text/html, Size: 7663 bytes --]

[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 630513 bytes --]

[-- Attachment #3: 10FDCFD95AAA43B4A0E7E5ABF4B19D86.png --]
[-- Type: image/png, Size: 150 bytes --]

      reply	other threads:[~2021-02-02 17:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1656E9FAA1FFAC66.9531@groups.io>
2021-02-01 11:57 ` [edk2-devel] reg: IPv6 ISCSI Boot with Windows 2019 Sivaraman Nainar
2021-02-02 11:26   ` Maciej Rabeda
2021-02-02 11:55     ` Sivaraman Nainar
2021-02-02 13:53       ` Maciej Rabeda
2021-02-02 17:34         ` Bret Barkelew [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=MWHPR21MB01890FF267BBD59DCA986850EFB59@MWHPR21MB0189.namprd21.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox