ACPI: If I shutdown or hibernate, the notebook doesn't switch off, but just shows a message: acpi power off called. The bad thing about it: the system gets stuck in a CPU eating loop, creating a lot of heat! That makes it sort of critical on a fan-less notebook. ipw2200: The drivers compile fine, when deleting the header file mentioned in bug #97397 (btw, a solution of this bug should get into portage). The card sort of works, except it does not receive DHCP responses. So it is impossible to get a dhcp'ed connection. Hardware: Dell Latitude X1 Reproducible: Always Steps to Reproduce:
Created attachment 67391 [details] kernel config
Created attachment 67392 [details] emerge info
Created attachment 67394 [details] scanpci -v output
Created attachment 67425 [details] ethereal cap The capture contains some dhcp packets, but there is now response visible. In the logfiles of the dhcpd/router, I can see the requests and logentries for successful leases. dmesg output: # dmesg | grep ipw ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6 ipw2200: Copyright(c) 2003-2004 Intel Corporation ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection # dmesg | grep ieee ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, 1.0.3 ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com> ieee80211_crypt: registered algorithm 'WEP' ieee80211_crypt: registered algorithm 'CCMP' ieee80211_crypt: registered algorithm 'TKIP' ieee1394: Initialized config rom entry `ip1394' ieee1394: Host added: ID:BUS[0-00:1023] GUID[484fc0000c60d430]
Correction: The hanging on ACPI power off only happens on hibernate with swsusp2, not on normal shutdown.
Reverting this patch fixes the problem: http://www.kernel.org/diff/diffview.cgi?file=%2Fpub%2Flinux%2Fkernel%2Fv2.6%2Fsnapshots%2Fpatch-2.6.13-rc7-git3.bz2;z=14
The poweroff problem is fixed in sys-kernel/suspend2-sources-2.6.13-r1. The ipw2200 problem is known already and being investigated. Closing as INVALID since you can only report one issue per bug report - otherwise it's rather impossible for us to track them.
