[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
Title:
Network broken after resume
To manage notifications about this bug go
Actually the 3.13.11.6 kernel is now published. It would be best to
test that:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.6-trusty/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
Hi Jaap,
I can assist you with the reverse bisect to find the commit that fixes
this. Can you first test the latest upstread 3.13 kernel to see if the
fix already made it to stable? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11.5-trusty/
** Tags added:
Hi Cristopher
As Jeroen might be less available the comming weeks I will try to debug
this
I will test with the latest upstream kernel as soon as I have physical
access to this type of machine
The issue affects 44 Dell 7010ś that werre bought with Ubuntu as
installed OS.
As such it affects at
Upstream kernel seems to fix it, When comming back from resume there is an
added glitch of the screen, but networking works right away
Kernel version tested:
Linux os3-OptiPlex-7010 3.16.0-999-generic #201408080205 SMP Fri Aug 8
06:06:19 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
** Tags added:
Jaap van Ginkel, thank you for performing the requested test. The next
step is to fully reverse commit bisect the kernel in order to identify
the fix commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?
--
You
The first time it takes 60 seconds to log in, and it seems that
networking is broken during that time.
Subsequent logins take only three seconds, and also see almost no
downtime in networking.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Jeroen van der Ham, to further clarify, before the BIOS update, on
resume from first suspend, networking is not working until restarted.
However, after the BIOS update, on resume from first suspend, you would
have to wait ~60 seconds but can ultimately log in with functional
networking. Correct?
Yes, it takes roughly 60 seconds before networking is started.
Hibernation would not be an option for us, the hardware is capable of
resuming, and the subsequent attempts show that it should be able to do
so quickly.
Attached is a log again of login, suspend, and resume cycles.
16:02:27 the
Just a note, I'm not 100% certain that it was completely broken before
the bios update. It could very well be that it had the same 60 second
delay. Then again, that long a delay means broken in my eyes anyway. No
user is going to wait that long to log back in every time his system
suspends.
--
Jeroen van der Ham, since you cannot confirm the issue has changed after
the BIOS update, the scope of this report will change to what is
confirmable, a 60 second delay in logging in after a first suspend.
Hence, could you please test the latest upstream kernel available from the very
top line
We have upgraded the BIOS of the machine:
# sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
A18
04/30/2014
We now find that after a reboot, the first suspend and resume cycle
takes long: after pressing enter in the password screen it takes about
60 seconds to either log that
Jeroen van der Ham, just to clarify is your network broken after either
the first or subsequent resumes?
** Tags removed: bios-outdated-a18
** Tags added: latest-bios-a18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jeroen van der Ham, thank you for reporting this and helping make Ubuntu
better. As per
http://www.dell.com/support/home/us/en/04/product-support/product/optiplex-7010/drivers
an update to your BIOS is available (A18). If you update to this following
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1352379/+attachment/4169576/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
Title:
apport information
** Tags added: apport-collected trusty
** Description changed:
We use Dell Optiplex 7010 machines in our student lab. These machines
are capable of suspending and resuming, so that we don't waste power
during the night. In our lab we also use LDAP authentication for the
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352379
Title:
Network broken after resume
To manage notifications about this bug go to:
18 matches
Mail list logo
