This bug was fixed in the package linux - 2.6.32-33.71
---
linux (2.6.32-33.71) lucid-proposed; urgency=low
[Andy Whitcroft]
* Release Tracking Bug
- LP: #813507
[ Upstream Kernel Changes ]
* splice: direct_splice_actor() should not use pos in sd
- LP: #588861
--
This fix has been committed in a kernel to proposed. Updating the
status of the bug to reflect that.
** Changed in: linux (Ubuntu Lucid)
Milestone: ubuntu-10.04.3 = lucid-updates
** Changed in: linux (Ubuntu Lucid)
Status: In Progress = Fix Committed
--
You received this bug
Opening task for Lucid as it seems this issue is now showing there. (as
per dupe Bug #813266)
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: eucalyptus
Reconfirmed on lucid 10.04.3 candidate iso; also proposed kernel fix
which resolved the issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/588861
Title:
pad block corrupted
** Changed in: linux (Ubuntu Lucid)
Assignee: Canonical Kernel Team (canonical-kernel-team) = Andy Whitcroft
(apw)
** Changed in: linux (Ubuntu Lucid)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
This bug was fixed in the package linux - 2.6.35-6.9
---
linux (2.6.35-6.9) maverick; urgency=low
[ Tim Gardner ]
* [Upstream] direct_splice_actor() should not use pos in sd
- LP: #588861
-- Leann Ogasawara leann.ogasaw...@canonical.com Mon, 28 Jun 2010 12:35:49
-0700
Upstream response:
On Sat, Jun 26, 2010 at 4:18 AM, Tim Gardner tim.gard...@canonical.com wrote:
Fat fingered the original email and didn't get the fsdevel address correct.
---
Hi,
I have bisected a strange regression down to this commit that you made. If I
apply
The fix from upstream appears to work. This bug can be closed out once
the fix goes into Maverick and will be in a ppa for alpha-2 testing from
what Tim has said on IRC.
Thanks for all the help Tim!
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
The above referenced patch appears to fix the issue. Pull request sent.
https://lists.ubuntu.com/archives/kernel-team/2010-June/011352.html
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification
This was a kernel regression.
** Changed in: eucalyptus (Ubuntu Maverick)
Importance: High = Undecided
** Changed in: eucalyptus (Ubuntu Maverick)
Status: Confirmed = Invalid
** Changed in: eucalyptus (Ubuntu Maverick)
Milestone: maverick-alpha-2 = None
** Changed in: eucalyptus
The test kernel is actually linux 2.6.35-6.9~maverick1
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Ok, so we've committed the fix to our git repo and will upload the
kernel to the archive late Wed. I suggest the release note recommend
using the kernel provided in the PPA and then update to the 2.6.35-6.9
kernel once it's available.
From #ubuntu-release on FreeNode:
[14:37:47] ogasawara
A Ubuntu-2.6.35-6.7 kernel with cc56f7de7f00d188c7c4da1e9861581853b9e92f
reverted also appears to clear up the error.
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a
sendfile is used by openjdk-6 directly in the following file:
http://pastebin.com/tceugS7r
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team,
We mentioned this bug during the 20100625 release meeting.
The A2 milestone will ship with an affected kernel, but Tim hopes to be
able to nail the issue before the milestone release.
If he does, we'll releasenote that UEC users should dist-upgrade before
registering their first image.
If no
During test of the following kernel it prints the following to dmesg
once for each pass:
ae0f36f0b964caf916c2ffc9f84b28c0f91c18a2-maverick
[ 365.268713] /home/rtg/kern/maverick/kern-64/ubuntu-
maverick/fs/read_write.c:849 should this happen?
--
pad block corrupted error when trying to
0a87a0c1b12f56bd556fd4506041966717c87fb1-maverick
failed as expected
[ 129.980324]
/home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849
816256e0 (null)
[ 178.931445]
/home/rtg/kern/maverick/kern-64/ubuntu-maverick/fs/read_write.c:849
816256e0 (null)
[
Works with 41440ffe21f29bdb985cab76b2d0b06d83e63b19 (required minor
compile fix)
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Works with 23eb3b64b5e44680c867e165fe1cd18e57fba255 (required compile
fix, probably the same one as Tim mentioned earlier).
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a
works with 23eb3b64b5e44680c867e165fe1cd18e57fba255 (required minor
compile fix)
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Fails with 79a56ed0e11c7d924762062a0e2a46b87014498d
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Fails with e33c01972239fee4696679ae5f7d1f340f424999
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Fails with 951c30d135390a108f102b0f6e3cfa6241f2a1aa
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Works with 4f570f995f68ef77aae7e5a441222f59232f2d0e
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
Works with 150e6c67f4bf6ab51e62defc41bd19a2eefe5709
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
works with f21121cde6e617b90cd03ce083652ca543004dc2
r...@zinc:~/linux-2.6$ git bisect good
cc56f7de7f00d188c7c4da1e9861581853b9e92f is first bad commit
commit cc56f7de7f00d188c7c4da1e9861581853b9e92f
Author: Changli Gao xiao...@gmail.com
Date: Wed Nov 4 09:09:52 2009 +0100
sendfile():
He appears to have made another update related to sendfile on May 26.
However, I am not sure if it fixes this problem or that it has been
applied to mainline yet.
http://marc.info/?a=119980668900012r=1w=2
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
** Changed in: linux (Ubuntu Maverick)
Assignee: John Johansen (jjohansen) = Tim Gardner (timg-tpi)
** Changed in: linux (Ubuntu Maverick)
Status: Triaged = In Progress
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
Tracked down to occurring in 2.6.33rc1, so will be checking between that
and 2.6.32-15.5
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team,
Fails with 701791cc3c8fc6dd83f6ec8af7e2541b4a316606
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in
After changing my test to just be registering the images per Dave's
recommendation I was able to come up with this list:
I tested the following kernels, 10 times each:
Passed:
v2.6.32 (10/10)
v2.6.32.15.5-lucid (10/10)
Failed:
v2.6.33 (10/10)
v2.6.34-rc3-maverick (10/10)
v2.6.34-lucid (09/10)
** Tags removed: kernel-candidate
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
** Changed in: linux (Ubuntu Maverick)
Assignee: (unassigned) = John Johansen (jjohansen)
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server
I am attaching a tarball with a stand-alone Java program that exercises
BouncyCastle in the same exact way as Walrus does for image decryption.
Included with the code are a couple of the JARs it needs and three input
files: an encrypted compressed image (originally a ~1-GB Ubuntu image),
the
works:
Linux beagle 2.6.32-020632-generic #020632 SMP Thu Dec 3 10:09:58 UTC 2009
x86_64 GNU/Linux
Linux beagle 2.6.32-0206321505-generic #0206321505 SMP Wed Jun 2 19:09:40 UTC
2010 x86_64 GNU/Linux
bad:
Linux beagle 2.6.33-020633-generic #020633 SMP Thu Feb 25 10:10:03 UTC
2010 x86_64
Hmm I tried 2.6.33 again just to be certain and now it is working on
2.6.33, hmm :-\
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I now can't get it to crash anymore. I am upgrading from maverick alpha
1 to current and then will do further testing.
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a
I tried upgrading to current and now I can't see my nc anymore. :-\
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Chris Cheney-
Please bisect the kernels at:
* http://kernel.ubuntu.com/~kernel-ppa/mainline
and try to identify which kernel introduces this regression.
--
pad block corrupted error when trying to register an image with 2.6.34 kernel
https://bugs.launchpad.net/bugs/588861
You received this bug
** Summary changed:
- Instances block in pending state, and don't start
+ pad block corrupted error when trying to register an image with 2.6.34
kernel
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
pad block corrupted error when trying to register an image with
40 matches
Mail list logo
