Arthur Fragoso, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349000/comments/17
regarding you no longer have the original hardware this is reproducible
with. For future reference you can manage the status of your own bugs by
The problem stopped happening, so I contacted the network manager and he
told me that they changed many equipment that was damaged after a
lightning in a thunderstorm night, he also told me that it probably was
some rule in the firewall of the old router.
Thanks for all the help, and I'm sorry
Arthur Fragoso, you may want to update your test with the latest
mainline kernel 3.19-rc2, re-send the e-mail following the format noted
in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349000/comments/14
(November's e-mail did not), and CC both the regression submitter and
the
I wrote to the netdev mailing list in november (
http://www.spinics.net/lists/netdev/msg305646.html ) and I got no reply,
so I'm attaching the result of a test another test that I did that could
make it more easy to find the problem.
This test shows the wireshark output of how a git push behaves
Attached BISECT_LOG
** Attachment added: BISECT_LOG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349000/+attachment/4265786/+files/BISECT_LOG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did the bisection and the results are:
c0efc887dcadbdbfe171f028acfab9c7c00e9dde is good.
97bab73f987e2781129cd6f4b6379bf44d808cc6 - gives me a kernel panic when
trying to do an upload of data.
7b34ca2ac7063f4ebf07f85fd75253ed84d5c648 - same problem, kernel panic
when trying to do an upload
Almost forgot to say,
to be able to compile those commits, I had to apply this patch:
wget
https://crewrktablets.arctablet.com:8081/opendev/kernel_rockchip/commit/33d5e332b9c5ce0bf3bfd44ca2127d1773b3f2ad.diff
--no-check-certificate
patch -p1 33d5e332b9c5ce0bf3bfd44ca2127d1773b3f2ad.diff
--
Arthur Fragoso, it is best to both send an e-mail to the maintainer
mailing list, as well as CC the person who made the commit. Hence, the
issue you are reporting is an upstream one. Could you please report this
problem to the appropriate mailing list (netdev) by following the
instructions
** Tags removed: kernel-bug-exists-upstream-3.16-rc7
** Tags added: kernel-bug-exists-upstream-3.18-rc5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349000
Title:
Networking - Destination
Sorry for being so late, my disk was full and I procrastinated to get
the about 10 GB for compiling the kernel.
I started doing the bisection:
arthur@XPS:/media/arthur/Storage/kernel/ubuntu-raring$ git bisect start
Ubuntu-3.6.0-0.1 Ubuntu-3.5.0-5.5
Bisecting: a merge base must be tested
Sorry, I just read in the docs, `git bisect --help`
I can skip some versions, I will try `git reset --hard HEAD~50`
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349000
Title:
Networking -
[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/1349000
Arthur Fragoso, the next step is to fully commit bisect the kernel in
order to identify the offending commit. Could you please do this
following https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Tags removed: kernel-bug-exists-upstream-3.16-rc6
** Tags added: needs-bisect
** Changed in: linux
I tested on 3.16-rc6-utopic and the problem was still there.
I also downloaded an old kernel, the v3.4-rc6-precise to test if it was
working in a past kernel, and it was working without problems.
I'm going to test other kernel versions to see in what version the bug
was introduced.
** Tags
I did more tests, and here is the result:
The version v3.5.7.33-quantal and older versions works without problems.
The version v3.6-quantal and newer has the problem/bug.
** Tags added: kernel-bug-exists-upstream-3.16-rc7
--
You received this bug notification because you are a member of Ubuntu
Arthur Fragoso, thank you for reporting this and helping make Ubuntu better.
Could you please test the latest upstream kernel available from the very top
line at the top of the page (not the daily folder) following
https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional
wireshark output
** Attachment added: wireshark output
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349000/+attachment/4163526/+files/wireshark-retransmission-small.txt
** Description changed:
A few years ago, I was using Fedora 16 and I was unable to do any HTTP POST
at the
17 matches
Mail list logo
