From: Arjan van de Ven <arjan@infradead.org>
To: "Justin Mattock" <justinmattock@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: BUG kmalloc-2048: Poison overwritten
Date: Sun, 1 Jun 2008 21:15:36 -0700 [thread overview]
Message-ID: <20080601211536.1e3ba47c@infradead.org> (raw)
In-Reply-To: <dd18b0c30806012053q27b00fd6p40fa63bcb4bb19a3@mail.gmail.com>
On Mon, 2 Jun 2008 03:53:43 +0000
"Justin Mattock" <justinmattock@gmail.com> wrote:
> On Mon, Jun 2, 2008 at 2:01 AM, Arjan van de Ven
> <arjan@infradead.org> wrote:
> > On Sun, 1 Jun 2008 23:13:51 +0000
> > "Justin Mattock" <justinmattock@gmail.com> wrote:
> >
> >> I received this after the second simultaneous suspend: (I will try
> >> and see if this is re creatable or not)
> >>
> >> [ 232.270737] BUG: unable to handle kernel paging request at
> >> 6b6b6c6b
> >
> > bad bad bad
> >
> >
> >> [ 232.270743] IP: [<c013f96d>] module_put+0x12/0x2b
> >> [ 232.270750] *pde = 00000000
> >> [ 232.270753] Oops: 0002 [#1] SMP
> >> [ 232.270757] Modules linked in: hci_usb cpufreq_ondemand
> >> cpufreq_performance cpufreq_powersave rfcomm hidp l2cap bluetooth
> >> fan ipmi_watchdog ipmi_msghandler uinput wlan_tkip
> >> ieee80211_crypt_tkip ieee80211_crypt arpt_mangle arptable_filter
> >> arp_tables nf_conntrack_ipv4 nf_conntrack iptable_mangle
> >> iptable_filter ip_tables x_tables intelfb i2c_i810 i2c_algo_bit
> >> coretemp eeprom acpi_cpufreq fglrx(P) applesmc joydev uvcvideo
> >> appletouch wlan_scan_sta
> > ^^^^^
> >
> > naughty
> >
> >> ath_rate_sample firewire_ohci firewire_core snd_hda_intel ath_pci
> >> snd_pcm wlan ohci1394 intel_agp evdev ath_hal(P) snd_timer ieee1394
> > ^^^^^^^^^^
> >
> > worse
> >
> >
> >> Hopefully this is nothing serious,
> >> regards;
> >
> > actually it's very serious, something is scribbling all over your
> > memory, it's just a matter of time before that overwrites something
> > important on your filesystem, and then you have a high risk of
> > losing most of your data.
> >
> > However, since you're using 2 proprietary kernel modules, you
> > really ought to contact the vendors for those modules for support;
> > they're a very likely cause for problems
> > (for example, these two are the cause for the number 1, 2, 5 and 7
> > of the top 10 kernel oopses/crashes for the last week)
> >
> >
> >
> great!!! Well The problem I have with these modules is A) madwifi
> "waiting until support is in the kernel for this one,
you mean the ath5k driver which already is in the kernel?
If it doesnt work for you, have you filed a bugzilla ?
> for now I
> just have to deal with risking loosing any data". B) graphics driver I
> can unload the driver but then loose suspend to mem "argh!!"
A current ATI driver in X.org ought to be close to getting this one
right.
> aside from that, I just performed the test again of simultaneously
> suspending to memory and didn't receive this message,
sure the corruption this time wasn't in a redzone.. but maybe elsewhere.
> so now I'm at a
> lost for words as to what is happening. The positive side is there
> isn't any important data on my system i.g. important doc's etc..., but
>
good luck.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-06-02 4:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 23:13 Justin Mattock
2008-06-01 23:25 ` Rafael J. Wysocki
2008-06-02 1:02 ` Justin Mattock
2008-06-02 22:21 ` hci_usb strikes again (was Re: BUG kmalloc-2048: Poison overwritten) Pavel Machek
2008-06-02 23:12 ` Justin Mattock
2008-06-03 6:43 ` Pavel Machek
2008-06-03 8:30 ` Justin Mattock
2008-06-02 2:01 ` BUG kmalloc-2048: Poison overwritten Arjan van de Ven
2008-06-02 3:53 ` Justin Mattock
2008-06-02 4:15 ` Arjan van de Ven [this message]
2008-06-02 4:44 ` Justin Mattock
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=20080601211536.1e3ba47c@infradead.org \
--to=arjan@infradead.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®