Happened again today.
[228215.830259] PM: Entering mem sleep
[228215.830326] Suspending console(s) (use no_console_suspend to debug)
[228215.953981] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[228215.954146] sd 0:0:0:0: [sda] Stopping disk
[228216.173167] nouveau [ DRM] suspending display...
OK.
But I still think this is to do with power management in the e1000e
driver, and that a newer version of the e1000e driver needs merging into
the kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
jammy@pk0k4dr:~$ uname -a
Linux pk0k4dr 3.15.0-031500rc5-generic #201405091635 SMP Fri May 9 20:36:31 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
jammy@pk0k4dr:~$ sudo ethtool -i eth0
driver: e1000e
version: 2.3.2-k
firmware-version: 0.13-3
bus-info: :00:19.0
supports-statistics: yes
supports-test
Have updated the BIOS and upgraded to the final trusty. It hasn't
happened yet, but I will make another comment if the bug still exists.
jammy@pk0k4dr:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04 LTS
Release:14.04
Codename: trust
Just for completeness, e1000e driver in this kernel is the same:
jammy@pk0k4dr:~$ sudo ethtool -i eth0
driver: e1000e
version: 2.3.2-k
firmware-version: 0.13-3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
This is still affecting me.
According to the source in 3.12, it still ships with 2.3.2-k of the
intel driver, so I don't think the 3.12 kernel would solve the problem
even if it were stable.
http://lxr.free-
electrons.com/source/drivers/net/ethernet/intel/e1000e/netdev.c?a=m68knommu#L56
--
You
There are no stickers on the laptop, its a Lenovo ThinkPad W530, but
that's already in the collected information.
$ cat /proc/acpi/wakeup
Device S-state Status Sysfs node
LID S4*enabled
SLPB S3*enabled
IGBE S4*enabled pci::00:19.0
EXP3 S4*disabled
Full trace doesn't help - the system never gets to suspended state so
the suspend trace doesn't kick in.
We know which is the buggy driver anyway from dmesg, it is e1000e.
I will get bios 2.56, but then I'd really like to know what the next
steps for this are. So far, your suggestions have not he
jammy@pk0k4dr:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
G5ET96WW (2.56 )
11/27/2013
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250476
Title:
8086:150
Bug reproduced on latest bios, an rmmod of e1000e fixed it again:
[59789.643934] i915 :00:02.0: power state changed by ACPI to D3cold
[59789.876727] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2
[59789.876731] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
[59789.876732
*** This bug is a duplicate of bug 1213035 ***
https://bugs.launchpad.net/bugs/1213035
** This bug has been marked a duplicate of bug 1213035
8086:1502 [Lenovo ThinkPad W530] e1000e module sometimes prevents suspend to
ram
--
You received this bug notification because you are a member of
This is also happening to me on saucy:
Nov 12 12:08:38 pk0k4dr kernel: [33964.643792] PM: Syncing filesystems ... done.
Nov 12 12:08:38 pk0k4dr kernel: [33965.021021] PM: Preparing system for mem
sleep
Nov 12 12:08:42 pk0k4dr kernel: [33965.134863] Freezing user space processes
... (elapsed 0.00
Public bug reported:
Sometimes, usually towards the end of the day, I find my e100e module does not
allow the system to suspend. The following is seen in dmsg:
Nov 12 12:08:38 pk0k4dr kernel: [33964.643792] PM: Syncing filesystems ... done.
Nov 12 12:08:38 pk0k4dr kernel: [33965.021021] PM: Prepa
This is probably a dup of 1213035, but raising a new bug as it was the
advice of penalcvh (now subscribed)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250476
Title:
e1000e module som
I put on 3.12 but the system hung twice. Take a look at the syslog from
12 Nov at about 19:30 to see where lightdm hung.
Its not stable enough to test the bug here, and didn't stay up long
enough to run apport-collect. Should I raise another bug against 3.12,
and if so, what do I need to collect?
I had a look at the e1000e driver and tried a new version of that, so I
installed a new version of that. It suspended fine today (in
circumstances that have previously caused a problem). I'll run like this
for a week before updating the bios. I think its version 2.3.2 in saucy,
not sure why it woul
This hasn't occurred again since upgrading the driver. Just to be
certain I have downgraded it again today and upgraded my bios.
Assuming it is the driver level, what needs to happen to this item?
(Version in saucy:
jammy@pk0k4dr:~$ sudo ethtool -i eth0
driver: e1000e
version: 2.3.2-k
firmware-ve
jammy@pk0k4dr:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
G5ET95WW (2.55 )
09/13/2013
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250476
Title:
8086:150
Happened again today, so definitely not the bios.
[78915.536665] i915 :00:02.0: power state changed by ACPI to D3cold
[78915.769180] pci_pm_suspend(): e1000_suspend+0x0/0x20 [e1000e] returns -2
[78915.769184] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2
[78915.769185] PM: Device 000
Hi Chris,
3.12 was unstable on my machine so I could not test it.
Do you know what version of e1000e ships with 3.12?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1250476
Title:
8086
20 matches
Mail list logo
