>From a different client I can consistently get through most of the
install up to zipl segfaulting. When YaST2 attempts to reinstall the
bootloader, and it "hangs". 100% repeatable for me.
> - What type of disks?
> - Amoung of memory?
ECKD DASD (CDL formatted)
256 MB memory, plus the installer uses the specified device for swap.
I'm using NFS because it's the lightest. Zipl segfaults with both X
over ssh, and a straight ssh (ncurses) install.
# free
total used free shared buffers
cached
Mem: 253536 194608 58928 0 58136
51900
-/+ buffers/cache: 84572 168964
Swap: 107896 39684 68212
Here are the console messages from the zipl segfault:
illegal operation: 0001 [#1]
CPU: 0 Not tainted
Process pdflush (pid: 12, task: 0f694e48, ksp: 0f675da0)
Krnl PSW : 07081000 80000002 (0x2)
Krnl GPRS: 00000003 00000000 0e54f100 00000000
0000005d 0f675af0 00000001 0e54f1a4
00000000 00000094 0f675e18 007380a0
0e54f100 80192188 801928a8 0f675a08
Krnl Code: 00 00 80 10 ed ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Call Trace:
[<0000000000147118>] do_writepages+0x44/0x48
[<0000000000191658>] __writeback_single_inode+0x15c/0x2c0
[<0000000000191c04>] sync_sb_inodes+0x174/0x2f8
[<0000000000191fee>] writeback_inodes+0x106/0x1b4
[<0000000000147530>] wb_kupdate+0xe0/0x16c
[<00000000001479a8>] pdflush+0x194/0x26c
[<0000000000131304>] kthread+0x118/0x140
[<0000000000108296>] kernel_thread_starter+0xe/0x14
illegal operation: 0001 [#2]
CPU: 0 Not tainted
Process zipl (pid: 8812, task: 0e7cd718, ksp: 0fb01af8)
Krnl PSW : 07081000 80000002 (0x2)
Krnl GPRS: 00000001 00000000 08cfc900 00000000
00000001 0fb01b28 00000001 08cfc9a4
00000000 00000014 0fb01df0 00666fa0
08cfc900 80192188 801928a8 0fb01a40
Krnl Code: 00 00 80 10 ed ac 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Call Trace:
[<0000000000147118>] do_writepages+0x44/0x48
[<0000000000191658>] __writeback_single_inode+0x15c/0x2c0
[<0000000000191c04>] sync_sb_inodes+0x174/0x2f8
[<0000000000191e22>] sync_inodes_sb+0x9a/0xb0
[<0000000000191e80>] sync_inodes+0x48/0xb0
[<000000000016bfc8>] do_sync+0x44/0x90
[<000000000016c07a>] sys_sync+0x66/0x9c
[<000000000010e876>] sysc_do_restart+0xe/0x12
I re-IPLed the installation image and just after activating the dasd
devices, I mounted/chrooted and re-ran zipl from a second session. It
completed this time... but I don't know what yast does after zipl.
After ipling from DASD this time, the guest came up without its GUESTLAN
interface (only loopback). We're still on VM 4.3 so use GUESTLAN, there
was no chandev.conf (2.6?) and modules.conf was empty. I couldn't ssh
in so sent ^C at the console to try to get a shell there and all the
SuSEConfig stuff kicked off (I hadn't yet been able to run
YaST2.sshinstall) so I logged off. Any suggestions?
The md5sums on the .isos match what is listed on portal. Don't know if
it helps, but here's some info about the zipl that segfaults during
installation the first time and "hangs" the second time:
inst-sys:/sbin # md5sum zipl
38e33533797accdbe1aba7eb26072d99 zipl
inst-sys:/sbin # ls -l zipl
lrwxrwxrwx 1 root root 25 Nov 16 10:44 zipl ->
/mounts/instsys/sbin/zipl
The second time zipl is run, ps shows it usually in D+, but occasionally
R+. I let it run for a couple of hours, I never caught it with a
different PSW than:
inst-sys:/proc/9438 # cat status
Name: zipl
State: D (disk sleep)
SleepAVG: 116%
Tgid: 9438
Pid: 9438
PPid: 9437
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 32
Groups: 0
VmSize: 1520 kB
VmLck: 0 kB
VmRSS: 588 kB
VmData: 152 kB
VmStk: 8 kB
VmExe: 76 kB
VmLib: 1156 kB
Threads: 1
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000008000000
SigIgn: 0000000000001002
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
task: 0fc36e38, ksp: 0cf3faf0
User PSW : 070de000 c00cd6a2
User GPRS: 00000000 400cd6a0 00000000 00000000
80409d9a 004160e8 00000000 7ffffb38
00401110 00493130 7ffff9e0 00000000
00416008 80409b6c 80409dce 7ffff968 User ACRS: 40144460
00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
~ Daniel
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
