I don't really remember doing that, but it could be. Sorry for being
annoying :)
However, I still think it would be a good idea to not make libata choke
on unknown parameters.
Thanks
--
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486
--
ubuntu-bugs mailing list
ubuntu-bug
This file doesn't appear to exist with Ubuntu. Maybe you added it some
time ago?
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Rejected
--
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
Hi Cristian,
Right now, I don't have access to the computer where I originally had
the problem in. I will do as you suggest when I can, although I'm afraid
that the kernel version has been updated since, so I'm not sure that it
will be of much use.
However, I could reproduce the problem this way:
Thanks for taking the time to report this bug. Unfortunately we can't
fix it, because your description didn't include enough information.
Please include the following additional information, if you have not already
done so (please pay attention to lspci's additional options), as required by
the
** Changed in: linux-meta (Ubuntu)
Sourcepackagename: linux-meta => linux-source-2.6.20
--
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Sorry, forgot to report. Using kernel 2.6.20-5-generic.
--
[feisty] very nasty bug with libata
https://launchpad.net/bugs/82486
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
