Hi everyone,
I'm currently testing out the git repository of the linux kernel.
Unfortunately my system (Gentoo) always crashes shortly after the
Networkmanager service is started. Not starting the service or using the
radio killswitch is the only possibility to get the system up. I already
tested versions 0.8.4 and 0.9rc3 of Networkmanager resulting in the same
error. This behavior came up with using the git-Version of the kernel
whereas it was working in the 3.0.x releases.
The really bad news is that I cannot send a detailed trace with this
message as the relevant parts of the log message are gone due the
following hardreset. But luckily once a trace remained, which is from
the older rc1 but still describing the same problem. Unfortunately no
debugging symbols were active when this trace was generated.
I've also attached some information about my system.
I hope you can help me out. Thanks.
Best regards,
Alexander Diewald
Hi Alex,
I see that there's a null pointer dereference in one of the iwlagn functions.
Can you point me to the kernel tree you're using?
Thanks,
Meenakshi
>-----Original Message-----
>From: [email protected] [mailto:linux-wireless-
>[email protected]] On Behalf Of Guy, Wey-Yi W
>Sent: Wednesday, August 24, 2011 7:09 AM
>To: Alexander Diewald; [email protected]
>Cc: Guy, Wey-Yi W
>Subject: RE: [iwlagn] System crash on dell e6420 using iwlagn from kernel-git
>
>Hi Alex,
>
>I am on vacation now and I will asking the right people in the team to look into
>this problem and get back to you.
>
>Thanks
>Wey
>
>-----Original Message-----
>From: [email protected] [mailto:linux-wireless-
>[email protected]] On Behalf Of Alexander Diewald
>Sent: Wednesday, August 24, 2011 5:42 AM
>To: [email protected]
>Subject: [iwlagn] System crash on dell e6420 using iwlagn from kernel-git
>
>Hi everyone,
>
>I'm currently testing out the git repository of the linux kernel.
>Unfortunately my system (Gentoo) always crashes shortly after the
>Networkmanager service is started. Not starting the service or using the radio
>killswitch is the only possibility to get the system up. I already tested versions
>0.8.4 and 0.9rc3 of Networkmanager resulting in the same error. This behavior
>came up with using the git-Version of the kernel whereas it was working in
>the 3.0.x releases.
>The really bad news is that I cannot send a detailed trace with this message as
>the relevant parts of the log message are gone due the following hardreset.
>But luckily once a trace remained, which is from the older rc1 but still
>describing the same problem. Unfortunately no debugging symbols were
>active when this trace was generated.
>I've also attached some information about my system.
>I hope you can help me out. Thanks.
>
>Best regards,
>Alexander Diewald
>--
>To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the
>body of a message to [email protected] More majordomo info at
>http://vger.kernel.org/majordomo-info.html
Hi Alex,
I am on vacation now and I will asking the right people in the team to look into this problem and get back to you.
Thanks
Wey
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Alexander Diewald
Sent: Wednesday, August 24, 2011 5:42 AM
To: [email protected]
Subject: [iwlagn] System crash on dell e6420 using iwlagn from kernel-git
Hi everyone,
I'm currently testing out the git repository of the linux kernel.
Unfortunately my system (Gentoo) always crashes shortly after the Networkmanager service is started. Not starting the service or using the radio killswitch is the only possibility to get the system up. I already tested versions 0.8.4 and 0.9rc3 of Networkmanager resulting in the same error. This behavior came up with using the git-Version of the kernel whereas it was working in the 3.0.x releases.
The really bad news is that I cannot send a detailed trace with this message as the relevant parts of the log message are gone due the following hardreset. But luckily once a trace remained, which is from the older rc1 but still describing the same problem. Unfortunately no debugging symbols were active when this trace was generated.
I've also attached some information about my system.
I hope you can help me out. Thanks.
Best regards,
Alexander Diewald