It's alpha software, people should be considered as being aware that
using it might break stuff.
Furthermore, people should be smart enough to read about the known
issues prior to installing it.
Yes a warning and blacklisting the e1000 driver should be done, but
revoking an alpha because of a
Colin: FWIW, I think some kind of warning on cdimage and in the alpha
release notes seems highly prudent (not because of the bogus liability
claims here, but just because it's the good thing to do). I would
suggest:
Due to an unresolved bug in the Linux kernel currently used in Ubuntu 8.10
users
It's alpha software, people should be considered as being aware that
using it might break stuff.
That's absolutely ridiculous. I'm being aware that ubuntu alpha or beta can
break some stuff (like eating my filesystem or deleting my partitions etc). In
fact it already did. However, this is a
Folks,
I suggest to remove the respective Intrepid AlphaX images from the
mirrors ASAP.
Although testing is testing, and everybody knows that there is a risk (I
remember a similar issue with Mandrake Linux and CD-Rom drives) and you,
as a tester, take a known risk, we also have the
** Tags added: regression-potential
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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 the card
to be hosed.
--
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
** Bug watch added: Novell/SUSE Bugzilla #425480
https://bugzilla.novell.com/show_bug.cgi?id=425480
** Also affects: linux (Suse) via
https://bugzilla.novell.com/show_bug.cgi?id=425480
Importance: Unknown
Status: Unknown
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE
** Changed in: linux (Suse)
Status: Unknown = Incomplete
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Bug watch added: Linux Kernel Bug Tracker #11382
http://bugzilla.kernel.org/show_bug.cgi?id=11382
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=11382
Importance: Unknown
Status: Unknown
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at
** Changed in: linux
Status: Unknown = Confirmed
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Bug watch added: Red Hat Bugzilla #459202
https://bugzilla.redhat.com/show_bug.cgi?id=459202
** Also affects: linux (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=459202
Importance: Unknown
Status: Unknown
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE
** Changed in: linux (Fedora)
Status: Unknown = Confirmed
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This is just my humble opinion, but the Alpha CD downloads should be
pulled from the archive. This kernel can partially ruin your hardware,
and unsuspecting users shouldn't be able to merrily download it.
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
Jorge brought this bug to my attention just now; this really needs to be
fixed one way or another for beta, even if that would mean blacklisting
e1000e altogether until this is resolved. Even with as little as I use
the wired ethernet on my laptop, I wouldn't enjoy having to RMA it to
fix it
Jeffrey, we can't afford to do that; we need to be able to test with the
Alpha CDs on the wide variety of hardware not affected by this bug, or
our development schedules for 8.10 will be seriously compromised.
However, I'd be happy to add a warning to the cdimage web pages. Can
anyone suggest some
Colin,
Seems that a warning may be insufficient. I would think most of the
folks testing a pre-release may not know they have an e1000e driver or
affected NIC.
Maybe blacklist e1000e asap and then re-instate e1000e after a fix is
found.
Perhaps have the warning state something about the e1000e
Is Ubuntu willing to risk the liability of distributing software known
to destroy hardware?
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Unless Canonical wants liability for
a) Individual user's destroyed hardware
b) Crippling reputation damages, especially against the 'new to linux' groups
I'd echo the suggestion to pull the liveCD's until this is fixed.
When new linux users discovered permanently corrupted hardware after
trying
We just met a similar issue in the testing for Intrepid Alpha5. In the
beginning, the LAN works fine for x86 system. But after we met a system
hangs up in X86_64 system (caused by gfx) in the same machine,we found
the Ethernet card can't work any more. lspci can't show the correct
Ethernet card
Hi Chris,
Just an update here in case you missed chatter in #kernel on Sept 03,
tim has already began investigating this issue.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Tim Gardner (timg-tpi)
Status: New = Triaged
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE
http://marc.info/?t=12203833703r=1w=2 is another interesting
thread about this, on linux-netdev.
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Removed the regression-2.6.27 tag from this. The 2.6.26 kernel and
2.6.27 kernel have the exact same e1000e driver (one which we downloaded
from Intel's e1000 sf.net project).
Still a serious issue, but I don't want it to be classified as a
regression.
** Tags removed: regression-2.6.27
--
** Tags added: regression-2.6.27
--
[intrepid] 2.6.27 e1000e kernel places Intel gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm wondering if it would be possible for us to patch out the sections
of the driver which write to the NVRAM, assuming Intel are not able to
make suitable changes before 2.6.27 is released, which prevent this from
being possible (e.g. splitting the writing parts out into a separate
module which
25 matches
Mail list logo
