[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2009-01-07 Thread Leann Ogasawara
Based on the previous comments I'm marking this Fix Released against Intrepid. Thanks. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- [rt61] Lockups running Feisty on x86-64 https://bugs.launchpad.net/bugs/90243 You received this bug notification because you are a me

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2008-10-03 Thread iponeverything
Went Intrepid today -- The events/0 problems is gone. It was perhaps a the relationship between the version nm-manager in 8.04 and rt61pci driver in 2.6.27-4. For me this issue is gone with Intrepid and 2.6.27-4. many thanks -- [rt61] Lockups running Feisty on x86-64 https://bugs.launchpad.net

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2008-10-01 Thread iponeverything
linux-image-2.6.27-4-generic and rt61pci on my machine has serious problems with resume from suspend. events/0 pegs the cpu at 100% and keyboard becomes unresponsive. It happens on about 80% of time, the other 20% of time it will resume fine - but removing the network card and reinserting it wil

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2008-09-29 Thread iponeverything
I have a level one wpc-301 v4 that is affected by rt61pci lockup issue in hardy using 2.6.24-19-generic and version 2.0.10 of the rt61pci module. I slapped on linux-backports-modules which seemed to resolve the issue with the hard lockups, but activity light on the card stayed lit regardless of

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2008-08-28 Thread Leann Ogasawara
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-09-28 Thread figjam
See also https://bugs.launchpad.net/ubuntu/+bug/34902 The same issue. -- [rt61] Lockups running Feisty on x86-64 https://bugs.launchpad.net/bugs/90243 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ub

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-09-18 Thread figjam
Same here except I am running Gutsy, not Feisty. The computer locks up sometimes during boot, sometimes after a few minutes of usage, and even sometimes after a couple of hours. When using a graphical environment. The keyboard hangs first, mouse still works a couple of seconds, soon everything is

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-08-29 Thread Ariel Vardi
Same freeze here, and I confirm that it only happens on linux-generic (2.6.20). The bug does not occur on linux-386. The symptoms are the same as detailed above, i.e. complete lockup of the system except for the mouse and sometimes keyboard repeating indefinitely. My system is the following: 00:

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-05-22 Thread iopo
Hi! I don't know how much this could be useful, but I have unistalled Feisty and installed linux mint "cassandra" and I had no more freeze! Since the two OS 99% identical (linux mint has codecs-flash plug in and Java preinstalled and different menus and themes; nothing really essential) it may be

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-05-22 Thread DePui
Rather disappointing that Feisty went live with this bugged driver from SerialMonkey I had gone at length in Edgy to get the rt61 running with WEP, by removing the rt61pci module and downloading and compiling the rt61 driver from ralinktech.com, finally with success. Now after the upgrade to Feis

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-05-17 Thread nixnoob
possibly related to my issue, if eth0 is up and ra0 is brought up the system get soft lockup, try removing either of these entries from /etc/network/interfaces and see if the crashing persists. -- [rt61] Lockups running Feisty on x86-64 https://bugs.launchpad.net/bugs/90243 You received this bug

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-05-06 Thread NoWhereMan
try appending acpi=force irqpoll to your kernel parameters -- [rt61] Lockups running Feisty on x86-64 https://bugs.launchpad.net/bugs/90243 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@li

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-04-28 Thread Nicholaus Shupe
I'm experiencing the same problem with the following configuration: 00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS645DX Host & Memory & AGP Controller 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) 00:02.0 ISA bridge: Silicon Integrated Systems [S

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-04-14 Thread karamalz
** Changed in: linux-source-2.6.20 (Ubuntu) Status: Needs Info => Confirmed ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Confirmed => Needs Info ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Needs Info => Confirmed ** Changed in: linux-source-2.6.20 (Ubuntu)

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-04-13 Thread karamalz
I resolved my problem with the rt61 driver by switching to the 386 kernel and the system is rock-solid again. As the 386 Kernel isn't build with CONFIG_SMP this is just a work-around for people using old cpu's wich don't need the SMP feature. Of course this is not a solution to the problem as the

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-04-12 Thread Roland Dreier
Looking at the traceback that John Clemens just posted -- it looks pretty obviously like another variation of the same class of deadlock that I described before: - BeaconTimeout() ran from a timer, and calls into MlmeHandler() - MlmeHandler() runs the table-based state machine - The state machi

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-04-09 Thread John Clemens
This is still a problem as of 4/9/2007 (kernel 2.6.20-14). I just removed the rt61 card from my system for now, but if it's at all possible at this late date, please do -not- ship feisty with this bug. It's very hard to diagnose ('Everything just stops, except mouse movement!'), and rt61 cards are

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-03-28 Thread Frode Solheim
Regarding my last post, I managed to resolve my problem by downloading: rt2x00 nightly CVS tarball, from http://rt2x00.serialmonkey.com/wiki/index.php?title=Downloads a couple of weeks ago. I still use the same kernel version. If the drivers shipped with ubuntu are the same as the ones from rt2x0

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-03-23 Thread Roland Dreier
OK, I managed to get a traceback of the soft lockup on my system, but unfortunately I screwed up and it didn't get captured like I thought it was. So I don't have the traceback, and I didn't read it that closely before I rebooted, since I thought I had it saved to study later. However, I did look

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-03-19 Thread karamalz
I also can confirm this problem. A Ralink pci card 00:09.0 Network controller: RaLink RT2561/RT61 802.11g PCI is driven by the rt61 driver. I have a 32bit single core system, so I don't think that the problem is SMP related. Same problems here: The system freezes completly from one second to ano

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-03-12 Thread Frode Solheim
I can confirm lockups with rt61 driver loaded. I have a ralink card in a computer: 04:08.0 Network controller: RaLink RT2561/RT61 802.11g PCI When the rt61 driver is loaded the computer locks up sometimes during boot, sometimes after a few minutes of usage, and even sometimes after a couple of ho

[Bug 90243] Re: [rt61] Lockups running Feisty on x86-64

2007-03-08 Thread Roland Dreier
Thanks Kyle, but it seems that rebuilding the kernel is a little harder, or perhaps the linux-source package is broken. I had tried basically your suggestion before and failed, and I just tried again. I installed linux-source-2.6.20 and unpacked /usr/src/linux- source-2.6.20.tar.bz2, and then in