On 20.09.2010, Alan Stern wrote: > > Jiris patch obviously didn't made it into 2.6.36-rc4, and it doesn't > > apply nay longer either. > No, you're wrong. The patch _is_ in 2.6.36-rc4, and that's the reason > why it doesn't apply any longer. Yes, you're right. > The error you see must have a different cause. Have you read this > thread? > > http://marc.info/?t=128494644600005&r=1&w=2 No, not before until now. This problem seems not to be related to what I see on my machines, and reverting commit 8fe294caf8c868edd9046251824a0af91991bf43 as mentioned in there doesn't help either. 2.6.35.4 works, 2.6.36-rc4 does not. What can I do to help to find the issue? Attached are the dmesg output for both 2.6.35.4 and 2.6.36-rc4.
Attachment:
dmesg-2.6.35.4.txt.bz2
Description: Binary data
Attachment:
dmesg-2.6.36-rc4.txt.bz2
Description: Binary data