Larry Finger <[email protected]> : [...] > 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. -- Ueimor - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- From: "Uwe Bugla" <[email protected]>
- Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- From: Michael Buesch <[email protected]>
- Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- From: Andrew Morton <[email protected]>
- Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- From: Uwe Bugla <[email protected]>
- Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- From: Larry Finger <[email protected]>
- BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- Prev by Date: Re: software suspend doesn't work with 2.6.22-rc3
- Next by Date: Re: suspend2 merge (was Re: [Suspend2-devel] Re: CFS and suspend2: hang in atomic copy)
- Previous by thread: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- Next by thread: Re: BUG in 2.6.22-rc2-mm1: NIC module b44.c broken (Broadcom 4400)
- Index(es):
 |