[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#498593: marked as done (linux-image-2.6.26-1-amd64: No network traffic with intel 4965 N card connecting to N mode network)

Your message dated Mon, 9 Mar 2009 15:10:33 +0100
with message-id <20090309141033.GQ13313@stro.at>
and subject line Re: linux-image-2.6.26-1-amd64: No network traffic with intel 4965 N card connecting to N mode network
has caused the Debian Bug report #498593,
regarding linux-image-2.6.26-1-amd64: No network traffic with intel 4965 N card connecting to N mode network
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
498593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498593
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-4
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hello,

When connecting with the 2.6.25 or 2.6.26 stcok kernel to my home N-mode
network, the DHCP request fails. I suspect somehow network transport is
not possible.
Connecting to my wireless at work (G) I have no problems. Included is a
snapshot form the kern.log and syslog files, please let me know what
other information I should send.
Thanks for your efforts.

Sjoerd


- -- Package-specific info:

- -- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.26-1-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.22     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92g      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

linux-image-2.6.26-1-amd64 recommends no packages.

Versions of packages linux-image-2.6.26-1-amd64 suggests:
ii  grub                          0.97-47    GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.26              <none>     (no description available)

- -- debconf information:
  linux-image-2.6.26-1-amd64/postinst/create-kimage-link-2.6.26-1-amd64: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.26-1-amd64/postinst/kimage-is-a-directory:
  linux-image-2.6.26-1-amd64/postinst/old-initrd-link-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/preinst/bootloader-initrd-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/preinst/initrd-2.6.26-1-amd64:
  linux-image-2.6.26-1-amd64/postinst/old-system-map-link-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/postinst/depmod-error-initrd-2.6.26-1-amd64: false
  linux-image-2.6.26-1-amd64/preinst/overwriting-modules-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/preinst/elilo-initrd-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/postinst/bootloader-error-2.6.26-1-amd64:
  linux-image-2.6.26-1-amd64/preinst/abort-install-2.6.26-1-amd64:
  linux-image-2.6.26-1-amd64/preinst/lilo-initrd-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/postinst/depmod-error-2.6.26-1-amd64: false
  linux-image-2.6.26-1-amd64/prerm/removing-running-kernel-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/prerm/would-invalidate-boot-loader-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/postinst/bootloader-test-error-2.6.26-1-amd64:
  linux-image-2.6.26-1-amd64/preinst/abort-overwrite-2.6.26-1-amd64:
  linux-image-2.6.26-1-amd64/postinst/old-dir-initrd-link-2.6.26-1-amd64: true
  linux-image-2.6.26-1-amd64/preinst/lilo-has-ramdisk:
  linux-image-2.6.26-1-amd64/preinst/failed-to-move-modules-2.6.26-1-amd64:

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkjI914ACgkQHKEdNPY5OOVdtACffaiWGNVPqfPjO8IDCy4cX1FY
QhwAoIatVvBUZyqRxQiR+/zqRDjWvKj5
=Klo+
-----END PGP SIGNATURE-----

Sep  1 20:46:46 laptop kernel: [  129.834816] ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Sep  1 20:46:46 laptop kernel: [  129.834965] PM: Writing back config space on device 0000:0c:00.0 at offset 1 (was 100102, writing 100106)
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:radio
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:assoc
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:RX
Sep  1 20:46:46 laptop kernel: [  130.037299] Registered led device: iwl-phy0:TX
Sep  1 20:46:46 laptop kernel: [  130.059527] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  1 20:46:50 laptop kernel: [  133.645443] wlan0: Initial auth_alg=0
Sep  1 20:46:50 laptop kernel: [  133.645456] wlan0: authenticate with AP 00:1d:7e:ab:ac:66
Sep  1 20:46:50 laptop kernel: [  133.648162] wlan0: RX authentication from 00:1d:7e:ab:ac:66 (alg=0 transaction=2 status=0)
Sep  1 20:46:50 laptop kernel: [  133.648173] wlan0: authenticated
Sep  1 20:46:50 laptop kernel: [  133.648180] wlan0: associate with AP 00:1d:7e:ab:ac:66
Sep  1 20:46:50 laptop kernel: [  133.654179] wlan0: RX AssocResp from 00:1d:7e:ab:ac:66 (capab=0x431 status=0 aid=1)
Sep  1 20:46:50 laptop kernel: [  133.654192] wlan0: associated
Sep  1 20:46:50 laptop kernel: [  133.654222] wlan0: switched to short barker preamble (BSSID=00:1d:7e:ab:ac:66)
Sep  1 20:46:50 laptop kernel: [  133.654309] wlan0 (WE) : Wireless Event too big (366)
Sep  1 20:46:50 laptop kernel: [  133.670073] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  1 20:47:00 laptop kernel: [  143.777419] wlan0: no IPv6 routers present
Sep  1 20:47:37 laptop kernel: [  180.835813] wlan0: deauthenticate(reason=3)
Sep  1 20:47:38 laptop kernel: [  181.877911] wlan0: No STA entry for own AP 00:00:00:00:00:00
Sep  1 20:47:40 laptop kernel: [  184.168941] ACPI: PCI interrupt for device 0000:0c:00.0 disabled


Sep  1 20:49:18 laptop NetworkManager: <info>  User request to enable wireless.
Sep  1 20:49:18 laptop NetworkManager: <info>  SWITCH: no current connection, found better connection 'wlan0'.
Sep  1 20:49:18 laptop NetworkManager: <info>  Will activate connection 'wlan0/sjoerd'.
Sep  1 20:49:18 laptop NetworkManager: <info>  Device wlan0 activation scheduled...
Sep  1 20:49:18 laptop NetworkManager: <info>  Activation (wlan0) started...
Sep  1 20:49:18 laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Sep  1 20:49:18 laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Sep  1 20:49:18 laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Sep  1 20:49:18 laptop NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Sep  1 20:49:18 laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Sep  1 20:49:18 laptop kernel: [  282.399928] ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17
Sep  1 20:49:18 laptop kernel: [  282.399928] PM: Writing back config space on device 0000:0c:00.0 at offset 1 (was 100102, writing 100106)
Sep  1 20:49:18 laptop kernel: [  282.601978] Registered led device: iwl-phy0:radio
Sep  1 20:49:18 laptop kernel: [  282.601978] Registered led device: iwl-phy0:assoc
Sep  1 20:49:18 laptop kernel: [  282.601978] Registered led device: iwl-phy0:RX
Sep  1 20:49:18 laptop kernel: [  282.601978] Registered led device: iwl-phy0:TX
Sep  1 20:49:18 laptop kernel: [  282.623915] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Sep  1 20:49:18 laptop NetworkManager: <info>  Activation (wlan0/wireless): access point 'sjoerd' is encrypted, and a key exists.  No new key needed.
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'INTERFACE_ADD wlan0^I^Iwext^I/var/run/wpa_supplicant^I'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was 'OK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'AP_SCAN 1'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was 'OK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'ADD_NETWORK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was '0'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 ssid 736a6f657264'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was 'OK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 proto WPA2'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was 'OK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was 'OK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'SET_NETWORK 0 psk <key>'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was 'OK'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: sending command 'ENABLE_NETWORK 0'
Sep  1 20:49:19 laptop NetworkManager: <info>  SUP: response was 'OK'
Sep  1 20:49:19 laptop NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Sep  1 20:49:20 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Sep  1 20:49:21 laptop kernel: [  286.204530] wlan0: Initial auth_alg=0
Sep  1 20:49:21 laptop kernel: [  286.204530] wlan0: authenticate with AP 00:1d:7e:ab:ac:66
Sep  1 20:49:21 laptop kernel: [  286.205635] wlan0: RX authentication from 00:1d:7e:ab:ac:66 (alg=0 transaction=2 status=0)
Sep  1 20:49:21 laptop kernel: [  286.205635] wlan0: authenticated
Sep  1 20:49:21 laptop kernel: [  286.205635] wlan0: associate with AP 00:1d:7e:ab:ac:66
Sep  1 20:49:21 laptop kernel: [  286.214691] wlan0: RX AssocResp from 00:1d:7e:ab:ac:66 (capab=0x431 status=0 aid=1)
Sep  1 20:49:21 laptop kernel: [  286.214691] wlan0: associated
Sep  1 20:49:21 laptop kernel: [  286.214691] wlan0: switched to short barker preamble (BSSID=00:1d:7e:ab:ac:66)
Sep  1 20:49:21 laptop kernel: [  286.214691] wlan0 (WE) : Wireless Event too big (366)
Sep  1 20:49:22 laptop kernel: [  286.234067] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Sep  1 20:49:22 laptop NetworkManager: <info>  Supplicant state changed: 1
Sep  1 20:49:22 laptop NetworkManager: <info>  Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to access point 'sjoerd'.
Sep  1 20:49:22 laptop NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Sep  1 20:49:22 laptop NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Sep  1 20:49:23 laptop NetworkManager: <info>  Activation (wlan0) Beginning DHCP transaction.
Sep  1 20:49:23 laptop dhclient: wmaster0: unknown hardware address type 801
Sep  1 20:49:23 laptop NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface wlan0
Sep  1 20:49:23 laptop NetworkManager: <info>  Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Sep  1 20:49:23 laptop avahi-daemon[7082]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::21f:3bff:fe89:529b.
Sep  1 20:49:23 laptop avahi-daemon[7082]: New relevant interface wlan0.IPv6 for mDNS.
Sep  1 20:49:23 laptop avahi-daemon[7082]: Registering new address record for fe80::21f:3bff:fe89:529b on wlan0.*.
Sep  1 20:49:24 laptop NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface wlan0
Sep  1 20:49:24 laptop dhclient: wmaster0: unknown hardware address type 801
Sep  1 20:49:26 laptop NetworkManager: <info>  Old device 'wlan0' activating, won't change.
Sep  1 20:49:28 laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
Sep  1 20:49:32 laptop kernel: [  296.956209] wlan0: no IPv6 routers present
Sep  1 20:49:33 laptop dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
Sep  1 20:49:33 laptop dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
..........

--- End Message ---
--- Begin Message --- 
upstream closed as reporter wasn't responsive.

most probably fixed with latest kernel and firmware.

-- 
maks

--- End Message ---
Reply to: