ipw2200 gdm hang

[Imre Péntek]

Binary package hint: linux-amd64-generic

when any X sessions used with ipw2200 they together hang the system. My previous experiments with another distro (UHU-Linux dev pre 2.1) suggests that ipw2200+any X session constellation would cause this hang.

Now verified on 8.04 installed today, up-to-date

[Imre Péntek (pentek-imre)]

based on my previous experiments no matter if you use a 64 bit, or a 32 bit kernel.

[Connor Imes (ckimes)]

I tested this on my Dell 600m laptop which uses an IPW2200, but could not duplicate the problem. I successfully launched a second X session by going to tty1 and running
startx -- :1
A new X session appeared where tty8 would be, and both X sessions functioned normally, with internet capability.
Perhaps posting /var/log/Xorg.0.log (or other appropriate X log) might help.

I am using Ubuntu 8.04 Hardy Heron, x86 (i686) with 2.6.24-17-generic kernel.

[Connor Imes (ckimes)]

Imre, can you please check if this is still a problem in Intrepid? Thanks in advance.

[Imre Péntek (pentek-imre)]

I will run a test with the LiveCD. IIRC no matter if you use the proprietrary ati driver, you can even use vesa driver, the hang occassionally occurs. Maybe there is some hardware elements needed to reproduce this bug (ipw2000 wifi + ati mobility radeon (9700))
However when the system hangs, it leaves no opportunity to save the logs: after the reboot I saw no lines implying to the hang.

[Connor Imes (ckimes)]

After you reproduce the crash/freeze, can you please attach the following to this bug report:
   uname -a > uname-a.log
   cat /proc/version_signature > version.log
   dmesg > dmesg.log
   sudo lspci -vvnn > lspci-vvnn.log

as well as /etc/X11/xorg.conf and /var/log/Xorg.0.log and Xorg.0.log.old

Also, please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager. If you have trouble, do not hesitate to ask for more assistance. Hopefully we can get some good information from debugging.

Thanks in advance.

[Connor Imes (ckimes)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!