plustek: Device or resource busy


Previous by date: 24 Jan 2001 01:38:39 -0000 Re: Plustek 9636T scans color/grey incorrectly FURTHER, kevin
Next by date: 24 Jan 2001 01:38:39 -0000 Re: Plustek 9636T scans color/grey incorrectly FURTHER, Mark Bratcher
Previous in thread: 24 Jan 2001 01:38:39 -0000 Re: Device or resource busy, Jaeger, Gerhard
Next in thread: 24 Jan 2001 01:38:39 -0000 Re: Device or resource busy, G. Jaeger

Subject: Device or resource busy
From: François ####@####.####
Date: 24 Jan 2001 01:38:39 -0000
Message-Id: <3A6E32E3.71E32680@free.fr>

I've just compiled sane 1.0.4 and pt_drv 0.37-24
bur the driver don't seem to load whith  modprobe.
I have these error messages :


Jan 24 02:13:19 CHOUPI kernel: parport0: PC-style at 0x278 [SPP]
Jan 24 02:13:20 CHOUPI kernel: parport_probe: failed
Jan 24 02:13:20 CHOUPI kernel: parport0: no IEEE-1284 device present.
Jan 24 02:13:20 CHOUPI kernel: lp0: using parport0 (polling).
Jan 24 02:15:27 CHOUPI kernel:
*********************************************
Jan 24 02:15:27 CHOUPI kernel: pt_drv: init_module()
Jan 24 02:15:27 CHOUPI kernel: pt_drv : driver version 0.37-24
Jan 24 02:15:27 CHOUPI kernel: ptdrvInit(0)
Jan 24 02:15:27 CHOUPI kernel: Init settings done
Jan 24 02:15:27 CHOUPI kernel: ScanData = 0xc05e4000
Jan 24 02:15:27 CHOUPI kernel: Requested port at 0x378
Jan 24 02:15:27 CHOUPI kernel: ptdrvShutdown()
Jan 24 02:15:27 CHOUPI kernel: cleanup device 0
Jan 24 02:15:27 CHOUPI kernel: Lamp-Timer stopped !
Jan 24 02:15:27 CHOUPI kernel: Try to claim the parport
Jan 24 02:15:27 CHOUPI kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000004
Jan 24 02:15:27 CHOUPI kernel: current->tss.cr3 = 02340000, %%cr3 =
02340000
Jan 24 02:15:27 CHOUPI kernel: *pde = 00000000
Jan 24 02:15:27 CHOUPI kernel: Oops: 0000
Jan 24 02:15:27 CHOUPI kernel: CPU:    0
Jan 24 02:15:27 CHOUPI kernel: EIP:   
0010:[3c59x:__insmod_3c59x_S.bss_L4+22342/3554974]
Jan 24 02:15:27 CHOUPI kernel: EFLAGS: 00010282
Jan 24 02:15:27 CHOUPI kernel: eax: 00000000   ebx: c05e4000   ecx:
00000006   edx: c3898000
Jan 24 02:15:27 CHOUPI kernel: esi: 00000000   edi: c4dd5c64   ebp:
00000000   esp: c23bfe7c
Jan 24 02:15:27 CHOUPI kernel: ds: 0018   es: 0018   ss: 0018
Jan 24 02:15:27 CHOUPI kernel: Process modprobe (pid: 963, process nr:
50, stackpage=c23bf000)
Jan 24 02:15:27 CHOUPI kernel: Stack: c4dd5c64 00000019 c05e4000
00000000 c4dd5c64 c4dc7c40 00000000 00000001
Jan 24 02:15:27 CHOUPI kernel:        c02710d8 00000015 c05e4000
c05e4000 00000000 c4dceb80 c4dd415f 00000001
Jan 24 02:15:27 CHOUPI kernel:        c02710d4 c4dcefc7 c05e4000
00000001 c4dc004f c4dcefbe c05e4000 00000000
Jan 24 02:15:27 CHOUPI kernel: Call Trace:
[3c59x:__insmod_3c59x_S.bss_L4+343496/3233820] [3c59x:__insmod_3c59x_S
.bss_L4+343496/3233820] [3c59x:__insmod_3c59x_S.bss_L4+286116/3291200]
[3c59x:__insmod_3c59x_S.bss_L4+314596/3262
720] [3c59x:__insmod_3c59x_S.bss_L4+336579/3240737]
[3c59x:__insmod_3c59x_S.bss_L4+315691/3261625] [3c59x:__insmo
d_3c59x_S.bss_L4+254387/3322929]
Jan 24 02:15:27 CHOUPI kernel:       
[3c59x:__insmod_3c59x_S.bss_L4+315682/3261634]
[3c59x:__insmod_3c59x_S.bss_
L4+254387/3322929] [3c59x:__insmod_3c59x_S.bss_L4+315209/3262107]
[3c59x:__insmod_3c59x_S.bss_L4+343496/3233820]
[3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929] [3c59x:__insmod_3c5
9x_S.bss_L4+319003/3258313]
[3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
Jan 24 02:15:27 CHOUPI kernel:       
[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929]
[3c59x:__insmod_3c59x_S.bss_
L4+254380/3322936] [3c59x:__insmod_3c59x_S.bss_L4+254308/3323008]
[3c59x:__insmod_3c59x_S.bss_L4+254387/3322929]
[3c59x:__insmod_3c59x_S.bss_L4+254380/3322936]
[sys_init_module+1095/1208] [3c59x:__insmod_3c59x_S.bss_L4+57700/3
519616] [3c59x:__insmod_3c59x_S.bss_L4+254380/3322936]
Jan 24 02:15:27 CHOUPI kernel:        [error_code+45/64]
[system_call+52/64]
Jan 24 02:15:27 CHOUPI kernel: Code: 8b 5e 04 39 73 1c 75 1a 83 c4 fc 8b
06 50 8b 43 08 50 68 02

when i use depmod -e, i have this message :
depmod: *** Unresolved symbols in
/lib/modules/2.2.17-21mdk/misc/pt_drv.o
depmod:         proc_register
depmod:         __generic_copy_from_user
depmod:         parport_unregister_device
depmod:         get_fast_time
depmod:         schedule
depmod:         __udelay
depmod:         parport_enumerate
depmod:         kmalloc
depmod:         unregister_chrdev
depmod:         register_chrdev
depmod:         vfree
depmod:         parport_register_device
depmod:         proc_unregister
depmod:         del_timer
depmod:         kfree
depmod:         vmalloc
depmod:         parport_claim
depmod:         parport_release
depmod:         proc_root
depmod:         sprintf
depmod:         jiffies
depmod:         printk
depmod:         add_timer
depmod:         __const_udelay
depmod:         __generic_copy_to_user

So any idea about what's going wrong ?
Thanks
François

Previous by date: 24 Jan 2001 01:38:39 -0000 Re: Plustek 9636T scans color/grey incorrectly FURTHER, kevin
Next by date: 24 Jan 2001 01:38:39 -0000 Re: Plustek 9636T scans color/grey incorrectly FURTHER, Mark Bratcher
Previous in thread: 24 Jan 2001 01:38:39 -0000 Re: Device or resource busy, Jaeger, Gerhard
Next in thread: 24 Jan 2001 01:38:39 -0000 Re: Device or resource busy, G. Jaeger


Powered by ezmlm-browse 0.20.