/sysfs problems with SDIO/MMC and sd8686 Wlan driver

[Tony Espy]

Binary package hint: linux-source-2.6.24

We've run into a problem on Ubuntu Mobile ( based on Hardy ) with the Marvell sd8686 driver which seems to be caused by the SDIO core driver.

The short description is that when NetworkManager looks up the net.physical_device ( or net.originating_device ) using HAL, the node it finds is missing a driver property. NetworkManager sometimes uses the value of this property to gate driver-specific logic. Sometimes, in the past, patches have crept in which don't check for NULL, and NM crashes. We've had to patch NM in the past due to this problem.

I've looked at the sd8686 driver source, and it just sets the value "sdio_8686" in the sdio_driver struct ( see LUM/ubuntu/wireless/marvell/8686_wlan/if/if_sdio.c ) and passes it to the sdio code via the call sdio_register_driver().

In order to follow this bug, please refer to the attached lshal.log file.

The physical device that NM is returned is a property of the following UDI ( note - I also include the corresponding sysfs_path ):

'/org/freedesktop/Hal/devices/net_00_10_61_64_10_10' [ /sys/devices/pci0000:00/0000:00:1e.2/mmc_host/mmc2/mmc2:0001/net/wlan0 ]

The net.physical_device ( or net.originating_device ) property has the following value:

'/org/freedesktop/Hal/devices/net/pci_8086_811e_mmc_card_rca1'

The abbreviated sysfs_path is: ../mmc_host/mmc2/mmc2:0001

This node in the Hal output has not property ( info.linux_driver ), nor does the above sysfs_path have a link called "driver".

You'll note however that there's another node that has parent equal to the net.physical_device ( ie. mmc_card_rca1 ). It's UDI is:

'/org/freedesktop/Hal/devices/net/pci_8086_811e_mmc_card_rca1_sdio1'

...and this node has a driver property. In fact, it's sysfs_path is a subdirectory of the net.physical_device's sysfs_path:

/sys/devices/pci0000:00/0000:00:1e.2/mmc_host/mmc2/mmc2:0001/mmc2:0001:1

In fact, all of the driver specific values are present in this directory ( ie. vendor, class, type, etc... ).

So, from all the evidence, if the top-level sysfs directory ( ../mmc_host/mmc2/mmc2:0001/net/wlan0 ) had it's driver link updated to point the right place ( ../mmc_host/mmc2/mmc2:0001/mmc2:0001:1 ), things would just work.

I have a hunch this problem may be due to the fact that SDIO cards can be multi-function, but that's just a guess.

By the way, the kernel and LUM involved are the latest on the abi-12 branches of these git trees:

http://kernel.ubuntu.com/git?p=mid-team/hardy-jax.git;a=summary
http://kernel.ubuntu.com/git?p=mid-team/hardy-lum-jax.git;a=summary

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Amit Kucheria (amitk)]

Is this still an issue?

[Tony Espy (awe)]

It's not a pending customer issue if that's what you're asking...

[keller (agent60092594)]

I have an raon everun note with the same sdio stack and wireless "card" and intrepid ibex with the 2.6.27.x kernel STILL doesn't recognize the card! So it IS still an issue, and it probably won't be fixed until they come out with another ubuntu distribution with a new goofy animal name.

[diJenerate (dijenerate)]

@keller

For those suffering this bug on the everun with 2.6.27.9-generic or any other kernel build, what do you suggest as an easy fix? I've got a system that destabilizes and hangs after the wireless has been in use for a while... and since the true fix won't occur until the next 'goofy animal name' is released, I will need something to allow wireless to work right now... help please.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[diJenerate (dijenerate)]

Jeremy,

To be honest, I have given up on Ubuntu and moved back to core Debian
because of the direction things seemed to be going in long ago, and have
actually gone with the Ubuntu development. In my 15 years of linux
experience, I have never seen any single distro follow Microsoft down
the slippery slope of poor prioritisation as closely as Ubuntu has.
Focus has gone full cycle to be about the UI so much more than core
functions that simple things that worked before go broken like Audio
(with the introduction and poor integration of pulse) among other issues
too numerous to count. Regression is the order of the day with Ubuntu so
much so I have abandoned any bug reporting in it and even use of it at
this stage.

I focus my development efforts on Debian and Maemo (and shortly
depending on how things pan out, Meego) as far as linux goes and for the
upper end stuff OpenSolaris. Some of the problems of Ubuntu seem to be
leaking into the global distribution world and we now see mass
regressions in Gnome under other distros. If this continues, I fear the
anti-OpenSource advocates (MS, Apple et al) would have won in this OS
war since the only thing worse than obscurity where an OS is concerned
is negative mass exposure. I fear linux is on a path to notoriety where
the desktop and non-tech users are concerned and if this continues
unchecked, the developers who have been around from the beginning and
the experienced ones like myself with a bit less experience than the
older guys will abandon desktop and handheld development out of frustration.

I have the Sharp Zaurus project of 2001-2002 under my belt of experience
but today's linux world is full of programmers who don't seem to really
grasp what the OpenSource movement is really about. These 'nu-devs' have
too much say in the direction the community is going in and not enough
understanding of where GNU and then Linux came from. Without knowing
where you came from, or who you are, you have no way of knowing where
you're going.

Regrets,
Paul

Jeremy Foshee wrote:
> This bug report was marked as Triaged a while ago but has not had any
> updated comments for quite some time. Please let us know if this issue
> remains in the current Ubuntu release,
> http://www.ubuntu.com/getubuntu/download . If the issue remains, click
> on the current status under the Status column and change the status back
> to "New". Thanks.
>
> [This is an automated message. Apologies if it has reached you
> inappropriately; please just reply to this message indicating so.]
>
>
> ** Tags added: kj-triage
>
> ** Changed in: linux (Ubuntu)
> Status: Triaged => Incomplete
>
>

[Po-Hsu Lin (cypressyew)]

Closing this bug with Won't fix as Hardy is no longer supported.
Please feel free to open a new bug report if you're still experiencing this on a newer release (Bionic 18.04.3 / Disco 19.04)
Thanks!