I am getting kernel oops whenever I try to emerge -sync. Here is an example oops, but they repeat many times (on all CPUs) (emerge --info too big to put here without error, see attachment). Oops: 0000 [42] SMP CPU 2 Modules linked in: nvidia parport_pc parport snd_pcm_oss snd_mixer_oss snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_intel8x0 snd_ac97_codec snd_ac97_bus snd_pcm snd_timer snd soundcore snd_page_alloc w83627hf hwmon_vid hwmon i2c_isa eth1394 shpchp pci_hotplug ohci1394 ieee1394 serio_raw tg3 i2c_nforce2 Pid: 26731, comm: rsync Tainted: P 2.6.17-gentoo-r6 #1 RIP: 0010:[<ffffffff80287dba>] <ffffffff80287dba>{vfs_getattr+74} RSP: 0018:ffff8100510a5e38 EFLAGS: 00010246 RAX: 0000001f00000000 RBX: ffff8100b5a937c8 RCX: 0000000000000004 RDX: ffff8100510a5ef8 RSI: ffff8100b5a937c8 RDI: ffff81012a5fe880 RBP: ffff81004ffc1110 R08: 8508fae822d3cdd1 R09: ffff81011bca5025 R10: 722d312e32312e32 R11: ffffffff80421390 R12: ffff81012a5fe880 R13: ffff8100510a5ef8 R14: 000000000000a377 R15: 0000000000000003 FS: 00002b5e20c29b00(0000) GS:ffff81012bc0c140(0000) knlGS:00000000f7220ba0 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000001f00000078 CR3: 0000000010c42000 CR4: 00000000000006e0 Process rsync (pid: 26731, threadinfo ffff8100510a4000, task ffff81012a12c870) Stack: 00007fff8aae75c0 0000000000000000 ffff8100510a5ef8 0000000001238600 000000000000a377 ffffffff80287e9d ffff8100b5a937c8 ffff81012a5fe880 000000000000011b 0000000000001000 Call Trace: <ffffffff80287e9d>{vfs_lstat_fd+61} <ffffffff802880f7>{sys_newlstat+39} <ffffffff80209cea>{system_call+126} Code: 48 8b 40 78 48 85 c0 74 2d 4c 89 ea 48 89 de 4c 89 e7 48 8b RIP <ffffffff80287dba>{vfs_getattr+74} RSP <ffff8100510a5e38> CR2: 0000001f00000078 Things i have tried: - downgraded rsync from 2.6.8-r1 to 2.6.0-r6 (no effect) - toolchain rebuild, followed by emerge -e system (no effect) - emerge-webrsync (successful), followed by emerge --sync (same error/no effect) - move from 2005.1 profile to 2006.1 profile (in progress now) - mirrorselect -H (no effect) This system with very little changes except updates has been operating on this network for over 1.5 years, and I have never had a similar problem. I can emerge -e system and it runs all night - I do not think I have a firewall issue.
Created attachment 97029 [details] emerge --info
Well, your kernel is tainted. Reopen if you can reproduce the issue without nvidia drivers and whatever else that taints the kernel.
