On 09/24/2010 06:02 PM, M A Young wrote:
> I have built a new kernel (kernel- at
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2477887  or at the
> repositoryhttp://repos.fedorapeople.org/repos/myoung/dom0-kernel/
> It includes fixes for the recent x86_64 local root exploit.
> I also have a temporary test build xen-4.0.1-1.fc13.1 for Fedora 13 at
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2478501  . This is
> slightly misnamed as it is actually of 4.0.2-rc1-pre and includes the
> fixes above. Note that he build system will delete those RPMs
> automatically after a week or so.

I'm trying these two under f13, and not getting past udev starting on 
the pv_ops kernel. (Xen oops)  The non-xen kernel works fine on this 
hardware. A pv_ops version from back around January was working well for 
me, but I wanted to grab the x86_64 multilib-problem patched version. 
That brought me to upgrade my xen-* versions, and f12 to f13.

The top of the stack has 'xen_force_evtchn_callback' on it.  I see 
udev's [OK] message, and then it very reliably crashes (I can get it to 
tell me it's going down for reboot with a three-finger salute, but 
nothing really happens).

Is a serial console the only way to get a good Xen log?  Looking at this 
board, I think I need to take the heatsink off the CPU to get at the 
serial header, so I haven't tried yet...


Bill McGonigle, Owner
BFC Computing, LLC
Telephone: +1.603.448.4440
Email, IM, VOIP: b...@bfccomputing.com
VCard: http://bfccomputing.com/vcard/bill.vcf
Social networks: bill_mcgonigle/bill.mcgonigle
xen mailing list

Reply via email to