Here is a better link that might allow anyone who wants to review the
thread or use a local email client to reply
https://lore.kernel.org/lkml/92785039-0941-4626-610b-
f4e3d9613...@ristioja.ee/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
this is NOT a duplicate of #1015297. The issue likely still exists
(although I am unable to test anymore as my laptop has been replaced)
** This bug is no longer a duplicate of bug 1015297
Screen partially darkened after suspend and resume in Xubuntu
--
You received this bug notification bec
Is there anything I can do to help fix this? Willing to provide any
data and debug, including remote access if that would help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921321
Title:
nouveau:
Hi Emil, thanks. Behavior is unchanged with new kernels. I've tested
through nouveau commit:
commit 9a0a03b43176ee676693232f2afe92b83b15233e
Author: Roy Spliet
Date: Tue Feb 7 00:29:06 2012 +0100
drm/nouveau/pm: several fixes for nvc0 memory timings
and 3.3.0-rc2 (actually the above is on
** Bug watch added: freedesktop.org Bugzilla #39550
https://bugs.freedesktop.org/show_bug.cgi?id=39550
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=39550
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a membe
At the time the report was generated I had tried to boot to latest
upstream kernel to test nouveau (which is broken) but this issue is
against stock Ubuntu kernel 3.0.0-14
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Public bug reported:
Nouveau works fine with brightness controls working fine after initial
boot, but I do S3 suspend, and then resume via power button, and
brightness controls don't work at all, and backlight is on, but set at
extremely low level.
hardware is Quadro 770M on HP 8530w laptop
/sys
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/921321
Title:
nouveau: dark screen after suspend/resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-
same problem in 11.10 (oneiric)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/767066
Title:
natty distcc /usr/bin/python: can't open file
'/usr/bin/include_server/include_server.py': [Errno 2] No
this bug is not a catchall for all e1000e issues, the original issue
this bug was filed against is fixed and will be highly unlikely to
reoccur. If you're having e1000e issues please file a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
probably the same bug as
http://bugzilla.kernel.org/show_bug.cgi?id=13914
--
karmic installer fails to detect Intel 82567 network card
https://bugs.launchpad.net/bugs/404264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I suspect that this patch will fix the issue, seems that since they were
able to boot the old OS and dump the eeprom that the eeprom is not
actually corrupt.
http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commitdiff;h=148675a7b2061b5a5eb194530b7c4d8de1f2887e;hp=373a88d78be540c1331ea
So in the interests of adding some closure to this bug. The issue turns out to
have never been the e1000e driver's fault. The fault lies with the
CONFIG_DYNAMIC_FTRACE option. So specifically when the FTRACE code was
enabled, it was doing a locked cmpxchg instruction on memory that had been
prev
*** This bug is a duplicate of bug 263555 ***
https://bugs.launchpad.net/bugs/263555
The e1000e device driver was disabled until resolution of the NVM
corruption mentioned in the other bug.
--
Network card not detected with the 2.6.27-4 kernel
https://bugs.launchpad.net/bugs/276021
You recei
Tom Jaeger wrote:
> I just checked my syslog and interestingly, the first time I got the
> "e1000e: probe of :00:19.0 failed with error -5" error was during
> wake-up from standby. The syslog doesn't indicate an X server crash
> (or restart) between booting the computer and suspending it. I'm
2.6.26 as far as we know is uneffected. The problem reports all started
with 2.6.27. So in short I think you have nothing to worry about.
--
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification
On Wed, 24 Sep 2008, Leonardo Silva Amaral wrote:
> Ive created a VERY stupid script to find if the system have a NIC
> vulnerable to the faillure (Used the list from
> http://episteme.arstechnica.com/eve/forums/a/tpc/f/96509133/m/302000834931?r=202000364931#202000364931)
>
> Here is: http://paste
okay, lets just use the data we *have* now. What we know is that some
users have reported a corrupt NVM. Intel networking does not have a
current reproduction but is *fully engaged* on trying to solve this
problem. We have only had reports on 82566 and 82567 based machines, no
others. Trying to
I strongly recommend if you are going to test for this bug or haven't seen it
yet on your ich8/9 system, that you RIGHT NOW, do ethtool -e ethX >
savemyeep.txt
Having a saved copy of your eeprom means we can help you write it back to your
system.
--
[intrepid] 2.6.27 e1000e driver places Intel I
John Dong wrote:
> Shall we pull in e1000e-prevent-corruption-of-eeprom-nvm.patch? It
> seems from the discussion that it isn't a 100% fix (other methods of
> reaching mmio'ed EEPROM probably exist) but should at least eliminate
> this disaster scenario of just booting up the distribution causing
>
20 matches
Mail list logo
