@Po-Hsu Lin My question is that whether the linux driver is related with the issue? If you don't install linux, and just power it on (not boot to linux) and power it off, does the mac address also get an invalid address? If yes, it seems that it's the hardware issue. Please help me to test. Thanks a lot!
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1358704 Title: Atheros AR8161[1969:1091] and AR8162 [1969:1090] mac address would change after powered off for a while Status in HWE Next Project: Confirmed Status in linux-lts-trusty package in Ubuntu: New Bug description: CID: 201202-10508 CID: 201202-10511 CID: 201202-10527 The MAC address would change after you power off the system for a while (few days) 201202-10508 and 201202-10511 equipped with AR8162 [1969:1090] 201202-10527 equipped with AR8161[1969:1091] I found this issue when trying to install 12.04.5 via PXE network installation. The MAC address changing pattern is interesting, there is a common address they will change into - 00:13:74:00:00:00 This looks like a HW issue, but I'm not very confident about it. Maybe not a big deal, but this issue would prevent these system from being selected into our SRU pool, the worse scenario is that this system is attached to a MAC-address-registered network (my dormitory network back into university require users to register they MAC address) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Aug 19 06:00:11 2014 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140807.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1358704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
