Re: 3.7-rc3 oops on reboot

2012-10-29 Thread Alexandre Pereira da Silva
On Mon, Oct 29, 2012 at 12:41 PM, Roland Stigge  wrote:
> On 10/29/2012 02:51 PM, Alexandre Pereira da Silva wrote:
>>> I just tried both on a PHY3250 reference machine, and on a custom board
>>> and couldn't reproduce sth. like this. Booted the kernel and connected
>>> the ethernet cable later on, as well as with cable connected on boot.
>>
>> This is happening on my custom board. I didn't try this on the
>> reference board yet.
>>
>>> Any related patches applied? Can you reproduce this on a reference
>>> machine? Can you provide a .config for this? Any more detail about how
>>> this could be reproduced?
>>
>> No patches applied. I'm trying to bisect this. This happens on a clean
>> -rc1 as well. Doesn't happen on v3.6.
>>
>> Attached my .config
>>
>> To reproduce this, I am just running "reboot". I have the ethernet
>> cable always connected here.
>
> Just tried this with your .config on the PHY3250 (w/o your initrd
> thought) but couldn't reproduce the issue.
>
> Maybe it's related to your Micrel ethernet PHY (activated in your
> config) which I don't have hardware for?
>
> Otherwise, we would need to have a look at your devicetree.

Thanks for testing. I will investigate this further to see if I can
narrow source of the problem.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: 3.7-rc3 oops on reboot

2012-10-29 Thread Roland Stigge
On 10/29/2012 02:51 PM, Alexandre Pereira da Silva wrote:
>> I just tried both on a PHY3250 reference machine, and on a custom board
>> and couldn't reproduce sth. like this. Booted the kernel and connected
>> the ethernet cable later on, as well as with cable connected on boot.
> 
> This is happening on my custom board. I didn't try this on the
> reference board yet.
> 
>> Any related patches applied? Can you reproduce this on a reference
>> machine? Can you provide a .config for this? Any more detail about how
>> this could be reproduced?
> 
> No patches applied. I'm trying to bisect this. This happens on a clean
> -rc1 as well. Doesn't happen on v3.6.
> 
> Attached my .config
> 
> To reproduce this, I am just running "reboot". I have the ethernet
> cable always connected here.

Just tried this with your .config on the PHY3250 (w/o your initrd
thought) but couldn't reproduce the issue.

Maybe it's related to your Micrel ethernet PHY (activated in your
config) which I don't have hardware for?

Otherwise, we would need to have a look at your devicetree.

Roland
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: 3.7-rc3 oops on reboot

2012-10-29 Thread Alexandre Pereira da Silva
Roland, thanks for the quick response.

> I just tried both on a PHY3250 reference machine, and on a custom board
> and couldn't reproduce sth. like this. Booted the kernel and connected
> the ethernet cable later on, as well as with cable connected on boot.

This is happening on my custom board. I didn't try this on the
reference board yet.

> Any related patches applied? Can you reproduce this on a reference
> machine? Can you provide a .config for this? Any more detail about how
> this could be reproduced?

No patches applied. I'm trying to bisect this. This happens on a clean
-rc1 as well. Doesn't happen on v3.6.

Attached my .config

To reproduce this, I am just running "reboot". I have the ethernet
cable always connected here.


.config
Description: Binary data


Re: 3.7-rc3 oops on reboot

2012-10-29 Thread Roland Stigge
On 10/29/2012 01:08 PM, Alexandre Pereira da Silva wrote:
> I am getting oops on 3.7-rc3 at reboot.
> 
> This is an LPC32XX machine. This problem only happens when I connect
> the ethernet cable and get an IP address.
> 
> Here are the kernel messages.
> [   38.57] Unable to handle kernel paging request at virtual
> address a014
> [   38.57] pgd = c173
> [   38.58] [a014] *pgd=
> [   38.58] Internal error: Oops: 5 [#1] PREEMPT ARM
> [   38.58] Modules linked in:
> [   38.58] CPU: 0Not tainted  (3.7.0-rc3 #4)
> [   38.58] PC is at trie_firstleaf+0xc/0x2c
> [   38.58] LR is at fib_table_flush+0x1c/0x170
> [   38.58] pc : []lr : []psr: a013
> [   38.58] sp : c1719d50  ip : c1719d60  fp : c1719d5c
> [   38.58] r10:   r9 :   r8 : c16341e0
> [   38.58] r7 : c09d2c24  r6 : 0001  r5 : a000  r4 : 03fc
> [   38.58] r3 : c18dac00  r2 : c09c6fc0  r1 : c09c6fc0  r0 : a014
> [   38.58] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment 
> user
> [   38.58] Control: 0005317f  Table: 8173  DAC: 0015
> [   38.58] Process ifconfig (pid: 396, stack limit = 0xc17181b8)
> [   38.58] Stack: (0xc1719d50 to 0xc171a000)
> [   38.58] 9d40: c1719d9c
> c1719d60 c0298dec c02965a0
> [   38.58] 9d60: c170f308 c14d42e0  a014 c16341e0
> 03fc a000 0001
> [   38.58] 9d80: c09d2c24 c16341e0   c1719dbc
> c1719da0 c0294244 c0298de0
> [   38.58] 9da0: c160f800 c160f800   c1719dd4
> c1719dc0 c0294294 c0294224
> [   38.58] 9dc0:  c16341e0 c1719dec c1719dd8 c0294bf0
> c0294284 0002 
> [   38.58] 9de0: c1719e14 c1719df0 c003e810 c0294b60 
> c09d4698  c16341e0
> [   38.58] 9e00: 0002  c1719e3c c1719e18 c003ea9c
> c003e7e0  c1719e28
> [   38.58] 9e20: c16341e0   c16341e0 c1719e54
> c1719e40 c003ead4 c003ea5c
> [   38.58] 9e40:   c1719e8c c1719e58 c028b9bc
> c003eac4  c145edec
> [   38.58] 9e60: c1719e8c c16341e0  c160f800 c145ede0
> c145edec  
> [   38.58] 9e80: c1719ea4 c1719e90 c028ba94 c028b828 
> c09d2c24 c1719f14 c1719ea8
> [   38.58] 9ea0: c028d278 c028ba88 c003d890  8916
> bef74c18 30687465 
> [   38.58] 9ec0:   0002  0001
> 00084a10 0002 
> [   38.58] 9ee0: 0001 00084a10 1000 8914 bef74c18
> bef74c18 8916 0003
> [   38.58] 9f00: c1718000  c1719f2c c1719f18 c028e284
> c028cf18 c1404420 8916
> [   38.58] 9f20: c1719f4c c1719f30 c022ed8c c028e1c4 c022eb6c
> 0003 bef74c18 bef74c18
> [   38.58] 9f40: c1719f74 c1719f50 c009e5e8 c022eb7c 000ac000
> 000ad000 bef74c18 8916
> [   38.58] 9f60: c14dcbe0  c1719fa4 c1719f78 c009e66c
> c009e304 c0080184 
> [   38.58] 9f80: b6f73ee4 bef74c18 8916 0003 0036
> c000e224  c1719fa8
> [   38.58] 9fa0: c000e0c0 c009e638 bef74c18 8916 0003
> 8916 bef74c18 
> [   38.58] 9fc0: bef74c18 8916 0003 0036 00085a28
>  000859a8 
> [   38.58] 9fe0: b6f2bde4 bef74bc0 ddb4 b6f2be28 6010
> 0003  
> [   38.58] Backtrace:
> [   38.58] [] (trie_firstleaf+0x0/0x2c) from
> [] (fib_table_flush+0x1c/0x170)
> [   38.58] [] (fib_table_flush+0x0/0x170) from
> [] (fib_flush.clone.27+0x30/0x60)
> [   38.58] [] (fib_flush.clone.27+0x0/0x60) from
> [] (fib_disable_ip+0x20/0x38)
> [   38.58]  r7: r6: r5:c160f800 r4:c160f800
> [   38.58] [] (fib_disable_ip+0x0/0x38) from
> [] (fib_inetaddr_event+0xa0/0xb4)
> [   38.58]  r4:c16341e0 r3:
> [   38.58] [] (fib_inetaddr_event+0x0/0xb4) from
> [] (notifier_call_chain+0x40/0x70)
> [   38.58]  r5: r4:0002
> [   38.58] [] (notifier_call_chain+0x0/0x70) from
> [] (__blocking_notifier_call_chain+0x50/0x68)
> [   38.58]  r8: r7:0002 r6:c16341e0 r5: r4:c09d4698
> r3:
> [   38.58] [] (__blocking_notifier_call_chain+0x0/0x68)
> from [] (blocking_notifier_call_chain+0x20/0x28)
> [   38.58]  r7:c16341e0 r6: r5: r4:c16341e0
> [   38.58] [] (blocking_notifier_call_chain+0x0/0x28)
> from [] (__inet_del_ifa+0x1a4/0x260)
> [   38.58] [] (__inet_del_ifa+0x0/0x260) from
> [] (inet_del_ifa+0x1c/0x24)
> [   38.58] [] (inet_del_ifa+0x0/0x24) from []
> (devinet_ioctl+0x370/0x634)
> [   38.58] [] (devinet_ioctl+0x0/0x634) from
> [] (inet_ioctl+0xd0/0x110)
> [   38.58] [] (inet_ioctl+0x0/0x110) from []
> (sock_ioctl+0x220/0x278)
> [   38.58]  r4:8916 r3:c1404420
> [   38.58] [] (sock_ioctl+0x0/0x278) from []
> (do_vfs_ioctl+0x2f4/0x334)
> [   38.58]  r6:bef74c18 r5:bef74c18 r4:0003 r3:c022e