Summary: | gentoo-sources-2.6.31 + net-wireless/hostapd-0.6.9 + p54usb crashes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Enne Eziarc <gentoo+bugs> |
Component: | Current packages | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | chewi, fauli, gurligebis, mobile+disabled |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://bugzilla.kernel.org/show_bug.cgi?id=13725 | ||
Whiteboard: | linux-2.6.31 | ||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 291783 |
Description
Enne Eziarc
2009-09-21 20:05:18 UTC
You'll probably be glad to know that I think I have the same problem. I am also running hostapd 0.6.9 with p54usb. All is well on 2.6.30-gentoo-r6. I upgraded to 2.6.31 and encountered several seemingly random freezes before switching back. At the time, I put it down to fglrx but now I think about it, fglrx usually only freezes when you do something like start or stop X. I was experimenting with KMS yesterday, first with 2.6.31 and then with 2.6.32-rc3. After a few freezes, I disabled p54usb but KMS was also causing freezes so it was hard to tell whether this was still affecting 2.6.32 or not. I'm going to try KMS again when rc4 comes out so I'll also try and see whether this p54usb issue is fixed or not. Have you reported this anywhere else? It would probably be best to report this at bugzilla.kernel.org. Since it works with 2.6.30 and not 2.6.31, I think it is safe to say, that this is a kernel driver bug, and not a bug in hostapd. Can you try this patch: http://patchwork.kernel.org/patch/34618/ against a 2.6.31 kernel and see if the problem persists? I've just tried gentoo-sources-2.6.31-r2 which apparently already has that patch applied; still crashes. Let's follow this upstream bug report, for now, which seems to addressing the same issue as yours, Anthony: http://bugzilla.kernel.org/show_bug.cgi?id=13725 A user in http://bugzilla.kernel.org/show_bug.cgi?id=13725 reports the following: " I think this might be fixed now. I was experiencing it too but I've just been running yesterday's linux-next for a couple of hours, with a Wii and Vista both connecting, and there were no panics or freezes. " Care to test it? Running 2.6.32-rc4-next-20091012 for 20 hours now. It hasn't crashed in that time and dmesg seems to be quiet again. (In reply to comment #7) > Running 2.6.32-rc4-next-20091012 for 20 hours now. It hasn't crashed in that > time and dmesg seems to be quiet again. > Good to know. I'll be watching the upstream report for the specific commit that causes the issue and backport it for the gentoo-sources. We'll watch the upstream bug and work to backport the fix if they identify it. (In reply to comment #9) > We'll watch the upstream bug and work to backport the fix if they identify it. According to http://forums.gentoo.org/viewtopic-t-795441-highlight-.html the bug is fixed in linux-next, so a backport is appreciated because several users are hit by this problem. If someone can identify the patch that acutally fixes the issue, we'll be happy to look into back-porting it. (In reply to comment #11) > If someone can identify the patch that acutally fixes the issue, we'll be happy > to look into back-porting it. http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commit;h=47ab3840a389ff1b9959734995123e5bc94c3443 This is the fix, please backport. Did you apply this against 2.6.31-r6 and test? This is probably not the patch, since this patch has been in the kernel since 2.6.31-rc3. http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.31.y.git;a=commitdiff;h=47ab3840a389ff1b9959734995123e5bc94c3443 (In reply to comment #14) > This is probably not the patch, since this patch has been in the kernel since > 2.6.31-rc3. > > http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.31.y.git;a=commitdiff;h=47ab3840a389ff1b9959734995123e5bc94c3443 Hm, it is said to fix the issue from upstream bug report. Let's hope for the best. I don't think this is it either seeing as it happened to me in a later rc. The upstream bug actually says... "I am using 2.6.31-rc6-git7 as I saw patch from http://patchwork.kernel.org/patch/34618/ is already applied but the problem still occurs." |