On August 2, 2016 9:22:53 PM MST, Ding Tianhong wrote:
>On 2016/8/3 10:41, Florian Fainelli wrote:
>> On August 2, 2016 6:21:52 PM MST, Ding Tianhong
> wrote:
>>> On 2016/8/3 0:42, Florian Fainelli wrote:
Le 02/08/2016 à 06:00, Ding Tianhong
On August 2, 2016 9:22:53 PM MST, Ding Tianhong wrote:
>On 2016/8/3 10:41, Florian Fainelli wrote:
>> On August 2, 2016 6:21:52 PM MST, Ding Tianhong
> wrote:
>>> On 2016/8/3 0:42, Florian Fainelli wrote:
Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
> The nic in my board use the phy
On 2016/8/3 10:41, Florian Fainelli wrote:
> On August 2, 2016 6:21:52 PM MST, Ding Tianhong
> wrote:
>> On 2016/8/3 0:42, Florian Fainelli wrote:
>>> Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
The nic in my board use the phy dev from marvell, and
the
On 2016/8/3 10:41, Florian Fainelli wrote:
> On August 2, 2016 6:21:52 PM MST, Ding Tianhong
> wrote:
>> On 2016/8/3 0:42, Florian Fainelli wrote:
>>> Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
The nic in my board use the phy dev from marvell, and
the system will load the marvell
On August 2, 2016 6:21:52 PM MST, Ding Tianhong wrote:
>On 2016/8/3 0:42, Florian Fainelli wrote:
>> Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
>>> The nic in my board use the phy dev from marvell, and
>>> the system will load the marvell phy driver automatically,
>>>
On August 2, 2016 6:21:52 PM MST, Ding Tianhong wrote:
>On 2016/8/3 0:42, Florian Fainelli wrote:
>> Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
>>> The nic in my board use the phy dev from marvell, and
>>> the system will load the marvell phy driver automatically,
>>> but when I remove the
On 2016/8/3 0:42, Florian Fainelli wrote:
> Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
>> The nic in my board use the phy dev from marvell, and
>> the system will load the marvell phy driver automatically,
>> but when I remove the phy drivers, the system immediately panic:
>>
>> localhost
On 2016/8/3 0:42, Florian Fainelli wrote:
> Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
>> The nic in my board use the phy dev from marvell, and
>> the system will load the marvell phy driver automatically,
>> but when I remove the phy drivers, the system immediately panic:
>>
>> localhost
Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
> The nic in my board use the phy dev from marvell, and
> the system will load the marvell phy driver automatically,
> but when I remove the phy drivers, the system immediately panic:
>
> localhost login: [ 2582.052465] Unable to handle kernel NULL
Le 02/08/2016 à 06:00, Ding Tianhong a écrit :
> The nic in my board use the phy dev from marvell, and
> the system will load the marvell phy driver automatically,
> but when I remove the phy drivers, the system immediately panic:
>
> localhost login: [ 2582.052465] Unable to handle kernel NULL
The nic in my board use the phy dev from marvell, and
the system will load the marvell phy driver automatically,
but when I remove the phy drivers, the system immediately panic:
localhost login: [ 2582.052465] Unable to handle kernel NULL pointer
dereference at virtual address 00c0
[
The nic in my board use the phy dev from marvell, and
the system will load the marvell phy driver automatically,
but when I remove the phy drivers, the system immediately panic:
localhost login: [ 2582.052465] Unable to handle kernel NULL pointer
dereference at virtual address 00c0
[
12 matches
Mail list logo