Change MAC address locks up Ubuntu after hibernate

Bug #74170 reported by Sebastian Schauenburg
8
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Fresh boot -> change MAC -> hibernate -> return from hiberation (works). I return from hibernation with my original MAC address, so my manually entered MACaddress is lost. When I try to change my MACaddress once again (after hibernation), my system locks up.
Note: This also happens when X is turned off.

Revision history for this message
kanduvisla (giel-berkers) wrote :

I too have this problem, only my system doesn't lock up.

I change mac address with terminal:

sudo ifconfig eth0 down
sudo ifconfig eth0 hw ether 001122334455
sudo ifconfig eth0 up

Now if I return from hibernate I have to change my Mac Address again using the above commands. My system doesn't lock up, but it's really annoying to do this each time the computer returns from hibernation.

I'm using Ubuntu 7.04.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Not a X bug.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Now that the 7.10 Gutsy Gibbon release of Ubuntu is out, we were wondering if you can still reproduce this issue. Could you please download and try the new version of Ubuntu from http://www.ubuntu.com/getubuntu/download and report back your results. If the issue is still present in the new release, please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux-source-2.6.20:
status: New → Incomplete
Revision history for this message
wolfger (wolfger) wrote :

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!

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.