From: Guilherme Piccoli <gpiccoli@canonical.com>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>,
"K, Narendra" <Narendra.K@dell.com>
Cc: "Barabash, Alexander" <Alexander.Barabash@dell.com>,
"Engel, Amit" <Amit.Engel@dell.com>,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>,
"halves@canonical.com" <halves@canonical.com>,
Jay Vosburgh <jay.vosburgh@canonical.com>,
Dan Streetman <ddstreet@canonical.com>,
Gavin Guo <gavin.guo@canonical.com>,
"x86@kernel.org" <x86@kernel.org>,
"grub-devel@gnu.org" <grub-devel@gnu.org>
Subject: Re: Dell BIOS issue reading Disk Extended data
Date: Fri, 12 Mar 2021 12:44:16 -0300 [thread overview]
Message-ID: <CAHD1Q_ymyoN5rFmmcA4JseGsb_2sesHCwPoAcBPrdYDFvXWfGQ@mail.gmail.com> (raw)
In-Reply-To: <SA1PR19MB4926F137272CF5AB3FB788A6FAA09@SA1PR19MB4926.namprd19.prod.outlook.com>
On Fri, Jan 22, 2021 at 3:41 PM Limonciello, Mario
<Mario.Limonciello@dell.com> wrote:
>
> >
> > Hello Dell folks, I'm Guilherme Piccoli from Canonical - first of all,
> > apologies for the out-of-nowhere communication. We've been investigating
> > an issue that seems to date long time ago, and eventually we could
> > narrow it to what appears to be a Dell BIOS bug. Notice I'm also looping
> > a kernel x86 ML and grub-devel, just for the purpose of archiving such
> > discussion in public lists, to help others that may find such an issue
> > in the future.
> >
> > Since I don't have contacts of Dell representatives, I've just raised a
> > list of people from Dell contributing to kernel in the last 2 years -
> > maybe one of you could point me towards the path of a proper
> > contact/channel to discuss such an issue. If not, I'm sorry for the noise.
> > Let me detail the problem we're observing - notice all of this is about
> > legacy BIOS mode, not UEFI.
>
> Most of the guys you CC'ed from Dell work on client related things, not
> servers. So I'll move some of the client guys off of this thread into BCC.
> @K, Narendra can you please raise this with the appropriate team?
>
Thanks Mario and K, Narendra - do we have any news about that?
Cheers,
Guilherme
next prev parent reply other threads:[~2021-03-12 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 18:35 Dell BIOS issue reading Disk Extended data Guilherme G. Piccoli
2021-01-22 18:41 ` Limonciello, Mario
2021-03-12 15:44 ` Guilherme Piccoli [this message]
2021-03-30 17:43 ` K, Narendra
2021-03-31 14:43 ` Guilherme Piccoli
2021-03-31 17:24 ` Jordan Uggla
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-all 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=CAHD1Q_ymyoN5rFmmcA4JseGsb_2sesHCwPoAcBPrdYDFvXWfGQ@mail.gmail.com \
--to=gpiccoli@canonical.com \
--cc=Alexander.Barabash@dell.com \
--cc=Amit.Engel@dell.com \
--cc=Mario.Limonciello@dell.com \
--cc=Narendra.K@dell.com \
--cc=ddstreet@canonical.com \
--cc=gavin.guo@canonical.com \
--cc=grub-devel@gnu.org \
--cc=halves@canonical.com \
--cc=jay.vosburgh@canonical.com \
--cc=kernel@gpiccoli.net \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.