kernel panic avec cable usbserial

Pàgina inicial

Reply to this message
Autor: anne-guilde-free
Data:  
A: ML Guilde
Assumpte: kernel panic avec cable usbserial
bonjour,

J'ai un souci quand j'envoie un fax avec mon modem usr 56k message modem
et hylafax.
Le modem est connecté avec un câble usb-serial...
Je ne sais pas d'où vient le problème exactement

Le log de message
Nov 10 12:11:44 nuts FaxGetty[4990]: LOCKWAIT
Nov 10 12:11:45 nuts kernel: Unable to handle kernel NULL pointer 
dereference at virtual address 000000a0
Nov 10 12:11:45 nuts kernel:  printing eip:
Nov 10 12:11:45 nuts kernel: f8a61a23
Nov 10 12:11:45 nuts kernel: *pde = 38fc7067
Nov 10 12:11:45 nuts kernel: Oops: 0000 [#1]
Nov 10 12:11:45 nuts kernel: Modules linked in: appletalk(U) 8139too 
ipt_ULOG ipt_REJECT ipt_MASQUERADE ipt_state ip_nat_ftp ip_conntrack_ftp 
iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables 
ztdummy(U) xpp_usb(U) xpp(U) wcusb(U) wctdm(U) wcfxo(U) wctdm24xxp(U) 
wcte11xp(U) wct1xxp(U) wcte12xp(U) wct4xxp(U) tor2(U) zaptel(U) 
crc_ccitt loop hci_usb bluetooth pl2303 usbserial button battery ac 
yenta_socket pcmcia_core uhci_hcd ehci_hcd 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 
ieee80211 ieee80211_crypt mii bonding(U) dm_snapshot dm_zero dm_mirror 
ext3 jbd dm_mod ata_piix libata sd_mod scsi_mod
Nov 10 12:11:45 nuts kernel: CPU:    0
Nov 10 12:11:45 nuts kernel: EIP:    0060:[<f8a61a23>]    Not tainted VLI
Nov 10 12:11:45 nuts kernel: EFLAGS: 00010246   (2.6.9-67.0.7.EL)
Nov 10 12:11:45 nuts kernel: EIP is at serial_tiocmset+0x33/0x89 [usbserial]
Nov 10 12:11:45 nuts kernel: eax: db7ad000   ebx: 00000000   ecx: 
00000000   edx: e3c11900
Nov 10 12:11:45 nuts kernel: esi: f7fe2a00   edi: 00000000   ebp: 
e3c11900   esp: db3aff6c
Nov 10 12:11:45 nuts kernel: ds: 007b   es: 007b   ss: 0068
Nov 10 12:11:45 nuts kernel: Process faxsend (pid: 2976, 
threadinfo=db3af000 task=dc3aed50)
Nov 10 12:11:45 nuts kernel: Stack: 00005417 f7fe2a00 db7ad000 e3c11900 
c0230682 00000002 00000000 c0380d00
Nov 10 12:11:45 nuts kernel:        bfed9728 e3c11900 00005417 c0181b2d 
bfed9728 f6ef39bc ffffffe7 00747ff4
Nov 10 12:11:45 nuts kernel:        00000004 00000004 00000000 08e2b290 
db3af000 c031dc23 00000004 00005417
Nov 10 12:11:45 nuts kernel: Call Trace:
Nov 10 12:11:45 nuts kernel:  [tty_tiocmset+118/132] tty_tiocmset+0x76/0x84
Nov 10 12:11:45 nuts kernel:  [<c0230682>] tty_tiocmset+0x76/0x84
Nov 10 12:11:45 nuts kernel:  [sys_ioctl+663/822] sys_ioctl+0x297/0x336
Nov 10 12:11:45 nuts kernel:  [<c0181b2d>] sys_ioctl+0x297/0x336
Nov 10 12:11:45 nuts kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Nov 10 12:11:45 nuts kernel:  [<c031dc23>] syscall_call+0x7/0xb
Nov 10 12:11:45 nuts kernel: Code: f8 00 57 89 cf 56 53 8b 98 0c 0a 00 
00 74 1c 0f b6 43 08 50 68 8c 35 a6 f8 68 8f 37 a6 f8 68 f5 37 a6 f8 e8 
ed 2e 6c c7 83 c4 10 <83> bb a0 00 00 00 00 75 22 83 3d 04 71 a6 f8 00 
74 3a 68 8c 35
Nov 10 12:11:45 nuts kernel:  <0>Fatal exception: panic in 5 seconds


Si vous avez une idée...

Cela arrive de plus en plus souvent...
modem, câble, hylafax? Je ne sais pas trop où chercher

Anne