In order to get wireless stack bug fixes you are going to have to
upgrade to a more recent release.
** Changed in: linux-restricted-modules-2.6.15 (Ubuntu Dapper)
Status: Confirmed = Won't Fix
** Changed in: linux-restricted-modules-2.6.15 (Ubuntu)
Status: Confirmed = Won't Fix
--
I'm having a similar problem in Feisty with the Madwifi-ng driver on a TrendNet
TEW-443PI
Already ran memtest - no problems there. Here's what the kern.log outputs
before I have to reboot:
Kern.log:
Apr 13 22:09:40 Sparta kernel: [ 8413.883195] BUG: soft lockup detected on
CPU#1!
Apr 13
** Changed in: linux-restricted-modules-2.6.15 (Ubuntu Dapper)
Importance: Undecided = Critical
Status: New = Confirmed
** Changed in: linux-restricted-modules-2.6.17 (Ubuntu Dapper)
Status: New = Fix Released
--
[madwifi] Semi-random system lockups in Dapper
Hello! First of all let me say I am truly regretting doing this. This is
a spam message sent to all critical bug message lists. It's purpose:
making this (https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/59695) bug critical too. This is a long standing bug and
has a very serious impact
Hi
Mircea Deaconu wrote:
making this (https://bugs.launchpad.net/ubuntu/+source/acpi-
support/+bug/59695) bug critical too. This is a long standing bug and
has a very serious impact on laptop type of hardware. It's priority is
This is simply incorrect. I have just commented on the bug to
As of Gutsy Gibbon, this bug seems to be fixed for me too.
--
[madwifi] Semi-random system lockups in Dapper
https://bugs.launchpad.net/bugs/37773
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
me too, no problems related to madwifi.
--
E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine
Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716)
Luca Lorenzetto,
Is this still an issue in gutsy?
Please try with a live cd of the latest (tribe 5) release:
http://cdimage.ubuntu.com/releases/gutsy/tribe-5/
--
[madwifi] Semi-random system lockups in Dapper
https://bugs.launchpad.net/bugs/37773
You received this bug notification because you are a member of
Erik: this is purely an issue in dapper. It was fixed in edgy because it
was fixed in madwifi-ng and not in madwifi.
--
[madwifi] Semi-random system lockups in Dapper
https://bugs.launchpad.net/bugs/37773
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
On Tue, Mar 27, 2007 at 05:47:22PM -, Ramin Nakisa wrote:
It is still broken in Feisty. I did a clean install from the latest ISO, did
all the updates. Then it crashed with this error in /var/log/messages:
wifi0: hardware error; resetting
wifi0: ath_reset: unable to reset hardware:
It is still broken in Feisty. I did a clean install from the latest ISO, did
all the updates. Then it crashed with this error in /var/log/messages:
wifi0: hardware error; resetting
wifi0: ath_reset: unable to reset hardware: 'Hardware didn't respond as
expected' (HAL status 3)
--
[madwifi]
On Sun, Mar 25, 2007 at 09:43:04PM -, Ramin Nakisa wrote:
Could you please test if it's fixed in Feisty?
How do I upgrade to Feisty before the official release? I don't
suppose it could be more unstable than my current Ubuntu install!
https://help.ubuntu.com/community/FeistyUpgrades
This is still broken in 2.6.17. I get random lockups in Edgy. I've got
an atheros card, so lspci -n gives 168c:0013. When I boot I get an
error:
ERROR
Resource Conflict - PCI Network Controller in slot 01
Bus:02, Device:02, Function:00
Before it hangs /var/log/messages contains this error:
On Sun, Mar 25, 2007 at 08:48:20PM -, Ramin Nakisa wrote:
This is still broken in 2.6.17. I get random lockups in Edgy. I've got
an atheros card, so lspci -n gives 168c:0013. When I boot I get an
error:
I'm afraid you're experiencing a different issue. This lockup is fixed
in madwifi-ng
On Sunday 25 March 2007 20:58, Soren Hansen wrote:
On Sun, Mar 25, 2007 at 08:48:20PM -, Ramin Nakisa wrote:
This is still broken in 2.6.17. I get random lockups in Edgy. I've got
an atheros card, so lspci -n gives 168c:0013. When I boot I get an
error:
I'm afraid you're experiencing
--- Soren Hansen [EMAIL PROTECTED] wrote:
Odd, that's the exact same card I have. Oh, did you
still have my
madwifi-ng-default package installed? That might
break stuff because the
modules were renamed.
Thanks for this info, Soren! Indeed that's very odd,
as I tested the same wifi card (I
** Changed in: linux-restricted-modules-2.6.17 (Ubuntu)
Status: Unconfirmed = Fix Released
As this bug was never fixed in Dapper (LTS anyone?), I freshly installed Edgy.
However, with the madwifi-ng driver present there, my Wifi card with following
ID did not even work:
$ lspci -n | grep
On Mon, Nov 27, 2006 at 09:41:36AM -, tuxo wrote:
As this bug was never fixed in Dapper (LTS anyone?), I freshly
installed Edgy. However, with the madwifi-ng driver present there, my
Wifi card with following ID did not even work:
$ lspci -n | grep $(lspci | grep -i atheros | cut -f1 -d'
I've experienced the same bug only after last software update. About
three times in a row computer worked for 10-15 min and hanged. At first
time I haven't even done anything, I wasn't even logged in, because I
left computer for a while. On the other day this bug occurred only once.
And It hasn't
This bug does not exist in 2.6.17 (Edgy kernel) since it's a madwifi-old
issue and Edgy uses madwifi-ng.
** Changed in: linux-restricted-modules-2.6.17 (Ubuntu)
Status: Unconfirmed = Fix Released
--
[madwifi] Semi-random system lockups in Dapper
https://launchpad.net/bugs/37773
--
GlebV: This is not the bug you are looking for, this is specific to the
mad-wifi wireless card drivers, so if you are having system lockups, it
is a separate bug
--
[madwifi] Semi-random system lockups in Dapper
https://launchpad.net/bugs/37773
--
ubuntu-bugs mailing list
Also have this problem on my PentiumIII 866 + GA-60XE(815EP)
But i don't have any wireless card on this machine.
just a 3com ethernet adapter.
just simply Dapper Server 6.06.1 + Kernel 2.6.15 server
running amule+azureus.
randomly shows BUG: soft lockup detected on CPU#0 and than hanged up.
On Tue, Nov 14, 2006 at 02:58:46PM -, CNBorn wrote:
Also have this problem on my PentiumIII 866 + GA-60XE(815EP)
But i don't have any wireless card on this machine.
just a 3com ethernet adapter.
Then you're experiencing a different bug.
This machine running Memtest+ and have lots of
** Also affects: linux-restricted-modules-2.6.17 (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
[madwifi] Semi-random system lockups in Dapper
https://launchpad.net/bugs/37773
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I see someone just added this as also affecting l-r-m-2.6.17, ie edgy. I
would like to refute this as my atheros based thinkpad has been solidly
stable since I switched to madwifi-ng (first in dapper, then by
upgrading to edgy).
Juanje - what leads you to add 2.6.17?
--
[madwifi] Semi-random
I solved some random wifi-related lockups by uninstalling network-
manager and directly configuring wpa_supplicant. I added a bit to the
ubuntu wiki https://help.ubuntu.com/community/WifiDocs/WPAHowTo.
Basically I just start wpa_supplicant with a pre-up stanza in
/etc/network/interfaces rather
My laptop hangs up randomly with Ubuntu 6.06. I tried everythings for months,
but no result.
I installed Kubuntu 6.06 and interestingly it has been working fine. No hang up
any longer. I do not see any differences in the configuration.
It was rock solid with Ubuntu 5.10 too.
Compaq Evo160, Ati
Dapper is out now for almost 4 months. And I can still not use my
wireless, as it freezes up my computer randomly. This bug is labeled
critical, but no offical fix has been released yet.
As I got tired of the Ethernet cable crossing our whole appartment and
like Chris Jones not keen on installing
I've just started using my X40 fulltime for work and I've had 4 lockups
so far today. I have just installed Soren's madwifi-ng (and related)
packages as described above because I have to have this working, but it
still would be really nice if the bug could be fixed in the version that
dapper uses.
Has anyone experiencing this bug tried 2.6.17 in edgy?
--
[madwifi] Semi-random system lockups in Dapper
https://launchpad.net/bugs/37773
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
On Wed, Aug 23, 2006 at 10:40:30AM -, Matt Zimmerman wrote:
Has anyone experiencing this bug tried 2.6.17 in edgy?
We've switched to madwifi-ng in Edgy, so the problem is gone there. It
only happens with madwifi-old.
--
[madwifi] Semi-random system lockups in Dapper
** Tags added: dapper freeze
--
[madwifi] Semi-random system lockups in Dapper
https://launchpad.net/bugs/37773
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Just to add some more notes, I've had the crash happen a few more times and
investigated more closely what's going on.
I enabled the wireless LED a few days ago and I've noticed that when the
machine hangs, the LED is on and stays on, so I am tempted to guess that it's
hanging inside a wireless
On Tue, Jul 25, 2006 at 11:10:11AM -, Chris Jones wrote:
However, all of this makes it extraordinarily difficult to track down
what's really going on, especially with no serial port. Can anyone
think of some other way(s) we can collect information about what
failed?
There's always
Very similar problem.
My Compaq EVO 110 laptop was rock solid with Breesy. With Dapper it locks up
randomly when I use Firefox. No mouse, no keyboard, no any massage. I use ATI
Radeon Mobility and the ATI prop. driver. I use the latest upgrade, but this
bug persists from the beginning. I have
I have a desktop system (AMD64 on an ABit AV8) which has an atheros chipset
(pci id 168c:0013) and it works completely reliably, the machine simply never
crashes.
However, I have just also acquited a Thinkpad x40 with the atheros chipset and
I have seen a few crashes where the whole system
Soren,
Thanks it now works. But it is subject to an annoying behavior that others have
observed. NetworkManager continuously disconnect and reconnects. Apparently the
way to get it fixed is stop NetworkManager from continuously scanning...
How does one do that?
--
[madwifi] Semi-random system
On Wed, Jul 19, 2006 at 02:22:36PM -, Michel Lesoinne wrote:
Apparently the way to get it fixed is stop NetworkManager from
continuously scanning... How does one do that?
I don't know. I have not experienced this behaviour.
--
[madwifi] Semi-random system lockups in Dapper
On Tue, Jul 18, 2006 at 02:28:44AM -, Michel Lesoinne wrote:
Still as soon as NetworkManager starts it gets the wifi in a weird state
and never connects. I have to kill NetworkManager, unload the modules
and reload them to be able to connect manually. Soren, do you have a
package of what
On Mon, Jul 17, 2006 at 10:33:26PM -, Michel Lesoinne wrote:
I do not understand the changes you did when I installed a new
version of madwifi, it removed all the new_ath_* drivers and instead
installed the ath_* in their place. So why did you modify
NetworkManager and wpa_supplicant?
Still as soon as NetworkManager starts it gets the wifi in a weird state
and never connects. I have to kill NetworkManager, unload the modules
and reload them to be able to connect manually. Soren, do you have a
package of what you did that I can install?
--
[madwifi] Semi-random system lockups
Just a quick thanks for the heads up on this bug. I was just about to upgrade
a Suse 10.0 machine with an Atheros Wifi adapter to Dapper but I really don't
need this kind of trouble, and so will wait until this problem is flattened.
Good luck with it and thanks again for keeping me out of
I have been experiencing the same problem. I have an Apple MacBook Pro 17 and
installed dapper on it. I also noticed it was network related and perhaps
triggered by wpa_supplicant/knetworkmanager combo. This led me to find this
thread.
Unlike others, my lspci gives me slightly different
On Thu, Jul 13, 2006 at 04:41:33PM -, Michel Lesoinne wrote:
I have been experiencing the same problem. I have an Apple MacBook Pro
17 and installed dapper on it. I also noticed it was network related
and perhaps triggered by wpa_supplicant/knetworkmanager combo. This
led me to find this
Me tto I'm experiencing these freezes.
In addition I'v an ATI video card on my Compaq Evo N800v, and it seems to be a
relation between madwifi and ati:
https://launchpad.net/distros/ubuntu/+source/xserver-xorg-driver-ati/+bug/38181
--
[madwifi] Semi-random system lockups in Dapper
I've had a terrible lockup problem since SMP was enabled by default in
the kernel. Maybe try adding nosmp to the kernel line in grub's menu.lst
(you may need noapic too, not sure though. I needed it, but all cases
are different). I haven't tried removing that nosmp line ever since I
found out it
I never found the time to play with the nice patches, but the latest
kernel update/restricted modules update seems to have made a difference.
A bit early to cry success, but it's been on more or less the last 24
hours without a hitch.
-- Glenn
--
[madwifi] Semi-random system lockups in
On Fri, Jun 16, 2006 at 07:24:21PM -, Glenn Steen wrote:
I never found the time to play with the nice patches, but the latest
kernel update/restricted modules update seems to have made a difference.
A bit early to cry success, but it's been on more or less the last 24
hours without a
48 matches
Mail list logo
