lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140914125522.GF26638@schottelius.org>
Date:	Sun, 14 Sep 2014 14:55:22 +0200
From:	Nico Schottelius <nico-kernel-2014-08-14@...ottelius.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Nico Schottelius <nico-kernel-2014-08-14@...ottelius.org>,
	linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org
Subject: Re: Linux 3.16: O2 Micro MMC missing in lspci

Hey Stefan,

(un-)fortunately I don't have the device anymore,
so I cannot test anymore.

Cheers,

Nico

Stefan Richter [Sun, Sep 14, 2014 at 10:24:08AM +0200]:
> On Aug 14 Nico Schottelius wrote:
> > Hello,
> > 
> > when booting into 3.16.0-2-ARCH I miss the following
> > entry in lspci:
> > 
> > [12:50] gold:debug-sd-card-reader% diff 3.15/lspci 3.16/lspci 
> > 17d16
> > < 03:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader
> > Controller (rev 01)
> > 
> > This causes my system to be unable to mount/see the sd cards.
> > My hardware is a Dell E7440 notebook.
> > 
> > I attached dmesg & lspci of both kernels.
> > 
> > Anyone an idea on what might be wrong?
> > 
> > The only related issues I found is
> >     https://bugs.archlinux.org/task/26971
> > 
> > and that there was a change in the mmc area:
> > 
> >     https://lkml.org/lkml/2014/6/10/491
> > 
> > Cheers,
> > 
> > Nico
> > 
> > p.s.: Please cc on reply
> 
> Both the archlinux bug and the pull request very much appear to be
> unrelated to your issue.  In your case, the MMC subsystem is not involved
> since the PCI device of the SD controller is not exposed to the MMC
> subsystem anymore, just like it is not exposed in lspci anymore.
> 
> I suggest as next steps:
>   - Test whether the issue still exists in the newest kernel that you are
>     able to install.  (v3.17-rc4 is current, v3.16.2 is the lastest on in
>     the 3.16 branch.)
>   - Post the dmesg output from a successful boot with 3.15 and from an
>     unsuccessful boot with 3.16.
> 
> [added Cc: linux-pci]
> -- 
> Stefan Richter
> -=====-====- =--= -===-
> http://arcgraph.de/sr/

-- 
New PGP key: 659B 0D91 E86E 7E24 FD15  69D0 C729 21A1 293F 2D24
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ