Jean Delvare wrote:
> I wrongly assumed it had been merged upstream meanwhile but I was
> wrong. David, any reason why this didn't happen?
There were last-minute objections.
The patches got redesigned somewhat by Matthew Garrett and are now pending
pulling once again:
On Monday, September 9, 2019 3:09:57 PM CEST Jean Delvare wrote:
> Hi Greg,
...
> > Sure, feel free to not register it at all if the mode is enabled.
> Now I feel sorry that I asked my question upstream when there's nothing
> to be done there. I'll go bother SUSE kernel folks instead, sorry for
Hi Greg,
On Fri, 6 Sep 2019 14:15:10 +0200, Greg Kroah-Hartman wrote:
> On Fri, Sep 06, 2019 at 01:02:21PM +0200, Jean Delvare wrote:
> > I've been bitten recently by mcelog not working on machines started in
> > secure boot mode. mcelog tries to read DMI information from /dev/mem
> > and fails
D'oh, I hit reply while still editing... Sorry for the noise, a better
answer will come later when ready.
--
Jean Delvare
SUSE L3 Support
On Fri, 6 Sep 2019 14:15:10 +0200, Greg Kroah-Hartman wrote:
> On Fri, Sep 06, 2019 at 01:02:21PM +0200, Jean Delvare wrote:
> > I've been bitten recently by mcelog not working on machines started in
> > secure boot mode. mcelog tries to read DMI information from /dev/mem
> > and fails to open it.
On Fri, Sep 06, 2019 at 01:02:21PM +0200, Jean Delvare wrote:
> I've been bitten recently by mcelog not working on machines started in
> secure boot mode. mcelog tries to read DMI information from /dev/mem
> and fails to open it.
What do you mean by "secure boot"? Is this matthew's patchset that
I've been bitten recently by mcelog not working on machines started in
secure boot mode. mcelog tries to read DMI information from /dev/mem
and fails to open it.
This made me wonder: if not even root can read /dev/mem (nor, I
suppose, /dev/kmem and /dev/port) in secure boot mode, why are we
7 matches
Mail list logo
