Greg KH wrote:
> On Thu, Oct 12, 2000 at 08:06:46AM -0400, tytso@mit.edu wrote:
> > * USB: booting with USB compiled into kernel causes a lot of syslog
> > entries as the root hubs are probed by all drivers (this is
> > especially obnoxious as the usb-serial drivers start up)
> Fixed in test9. If anyone still sees this, please let me know.
>
> > * USB: fix setting urb->dev in printer, acm, bluetooth, all serial
> > drivers (Greg KH) {CRITICAL}
> Fixed in test10-pre1.
>
> > * USB: fix usb-uhci setting urb->dev = NULL at correct places only
> > {CRITICAL}
> Fixed in test10-pre1.
>
> thanks,
>
> greg k-h
>
> --
> greg@(kroah|wirex).com
> http://immunix.org/~greg
>
USB still have problems, when starting to grab with my ov511 webcam i got the
attached oops. This bug appeared
in test9-preX(X beeing at least > 2) series. Some people have claimed that
test10-pre1 fixed the problem, but
the bug is still present in the last two pre(test10-pre1 and test10-pre2).
To be noted:
-this oops is obtained with "Enforce USB bandwidth allocation", but it occurs
in the same place when disabled
-I'm using usb-uhci
-the attached oops is truncated as each following schedule call produce a new
oops
-- %--IRIN->-Institut-de-Recherche-en-Informatique-de-Nantes-----------------% % FORT David, % % 7 avenue de la morvandière 0240726275 % % 44470 Thouare, France epopo@onetelnet.fr % % ICU:78064991 AIM: enlighted popo fort@irin.univ-nantes.fr % %--LINUX-HTTPD-PIOGENE----------------------------------------------------% % -datamining <-/ | .~. % % -networking/flashed PHP3 coming soon | /V\ L I N U X % % -opensource | // \\ >Fear the Penguin< % % -GNOME/enlightenment/GIMP | /( )\ % % feel enlighted.... | ^^-^^ % % http://ibonneace.dnsalias.org/ when connected % %-------------------------------------------------------------------------%
ksymoops 2.3.4 on i686 2.4.0-test10. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.0-test10/ (default) -m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options.
Unable to handle kernel NULL pointer dereference at virtual address 000000a0 c8c7365d *pde = 00000000 Oops: 0000 CPU: 1 EIP: 0010:[<c8c7365d>] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00013246 eax: 00000000 ebx: c6e26480 ecx: 00000000 edx: 00000028 esi: c6e26480 edi: c2bb8d9c ebp: 00000000 esp: c0d05f28 ds: 0018 es: 0018 ss: 0018 Process X (pid: 974, stackpage=c0d05000) Stack: c1b236a8 c8c84814 00000000 c6e26480 00000001 c1b236a8 c2bb8d80 c2bb8d9c 00000001 00000000 00000000 c8c849bf c2bb8d80 c6e26488 c2fc4b60 04000001 00000020 0000000a c0020020 c010be71 0000000a c2bb8d80 c0d05fc4 c0282740 Call Trace: [<c8c84814>] [<c8c849bf>] [<c010be71>] [<c010c056>] [<c010a7c0>] Code: 8b 91 a0 00 00 00 8b 43 30 29 42 28 83 7c 24 10 00 74 10 8b
>>EIP; c8c7365d <[usbcore]usb_release_bandwidth+9/60> <===== Trace; c8c84814 <[usb-uhci]process_urb+d4/1f0> Trace; c8c849bf <[usb-uhci]uhci_interrupt+8f/e8> Trace; c010be71 <handle_IRQ_event+4d/78> Trace; c010c056 <do_IRQ+a6/f4> Trace; c010a7c0 <ret_from_intr+0/20> Code; c8c7365d <[usbcore]usb_release_bandwidth+9/60> 00000000 <_EIP>: Code; c8c7365d <[usbcore]usb_release_bandwidth+9/60> <===== 0: 8b 91 a0 00 00 00 mov 0xa0(%ecx),%edx <===== Code; c8c73663 <[usbcore]usb_release_bandwidth+f/60> 6: 8b 43 30 mov 0x30(%ebx),%eax Code; c8c73666 <[usbcore]usb_release_bandwidth+12/60> 9: 29 42 28 sub %eax,0x28(%edx) Code; c8c73669 <[usbcore]usb_release_bandwidth+15/60> c: 83 7c 24 10 00 cmpl $0x0,0x10(%esp,1) Code; c8c7366e <[usbcore]usb_release_bandwidth+1a/60> 11: 74 10 je 23 <_EIP+0x23> c8c73680 <[usbcore]usb_release_bandwidth+2c/60> Code; c8c73670 <[usbcore]usb_release_bandwidth+1c/60> 13: 8b 00 mov (%eax),%eax
Aiee, killing interrupt handler invalid operand: 0000 CPU: 1 EIP: 0010:[<c0116889>] EFLAGS: 00013282 eax: 0000001b ebx: 00000000 ecx: 0000001b edx: c021a8e8 esi: c5bce9e0 edi: c0d04000 ebp: c0d05cec esp: c0d05cac ds: 0018 es: 0018 ss: 0018 Process X (pid: 974, stackpage=c0d05000) Stack: c01e6e45 c01e7016 000002b8 00000000 c5bce9e0 c0d04000 00003286 c5bce9e0 c0d04000 c5bcea28 c0185373 c12b9e60 00000000 00000001 c0d04000 00000000 c5bcea28 c0131bd9 c13dc080 c13dfc00 00000000 00000000 c0d05d08 01234567 Call Trace: [<c01e6e45>] [<c01e7016>] [<c0185373>] [<c0131bd9>] [<c0132bf9>] [<c014eb64>] [<c014ed35>] [<c014ee67>] [<c010a8b6>] [<c0150bbd>] [<c014fca8>] [<c0131901>] [<c0130892>] [<c011b0cb>] [<c011b89c>] [<c010abf2>] [<c01127a7>] [<c01e661e>] [<c0112470>] [<c010a830>] [<c8c7365d>] [<c8c84814>] [<c8c849bf>] [<c010be71>] [<c010c056>] [<c010a7c0>] Code: 0f 0b 90 8d 74 26 00 8d 65 cc 5b 5e 5f 89 ec 5d c3 89 f6 55
>>EIP; c0116889 <schedule+611/624> <===== Trace; c01e6e45 <call_spurious_interrupt+5925/7a88> Trace; c01e7016 <call_spurious_interrupt+5af6/7a88> Trace; c0185373 <do_ide_request+f/14> Trace; c0131bd9 <__wait_on_buffer+b9/e0> Trace; c0132bf9 <bread+45/64> Trace; c014eb64 <read_block_bitmap+38/84> Trace; c014ed35 <__load_block_bitmap+185/198> Trace; c014ee67 <ext2_free_blocks+11f/2a8> Trace; c010a8b6 <nmi+1e/30> Trace; c0150bbd <ext2_discard_prealloc+59/94> Trace; c014fca8 <ext2_release_file+14/1c> Trace; c0131901 <fput+39/e8> Trace; c0130892 <filp_close+b2/bc> Trace; c011b0cb <put_files_struct+4f/b8> Trace; c011b89c <do_exit+130/284> Trace; c010abf2 <die+56/58> Trace; c01127a7 <do_page_fault+337/410> Trace; c01e661e <call_spurious_interrupt+50fe/7a88> Trace; c0112470 <do_page_fault+0/410> Trace; c010a830 <error_code+34/3c> Trace; c8c7365d <[usbcore]usb_release_bandwidth+9/60> Trace; c8c84814 <[usb-uhci]process_urb+d4/1f0> Trace; c8c849bf <[usb-uhci]uhci_interrupt+8f/e8> Trace; c010be71 <handle_IRQ_event+4d/78> Trace; c010c056 <do_IRQ+a6/f4> Trace; c010a7c0 <ret_from_intr+0/20> Code; c0116889 <schedule+611/624> 00000000 <_EIP>: Code; c0116889 <schedule+611/624> <===== 0: 0f 0b ud2a <===== Code; c011688b <schedule+613/624> 2: 90 nop Code; c011688c <schedule+614/624> 3: 8d 74 26 00 lea 0x0(%esi,1),%esi Code; c0116890 <schedule+618/624> 7: 8d 65 cc lea 0xffffffcc(%ebp),%esp Code; c0116893 <schedule+61b/624> a: 5b pop %ebx Code; c0116894 <schedule+61c/624> b: 5e pop %esi Code; c0116895 <schedule+61d/624> c: 5f pop %edi Code; c0116896 <schedule+61e/624> d: 89 ec mov %ebp,%esp Code; c0116898 <schedule+620/624> f: 5d pop %ebp Code; c0116899 <schedule+621/624> 10: c3 ret Code; c011689a <schedule+622/624> 11: 89 f6 mov %esi,%esi Code; c011689c <__wake_up+0/18c> 13: 55 push %ebp
1 warning issued. Results may not be reliable.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Oct 15 2000 - 21:00:23 EST