| 1 |
On 03/29/2011 06:49 PM, Anthony G. Basile wrote: |
| 2 |
> On 03/29/2011 11:59 AM, Michael Orlitzky wrote: |
| 3 |
>> On 03/29/11 07:17, Magnus Granberg wrote: |
| 4 |
>>> [22:55:55] <blueness> HP smart array, the CCISS driver is borked on 2.6.37 and maybe 2.6.38 |
| 5 |
>>> [22:56:07] <blueness> this is a blocker to stabilizing 2.6.37 right now |
| 6 |
>>> [22:56:25] <prometheanfire> I thought that has been known for a while now though |
| 7 |
>>> [22:56:29] <blueness> if i can't resolve it, i'll make a patch to revert the commits that changed how the pci bus is read on those systems |
| 8 |
>>> [22:56:48] <blueness> prometheanfire, yes, but there's some confusion about it |
| 9 |
>>> [22:57:10] <blueness> some people think it works, i've asked chainsaw to confirm before i file the bug, he has the same systems |
| 10 |
>> |
| 11 |
>> I have a bunch of these too and would rather they not die after an |
| 12 |
>> upgrade. Anything I can do to help? |
| 13 |
> |
| 14 |
> Yes. I've been busy, but what we should do is test hardened 2.6.37-r7 |
| 15 |
> and compare this to vanilla 2.6.37.4. If it happens on both, then we |
| 16 |
> need to file a bug upstream while I revert the commits in .37 to the way |
| 17 |
> the pci bus is scanned for cciss. |
| 18 |
> |
| 19 |
|
| 20 |
Got it. Any particular type of borkage I should be looking for? |
Archives