On Thu, 5 Mar 2009 23:20:51 +0100 Frans Pop <elendil@xxxxxxxxx> wrote: > During installation of a new Debian kernel package while running 2.6.27.19 > in the Hercules emulator, I got the following errors while the initamfs > initrd was being created for the new kernel. After the error I had to break > of the process. The second error is from a separate second try. > > With the current unstable Debian kernel (2.6.26) this error does not occur. > > The 2.6.27.19 kernel was cross-compiled on an amd64 host system using gcc > 4.2.4, while 2.6.26 was compiled using 4.1.3. Could that be the cause? I don't think that's the cause. > 17180168.889947! Kernel BUG at 000738b4 verbose debug info unavailable! > 17180168.890213! fixpoint divide exception: 0009 #1! SMP > 17180168.890487! Modules linked in: nfs lockd nfs_acl sunrpc ctcm fsm tape_34xx > cu3088 tape ccwgroup tape_class ext3 jbd mbcache dm_mirror dm_log dm_snapshot > dm_mod dasd_eckd_mod dasd_mod > 17180168.891891! CPU: 0 Not tainted 2.6.27.19 #13 > 17180168.892116! Process awk (pid: 2069, task: 0f9ed9b8, ksp: 0f4f7d18) > 17180168.892371! Krnl PSW : 070c1000 800738b4 (acct_update_integrals+0x4c/0x118) > 17180168.892830! R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:0 CC:1 PM:0 > 17180168.893115! Krnl GPRS: 00000000 000007d0 7fffffff fffff830 > 17180168.893376! 00000000 ffffffff 00000002 0f9ed9b8 > 17180168.893621! 00000000 00008ca0 00000000 0f9ed9b8 > 17180168.893873! 0f9edda4 8007386e 0f4f7ec8 0f4f7e98 > 17180168.894881! Krnl Code: 800738aa: a71807d0 lhi %r1,2000 > 17180168.895245! 800738ae: 8c200001 srdl %r2,1 > 17180168.895563! 800738b2: 1d21 dr %r2,%r1 > 17180168.895936! >800738b4: 5810d10e l %r1,270(%r13) > 17180168.896246! 800738b8: 1823 lr %r2,%r3 > 17180168.896598! 800738ba: 4130f060 la %r3,96(%r15) > 17180168.896913! 800738be: 0de1 basr %r14,%r1 > 17180168.897283! 800738c0: 5800f060 l %r0,96(%r15) > 17180168.897517! Call Trace: > 17180168.897656! ( <000000000004fdea>! blocking_notifier_call_chain+0x1e/0x2c) > 17180168.897987! <0000000000038502>! do_exit+0x106/0x7c0 > 17180168.898275! <0000000000038c36>! do_group_exit+0x7a/0xb4 > 17180168.898570! <0000000000038c8e>! SyS_exit_group+0x1e/0x30 > 17180168.898869! <0000000000021c28>! sysc_do_restart+0x12/0x16 > 17180168.899173! <0000000077e7e924>! 0x77e7e924 > 17180168.899971! <4>--- end trace fc7a0a826fc25194 !--- > 17180168.900510! Fixing recursive fault but reboot is needed Looks like this was caused by an overflow in cpu time accounting. Unfortunately I wasn't able to reproduce that here. We don't have any arch specific patches wrt to cpu time accouting between 2.6.26 and 2.6.27. However there was one patch in common code touching acct_update_integrals which claims to fix an overflow. Could you try to revert commit 49b5cf34727a6c1be1568ab28e89a2d9a6bf51e0 "accounting: account for user time when updating memory integrals" and see if the exception still occurs? -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
