linux-kernel - Re: Linux 3.8 broken for MacBookAir5,1

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:	Mon, 18 Feb 2013 19:10:41 -0300
From:	Otavio Salvador <otavio@...ystems.com.br>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Kernel development list <linux-kernel@...r.kernel.org>,
	"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>
Subject: Re: Linux 3.8 broken for MacBookAir5,1

On Mon, Feb 18, 2013 at 7:09 PM, Alan Stern <stern@...land.harvard.edu> wrote:
> On Sun, 10 Feb 2013, Otavio Salvador wrote:
>
>> On Sun, Feb 10, 2013 at 12:47 PM, Alan Stern <stern@...land.harvard.edu> wrote:
>> > On Sun, 10 Feb 2013, Otavio Salvador wrote:
>> >> I do have EHCI and PCI enabled so it should be working. Any clue about
>> >> why it breaks it?
>> >
>> > Perhaps your system is not loading the new ehci-pci kernel module.
>>
>> Yes; it should be the cause as building it built-in makes it work.
>> However it is a regression from my point of view.
>>
>> Those are the controllers I have in my system:
>>
>> 00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
>> Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04)
>> 00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
>> Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04)
>> 00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series
>> Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04)
>>
>> I thought the ehci-pci module would be load for every ehci PCI; What
>> do you think?
>
> The kernel can't guarantee anything about what driver modules are
> loaded.  That's up to userspace.  In particular, the initramfs image
> must be set up properly (if that is where these modules are loaded
> from).

But why kernel cannot load it if we have a PCI subsystem? Or do you
think my initrd did not put the module on the initramfs image?

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@...ystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br
--
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/