From: Robert Hancock <hancockrwd@gmail.com>
To: bugs+linux-ide@grueslayer.com
Cc: linux-ide@vger.kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pata_pdc202xx_old regression?
Date: Sat, 02 Jan 2010 20:58:27 -0600 [thread overview]
Message-ID: <4B4007D3.3090405@gmail.com> (raw)
In-Reply-To: <19263.64689.654744.283071@jabber.grueslayer.com>
On 01/02/2010 08:10 PM, David A. Sinck wrote:
>
>
>> SMTP quoth Robert Hancock on 1/2/2010 15:15 as having spake thusly:
>>
>> On 01/02/2010 02:21 PM, David A Sinck wrote:
>>>
>>> Greetings& Happy New Year!
>>>
>>> I believe I've come across one of two things:
>>>
>>> a) a regression in pata_pdc202xx_old
>>> b) a clueless end user wrt the list :-)
>>>
>>> The short version: running Ubuntu's Jaunty release (2.6.28-17-generic
>>> #58-Ubuntu i686) I can cleanly access the disks hanging off of an
>>> onboard Promise 20265; attempting to upgrade to Ubuntu Karmic
>>> (presumptively 2.6.31.16.29) has numerious problems reading these same
>>> drives, including:
>>>
>>> e2label: No such file or directory while trying to open /dev/sda1
>>> Couldn't find a valid filesystem superblock.
>>>
>>> I've documented as much as I can think of that's relevant here:
>>>
>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/489685
>>>
>>> I'm willing to run tests + update the bug with further information
>>> ... if I knew what would be useful.
>>>
>>> It might even be solved upstream from the release Karmic's using?
>>
>> That dmesg output is from the working setup, correct? Can you get any
>> output from the non-working one?
>
> I've uploaded /var/log/ { kern.log | syslog | dmesg } from a running
> Karmic live cd (post release); I snapshotted the whole directory but
> limited myself to those files figuring they'd be most likely to be the
> helpful ones.
>
> Let me know what else I can do; thanks for the timely response!
Well, it looks like all the drives got detected OK. I'm not sure what
the device-mapper errors are though, and I'm not sure why you wouldn't
be getting any device nodes showing up for them.. CCing linux-kernel.
Jan 3 01:43:51 ubuntu kernel: [ 4.978003] device-mapper: table:
252:0: zero-length target
Jan 3 01:43:51 ubuntu kernel: [ 4.978009] device-mapper: ioctl:
error adding target to table
Jan 3 01:43:51 ubuntu kernel: [ 4.996613] device-mapper: table:
252:0: zero-length target
Jan 3 01:43:51 ubuntu kernel: [ 4.996620] device-mapper: ioctl:
error adding target to table
Jan 3 01:43:51 ubuntu kernel: [ 5.372214] device-mapper: table:
252:0: zero-length target
Jan 3 01:43:51 ubuntu kernel: [ 5.372221] device-mapper: ioctl:
error adding target to table
Jan 3 01:43:51 ubuntu kernel: [ 5.680349] device-mapper: table:
252:0: zero-length target
prev parent reply other threads:[~2010-01-03 2:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 20:21 pata_pdc202xx_old regression? David A Sinck
2010-01-02 21:15 ` Robert Hancock
2010-01-03 2:10 ` David A. Sinck
2010-01-03 2:58 ` Robert Hancock [this message]
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=4B4007D3.3090405@gmail.com \
--to=hancockrwd@gmail.com \
--cc=bugs+linux-ide@grueslayer.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).