Re: boot panic after oops from sysfs_new_dirent

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tejun Heo wrote:
> Meelis Roos wrote:
>>>> I powered on my 6-CPU E3000 after a summer pause and tried todays 
>>>> 2.6.31-rc8+git on it. It fails - first it spills lots of warnings about 
>>>> percpu things, then oopses in sysfs_new_dirent and then panics.
>> Bisecting shows that there may be different crashes, like in
>> 56513ed50cc8a5c184a3f347e81d74c850cc14fa below:
> 
> Yeah, I was trying to fix that one with
> 74d46d6b2d23d44d72c37df4c6a5d2e782f7b088 and it seemingly fixed it on
> my machine.  Apparently broken on yours.  Are the errors different
> before and after 74d46d6b2d?

Ummm.... one more question.  Is cpu0 missing?  Can you please post the
output of "cat /proc/cpuinfo"?

Thanks.

-- 
tejun
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux