Hi all,
Running a Centos 4.2 default config in a P4 1.7 Mhz 512 MB Usb 1.1 (Acer Aspire
1400 XV Laptop) with a usb2serial interface plugged from the system boot, and
using that line as console line for a remote device, i had the following kernel
panic after few times performing the "reset" command in the
gnome-terminal due
font corruption, i had this kernel panic:
Dec 14 23:58:10 smarteyebox kernel: Unable to handle kernel NULL pointer
dereference at virtual address 00000080
Dec 14 23:58:10 smarteyebox kernel: printing eip:
Dec 14 23:58:10 smarteyebox kernel: e0b598da
Dec 14 23:58:10 smarteyebox kernel: *pde = 00000000
Dec 14 23:58:10 smarteyebox kernel: Oops: 0000 [#1]
Dec 14 23:58:10 smarteyebox kernel: Modules linked in: ppdev nfs lockd radeon
parport_pc lp parport autofs4 eeprom i2c_sensor i2c_i801 i2c_dev i2c_core sunrpc
ds ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables dm_multipath
button battery ac hci_usb bluetooth joydev ftdi_sio usbserial yenta_socket
pcmcia_core uhci_hcd shpchp 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 e100 mii floppy dm_snapshot dm_zero
dm_mirror ext3 jbd dm_mod
Dec 14 23:58:10 smarteyebox kernel: CPU: 0
Dec 14 23:58:10 smarteyebox kernel: EIP: 0060:[<e0b598da>] Not
tainted VLI
Dec 14 23:58:10 smarteyebox kernel: EFLAGS: 00210246 (2.6.9-22.0.1.EL)
Dec 14 23:58:10 smarteyebox kernel: EIP is at ftdi_set_termios+0x1d/0x479
[ftdi_sio]
Dec 14 23:58:10 smarteyebox kernel: eax: 00000000 ebx: def08500 ecx:
c035c940 edx: def08500
Dec 14 23:58:10 smarteyebox kernel: esi: dfdc2c00 edi: dedd8c00 ebp:
dedd8c00 esp: dad56e6c
Dec 14 23:58:10 smarteyebox kernel: ds: 007b es: 007b ss: 0068
Dec 14 23:58:10 smarteyebox kernel: Process cat (pid: 16510, threadinfo=dad56000
task=d9fa2780)
Dec 14 23:58:10 smarteyebox kernel: Stack: dedd8c00 0000869d 00000000 def08500
dfdc2c00 dedd8c00 00000000 e0b58b24
Dec 14 23:58:10 smarteyebox kernel: 00000040 00000000 00000000 dad56ea7
00000000 00001388 c018103f dad56f58
Dec 14 23:58:10 smarteyebox kernel: 00000000 c0178317 c17c6630 dfdccf80
0804c9c0 00000000 00200246 00000101
Dec 14 23:58:10 smarteyebox kernel: Call Trace:
Dec 14 23:58:10 smarteyebox kernel: [<e0b58b24>] ftdi_open+0x88/0x20a
[ftdi_sio]
Dec 14 23:58:10 smarteyebox kernel: [<c018103f>] dput+0x33/0x423
Dec 14 23:58:10 smarteyebox kernel: [<c0178317>] link_path_walk+0x90/0xb9
Dec 14 23:58:10 smarteyebox kernel: [<e0b172d5>] serial_open+0x95/0xd9
[usbserial]
Dec 14 23:58:10 smarteyebox kernel: [<c0223c23>] tty_open+0x182/0x3a6
Dec 14 23:58:10 smarteyebox kernel: [<c01724cc>] chrdev_open+0x325/0x3b9
Dec 14 23:58:10 smarteyebox kernel: [<c0167287>] dentry_open+0xbd/0x180
Dec 14 23:58:10 smarteyebox kernel: [<c01671c4>] filp_open+0x36/0x3c
Dec 14 23:58:10 smarteyebox kernel: [<c030e078>] __cond_resched+0x14/0x3b
Dec 14 23:58:10 smarteyebox kernel: [<c01e5d8e>]
direct_strncpy_from_user+0x3e/0x5d
Dec 14 23:58:10 smarteyebox kernel: [<c0167688>] sys_open+0x31/0x7d
Dec 14 23:58:10 smarteyebox kernel: [<c030f8cb>] syscall_call+0x7/0xb
Dec 14 23:58:10 smarteyebox kernel: Code: e8 2d 7d 5c df 83 c4 14 59 5b 5e 5f 5d
c3 55 57 56 89 c6 53 83 ec 0c 8b 00 83 3d 80 f4 b5 e0 00 8b 96 18 01 00 00 8b 28
8b 46 04 <8b> 80 80 00 00 00 89 54 24 04 8b 00 89 04 24 74 17 68 e1 a4 b5
Dec 14 23:58:10 smarteyebox kernel: <0>Fatal exception: panic in 5
seconds
Dec 15 00:11:05 smarteyebox syslogd 1.4.1: restart.
I'm not sure if it is due to the usb2serial adapter but i think so because
no
panic in that system before.
To reproduce it:
a) In a gnome-terminal im executing a bash script like this:
FILE=/root/dump
rm $FILE
stty cs8 ignbrk cread clocal raw 4800 -echo $1 < /dev/ttyUSB0
killall cat
cat /dev/ttyUSB0 | tee $FILE &
cat > /dev/ttyUSB0 ; kill %%
b) The other side is a modem with an available console via serial line where i
connect the USB2serial cable
c) From the modem power-on i start detecting hard font corruption in
gnome-terminal, if i break the link (CTRL+C) and i perform the '$ reset'
command, everything comes back ok, but after connecting again using the script
im having the same thing if the modem restarts (no matter if there is a modem
hard reset or sw reset, i mean, power on all the time in the modem)
d) After few 'resets' in gnome console, the kernel panic is happening.
Don't know where to send this panic, im sending it to this list, feel free
to
tell me if i have to inform others or use other reporting tools for kernel
panics... help appreciated.
TIA
Jose.
--
Linux smarteyebox.stigmatedbrain.net 2.6.9-22.0.1.EL i686 GNU/Linux
11:55:01 up 11:36, 12 users, load average: 4.52, 3.40, 2.53
---------------------------------------------------------
XXXI: The optimum committee has no members. XXXII: Hiring consultants to conduct
studies can be an excellent means of turning problems into gold -- your problems
into their gold. XXXIII: Fools rush in where incumbents fear to tread. XXXIV:
The process of competitively selecting contractors to perform work is based on a
system of rewards and penalties, all distributed randomly. XXXV: The weaker the
data available upon which to base one's conclusion, the greater the
precision
which should be quoted in order to give the data authenticity. -- Norman
Augustine
