Christopher M. Penalver,
I still don't understand why this bug should be marked invalid.
Martin Gamwell Dawids, marking this bug Invalid is well within Ubuntu
> Bug Control and Ubuntu Bug Squad triage procedures as noted in
>
> https://wiki.ubuntu.com/
In comment 19 I said that this was fixed by an _upgrade_ from 10.04LTS
to 12.04LTS. It was _not_ fixed by an update of 10.04LTS and the bug is
still existing in 10.04LTS.
On https://wiki.ubuntu.com/Bugs/ you can read what Invalid means:
* This status should be used when the bug report does not con
Christopher, I personally do not need a backport to a release prior to
Precise. However, I do not understand why this means the bug is
"Invalid". I have documented a bug in Ubuntu 10.04LTS which is supported
until 2013-04 (Client) and 2015-04 (Server). Therefore, I would have
expected "Confirmed" o
Thank you.
For your information, I have now upgraded the machine to 12.04.
$ lsb_release -rd
Description:Ubuntu 12.04.2 LTS
Release:12.04
$ uname -srv
Linux 3.2.0-37-generic #58-Ubuntu SMP Thu Jan 24 15:28:57 UTC 2013
I have tested the problem with this kernel and cannot reproduce w
Hello Christopher,
I have now finished the reverse-kernel-bisect on this bug. Could you please
reopen it (Expired->Complete)?
Best regards,
Martin Gamwell Dawids
2012/10/17 Christopher M. Penalver
> Martin Gamwell Dawids, regarding your comments
> https://bugs.launchpad.net/ubunt
As previously written, a single time where I tested with 2.6.32-59-lucid
I saw a kernel backtrace on screen. However, I couldn't make the crash
kernel install with this kernel and Netconsole was unfortunately
uninstalled during that test, so I did not capture the backtrace and
(since I thought it w
Hi Christopher,
I finally got this tested:
* v2.6.32.60.26-lucid -- vmlinuz-2.6.32-02063260-generic: Freeze
* v2.6.32 -- vmlinuz-2.6.32-020632-generic: OK
* v2.6.33.1-lucid -- vmlinuz-2.6.33-02063301-generic: Ok
** Tags added: kernel-fixed-upstream-2.6.32
--
You received this bug notification
Christopher, sorry but I might have misunderstood the ordering. I
thought the ordering was this:
v2.6.32/
v2.6.32.60.26-lucid/
v2.6.33/
v2.6.33.1-lucid/
v2.6.33.2-lucid/
v2.6.33.3-lucid/
v2.6.33.4-lucid/
v2.6.33.5-lucid/
v2.6.33.6-maverick/
v2.6.33.7-maverick/
v2.6.33.20-maverick/
(i.e. that 2.6.
Christopher, I forgot to test with the very first 2.6.33 kernel (as it
was further down the list). So now I have performed that test as well,
and 2.6.33 also works. Trying multiple times, I cannot freeze the
system.
My updated results are:
* 2.6.32-44 -- vmlinuz-2.6.32-44-generic (original kernel)
Christopher, in order to make sure this was not an Ubuntu patch thing, I
started out testing with the kernel closest to my current kernel:
* v2.6.32.59-lucid
According the the mainline kernel mapping it should correspond to the
Lucid/10.04 2.6.32-44-generic #98 kernel.
Testing with the v2.6.32.5
** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.6.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066496
Title:
fit-pc2 on Ubuntu 10.04 hangs/f
Sorry, I forgot to mention, that the problem had disappeared when using
the 3.6.2 kernel. The machine no longer freezes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066496
Title:
fit-pc2 on Ubunt
Ok, now I have tested with the latest kernel: 3.6.2
$ uname -svr
Linux 3.6.2-030602-generic #201210121823 SMP Fri Oct 12 22:31:22 UTC 2012
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.4 LTS
Release:10.04
Codename: lucid
$
Do you
Christopher, thank you for the pointer. For some reason I thought I
should test against a mainline kernel that matched my current kernel,
but I will test using the one you suggest above.
> Could you please capture the oops following
> https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Captur
Christopher, I have problems understanding which upstream kernel I
should test. You write:
> As well, could you please test the latest upstream kernel available
> following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will
> allow additional upstream developers to examine the issue. Please
>
I would like to try to test using the latest upstream kernel, but I am
unsure which to pick.
>From this mapping table:
- http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html
it looks like the one I should choose is this: 2.6.32.59+drm33.24
However, in this location
- http://kernel
Public bug reported:
I am running Ubuntu 10.04.4 LTS
$ lsb_release -rd
Description: Ubuntu 10.04.4 LTS
Release: 10.04
The machine is a fit-pc2 (http://www.fit-pc.com/web/fit-pc/fit-
pc2-specifications/).
My kernel is:
$ uname -srv
Linux 2.6.32-44-generic #98-Ubuntu SMP Mon Sep
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894188
Title:
Unstable network connection when moving large data sets
To manage notif
I am experiencing the exact same problem with Ubuntu 10.04 and fit-pc2.
If I saturate the network bandwidth -- e.g. by copying files using rsync
-- then after a while (10-20 seconds) the network connection to the
machine is lost.
I just reproduced it and after 5 minutes the network interface has n
19 matches
Mail list logo
