From: <cfs...@ya...> - 2004-02-21 16:58:06
|
Hi All, Sorry for the noise, but I didn't found the answer in the mailing list archive. previously I use uml-2.4.20 with a redhat9 rootfs perfectly. now I'm trying vallina-2.6.3, with uml-patch-2.6.3-rc2-1 donwloaded from sf. rootfs is the same. The symptom is: it hang on boot right after "mount devfs", and consuming 100% CPU all the time until was manually killed. remove the 'devfs' option dosen't help: it hang again right after "mount ext3 root filesystem readonly". break into gdb only got trace begin from something like "sigint_handler". I was told that rootfs with new distribution running on old machine have this kind of problem, but my laptop CPU is P4, and anyway 2.4.20-uml with the same rootfs works very well. have clue? appraciate any help! MeiJia --------------------------------- Do You Yahoo!? 完全免费的雅虎电邮,马上注册获赠额外60兆网络存储空间 |
From: BlaisorBlade <bla...@ya...> - 2004-02-22 15:50:14
|
Alle 17:50, sabato 21 febbraio 2004, MeiJia ha scritto: > Hi All, > > Sorry for the noise, but I didn't found the answer in the mailing list > archive. > > previously I use uml-2.4.20 with a redhat9 rootfs perfectly. now I'm > trying vallina-2.6.3, with uml-patch-2.6.3-rc2-1 donwloaded from sf. > rootfs is the same. > > The symptom is: it hang on boot right after "mount devfs", and consuming > 100% CPU all the time until was manually killed. remove the 'devfs' option > dosen't help: it hang again right after "mount ext3 root filesystem > readonly". break into gdb only got trace begin from something like > "sigint_handler". There is a problem that happens differently on 2.6 UML kernels. This has been reported as "2.6 stops at NET: Registered protocol family" and so on. Or better, we have some evidence about what that hang relates to; and so we can guess you have the same problem. The bug does not hit devfs, ext3, NET or anything such; it hits the core scheduler - or better wait queues and notifications (i.e. when code inside the kernel decides to wait for something, then this bug makes things not work). Would you post the backtrace you get, so we can be sure about what is happening? Also, you could probably try vanilla-2.6.0 linux kernel and patch-2.6.0-test9 (and disable module support). A lot of people reported that patch makes the problem go away. > I was told that rootfs with new distribution running on old machine have > this kind of problem, They have another kind of problem, with maybe seems to be the same until you do some debugging. -- Paolo Giarrusso, aka Blaisorblade Linux registered user n. 292729 |