How to resume the connection?

[Michael Schwendt]

On Thu, 18 Aug 2005 01:50:19 +0700, Strong wrote:

> Sometimes my modem brakes up the connection, i don't know how to resume
> it.

The following is a kernel oops and a severe failure. Could be due to
hardware instability. A kernel developer could tell you more.

> Aug 18 01:35:44 STNhome kernel: Unable to handle kernel NULL pointer
> dereference at virtual address 00000000
> Aug 18 01:35:44 STNhome kernel:  printing eip:
> Aug 18 01:35:44 STNhome kernel: c020e7ce
> Aug 18 01:35:44 STNhome kernel: *pde = 11f6b067
> Aug 18 01:35:44 STNhome kernel: Oops: 0000 [#1]
> Aug 18 01:35:44 STNhome kernel: Modules linked in: ppp_deflate
> zlib_deflate ppp_async crc_ccitt ppp_generic slhc cdc_acm radeon drm md5
> ipv6 w83627hf eeprom i2c_sensor i2c_isa ipt_REJECT ipt_state
> ip_conntrack iptable_filter ip_tables video button battery ac uhci_hcd
> ehci_hcd shpchp i2c_i801 i2c_core snd_intel8x0 snd_ac97_codec
> snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device
> snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc
> ext3 jbd
> Aug 18 01:35:44 STNhome kernel: CPU:    0
> Aug 18 01:35:44 STNhome kernel: EIP:    0060:[<c020e7ce>]    Not tainted
> VLI
> Aug 18 01:35:44 STNhome kernel: EFLAGS: 00210246   (2.6.11-1.1369_FC4)
> Aug 18 01:35:44 STNhome kernel: EIP is at get_kobj_path_length+0x19/0x31
> Aug 18 01:35:44 STNhome kernel: eax: 00000000   ebx: 00000000   ecx:
> ffffffff   edx: ffffffff
> Aug 18 01:35:44 STNhome kernel: esi: 00000001   edi: 00000000   ebp:
> df637cb8   esp: d6ab9e04
> Aug 18 01:35:44 STNhome kernel: ds: 007b   es: 007b   ss: 0068
> Aug 18 01:35:44 STNhome kernel: Process pppd (pid: 3106,
> threadinfo=d6ab9000 task=d2ac5550)
> Aug 18 01:35:44 STNhome kernel: Stack: 000000d0 df637c94 d3db9a18
> df637cb8 c020e844 d3db9a00 df637c94 d3db9a18
> Aug 18 01:35:44 STNhome kernel:        d9190988 c0288a86 c03e50e0
> 00000000 ffffffff ffffffff c03917b2 d6ab9e74
> Aug 18 01:35:44 STNhome kernel:        c03917b3 d3db9a00 00000000
> 00000000 d3db9a00 c03e5440 cd81ac53 c0288a52
> Aug 18 01:35:44 STNhome kernel: Call Trace:
> Aug 18 01:35:44 STNhome kernel:  [<c020e844>] kobject_get_path+0xd/0x48
> Aug 18 01:35:44 STNhome kernel:  [<c0288a86>] class_hotplug+0x34/0x1d1
> Aug 18 01:35:44 STNhome kernel:  [<c0288a52>] class_hotplug+0x0/0x1d1
> Aug 18 01:35:44 STNhome kernel:  [<c020f544>] kobject_hotplug
> +0x1a8/0x396
> Aug 18 01:35:44 STNhome kernel:  [<c020edd7>] kobject_release+0x0/0x8
> Aug 18 01:35:44 STNhome kernel:  [<c020f822>] kref_put+0x24/0x82
> Aug 18 01:35:44 STNhome kernel:  [<c01aac2c>] simple_unlink+0x3e/0x47
> Aug 18 01:35:44 STNhome kernel:  [<c0288f60>] class_device_del+0xa6/0xc7
> Aug 18 01:35:44 STNhome kernel:  [<c0288f89>] class_device_unregister
> +0x8/0x10
> Aug 18 01:35:44 STNhome kernel:  [<e09b1626>] acm_tty_close+0xb1/0xe3
> [cdc_acm]
> Aug 18 01:35:44 STNhome kernel:  [<c02590d4>] release_dev+0x157/0x977
> Aug 18 01:35:44 STNhome kernel:  [<c0103894>] do_signal+0x8c/0x111
> Aug 18 01:35:44 STNhome kernel:  [<c03748d1>] schedule_timeout
> +0xdb/0x124
> Aug 18 01:35:44 STNhome kernel:  [<c0259ee3>] tty_release+0x7/0xa
> Aug 18 01:35:44 STNhome kernel:  [<c017c683>] __fput+0x4b/0xfa
> Aug 18 01:35:44 STNhome kernel:  [<c017ae67>] filp_close+0x4f/0x6d
> Aug 18 01:35:44 STNhome kernel:  [<c0103a51>] syscall_call+0x7/0xb
> Aug 18 01:35:44 STNhome kernel: Code: 89 c6 85 c0 74 ee 89 d8 e8 67 0a
> fc ff 89 f0 5b 5e c3 55 57 56 53 89 c5 be 01 00 00 00 31 db ba ff ff ff
> ff 8b 7d 00 89 d1 89 d8 <f2> ae f7 d1 49 01 f1 8d 71 01 8b 6d 24 85 ed
> 75 e8 89 f0 5b 5e