Original Message from: Ben Hutchings
>
> One piece of my backport to 3.2.y went missing in the forward-port to
> 3.4.y. Can you test 3.4.83 with this patch on top?
>
> Ben.
iwlwifi works with the additional patch, thanks :)
--
To unsubscribe from this list: send the line "unsubscribe linux-ke
Original Message from: Ben Hutchings
>
> Andreas, could you test whether this regression is also present in
> 3.2.55? This patch is based on my backport for 3.2.y.
>
3.2.55 is OK here.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord
Original Message from: Greg Kroah-Hartman
>
> Does Linus's tree also have this problem for you? Or does it work
> there? If it works there, perhaps we just missed backporting something
> to 3.4?
>
Other trouble aside, iwlwifi works fine - writing this from today's build of
3.14.0-rc7+.
--
To
Original Message from: Greg Kroah-Hartman
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Johannes Berg
>
> commit 8a964f44e01ad3bbc208c3e80d931ba91b9ea786 upstream.
Forwarding original message to make sure it isn't lost - this pa
>On Wed, Mar 12, 2014 at 14:46:14, Andres Bertens wrote:
>
> I updated today to 3.4.83 kernel and my wireless card stop working (log
> says: iwlwifi :03:00.0: Unable to initialize device).
>
Same here with Intel(R) Centrino(R) Ultimate-N 6300 AGN, REV=0x74
>
> Reverting patch
> Johan
> So 3.5 and later really don't seem to have any issue with this patch.
> I'm as puzzled as ever. Thanks for testing this again.
>
Bad news from 3.6: I got a blank screen there too, yesterday. Maybe it had even
happened in 3.5 once before I got into testing all those 3.4/3.0 images - at my
week
> Andreas, can you please check whether 3.5.x works for you, just to
> make sure that this particular elephant is only wreaking havoc in 3.4
> and earlier?
I've been using 3.5 all the time since .0, I never had any trouble there - a
few reboots just now with a vanilla 3.5.4 image were
successful
> Ok, now reverted, thanks.
>
> greg k-h
The same patch also breaks 3.0 for me. A 3.0.42 image with the patch reverted
was fine, I checked with several restarts.
Sort of confirms there is something in >=3.5 that makes this thing work.
Regards
--
To unsubscribe from this list: send the line "un
>
> I haven't tried 3.4.11 yet
OK, first two tries just now, instant black screens:
- 3.4.11
- 3.0.42
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.htm
>
> Did anything ever come from this? I haven't reverted anything, or
> applied anything different, so if something needs to be done here,
> please let me know.
>
I haven't tried 3.4.11 yet, I was only coming back from 3.5 in the hunt for a
different bug, so - with a lot of bad coincidence - i
> On Fri, Sep 07, 2012 at 02:27:12AM +0200, Andreas Sturmlechner wrote:
> > Hello,
> >
> > please revert commit 0d8957c8a90bbb5d34fab9a304459448a5131e06 - for some
> > reason it breaks boot-up (screen stays blank) on my GM45 hardware despite
> > >= 3.5 b
Hello,
please revert commit 0d8957c8a90bbb5d34fab9a304459448a5131e06 - for some
reason it breaks boot-up (screen stays blank) on my GM45 hardware despite >=
3.5 being fine.
See bug 54575 on freedesktop.org for a full description:
https://bugs.freedesktop.org/show_bug.cgi?id=54575
No idea how
12 matches
Mail list logo
