netdev - Re: sd8686 linux system hang: not always

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 21 Aug 2009 08:04:16 -0500
From:	Dan Williams <dcbw@...hat.com>
To:	Benoît Vaillant <benoit.vaillant@...log.org>
Cc:	netdev@...r.kernel.org
Subject: Re: sd8686 linux system hang: not always

On Thu, 2009-08-20 at 22:40 +0200, Benoît Vaillant wrote:
> On Wed, Aug 19, 2009 at 02:39:57PM -0500, Dan Williams wrote:
> > On Wed, 2009-08-19 at 20:56 +0200, Benoît Vaillant wrote:
> > > /*
> > > Just a bit of context information:
> > > I'm using an MID (quite close to an Aigo, although bios differs,
> > > probably some hardware too, yet I've not checked much on that). I'm
> > > trying to use my Marvell card to get wifi access on a debian
> > > installation. The other OS installed (midinux) successfully gets a
> > > connection using the 8686_v9 mobilin driver, so I'd not go for any
> > > hardware issue. This driver failing to compile 'out of the box' on
> > > fresh kernels, I thought getting the libertas module working would be
> > > a better way to get through.
> > > */
> > > <snip>
> > 
> > Just for context, what SDIO controller are you using on this platform?
> 
> Sure, i can provide that!
> 
> lspci claims i's an:
> 00:e1.0 SD Host controler: Intel Corporation System Controller Hub (SCH Poulsbo) SDIO Controller #1 (rev 06)
> 00:e1.1 SD Host controler: Intel Corporation System Controller Hub (SCH Poulsbo) SDIO Controller #2 (rev 06)
> 
> Complete `lspci -vvv` is attached.
> 
> Could this lead to anything already known which i have might missed?

Well, besides the fact that the Poulsbo SDHC driver hasn't actually
passed review for the kernel yet...  That doesn't mean the Poulsbo
driver isn't a fine driver, but if Pierre hasn't acked it, I don't
really trust it.  The largest # of problems people have had with
Libertas SDIO have been with the host controller with things like
transfer widths, clocking, interrupt vs. polled mode, chunk size, etc.
When the SDHC driver and hardware they are using actually starts working
well, then libertas actually starts working well.

So I don't mean to brush you off, but we know the chip works pretty well
with the Ricoh line (which I'm typing this on right now with an sd8686)
and a few other embedded-type controllers.  So I'd start diving down
into the SDHC driver code for Poulsbo and try to figure out what's going
on there and in the MMC layer.

Dan

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html