On 04/30/2010 03:16 AM, scarleo wrote:
>
> I’m sorry to nag about this but I’m experiencing freezes from time to
> time and it’s starting to get annoying. This is not always related to a
> changed power state (unplugging or plugging in power adapter, changing
> from performance to powersave) but I feel that it’s more frequent during
> these changed states.
>
> I also believe it might be related to “Suspend 2 RAM” but I have some
> trouble to verify this since there are not very much in the logs (as far
> as I can say). I’m also a bit unexperienced so I’m not sure what
> lwfinger’s help really means. Is “the entire stack trace” the entire
> var/log/messages? How do I unload modules to untaint my kernel? I’m
> interested in learning and I guess it’s of interest for many others do
> discover if there are any real bugs in openSUSE, so if anyone could help
> me through this a bit more step by step I’d be most greatful.
Your kernel is not tainted by loading a proprietary module. I misread
the flags.
The call trace is info that looks like:
543.760028] Call Trace:
543.760028] <c03ff9c6>] pci_device_probe+0x56/0x80
543.760028] <c0491ed7>] driver_probe_device+0x87/0x290
543.760028] <c0492159>] __driver_attach+0x79/0x80
543.760028] <c0490ebb>] bus_for_each_dev+0x4b/0x70
543.760028] <c0491b96>] driver_attach+0x16/0x20
543.760028] <c04917d7>] bus_add_driver+0x1c7/0x310
543.760028] <c049233f>] driver_register+0x5f/0x100
543.760028] <c03ffbed>] __pci_register_driver+0x3d/0xb0
543.760028] <dd7bb015>] device_init_module+0x15/0x29 [vt6655_stage]
This one comes from entry 597299 in the openSUSE Bugzilla. With this
info, one can see that the call chain that lead to the bug started in
routine device_init_module() in module vt6655_stage. That info is
absolutely necessary.
> I have found more BUG-lines in my /var/log/messages so I post them here
> again with hope that someone might help me to both interpret what is
> going on and maybe even help me produce the info that is needed to
> either solve or report these bugs. Thanks in advance.
>
> part of /var/log/messages with more BUG-lines:
>
> Code:
> --------------------
The stuff you posted here was not relevant.
> Apr 30 09:43:32 linux-61g5 kernel: 2491.774986] BUG: unable to handle kernel NULL pointer dereference at 0000000000000052
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775034] IP: <ffffffff8148b6c3>] netlink_unicast+0x143/0x310
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775067] PGD 1048fe067 PUD 106115067 PMD 0
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775088] Oops: 0000 #1] PREEMPT SMP
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775106] last sysfs file: /sys/devices/LNXSYSTM:00/device:00/PNP0A03:00/ACPI0003:00/power_supply/AC0/online
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775131] CPU 1
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775142] Modules linked in: nfs lockd fscache nfs_acl auth_rpcgss sunrpc af_packet ip6t_LOG xt_tcpudp xt_pkttype ipt_LOG xt_limit snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device ip6t_REJECT nf_conntrack_ipv6 ip6table_raw radeon xt_NOTRACK drm ipt_REJECT xt_state iptable_raw iptable_filter ip6table_mangle nf_conntrack_netbios_ns nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables ip6table_filter cpufreq_conservative cpufreq_userspace cpufreq_powersave ip6_tables x_tables powernow_k8 sha256_generic ansi_cprng krng chainiv rng cryptd crypto_wq aes_x86_64 aes_generic cbc edd dm_crypt fuse loop arc4 ecb cryptomgr aead pcompress crypto_blkcipher crypto_hash crypto_algapi snd_hda_codec_realtek epl(C) 8139too snd_hda_intel snd_hda_codec ath5k snd_hwdep uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 pcspkr 8139cp joydev sr_mod sdhci_pci sdhci snd_pcm snd_timer snd amd64_edac_mod sg serio_raw cdrom mmc_core ricoh_mmc edac_core snd_pa
ge_alloc k8temp video i2c_piix4 ac battery ma
> Apr 30 09:43:32 linux-61g5 kernel: c80211 ath shpchp button cfg80211 asus_laptop pci_hotplug rfkill ext4 jbd2 crc16 dm_snapshot dm_mod fan processor ide_pci_generic atiixp ide_core ata_generic thermal thermal_sys pata_atiixp [last unloaded: preloadtrace]
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] Pid: 371, comm: udevd Tainted: G C 2.6.31.12-0.2-desktop #1 EASYNOTE_MX52-B-083FR
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] RIP: 0010:<ffffffff8148b6c3>] <ffffffff8148b6c3>] netlink_unicast+0x143/0x310
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] RSP: 0018:ffff880106117b08 EFLAGS: 00010202
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] RAX: ffff88010546b1e8 RBX: 000000000000001a RCX: 0000000000000005
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] RDX: ffffffff81c45fc0 RSI: 00000000b89ea4a2 RDI: ffff880107ba5528
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] RBP: ffff880106117b68 R08: 0000000000000172 R09: 000000000000000c
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] R10: 6c707075735f7265 R11: 0000000000000246 R12: 00000000ffffef8d
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] R13: ffff88008f9b9580 R14: ffff880104d42400 R15: ffff880106117b28
> Apr 30 09:43:32 linux-61g5 kernel: 2491.775299] FS: 00007f11b3221790(0000) GS:ffff880004666000(0000) knlGS:00000000f6972970
> Apr 30 09:43:32 linux-61g5 kernel: 2491.77Apr 30 09:47:01 linux-61g5 kernel: imklog 4.4.1, log source = /proc/kmsg started.
In general, if the traceback from dmesg output is available, it is
preferred over the one from /var/log/messages as it has less header
information in the form of date, etc.
Because your report does not have the necessary traceback information,
it is not possible to say what component is failing; however, the BUG
happened in routine netlink_unicast(), which points to a problem in
networking. I see wireless modules linked in, thus that may be where the
problem is located. I also see a module ath. Do you have an Atheros
wireless device? The wireless mailing list has had some chatter over
suspend/resume problems with those drivers. You might try using the
compat-wireless package to get the latest versions of those drivers.
