From: Justin Madru <jdm64@gawab.com>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: 2.6.30-rc1: OOPS on usb disk insert
Date: Wed, 08 Apr 2009 23:46:37 -0700 [thread overview]
Message-ID: <49DD99CD.4090201@gawab.com> (raw)
In-Reply-To: <ac3eb2510904080625m228ddc4dl611c3c5c368fab2a@mail.gmail.com>
Kay Sievers wrote:
> On Tue, Apr 7, 2009 at 23:07, Justin Madru <jdm64@gawab.com> wrote:
>
>> Andrew Morton wrote:
>>
>>> On Tue, 07 Apr 2009 22:05:24 -0700 Justin Madru <jdm64@gawab.com> wrote:
>>>
>
>
>>>> Testing out .30-rc1 and usb devises don't work. I insert my flash disk
>>>> and get this oops.
>>>>
>
>
>>> The trace appears to be claiming that kernel/async.c:async_new.func is
>>> NULL.
>>>
>>> But it cannot be - it's initialised at compilation time. Unless
>>> something scribbled on it of course.
>>>
>
> I've seen async problems with other subsystem too, maybe caused by a
> corruption which is fixed by:
> http://patchwork.kernel.org/patch/16776/
>
> -static void __init acpi_battery_init_async(void *unused, ...
> +static void acpi_battery_init_async(void *unused, ...
>
> Kay
>
>
I've applied the following patches (to try to fix other bugs) and I no
longer get a BUG/OOPS
although the patches might have not been the cause of the fix, but
inserting the disk still doesn't works.
http://patchwork.kernel.org/patch/17199/
http://patchwork.kernel.org/patch/17025/
http://patchwork.kernel.org/patch/17039/
It now complains of: FAT: IO charset cp437 not found
Which I've found a work around by:
<insert flash disk>
syslog complains: FAT: IO charset cp437 not found
sudo modprobe -r nls_cp437
sudo modprobe -i nls_cp437
<remove then reinsert flash disk>
syslog complains: FAT: IO charset iso8859_1 not found
sudo modprobe -r nls_iso8859_1
sudo modprobe -i nls_iso8859_1
<insert flash disk>
profit!!
So, I have to insert the disk 3 times before it works. although after
that it just works, until I reboot and I have to repeat the unload/load
modules.
Justin Madru
next prev parent reply other threads:[~2009-04-09 6:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 5:05 2.6.30-rc1: OOPS on usb disk insert Justin Madru
2009-04-08 5:38 ` Andrew Morton
2009-04-08 6:07 ` Justin Madru
2009-04-08 13:25 ` Kay Sievers
2009-04-09 6:46 ` Justin Madru [this message]
2009-04-16 21:10 ` Rafael J. Wysocki
2009-04-17 3:19 ` Justin Madru
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=49DD99CD.4090201@gawab.com \
--to=jdm64@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@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