linux-kernel - Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 26 May 2007 22:33:13 +0200
From:	Uwe Bugla <uwe.bugla@....de>
To:	Larry Finger <larry.finger@...inger.net>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Maximilian Engelhardt <maxi@...monizer.de>,
	linux-wireless@...r.kernel.org,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Michael Buesch <mb@...sch.de>
Subject: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)

Am Samstag, 26. Mai 2007 21:57 schrieben Sie:
> Uwe Bugla wrote:
> > OK, applied this one against 2.6.22-rc3, assuming a typo error by you,
> > Andrew.
> >
> > Result is: No change: non functionable b44 device!
>
> Could you please send the following:
>
> 1. the output of lsmod from the non-functioning kernel

Nonsense!
As I stated already, both modules (i. e. b44 and ssb) are loaded correctly.
So please read the thread before you post that, not vice versa!

>
> 2. the output of dmesg from the non-functioning kernel
>
> 3. your .config used to create your non-functioning kernel.
>
They are already in the thread. So please leave me alone with those lazy 
hints! Read bfore you post, not vice versa!

> Thanks,
>
> Larry

Cheers

Uwe
-
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/