Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Am Montag, 16. Januar 2006 07:55 schrieb Arne Groh: > dear drbdusers and developers, > > in the last two weeks we had some not reproducable kernel oopses like this: > > > Jan 13 21:12:57 fs01 kernel: Unable to handle kernel paging request at > virtual a > ddress f6ca5000 > Jan 13 21:12:57 fs01 kernel: printing eip: > Jan 13 21:12:57 fs01 kernel: c0166657 > Jan 13 21:12:57 fs01 kernel: *pde = 004db067 > Jan 13 21:12:57 fs01 kernel: *pte = 36ca5000 > Jan 13 21:12:57 fs01 kernel: Oops: 0000 [#1] > Jan 13 21:12:57 fs01 kernel: PREEMPT SMP DEBUG_PAGEALLOC > Jan 13 21:12:57 fs01 kernel: Modules linked in: drbd aic7xxx > scsi_transport_spi > Jan 13 21:12:57 fs01 kernel: CPU: 0 > Jan 13 21:12:57 fs01 kernel: EIP: 0060:[bio_clone+87/208] Not > tainted VLI > Jan 13 21:12:57 fs01 kernel: EFLAGS: 00010206 (2.6.15.smp1) > Jan 13 21:12:57 fs01 kernel: EIP is at bio_clone+0x57/0xd0 > Jan 13 21:12:57 fs01 kernel: eax: 000000c0 ebx: db5dbc20 ecx: > 00000008 edx > > : f230ff20 > > Jan 13 21:12:57 fs01 kernel: esi: f6ca5000 edi: f230ffc0 ebp: > d13819dc esp > > : d13819c0 > > Jan 13 21:12:57 fs01 kernel: ds: 007b es: 007b ss: 0068 > > someone who has an idea, how to fix this problem ? > we use kernel 2.6.15 with drbd 0.7.15 on a dual intel pentium III > machine. on the drbd device we have a xfs-filesystem. > Could you please post the whole OOPS, especially the call trace. Thanks, Philipp -- : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Schönbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :