From: Ian Pilcher <i.pilcher@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: AirPrime 5220 1xEVDO PC Card
Date: Thu, 28 Apr 2005 12:26:14 +0000 [thread overview]
Message-ID: <d4qkep$ne$1@sea.gmane.org> (raw)
In-Reply-To: <d4oi56$mvf$1@sea.gmane.org>
Greg KH wrote:
> Can you try the patch below to see if it fixes the issue?
That works. (Matthew Dharm suggested the same change.)
AFAICT, this driver is fully functional now. Less than 24 hours!
> What is the oops message?
Not sure that it matters, but here you go:
Unable to handle kernel NULL pointer dereference at virtual address 00000008
printing eip:
f8c48a4c
*pde = 3255d067
Oops: 0002 [#1]
Modules linked in: ppp_deflate zlib_deflate ppp_async crc_ccitt
ppp_generic slhc airprime usbserial ohci_hcd parport_pc lp parport md5
ipv6 ds ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables vfat
fat dm_mod yenta_socket pcmcia_core uhci_hcd hw_random snd_intel8x0m
snd_intel8x0 snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_timer
snd_page_alloc snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore
aes_i586 airo e100 mii floppy ext3 jbd
CPU: 0
EIP: 0060:[<f8c48a4c>] Not tainted VLI
EFLAGS: 00010282 (2.6.9-5.EL.root.evdo)
EIP is at usb_serial_generic_open+0x6e/0xef [usbserial]
eax: f8c48e7e ebx: f8c48e7e ecx: c0000480 edx: 00000000
esi: f6af9800 edi: f27f5000 ebp: f7f4dc00 esp: f306ded4
ds: 007b es: 007b ss: 0068
Process kppp (pid: 3847, threadinfoó06d000 taskó1aebd0)
Stack: f7f4dc00 f611dfc0 f27f5000 00000000 f8c472d5 f1cca480 ffffffed
f1cca480
f27f5000 00000100 c0216a87 00008902 0bc00001 f27f5000 00000001
f306d000
f7f4de04 f662a714 00000000 c016c6c4 f1cca480 00000001 f1cca480
f662a714
Call Trace:
[<f8c472d5>] serial_open+0x95/0xd9 [usbserial]
[<c0216a87>] tty_open+0x132/0x34a
[<c016c6c4>] chrdev_open+0x325/0x3b9
[<c01614e8>] dentry_open+0xbd/0x180
[<c0161425>] filp_open+0x36/0x3c
[<c011af55>] recalc_task_prio+0x128/0x133
[<c01d8e46>] direct_strncpy_from_user+0x3e/0x5d
[<c01618e9>] sys_open+0x31/0x7d
[<c0301bfb>] syscall_call+0x7/0xb
Code: a1 00 00 00 0f b6 45 20 8b 33 8b 55 1c 8b 0e c1 e0 0f c1 e1 08 09
c1 8b 43 04 81 c9 80 00 00 c0 8b 98 e8 00 00 00 b8 7e 8e c4 f8 <c7> 42
08 00 00 00 00 85 db 0f 44 d8 89 72 34 c7 42 04 3c 4b 24
(I'm pretty sure this translates to, "The hardware you just tried to
access doesn't exist.")
Thanks for your help!
--
====================================
Ian Pilcher i.pilcher@comcast.net
====================================
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id\x105hix
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2005-04-28 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 17:34 AirPrime 5220 1xEVDO PC Card Ian Pilcher
2005-04-27 18:00 ` Greg KH
2005-04-27 18:17 ` Greg KH
2005-04-28 0:57 ` Ian Pilcher
2005-04-28 2:47 ` David Brownell
2005-04-28 3:00 ` Matthew Dharm
2005-04-28 5:12 ` Greg KH
2005-04-28 12:26 ` Ian Pilcher [this message]
2005-04-28 20:47 ` Linas Vepstas
2005-04-28 21:33 ` Ian Pilcher
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='d4qkep$ne$1@sea.gmane.org' \
--to=i.pilcher@comcast.net \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).