Please advise me commands that I shall use to provide you the error log
so that I can be assisted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports "eth0: DMA Status error.
Dear All,
I am very new to Linux and absolutely do not know to fix the issues or
communicate the error log as well.
My machine is BenQ 32 Bit and gives similar error. It goes into loop an
does not boot at all.
DMA Status erro, Resetting Chip
CPU stuck for 22 sec.
Then address lines of memory,
** Changed in: linux (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To
** Bug watch added: Debian Bug tracker #678567
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678567
** Also affects: linux (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678567
Importance: Unknown
Status: Unknown
--
You received this bug notification because
** Changed in: linux (Debian)
Status: Unknown = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Tags removed: performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status
This bug was fixed in the package linux - 3.2.0-26.41
---
linux (3.2.0-26.41) precise-proposed; urgency=low
[Luis Henriques]
* Release Tracking Bug
- LP: #1012057
[ Andy Whitcroft ]
* [Config] fix up postinst to ensure we know which error is which
- LP: #1002388
** Branch linked: lp:ubuntu/precise-proposed/linux-armadaxp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To
** Branch linked: lp:ubuntu/precise-proposed/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To
This bug is awaiting verification that the kernel for Precise in
-proposed solves the problem (3.2.0-26.41). Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-precise' to 'verification-done-precise'.
If verification is not
Looks good.
$ dmesg | grep tg3 | cut -c16-
tg3.c:v3.121 (November 2, 2011)
tg3 :03:06.0: PCI INT A - GSI 28 (level, low) - IRQ 28
tg3 :03:06.0: eth0: Tigon3 [partno(349321-001) rev 2100]
(PCIX:133MHz:64-bit) MAC address XX:XX:XX:XX:XX:XX
tg3 :03:06.0: eth0: attached PHY is 5704
Thanks for the update, Adam.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To manage notifications about this
Okay, turns out that ross was just suffering from a botched kernel
upgrade (when they got a console attached to it, they just found it
sitting at a yaboot prompt, oops), and the belief that it was suffering
from this bug was conjecture. Turns out that, while it's a 5704, it's
not the right sort
@Adam, the ppc build completed. I posted the kernel to:
http://people.canonical.com/~jsalisbury/lp1005699/ppc/
It would be great if you could update the bug and confirm if it fixes
the bug.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Paul, there will be new debian-installer builds with SRU kernels
generated in the lead-up to the 12.04.1 release, which would include
this fix if and when it gets in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Joseph, would it be possible to get a test kernel spun up for powerpc
with this patch attached (if that's too much hassle, I can do my own, I
suppose). I think we're running into the same bug on the distro PPC
buildds, and it would be nice to test if this fixes them, so they can
continue to be
** Changed in: linux (Ubuntu Precise)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip.,
this new build works here too.
@Joseph
my comment #21 was in response to #17.
I didn't refresh the page before posting, and saw post #20 (which was posted
one minute before #21) after.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for testing, Mathieu. I'll submit the commit that fixed this bug
for SRU consideration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error.
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
** No longer affects: linux (Ubuntu Oneiric)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
--
You received this bug notification because you are a
Submitted to Ubuntu Kernel Team mailing list for SRU consideration:
https://lists.ubuntu.com/archives/kernel-team/2012-June/020609.html
https://lists.ubuntu.com/archives/kernel-team/2012-June/020610.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
If the SRU is accepted, will this also result in the netboot files on
cdimage.ubuntu.com being regenerated?
The bug makes it difficult for us to install precise on this class of
machine using our existing auto-install infrastructure, since the
installer needs to download the preseed file,
Just upgraded a Hewlett-Packard ProLiant DL385 G1 to precise, and ran
into the same issue.
Is there something I can do to help ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3:
@Mathieu,
You can test the kernels as Joe posts them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To manage
I'll do...
I'm waiting for builds based on 9753dfe19a85e7e45a34a56f4cb2048bb4f50e27
;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting
The following commit may be a fix for this issue:
cf9ecf4b631f649a964fa611f1a5e8874f2a76db - tg3: Fix TSO CAP for 5704 devs w /
ASF enabled
I'll build a precise test kernel with this commit and post it shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I posted a test kernel at:
http://people.canonical.com/~jsalisbury/lp1005699
This test kernel is patched with commit
cf9ecf4b631f649a964fa611f1a5e8874f2a76db
Can you test that kernel and report back if it resolves this bug?
--
You received this bug notification because you are a member of
@Mathieu,
I'll only be building a kernel up to commit
9753dfe19a85e7e45a34a56f4cb2048bb4f50e27 if the patch kernel posted in
comment #22 does not fix the bug. The commit I mention in comment #17
is for a bisect, which will no longer be needed if the bug is fixed by
the kernel in comment #22.
--
Looks like we have a winner, the patched kernel yields a machine with a
functioning NIC.
Linux version 3.2.0-25-generic (root@tangerine) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #40~lp1005699v1 SMP Tue Jun 5 15:16:15
UTC 2012
tg3.c:v3.121 (November 2, 2011)
tg3 :03:06.0: PCI INT A
Thanks great news, Paul. Thanks for all the help testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To
@Paul,
It would be great if we could perform a Reverse Bisect to identify the
commit that fixed this bug. Would it be possible for you to test a few
test kernels?
** Tags added: kernel-da-key performing-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@paul,
Can you test the Precise kernel that is currently in -proposed?
3.2.0-25.40
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting
If you can assist in bisecting, we need to identify which upstream
kernel fixed this issue, then bisect that version. To start, could you
test the following upstream kernels:
v3.2.18: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.18-precise/
v3.3-rc1 http://kernel.ubuntu.com/~kernel-
Both the kernel from -proposed and kernel-ppa's 3.2.18 evince the same
symptoms.
3.3 and 3.3-rc1 from kernel-ppa work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3:
Thanks for testing, Paul. I will bisect between v3.2 final and
v3.3-rc1. I'll post a test kernel shortly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA
Hi Paul,
I posted a test kernel at:
http://people.canonical.com/~jsalisbury/lp1005699
Can you test that kernel and report back if it has the bug or not?
The test kernel is built up to commit:
2ac9d7aaccbd598b5bd19ac40761b723bb675442
--
You received this bug notification because you are a
That kernel works.
Linux version 3.2.0-030200-generic (jsalisbury@tangerine) (gcc version
4.4.3 (Ubuntu 4.4.3-4ubuntu5.1) ) #201206042318 SMP Mon Jun 4 22:21:15
UTC 2012
When I compare tg3.c's dmesg entries between working and non-working
kernels, this jumps out:
-tg3 :03:06.0: eth0:
Thanks for the update, Paul. I'll kick off the next test kernel build
and look deeper into the fact that the failing systems have TSOcap[1].
The next text kernel will be built up to:
9753dfe19a85e7e45a34a56f4cb2048bb4f50e27
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Oneiric)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Precise)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
Title:
tg3: reports eth0: DMA Status error. Resetting chip., fails to work
To manage notifications about
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested
the upstream kernel, please remove the 'needs-upstream-testing' tag(Only
that
The machine boots and gets network with the kernel from v3.4-precise.
(Please let me know if you really did want v3.4-quantal. If so, do I
need to install the matching linux-image-extra package as well?)
pjdc@prat:~$ cat /proc/version
Linux version 3.4.0-030400-generic (apw@gomeisa) (gcc version
** Attachment added: lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005699/+attachment/3167216/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005699
** Attachment added: version.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005699/+attachment/3167217/+files/version.log
** Also affects: linux (Ubuntu Oneiric)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
It's not possible to run apport-collect as the machine has no network
connectivity when the problem is recreated.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu Oneiric)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu Precise)
46 matches
Mail list logo
