Andrew,
Which suggests ops is NULL. The #64 also matches with
[ 50.688935] Unable to handle kernel read from unreadable memory at
virtual address 0040
How did dev->netdev_ops become NULL?
Thanks. Yes, my debugging also led to this point but not further.
I am tracing the poin
There is a DSA master reference counting issue, but with dsa-loop, the
DSA master is already properly reference counted thanks to the
dev_get_by_name() call, I will keep digging.
Thank you Florain.
I am not dsa expert, am debugging the call chain.
- Allen
On 5/3/2020 2:06 PM, Florian Fainelli wrote:
> Le 2020-05-01 à 10:58, Allen a écrit :
It maps to "eth0". Please let me know if you need further details.
>>>
>>> I suppose I should have been clearer, what network device driver created
>>> eth0?
>>>
>>
>> This was seen on a VM.
>> eth
Le 2020-05-01 à 10:58, Allen a écrit :
>>>
>>> It maps to "eth0". Please let me know if you need further details.
>>
>> I suppose I should have been clearer, what network device driver created
>> eth0?
>>
>
> This was seen on a VM.
> eth0 [52:54:00:c1:cd:65]: virtio_net (up)
I have reproduced
On 5/1/20 10:58 AM, Allen wrote:
>>>
>>> It maps to "eth0". Please let me know if you need further details.
>>
>> I suppose I should have been clearer, what network device driver created
>> eth0?
>>
>
> This was seen on a VM.
> eth0 [52:54:00:c1:cd:65]: virtio_net (up)
Thanks, I will try to re
It maps to "eth0". Please let me know if you need further details.
I suppose I should have been clearer, what network device driver created
eth0?
This was seen on a VM.
eth0 [52:54:00:c1:cd:65]: virtio_net (up)
Thanks.
On 4/30/20 11:48 PM, Allen wrote:
>
>>
>> you have missed an important detail here which is the master device that
>> was used for DSA. The current code defaults to whatever "eth0" is, what
>> does this map to for your configuration?
>>
>
> It maps to "eth0". Please let me know if you need furth
On Thu, Apr 30, 2020 at 11:54:15AM +0530, Allen wrote:
> Hi,
>
> $ rmmod dsa-loop
> [ 50.688935] Unable to handle kernel read from unreadable memory at
> virtual address 0040
> [ 50.718185] pstate: 6045 (nZCv daif +PAN -UAO)
> [ 50.719274] pc : __dev_set_rx_mode+0x48/0xa0
f
you have missed an important detail here which is the master device that
was used for DSA. The current code defaults to whatever "eth0" is, what
does this map to for your configuration?
It maps to "eth0". Please let me know if you need further details.
- Allen
On 4/29/20 11:24 PM, Allen wrote:
> Hi,
>
> We ran into a kernel panic with dsa-loop.
> Here are the details:
>
> VM: aarch64 kvm running 5.7.0-rc3+
>
> $ modprobe dsa-loop
> [ 25.968427] dsa-loop fixed-0:1f: DSA mockup driver: 0x1f
> [ 25.978156] libphy: dsa slave smi: probed
> [ 25.979
On Thu, Apr 30, 2020 at 11:54:15AM +0530, Allen wrote:
> Hi,
>
> We ran into a kernel panic with dsa-loop.
> Here are the details:
>
> VM: aarch64 kvm running 5.7.0-rc3+
Hi Allen
Can you reproduce it? If so, could you do:
make net/core/dev.lst
and then show us the listing for __dev_set_rx_m
Hi,
We ran into a kernel panic with dsa-loop.
Here are the details:
VM: aarch64 kvm running 5.7.0-rc3+
$ modprobe dsa-loop
[ 25.968427] dsa-loop fixed-0:1f: DSA mockup driver: 0x1f
[ 25.978156] libphy: dsa slave smi: probed
[ 25.979230] dsa-loop fixed-0:1f: nonfatal error -95 setting MT
12 matches
Mail list logo
