Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4)

Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4)

[baoyb]

Hi All:

We are using a USB 3G card(HUAWEI e180) and wvdial+pppd(version 2.4.5) 
program. Sometimes kernel will crash when pppd disconnect the link. Our cpu 
platform is AMCC ppc405EX and kernel version is 2.6.37-rc4.
The following is log info when oops happened.

Unable to handle kernel paging request for data at address 0x000000d8
Faulting instruction address: 0xc0175a5c
Oops: Kernel access of bad area, sig: 11 [#1]
PowerPC 40x Platform
last sysfs file: /sys/kernel/uevent_seqnum
Modules linked in:
NIP: c0175a5c LR: c0175d9c CTR: c0211b6c
REGS: c77f7d50 TRAP: 0300   Not tainted  (2.6.37-rc4)
MSR: 00021030 <ME,CE,IR,DR>  CR: 88482028  XER: 2000005f
DEAR: 000000d8, ESR: 00000000
TASK = c71ec000[1500] 'wvdial' THREAD: c284e000
GPR00: 00021030 c77f7e00 c71ec000 00000000 0000000e 00000000 0000000e 
c0410580
GPR08: c683db00 00000000 00000001 c03c51f8 88482028 10073ef4 ffffffb9 
ffffff94
GPR16: 00000000 fde037e0 00200200 00100100 00000001 ffffff8d c712ca0c 
00000000
GPR24: c71120d4 00000000 00000000 0000000e 00021030 00000000 00000000 
0000000e
NIP [c0175a5c] tty_buffer_request_room+0x2c/0x194
LR [c0175d9c] tty_insert_flip_string_fixed_flag+0x3c/0xb0
Call Trace:
[c77f7e00] [00000003] 0x3 (unreliable)
[c77f7e30] [c0175d9c] tty_insert_flip_string_fixed_flag+0x3c/0xb0
[c77f7e60] [c0211cd0] usb_wwan_indat_callback+0x164/0x170
[c77f7e80] [c01e541c] usb_hcd_giveback_urb+0x5c/0xdc
[c77f7e90] [c01f65f0] ehci_urb_done+0xe4/0xf8
[c77f7eb0] [c01f66b8] qh_completions+0xb4/0x4d0
[c77f7f10] [c01f7788] ehci_work+0xdc/0x990
[c77f7f60] [c01fb014] ehci_irq+0x1c0/0x224
[c77f7f90] [c01e5984] usb_hcd_irq+0x68/0xa8
[c77f7fa0] [c0052848] handle_IRQ_event+0x54/0x12c
[c77f7fc0] [c00553ac] handle_level_irq+0xa0/0x13c
[c77f7fd0] [c0017ca4] uic_irq_cascade+0x100/0x128
[c77f7ff0] [c000cdb4] call_handle_irq+0x18/0x28
[c284ff10] [c0005230] do_IRQ+0xa4/0x140
[c284ff40] [c000da98] ret_from_except+0x0/0x18
Instruction dump:
4e800020 9421ffd0 7c0802a6 7d800026 bf410018 90010034 91810014 7c7e1b78
7c9f2378 7f8000a6 5780045e 7c000124 <83a300d8> 2e1d0000 4192014c 813d0010
Kernel panic - not syncing: Fatal exception in interrupt
Call Trace:
[c77f7c80] [c000700c] show_stack+0x44/0x16c (unreliable)
[c77f7cc0] [c00211f4] panic+0xa4/0x1dc
[c77f7d10] [c000abd8] die+0x190/0x19c
[c77f7d30] [c001091c] bad_page_fault+0xc0/0x108
[c77f7d40] [c000d904] handle_page_fault+0x7c/0x80
[c77f7e00] [00000003] 0x3
[c77f7e30] [c0175d9c] tty_insert_flip_string_fixed_flag+0x3c/0xb0
[c77f7e60] [c0211cd0] usb_wwan_indat_callback+0x164/0x170
[c77f7e80] [c01e541c] usb_hcd_giveback_urb+0x5c/0xdc
[c77f7e90] [c01f65f0] ehci_urb_done+0xe4/0xf8
[c77f7eb0] [c01f66b8] qh_completions+0xb4/0x4d0
[c77f7f10] [c01f7788] ehci_work+0xdc/0x990
[c77f7f60] [c01fb014] ehci_irq+0x1c0/0x224
[c77f7f90] [c01e5984] usb_hcd_irq+0x68/0xa8
[c77f7fa0] [c0052848] handle_IRQ_event+0x54/0x12c
[c77f7fc0] [c00553ac] handle_level_irq+0xa0/0x13c
[c77f7fd0] [c0017ca4] uic_irq_cascade+0x100/0x128
[c77f7ff0] [c000cdb4] call_handle_irq+0x18/0x28
[c284ff10] [c0005230] do_IRQ+0xa4/0x140
[c284ff40] [c000da98] ret_from_except+0x0/0x18
Rebooting in 1 seconds..


Any suggestions will be very appreciated.

Regards,

YunBing

 Shanghai Accurate Video Info-Tech Co.,Ltd.

Room 302-306, No.1 Building, No.33 Le Shan Road, Shanghai, 200030

TEL: 86-21-51556408-17(Ext.)

FAX: 86-21-51556407

Company Homepage: www.avit.org.cn 

Re: Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4)

[Greg KH]

On Wed, Dec 08, 2010 at 09:55:09PM +0800, baoyb wrote:
> Hi All:
> 
> We are using a USB 3G card(HUAWEI e180) and wvdial+pppd(version
> 2.4.5) program. Sometimes kernel will crash when pppd disconnect the
> link. Our cpu platform is AMCC ppc405EX and kernel version is
> 2.6.37-rc4.

Can you try 2.6.37-rc5 and see if that fixed the issue?  A number of tty
fixes went in between those two versions that should have resolved this.

thanks,

greg k-h

Re: Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4)

[Maciej Rutecki]

On środa, 8 grudnia 2010 o 14:55:09 baoyb wrote:
> Hi All:
> 
> We are using a USB 3G card(HUAWEI e180) and wvdial+pppd(version 2.4.5)
> program. Sometimes kernel will crash when pppd disconnect the link. Our cpu
> platform is AMCC ppc405EX and kernel version is 2.6.37-rc4.
> The following is log info when oops happened.
> 

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=24582
for your bug report, please add your address to the CC list in there, thanks!

-- 
Maciej Rutecki
http://www.maciek.unixy.pl

Re: Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4)

[baoyb]

Hi All:
I have tested 2.6.37-rc5 and the bug still exist.
I also tested 2.6.32.24, the oops frequency is much lower than 2.6.37. (Only 
happened 2 times in one week).

Regards,
Baoyb

--------------------------------------------------
From: "Greg KH" <gregkh@suse.de>
Sent: Wednesday, December 08, 2010 11:07 PM
To: "baoyb" <baoyb@avit.org.cn>
Cc: <linux-kernel@vger.kernel.org>; <alan@linux.intel.com>
Subject: Re: Kernel Oops at tty_buffer_request_room when using pppd program 
(2.6.37-rc4)

> On Wed, Dec 08, 2010 at 09:55:09PM +0800, baoyb wrote:
>> Hi All:
>>
>> We are using a USB 3G card(HUAWEI e180) and wvdial+pppd(version
>> 2.4.5) program. Sometimes kernel will crash when pppd disconnect the
>> link. Our cpu platform is AMCC ppc405EX and kernel version is
>> 2.6.37-rc4.
>
> Can you try 2.6.37-rc5 and see if that fixed the issue?  A number of tty
> fixes went in between those two versions that should have resolved this.
>
> thanks,
>
> greg k-h
>
> __________ Information from ESET NOD32 Antivirus, version of virus 
> signature database 5682 (20101207) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
> 

Re: Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4)

[Greg KH]

On Thu, Dec 16, 2010 at 07:00:16PM +0800, baoyb wrote:
> Hi All:
> I have tested 2.6.37-rc5 and the bug still exist.
> I also tested 2.6.32.24, the oops frequency is much lower than
> 2.6.37. (Only happened 2 times in one week).

{sigh}

I really don't know what to say here.  Do you have the full backtrace of
the oops with 2.6.37?  Is the device disconnecting right before the oops
happens?

thanks,

greg k-h