On Monday 21 June 2004 16:08, Andi Kleen wrote:
On Mon, Jun 21, 2004 at 02:50:48PM +0200, Martin Markgraf wrote:
Hello list,
I have an Asus K8V SE Delux with AMD Athlon 64, one S-ATA harddisk and an Adaptec 29160 wich is only connected to an DLT streamer. The system works fine until I have updated the kernel to kernel-default-2.6.5-7.75 via YAST Online-Update. After this update the system hangs during boot with
"ReiserFS: hda2: checking transactions log (hda2)"
hda2 is your root ?
as the last message. There the system stands forever.
Did you try pci=noacpi ?
If that doesn't help please boot into single user mode with the adaptec by specifying single on the boot loader prompt, then do
echo 1 > /proc/sys/kernel/sysrq echo 9 > /proc/sys/sysrq-trigger klogconsole -r0 mount -n -o remount,rw / (if hda2 wasn't your root do mount /path/to/hda2mountpoint )
Does it already hang? Are there are any messages on the screen?
If it hangs do alt-sysrq-t and check for the backtrace of the mount process and report that.
Best would be if you could connect a serial console before this to catch all messages.
-Andi
I've got the same problem as Martin Markgraf mentions above with kernel-default-2.6.5-7.75 . With me some other people do have this problem (according to the list Franz Mach pointed me to). Recovering is easy, just restore the original kernel or one of the earlier update kernels. My system has a MSI K8T Neo mainboard, AMD Athlon 64, one sata disk and a pata disk with Suse 9.1 on the sata disk and WinXP on the pata disk. For testing purposes I've got an installation of Suse 9.1 as well on the /hda3 as /hda2. The installation on /hda2 uses a LVM system on my extended partition, the installation on /hda3 has nothing special. Installed kernel-default-2.6.5-7.75 on /hda3. After that the system hangs during boot with the message: ReiserFS: hda3: checking transaction log (hda3) Tried the options mentioned by Andi Kleen above with my installation on /hda3. 1] pci=noacpi --> made it worse (even ctrl-alt-del or alt-sysrq-t didn't work anymore) I had to power off the system to reboot 2] specified 'single' on the boot prompt -->did'nt make difference, the system still hangs, so I don't reach the echo part 3] I did alt-sysrq-t after [2] but the output is too much to write down manually, can you specify more exact what to look for? Sorry, but I don't have a nullmodem cable for creating a serial console Roel Vestjens