Bug#515956: linux-image-2.6.26-1-alpha-generic: 2.6.26-1-alpha-generic fails to boot on DS10 (Tsunami)
Le 18 févr. 09 à 19:40, maximilian attems a écrit :
On Wed, Feb 18, 2009 at 02:39:43PM +0100, Thibaut VARENE wrote:
19:39 <vorlon> abrotman: upgrade the aboot on your disk
19:39 <abrotman> isn't that part of the upgrade process from etch-
>lenny ?
19:39 <vorlon> no
19:39 <vorlon> we never change the boot block on upgrade
can you confirm to have been hit by this?
Running "swriteboot /dev/sda /boot/bootlx -f1" allowed me to boot the
new kernel. AFAICT, this wasn't mentioned in the release notes...
Still, it's still a no go: with the new kernel booted, I can no longer
log into the box using SSH:
OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to pluto port 22.
debug1: Connection established.
debug1: identity file /home/varenet/.ssh/identity type -1
debug1: identity file /home/varenet/.ssh/id_rsa type -1
debug1: identity file /home/varenet/.ssh/id_dsa type 2
debug1: Remote protocol version 2.0, remote software version
OpenSSH_5.1p1 Debian-5
debug1: match: OpenSSH_5.1p1 Debian-5 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'pluto' is known and matches the RSA host key.
debug1: Found key in /home/varenet/.ssh/known_hosts:8
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
Disconnecting: Corrupted MAC on input.
This is consistently happening across reboots (box sporting a BCM5701,
tg3 driver). I guess I'm gonna have to submit another bug report...
HTH
--
Thibaut VARÈNE
http://www.parisc-linux.org/~varenet/
Reply to: