[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/1052861
Jan Ceuleers, thank you for reporting this and helping make Ubuntu better.
Lucid reached EOL on May 9, 2013.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We were wondering if this is still an issue in a supported release? If
so, could you
The released 2.6.32-43-generic (with the corresponding compat-wireless
package) has now been running for nearly 39 hours, so I'm going to go
ahead and remove the -43 compat-wireless package and reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The released 2.6.32-43-generic kernel crashed after about 5 hours uptime
while the corresponding compat-wireless package was not also installed.
So I think that this validates the hypothesis that the determining
factor is the presence of the compat-wireless package (i.e. whether or
not newer ath9k
I have now purged all -43 and -44 kernels (i.e. the released -43 kernel
and all test kernels v1 through v5), then reinstalled the released -43
kernel, and also pulled in the compat-wireless package for -43. After
rebooting the machine has stayed up overnight.
Luis and I both had a theory about
After looking into /var/log/apt/ logs (provided privately), it was
verified that the initial installation of kernel linux-
image-2.6.32-43-generic had failed, and this may be causing troubles. I
suggested Jan to purge this kernel (and any other kernel installed after
this failure) and try again
I can now explain one class of differences between the modules loaded
under -42 versus -44. I am using the compat-wireless package, a version
of which does not yet exist for the -44 kernel (or at least: I hadn't
installed it). The two ath9k-related modules which are not being loaded
under -44 but
Hi Jan, the only reason I can think of to have those FS-related modules
load is that you installed a kernel, i.e., running dpkg -i kernel-
image.deb will eventually cause the load of all these modules. If you
reboot again, the modules shouldn't be automatically loaded again.
--
You received
I ran the lsmod commands just after a fresh reboot, so this doesn't seem
to be it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052861
Title:
After upgrade to new kernel version, machine crashes
I guess I need to wait for a compat-wireless package to become available
that corresponds with the -44 ABI. Although I can start by installing
the -43 compat-wireless package and test that with the v1-v3 kernels you
previously built for me (just to see whether the results are any
different from
Ok, I've been re-reading all the comments in the bug report and realised
I may have made a wrong assumption:
Comment #11 suggests the tested kernel was a GOOD one, while comment #12
states the opposite. My comment #13 seems to be made after reading
comment #11 -- so, I may have missed comment
Ok, kernel built and uploaded here:
http://people.canonical.com/~henrix/lp1052861/v5/
If you have a chance, please give it a try and let me know if it made
any difference. As I referred in previous comment, this is just the
plain Lucid kernel with commit e1a07a02513462dd865e06c9dcc323eee226fba0
I'm really sorry, but this kernel (v5) is BAD.
But I noticed that for some reason a different set of modules is being
loaded. I have no idea why. I attach a file that shows the differences
between the first column of lsmod's sorted output under each kernel (-42
and -44 v5). Why are a lot more
A new Lucid kernel is available in the -proposed pocket and will soon be
released. Could you please try it to check whether it fixes your
problem? See https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you!
--
You received this bug
Assuming I've managed to install the correct package from -proposed:
Linux skr03 2.6.32-44-generic #98-Ubuntu SMP Mon Sep 24 17:32:45 UTC
2012 i586 GNU/Linux
the new kernel is BAD (it crashed after an hour and 10mins)
--
You received this bug notification because you are a member of Ubuntu
By the way, I just noticed that I should have mentioned the presence in
the box of a wireless adapter as well. Since the box is a broadband
router it also acts as a wireless access point, using an ath9k card. No
offload options (TSO, GSO) are active on this interface.
--
You received this bug
I can confirm that the box is stable when running -42.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052861
Title:
After upgrade to new kernel version, machine crashes after a few hours
of
v4 seems to behave similarly to v3: it also crashed after many hours,
i.e. after a longer period than the released -43 package and the v1 and
v2 packages did. But it still crashed.
Once again I'm back on -42. I think I now need to stay on this package
for a couple of days just to make sure that
v3 has stayed up overnight, which leads me to suspect that it is GOOD.
I can't be categorical about this you understand: if it freezes it is
certain to be bad, but if it doesn't it might merely not yet have
crashed. So I'll leave it running and report back tomorrow.
--
You received this bug
Right. I'm glad I qualified my previous statement. It crashed after
about 20 hours, which is much longer than than it took v1 and v2 to
crash before. Could be coincidence, who knows. Going back to the -42.96
package now.
--
You received this bug notification because you are a member of Ubuntu
Thank you for taking your time testing all these kernels. Definitely
something went wrong in this kernel bisection. I may have messed up
with the bisect operation, because the tests results ended up pointing
to commit:
23f18f3 eCryptfs: Initialize empty lower files when opening them
And I'm
I am indeed not using ecryptfs.
I am using GSO (generic segmentation offload) on one of the ethernet
interfaces (the one that faces the LAN). Whereas the box has four
ethernet interfaces I'm using only two. One faces the LAN (eth3), the
other faces the VDSL modem (eth2), across which I set up a
The v2 kernel is also BAD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052861
Title:
After upgrade to new kernel version, machine crashes after a few hours
of uptime
To manage notifications
By the way: I may be able to test a few more kernels than one per day
over the weekend. If this is a practical proposition, could you prepare
three or four packages in one go? Please only do so if it's not too much
trouble.
--
You received this bug notification because you are a member of Ubuntu
Great, I've just uploaded another kernel, which should tell us finally
which commit has caused the regression. You can download it in the
usual place:
http://people.canonical.com/~henrix/lp1052861/v3/i386/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks for the input. I've built the next kernel in this bisect session
and uploaded it here:
http://people.canonical.com/~henrix/lp1052861/v2/i386/
Same request: just let me know whether this is a good or a bad kernel.
--
You received this bug notification because you are a member of Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052861
Title:
After upgrade to new kernel version, machine crashes after a few hours
of uptime
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
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/1052861
Title:
After upgrade to new kernel version, machine crashes after a few hours
of
Hi,
can you confirm that the previous Lucid kernel version (2.6.32-42.96)
was working for you? If this is true, and you're available to assist in
a kernel bisect, I'll build a few test kernels (should be 2 or 3 at
most) for you to test so that we can identify the commit that introduced
this
** Changed in: linux (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052861
Title:
After upgrade to new kernel version, machine crashes after a few hours
I am the original bug reporter.
I can confirm that reverting to the previous kernel package (linux-
image-2.6.32-42-generic, version 2.6.32-42.96) returns the machine to
stability.
This is my broadband router, and my wife and I work from home a lot. I
can test kernels for you, but only overnight
Great, thanks a lot for your help. So, I've uploaded the 1st kernel
here:
http://people.canonical.com/~henrix/lp1052861/v1/i386/
This kernel contains the pae kernel up to commit
7db137a69f19021fe7c7614cac3883cc16992b0c.
Please let me know if this is a good (stable) or bad (unstable) kernel.
Looking at the security notice that describes this kernel update I see
that one of the changes is to do with TCP segmentation offload. Some
additional information therefore.
This machine has four Ethernet interfaces:
root@skr03:~# lspci | grep Ethernet
00:06.0 Ethernet controller: VIA
The v1 kernel you gave me to test is BAD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1052861
Title:
After upgrade to new kernel version, machine crashes after a few hours
of uptime
To manage
34 matches
Mail list logo
