BUG: unable to handle kernel paging request at ffff88ffa0e4

[samhain]

Hallo allerseits!

seit neuestem bekomme ich unten stehende Meldung in regelmäßigen Abständen. Betroffen sind alle Thinkpads der T6*-Serie und mein Desktop-Rechner, nicht aber aber die X6*. Weiß wer, woher das kommt und was ich dagen tun kann?

Kernel stammt aus dem Paket linux-image-3.2.0-4-amd64_3.2.54-2_amd64.deb

# uname -a
Linux dasding 3.2.0-4-amd64 #1 SMP Debian 3.2.54-2 x86_64 GNU/Linux

# dmesg

[ 4618.100543] BUG: unable to handle kernel paging request at ffff88ffa0e4f4b0
[ 4618.100548] IP: [<ffffffff810bd8b3>] __do_page_cache_readahead+0x100/0x1c3
[ 4618.100555] PGD 0
[ 4618.100556] Oops: 0000 [#1] SMP
[ 4618.100559] CPU 1
[ 4618.100560] Modules linked in: ext3 jbd ppdev lp bnep rfcomm bluetooth rfkill loop dm_crypt dm_mod kvm_intel kvm snd_hda_codec_hdmi joydev hid_waltop hid_cherry usb_storage nvidia(P) snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hwdep snd_pcm_oss snd_mixer_oss snd_rawmidi snd_pcm snd_seq snd_page_alloc snd_seq_device snd_timer snd soundcore psmouse iTCO_wdt i2c_i801 iTCO_vendor_support i2c_core serio_raw acpi_cpufreq coretemp pcspkr mperf processor parport_pc evdev parport thermal_sys button ext4 crc16 jbd2 mbcache microcode sr_mod sg cdrom sd_mod crc_t10dif usbhid hid ata_generic ata_piix pata_jmicron uhci_hcd r8169 firewire_ohci mii ahci libahci firewire_core crc_itu_t libata ehci_hcd scsi_mod usbcore usb_common [last unloaded: scsi_wait_scan]
[ 4618.100603]
[ 4618.100605] Pid: 493, comm: rsync Tainted: P O 3.2.0-4-amd64 #1 Debian 3.2.54-2 Gigabyte Technology Co., Ltd. EP35-DS4/EP35-DS4
[ 4618.100608] RIP: 0010:[<ffffffff810bd8b3>] [<ffffffff810bd8b3>] __do_page_cache_readahead+0x100/0x1c3
[ 4618.100612] RSP: 0018:ffff8801ac3ddc48 EFLAGS: 00010246
[ 4618.100614] RAX: ffff88ffa0e4f490 RBX: ffff8801b0bf8260 RCX: 0000000000000001
[ 4618.100616] RDX: ffff8801ac3ddc90 RSI: 0000000000000000 RDI: ffff8801ac3ddc78
[ 4618.100618] RBP: 0000000000000001 R08: 0000000000000000 R09: 00000000000039e0
[ 4618.100619] R10: 0000000000000002 R11: 0000000000002e74 R12: 0000000000000000
[ 4618.100621] R13: 0000000000000004 R14: 0000000000000001 R15: 0000000000000000
[ 4618.100623] FS: 00007fbb9b81f700(0000) GS:ffff88021fc80000(0000) knlGS:0000000000000000
[ 4618.100625] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 4618.100627] CR2: ffff88ffa0e4f4b0 CR3: 00000001f71e9000 CR4: 00000000000406e0
[ 4618.100629] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4618.100631] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4618.100633] Process rsync (pid: 493, threadinfo ffff8801ac3dc000, task ffff8801ac278340)
[ 4618.100635] Stack:
[ 4618.100636] 0000000000000800 0000000000000001 0000000000000001 ffff8801f0bb0dc0
[ 4618.100639] ffff8801b0bf8268 0000000000000001 0000000091827364 ffff8801ac3ddc80
[ 4618.100642] ffff8801ac3ddc80 ffff8801ac3ddc90 ffff8801ac3ddc90 ffff880100000000
[ 4618.100645] Call Trace:
[ 4618.100648] [<ffffffff810bdbce>] ? ra_submit+0x19/0x1d
[ 4618.100651] [<ffffffff810b643b>] ? generic_file_aio_read+0x282/0x5cf
[ 4618.100655] [<ffffffff811056ea>] ? do_last+0x4ec/0x58d
[ 4618.100658] [<ffffffff810fa464>] ? do_sync_read+0xb4/0xec
[ 4618.100661] [<ffffffff810fab4f>] ? vfs_read+0x9f/0xe6
[ 4618.100663] [<ffffffff810fabdb>] ? sys_read+0x45/0x6b
[ 4618.100666] [<ffffffff81354d92>] ? system_call_fastpath+0x16/0x1b
[ 4618.100668] Code: c5 41 ff c6 49 63 ce 4c 39 e9 48 89 4c 24 08 0f 82 73 ff ff ff 85 ed 0f 84 b0 00 00 00 48 8d 7c 24 30 e8 e8 7a 0d 00 48 8b 43 70 <48> 8b 40 20 48 85 c0 0f 84 83 00 00 00 48 8b 7c 24 18 89 e9 48
[ 4618.100692] RIP [<ffffffff810bd8b3>] __do_page_cache_readahead+0x100/0x1c3
[ 4618.100695] RSP <ffff8801ac3ddc48>
[ 4618.100696] CR2: ffff88ffa0e4f4b0
[ 4618.100698] ---[ end trace bcb2ea67a4136e69 ]---

[samhain]

Ich vergaß: das Problem tritt auf, sobald auf eine 2. SATA-Platte stärker zugegriffen wird. Im Dump oben macht RSYNC grad' ein Backup. Bei den Tinkpads betrifft es Fetplatten im Wechselschacht.

[rendegast]

nvidia?
<->(?)
3.2.54-2
Ist erst kürzlich gekommen, versuche die Vorversion oder den backports-Kernel.

[samhain]

Danke, Kernel aus Backports rennt perfekt