on 09/11/2010 20:14 Alexander Motin said the following:
> Hmm. There was not much changes in ATA last time and I can't expect what
> of them could affect PATA. Probe code wasn't changed for long time.
>
> This check was actually added after some ata(4) bug found two years ago.
> So I am not sure y
Andriy Gapon wrote:
> on 09/11/2010 19:04 Alexander Motin said the following:
>> Andriy Gapon wrote:
>>> Since one of the recent updates (not sure which revision though) I started
>>> to get
>>> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
>>> message
>>> every other b
on 09/11/2010 19:04 Alexander Motin said the following:
> Andriy Gapon wrote:
>> Since one of the recent updates (not sure which revision though) I started
>> to get
>> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
>> message
>> every other boot, i.e. not always.
>>
>>
Andriy Gapon wrote:
> Since one of the recent updates (not sure which revision though) I started to
> get
> "Unable to set devclass" messages in boot dmesg. I'd say that I see the
> message
> every other boot, i.e. not always.
>
> I added some more debug code there and here's a tack trace:
>
>
Since one of the recent updates (not sure which revision though) I started to
get
"Unable to set devclass" messages in boot dmesg. I'd say that I see the message
every other boot, i.e. not always.
I added some more debug code there and here's a tack trace:
driver bug: Unable to set devclass (c
