From: Jiri Slaby <jirislaby@gmail.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Parag Warudkar <parag.warudkar@gmail.com>,
linux-kernel@vger.kernel.org, sds@tycho.nsa.gov,
jmorris@namei.org, eparis@parisplace.org,
cpufreq@vger.kernel.org
Subject: Re: 2.6.31-rc2: BUG: unable to handle kernel NULL pointer dereference
Date: Mon, 13 Jul 2009 19:45:05 +0200 [thread overview]
Message-ID: <4A5B72A1.5090605@gmail.com> (raw)
In-Reply-To: <1247504406.5437.3.camel@localhost>
On 07/13/2009 07:00 PM, Thomas Meyer wrote:
>> What warning tainted the kernel before this oops is still interesting...
>
> There seems to be no OOPS before that BUG. Does a WARNING also set the G
> flag?
No, W is set by warning. G means no proprietary modules loaded.
> Something like that:
>
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] ------------[ cut here ]------------
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] WARNING: at lib/kref.c:43 kref_get+0x2f/0x4c()
It tried to get a reference of a structure which was already "freed".
Its reference count already had lowered to 0.
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] Hardware name: MS-7250
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] Modules linked in: rndis_wlan floppy olympic forcedeth [last unloaded: scsi_wait_scan]
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] Pid: 27483, comm: pm-suspend Tainted: G W 2.6.31-rc2 #79
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] Call Trace:
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff8106c1c6>] ? warn_slowpath_common+0x84/0xb2
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff8134876b>] ? kref_get+0x2f/0x4c
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff813476b2>] ? kobject_get+0x26/0x44
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff815a344f>] ? cpufreq_cpu_get+0x74/0xca
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff815a3675>] ? cpufreq_suspend+0x5f/0x16f
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff81044a4f>] ? disable_local_APIC+0x2d/0x6d
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff81449b54>] ? sysdev_suspend+0xa7/0x28d
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff810a1229>] ? suspend_devices_and_enter+0x11c/0x1e6
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff810a13d8>] ? enter_state+0xe5/0x14c
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff810a0841>] ? state_store+0xc1/0xf6
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff81178bb8>] ? sysfs_write_file+0xe6/0x137
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff81117d03>] ? vfs_write+0xb4/0x126
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff81117e5d>] ? sys_write+0x55/0x90
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] [<ffffffff8102bf2b>] ? system_call_fastpath+0x16/0x1b
> Jul 12 16:42:34 localhost kernel: [ 6179.647004] ---[ end trace f7a4d612974b9b3e ]---
>
> Btw this seems also to be new in 2.6.31-rc2:
This is unrelated I think. I met it many times.
> Jul 12 16:42:34 localhost kernel: [ 6187.256748] sd 2:0:0:0: [sdb] Starting disk
> Jul 12 16:42:34 localhost kernel: [ 6190.318012]
> Jul 12 16:42:34 localhost kernel: [ 6190.318128] floppy driver state
> Jul 12 16:42:34 localhost kernel: [ 6190.318244] -------------------
> Jul 12 16:42:34 localhost kernel: [ 6190.320684] now=4300857616 last interrupt=4294760495 diff=6097121 last called handler=ffffffffa00263ea
> Jul 12 16:42:34 localhost kernel: [ 6190.320896] timeout_message=lock fdc
next prev parent reply other threads:[~2009-07-13 17:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 14:47 2.6.31-rc2: BUG: unable to handle kernel NULL pointer dereference Thomas Meyer
2009-07-12 17:30 ` Parag Warudkar
2009-07-12 20:26 ` Jiri Slaby
2009-07-12 21:54 ` Parag Warudkar
2009-07-12 21:56 ` Eric Paris
2009-07-13 17:00 ` Thomas Meyer
2009-07-13 17:45 ` Jiri Slaby [this message]
2009-07-20 19:23 ` Thomas Meyer
2009-07-22 20:28 ` Rafael J. Wysocki
2009-07-24 11:03 ` Jiri Slaby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A5B72A1.5090605@gmail.com \
--to=jirislaby@gmail.com \
--cc=cpufreq@vger.kernel.org \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=parag.warudkar@gmail.com \
--cc=sds@tycho.nsa.gov \
--cc=thomas@m3y3r.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.