hi, could you please provide some more info:
- What type of disks? - Amoung of memory? Ihno On Mon, Nov 15, 2004 at 03:50:13PM -0500, Daniel Jarboe wrote: > I didn't see anything in the installation doc so I thought I'd ask if > anyone has seen this before: > > I'm trying a new install of SLES9 (s390 31bit) under VM. I had > previously formatted all the DASD from another SLES8 system. The > install was working on the second CD (core9/CD1) over NFS (loop mounted > isos) with an ssh client. Several progress bars into it, the ssh client > disappeared and this was written to /var/log/messages... > > Nov 15 19:58:22 suse kernel: JBD: barrier-based sync failed on dasde1 - > disabling barriers > > Nov 15 19:58:22 suse kernel: JBD: barrier-based sync failed on dasdf1 - > disabling barriers > > Nov 15 20:13:18 suse sshd[245]: Received signal 15; terminating. > > Nov 15 20:13:18 suse kernel: illegal operation: 0001 [#1] > > Nov 15 20:13:18 suse kernel: CPU: 0 Not tainted > > Nov 15 20:13:18 suse kernel: Process linuxrc (pid: 292, task: 0f849b70, > ksp: 0e433ea0) > > Nov 15 20:13:18 suse kernel: Krnl PSW : 07081000 80000002 (0x2) > > Nov 15 20:13:18 suse kernel: Krnl GPRS: 00000001 00000000 073b6500 > 00000000 > > Nov 15 20:13:18 suse kernel: 00000036 0e433b28 00000001 073b65a4 > > Nov 15 20:13:18 suse kernel: 00000000 00000295 0e433df0 006ab360 > > Nov 15 20:13:18 suse kernel: 073b6500 80192188 801928a8 0e433a40 > > Nov 15 20:13:18 suse kernel: Krnl Code: 00 00 80 10 ed ac 00 00 00 00 00 > 00 00 00 00 00 00 00 00 00 > > Nov 15 20:13:18 suse kernel: Call Trace: > > Nov 15 20:13:18 suse kernel: [do_writepages+68/72] > do_writepages+0x44/0x48 > > Nov 15 20:13:18 suse kernel: [__writeback_single_inode+348/704] > __writeback_single_inode+0x15c/0x2c0 > > Nov 15 20:13:18 suse kernel: [sync_sb_inodes+372/760] > sync_sb_inodes+0x174/0x2f8 > > Nov 15 20:13:18 suse kernel: [sync_inodes_sb+154/176] > sync_inodes_sb+0x9a/0xb0 > > Nov 15 20:13:18 suse kernel: [sync_inodes+72/176] sync_inodes+0x48/0xb0 > > Nov 15 20:13:18 suse kernel: [do_sync+68/144] do_sync+0x44/0x90 > > Nov 15 20:13:18 suse kernel: [sys_sync+102/156] sys_sync+0x66/0x9c > > Nov 15 20:13:18 suse kernel: [sysc_do_restart+14/18] > sysc_do_restart+0xe/0x12 > > Nov 15 20:13:18 suse kernel: > > SuSE Instsys linfs3:/ # > > > We've tried fresh a few times... I've verified that the md5sums of the > isos match what SuSE reports as correct. Everything seems in order, > except for the installer crashes. Has anyone seen anything like this? > > Thanks, > ~ 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 -- Best regards/Mit freundlichen Grüßen Ihno Krumreich "Never trust a computer you can lift." -- Ihno Krumreich [EMAIL PROTECTED] SUSE LINUX Products GmbH Projectmanager S390 & zSeries Maxfeldstr. 5 +49-911-74053-439 D-90409 Nürnberg http://www.suse.de ---------------------------------------------------------------------- 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
