https://bugzilla.novell.com/show_bug.cgi?id=350051
User nice@titanic.nyme.hu added comment
https://bugzilla.novell.com/show_bug.cgi?id=350051#c12
--- Comment #12 from Tamás Németh
What you're describing sounds more like problems with the originally shipped kernel, which indeed was severly broken. It happens on the newest 10.3 kernels, too.
Also, are you sure you're not running into the time problem we're aware of and have a fix queued (bug 335121)?
Oh, that bug seems to be the same as https://bugzilla.novell.com/show_bug.cgi?id=344877 don't you think so? Unfortunately I'm familiar with that issue but I think, that differs from this one. Seting the clocksource to jiffies was a good workaround for me, but currently I'm testing a 100Hz kernel instead. I will investigate if that bug is identical to this problem.
Also, you seem to imply that that's happening with Dom0, too: In that case, I can't see how /block/xvda1/dev would come into the picture unless you also have DomU-s running.
Yes, it definitely happens in in dom0 too, just like bug 335121. I just wrote about xvda because I could observe the tty10 logs of only a domU syses (that infamous SuSE Linux 8.2).
Could you get us this information (even if similar to #1, I would still want it from a pure 10.3 setup)?
- logs (Xen, kernel) showing anomalies - crash data (register+stack traces) - any other technical information you have.
Where can I get those kernel and Xen logs and crash data from? What do you mean exactly? (dmesg, xm dmesg, tty10, /var/log/messages or /var/log/xen/*) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.