From: cwillu <cwillu@cwillu.com>
To: "Sebastian 'gonX' Jensen" <gonx@overclocked.net>
Cc: Francis Galiegue <fgaliegue@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Another checksum error bugreport
Date: Wed, 29 Sep 2010 09:05:42 -0600 [thread overview]
Message-ID: <AANLkTi=BFpyN_sTzzdboCMVoFEmU_pz3T2ezuHMh=5Ok@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=b-BXPzYS2H0H6v1Nvj--Q+0Czb0CLmwSusEYR@mail.gmail.com>
On Wed, Sep 29, 2010 at 8:31 AM, Sebastian 'gonX' Jensen
<gonx@overclocked.net> wrote:
> On 29 September 2010 15:15, cwillu <cwillu@cwillu.com> wrote:
>>>>> Which kernel is that?
>>>> It was one of the 2.6.35 versions from the Ubuntu repository. I'm
>>>> running Ubuntu 10.04 Server.
>>>>
>>>
>>> Since 2.6.32 works, you should report that bug to Ubuntu.
>>
>> Alternatively, retest using ubuntu's mainline kernel ppa
>> (http://kernel.ubuntu.com/~kernel-ppa/mainline/), which doesn't
>> include any ubuntu patches.
>
> I used the mainline ppa when I used 2.6.35. That is where I had the
> issue. Forgive me for saying it was in the repository, but I did not
> realize they were not the same thing.
Well, it is a repository, but that one specifically doesn't include
ubuntu patches, as opposed to whats in the default repositories.
Given that you used the mainline kernels, it's unlikely to be an
ubuntu bug.
next prev parent reply other threads:[~2010-09-29 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 10:48 Another checksum error bugreport Sebastian 'gonX' Jensen
2010-09-29 11:12 ` Francis Galiegue
2010-09-29 11:37 ` Sebastian 'gonX' Jensen
2010-09-29 12:50 ` Francis Galiegue
2010-09-29 13:15 ` cwillu
2010-09-29 14:31 ` Sebastian 'gonX' Jensen
2010-09-29 15:05 ` cwillu [this message]
2010-09-29 17:35 ` Lubos Kolouch
2010-09-29 18:36 ` Sebastian 'gonX' Jensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=BFpyN_sTzzdboCMVoFEmU_pz3T2ezuHMh=5Ok@mail.gmail.com' \
--to=cwillu@cwillu.com \
--cc=fgaliegue@gmail.com \
--cc=gonx@overclocked.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).