Hallo,
wir haben hier mit einem 3.2.54-2 x86_64 Kernel Probleme dass Oops bei CIFS Zugriffen vorkommen. Dabei startet der Server jedesmal neu obwohl kernel.panic_on_oops = 0 gesetzt ist.
Hier der Ausschnitt aus dem Backtrace:
[571534.210147] BUG: unable to handle kernel paging request at ffff88025c874848
[571534.210342] IP: [<ffffffff81043eb4>] sched_destroy_group+0x34/0x11c
[571534.210398] PGD 1606063 PUD 0
[571534.210424] Oops: 0000 [#1] SMP
[571534.210452] CPU 0
[571534.210468] Modules linked in: des_generic ecb md4 hmac nls_utf8 cifs autofs4 nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc vsock(O) ext2 mbcache loop coretemp crc32c_intel vmw_balloon snd_pcm snd_page_alloc snd_timer snd soundcore evdev psmouse serio_raw pcspkr parport_pc parport processor ac thermal_sys container power_supply button vmci(O) vmwgfx ttm drm i2c_piix4 i2c_core shpchp xfs dm_mod vmxnet(O) vmw_pvscsi vmxnet3 sr_mod cdrom ata_generic sg sd_mod crc_t10dif floppy ata_piix e1000 libata mptspi scsi_transport_spi mptscsih mptbase scsi_mod [last unloaded: scsi_wait_scan]
[571534.210943]
[571534.210957] Pid: 3, comm: ksoftirqd/0 Tainted: G O 3.2.0-4-amd64 #1 Debian 3.2.54-2 VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform
[571534.211071] RIP: 0010:[<ffffffff81043eb4>] [<ffffffff81043eb4>] sched_destroy_group+0x34/0x11c
[571534.211188] RSP: 0018:ffff880236cb5d80 EFLAGS: 00010297
[571534.211241] RAX: ffff88025c8747c0 RBX: ffff8800075755c0 RCX: 0000000000000000
[571534.211328] RDX: 0000000000000000 RSI: ffff88021392f080 RDI: 0000000000000200
[571534.211412] RBP: 0000000000000000 R08: 0000000000000000 R09: ffffffff8168f0a0
[571534.211493] R10: ffff880009606558 R11: ffff8802138fcae8 R12: 0000000000013780
[571534.211573] R13: ffff88023fc00000 R14: ffffffff8168f0a0 R15: 0000000000000000
[571534.211653] FS: 0000000000000000(0000) GS:ffff88023fc00000(0000) knlGS:0000000000000000
[571534.211740] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[571534.211797] CR2: ffff88025c874848 CR3: 0000000066beb000 CR4: 00000000000006f0
[571534.211897] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[571534.211992] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[571534.212073] Process ksoftirqd/0 (pid: 3, threadinfo ffff880236cb4000, task ffff880236ca8730)
[571534.212163] Stack:
[571534.212193] 0000000000000000 ffff880066812c80 ffffffff81043fa5 ffff88022fba17d8
[571534.212287] 0000000000000005 ffff88023fc0edf0 ffff8801da606b08 ffffffff811ad1c2
[571534.212375] ffff88021392f080 ffff880097ca51c0 ffff880097ca51c0 ffffffff81044753
[571534.212462] Call Trace:
[571534.212497] [<ffffffff81043fa5>] ? cpu_cgroup_destroy+0x9/0x9
[571534.212557] [<ffffffff811ad1c2>] ? kref_put+0x3e/0x47
[571534.212611] [<ffffffff81044753>] ? free_signal_struct+0x24/0x34
[571534.212671] [<ffffffff81044959>] ? __put_task_struct+0x9d/0xb9
[571534.212731] [<ffffffff81095d52>] ? __rcu_process_callbacks+0x1c8/0x2ce
[571534.212795] [<ffffffff81095e82>] ? rcu_process_callbacks+0x2a/0x54
[571534.212857] [<ffffffff8104c346>] ? __do_softirq+0xb9/0x177
[571534.212913] [<ffffffff8104c47e>] ? run_ksoftirqd+0x7a/0x118
[571534.212970] [<ffffffff8104c404>] ? __do_softirq+0x177/0x177
[571534.213029] [<ffffffff8105f681>] ? kthread+0x76/0x7e
[571534.213082] [<ffffffff81356ef4>] ? kernel_thread_helper+0x4/0x10
[571534.213143] [<ffffffff8105f60b>] ? kthread_worker_fn+0x139/0x139
[571534.213203] [<ffffffff81356ef0>] ? gs_change+0x13/0x13
[571534.213255] Code: c7 c4 80 37 01 00 55 83 cd ff 53 48 89 fb 50 4c 8b 35 b9 1e 3c 00 eb 73 48 8b 43 28 4c 63 fd 4e 8b 2c fd c0 da 68 81 4a 8b 04 f8 <83> b8 88 00 00 00 00 74 57 4d 01 e5 4c 89 ef e8 b8 be 30 00 48
[571534.213521] RIP [<ffffffff81043eb4>] sched_destroy_group+0x34/0x11c
[571534.213584] RSP <ffff880236cb5d80>
[571534.213625] CR2: ffff88025c874848
Wie man sieht läuft das auf VMware. Dort laufen auch noch andere Debian Instanzen ohne Probleme.
Meine Frage - kennt jemand das Paging request Problem? Und warum macht er einen Reboot obwohl ich das deaktiviert habe?
Vielen Dank im Voraus.
Markus