[PlanetCCRMA] rt kernels, ho, ho, ho!
nando at ccrma.Stanford.EDU
Mon Jan 3 19:52:57 PST 2011
On 01/03/2011 07:44 PM, Fernando Lopez-Lezcano wrote:
> On 01/03/2011 05:45 PM, Donald Steven wrote:
>> Alas, Paul's solution to blacklist b43 didn't work for me.
>> Using the stock kernel, towards the end of dmesg I get:
>> [ 2.202021] ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> [ 2.202095] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
>> [ 2.205252] ata9.00: ATA-7: Maxtor 7Y250M0, YAR511W0, max UDMA/100
>> [ 2.205254] ata9.00: 488397168 sectors, multi 16: LBA48
>> [ 2.211148] ata9.00: configured for UDMA/100
>> [ 2.211342] ata7.00: ATA-8: WDC WD3200AAKS-00V1A0, 05.01D05, max UDMA/133
>> [ 2.211345] ata7.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
>> [ 2.218071] ata7.00: configured for UDMA/133
>> With the CCRMA kernel, it hangs at this point and goes around and arounf
>> two or three ata#s (like ata3 and ata12) with messages that include:
>> ata12:000:device reported invalid CHS sector 0
> And then just stops?
>> Any ideas?
> Maybe the kernel is just too old for your hardware. This is 2.6.33 and
> it may have a bug or may not be handling properly the disk interface
> (Fedora's kernel is 2.6.35).
For example see:
A suggestion would be to go into the BIOS and change the mode of the
hard disk interface from AHCI to (maybe) legacy or something like that
(which is a suggestion in that thread).
But of course if you don't really need the rt kernel you can always work
with the Fedora one and wait for a newer rt patch to be released
(apparently the next one will be for 2.6.37). That is probably what I
would do - unless you have backups I would not experiment too much with
the hard disk interface :-)
More information about the PlanetCCRMA