>Odd, I never got such messages. I suspect that if you enable DEBUG for
>that driver you'll notice that request_mem_region() failed, so you
should
>find out why it did that ... was some other driver grabbing BAR 0 on
that
>PCI device?
>Does it happen on 2.6.14?
David,
Thanks for the response. You are right, it failed to grab BAR 0.
Debug results shows that, it is calling "done" after failing
request_mem_region call. The goto goes to done, where it calls
net2280_remove (pdev) and then crashes.
if (!request_mem_region (resource, len, driver_name)) {
DEBUG (dev, "controller already in use\n");
retval = -EBUSY;
goto done;
}
Not grabbing the BAR 0 is fine, but it should not crash while calling
net2280_remove (pdev);
I did lsmod and saw ehci_hcd and ohci_hcd were loaded, thought this
might have grabbed the BAR0. Even after removing these host controller
drivers, the crash still remains. The crash observed in 2.6.12, which is
rpm installed source on my Fedora system.
Are you guessing something wrong with the kernel? Please let me know,
which kernel it works fine.
Thanks
Iqbal
-----Original Message-----
From: David Brownell [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 03, 2005 12:38 PM
To: [email protected]
Cc: Iqbal
Subject: Re: [linux-usb-devel] Issues loading netchip2280
On Wednesday 02 November 2005 1:58 pm, Iqbal wrote:
>
> Hi,
>
> When I load the net2280.ko on 2.6.12 I get the following oops message.
I
> am connected with netchip2280 on PCI slot.
Odd, I never got such messages. I suspect that if you enable DEBUG for
that driver you'll notice that request_mem_region() failed, so you
should
find out why it did that ... was some other driver grabbing BAR 0 on
that
PCI device?
Does it happen on 2.6.14?
> The dump follows.
>
> Nov 2 14:47:12 localhost kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 000002a8
> Nov 2 14:47:12 localhost kernel: printing eip:
> Nov 2 14:47:12 localhost kernel: f8b25f13
> Nov 2 14:47:12 localhost kernel: *pde = 00000000
> Nov 2 14:47:12 localhost kernel: Oops: 0000 [#1]
> Nov 2 14:47:12 localhost kernel: Modules linked in: net2280(U) md5
ipv6
> parport_pc lp parport autofs4 sunrpc video button battery ac joydev
> uhci_hcd ehci_hcd i2c_i801 i2c_core snd_intel8x0 snd_ac97_codec
> snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore
snd_page_alloc
> e100 mii floppy dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod
> Nov 2 14:47:12 localhost kernel: CPU: 0
> Nov 2 14:47:12 localhost kernel: EIP: 0060:[<f8b25f13>]
Tainted:
> GF VLI
> Nov 2 14:47:12 localhost kernel: EFLAGS: 00010292
(2.6.12-1.1381_FC3)
> Nov 2 14:47:12 localhost kernel: EIP is at net2280_remove+0x13/0x1b0
> [net2280]
> Nov 2 14:47:12 localhost kernel: eax: f7f6e444 ebx: f774b000 ecx:
> f7f71d14 edx: 00000022
> Nov 2 14:47:12 localhost kernel: esi: f7f6e49c edi: 00000000 ebp:
> f7f6e400 esp: f53f4ebc
> Nov 2 14:47:12 localhost kernel: ds: 007b es: 007b ss: 0068
> Nov 2 14:47:12 localhost kernel: Process insmod (pid: 8579,
> threadinfo=f53f4000 task=f5291aa0)
> Nov 2 14:47:12 localhost kernel: Stack: badc0ded f7f71d14 f77247dc
> c01286cd f7f6e400 f7f6e444 f774b000 f7f6e49c
> Nov 2 14:47:12 localhost kernel: fffffff0 07981b65 f8b2638d
> f8b26580 c037a198 00000282 c03c6608 f53a6180
> Nov 2 14:47:12 localhost kernel: f774b03e f7f6e444 00000000
> f7f6e400 0000021f 00000000 f8b27f00 f7f6e400
> Nov 2 14:47:12 localhost kernel: Call Trace:
> Nov 2 14:47:12 localhost kernel: [<c01286cd>]
> __request_region+0x6d/0x77
> Nov 2 14:47:12 localhost kernel: [<f8b2638d>]
> net2280_probe+0x2dd/0x4c0 [net2280]
> Nov 2 14:47:12 localhost kernel: [<c021177f>]
> pci_device_probe_static+0x30/0x43
> Nov 2 14:47:12 localhost kernel: [<c02117b4>]
> __pci_device_probe+0x22/0x33
> Nov 2 14:47:12 localhost kernel: [<c02117e0>]
> pci_device_probe+0x1b/0x32
> Nov 2 14:47:12 localhost kernel: [<c027f5af>]
> driver_probe_device+0x21/0x55
> Nov 2 14:47:12 localhost kernel: [<c027f6c1>]
driver_attach+0x46/0x85
> Nov 2 14:47:12 localhost kernel: [<c0205648>]
> kobject_register+0x2e/0x59
> Nov 2 14:47:12 localhost kernel: [<c027fad5>]
bus_add_driver+0x8a/0xb7
> Nov 2 14:47:12 localhost kernel: [<c02119cb>]
> pci_register_driver+0x93/0xaa
> Nov 2 14:47:12 localhost kernel: [<c014680e>]
> sys_init_module+0x132/0x1c1
> Nov 2 14:47:12 localhost kernel: [<c0176d13>] filp_close+0x3f/0x6f
> Nov 2 14:47:12 localhost kernel: [<c010394d>] syscall_call+0x7/0xb
> Nov 2 14:47:12 localhost kernel: Code: ff 8d b4 26 00 00 00 00 8b 40
74
> e9 89 40 63 c7 90 8d b4 26 00 00 00 00 55 89 c5 8d 40 44 57 56 53 83
ec
> 14 89 44 24 10 8b 78 74 <8b> 97 a8 02 00 00 85 d2 0f 85 0f 01 00 00 8b
> 97 b4 02 00 00 8b
>
> This happens immediately after the insmod.
>
> Could some one help.
>
>
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
