Andrei POPESCU wrote:
On Vi, 30 mar 12, 08:31:31, Miles Fidelman wrote:
Any suggestions on:
- very low level configuration items to fiddle with,
- adding even more detailed logging to the very low level code,
- or kicking into single step or debug mode down at the very low level,
- or something else?
Just to eliminate any Xen issues:
- stop all virtual machines before reboot
- try with the normal kernel (i.e. non-Xen)
Well dooh (sound of my hand hitting my forehead....).
Ok...
- booting with normal kernel... still doesn't reboot
- booting with normal kernel, in single-user mode, with loglevel=7,
still doesn't work, with the following as the last few console messages:
[36. ...] md: stopping all md devices
[36. ...] md: md2 switched to read-only mode
[38. ...] sd 0:0:1:0: [sdb: Synchronizing SCSI cache]
[38. ...] sd 0:0:0:0: [sda: Synchronizing SCSI cache]
[38. ...] ehci_hcd 0000:00:03.3 PCI INT D disabled
[38. ...] ehci_hcd 0000:00:03.2 PCI INT C disabled
[38. ...] ehci_hcd 0000:00:03.1 PCI INT B disabled
[38. ...] ehci_hcd 0000:00:03.0 PCI INT A disabled
[38. ...] Restarting system
[38. ...] machine restart
So.. it's not Xen, and the last console message is from the kernel, just
before it does <something> to jump to the restart code.
This is the point at which you can use reboot=bios to tell an x86 kernel
to jump to the BIOS' restart code, but you can't do that for an amd64
kernel.
Hmmm...... what next? (I've tried pretty much all of the other reboot
options.)
Miles
--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f75c123.7090...@meetinghouse.net
