Any update about the bug? We still keep an eay on it :)
Liu, Jinsong wrote:
> I cannot reproduce the bug at my desktop according to the
> environment/config you send me.
> I try inserting processor.ko during boot/ after boot, transferring
> max_cstate=2 to processor.ko through /etc/modprobe.conf, dom0 boot
> However, some minor suggestions for you :)
> 1. for Jeremy kernel .config, set 'CONFIG_SYSFS_DEPRECATED=y'.
> Without it, dom0 will panic during boot;
> 2. would you please try some other platform? maybe it's machine
> specific issue;
> I think at your case Xen is still alive. With serial console, type
> 'ctrl+a' 3 times will switch to xen console, and under xen console,
> type key '0'/ 'c'/ 'd'/ 'q' will get some xen-dump-log (and prove Xen
> Martin Wilck wrote:
>> Dear Jinsong,
>>> I'd like to reproduce the bug at my desktop and have a look at it.
>>> I'm setting up debug environment now, and need some
>>> environment/config info at your side:
>> I sent some Infos in November, but they may have got lost on their
>> way to the mailing list.
>>> 1. xen-upstable changeset
>>> 2. Jeremy pvops kernel version/ git commit/ .config file
>> xen/stable-2.6.32.x commit: 481bd8e6b8dafed2ea445e8cde2abbbb95b49ec1
>> config file attached
>>> 3. ioemu git commit
>> But I am certain none of these really matter a lot - I got the same
>> result with all kernels and hypervisors I tried so far since
>> upgrading to OpenSUSE 11.3. My previous xen hypervisor had no
>> cpuidle or cpufreq support.
>>> 4. grub.conf file
>> title Xen4.1
>> root (hd0,5)
>> kernel /xen-4.1.gz vga=mode-0,keep cpufreq=xen cpuidle loglvl=all
>> module /vmlinuz-184.108.40.206 root=/dev/mapper/vg-os11.2 vga=0
>> nomodeset debug sysrq=9 S module /initrd-220.127.116.11
>>> 5. processor.ko related config to load the modules at booting time
>>> (of Jeremy pvops kernel, not SUSE)
>> I am not sure what you are referring to here. I have tried different
>> things. The usual SUSE way is to load processor.ko in the initrd
>> (INITRD_MODULES="ahci processor" in /etc/sysconfig/kernel).
>>> 6. xen/kernel booting serial log
>> I'd love to provide it, but I have no serial port. I am considering
>> to by a docking station to be able to get one.
>>> BTW, is xen still alive when dom0 kernel freeze? I don't think so.
>>> If yes, some dump log like key '0'/ 'c'/ 'd'/ 'q' is highly
>> Please give me more hints - just hit '0' no Alt-sysrq or anything?
>> BTW, have you tried at some other platform beside Samsung XS50
>> laptop? is it a machine specific issue?
>>> It could be. Noone else reported anything similar to SUSE. I only
>>> saw it on this laptop.
> Xen-devel mailing list
Xen-devel mailing list