mmc1 timeout issue with rpi3

mmc1 timeout issue with rpi3

[Stefan Wahren]

Hi Sergey,

> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 22:07 geschrieben:
> 
> 
> sure, here you go
> 
> https://pastebin.com/kAHUrb6m
> 
> 
> On 01/16/2018 11:54 PM, Stefan Wahren wrote:
> > Hi Sergey,
> >
> >> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 21:27 geschrieben:
> >>
> >>
> >> Hi,
> >> I still have the issue "mmc1 timeout" with mainline 4.15rc7, discussed here
> >>
> >> http://lists.infradead.org/pipermail/linux-rpi-kernel/2016-June/004003.html
> >>
> >> Is there any progress on this ?
> >> Thanks
> >>
> > please provide the dmesg output.

first of all please avoid top-posting.

These mmc1 timeouts are unexpected for Raspberry Pi 3 with mailine kernel. I'm using multi_v7_defconfig and get the following:

[    0.730597] mmc1: SDHCI controller on 3f300000.sdhci [3f300000.sdhci] using PIO
[    0.738238] ledtrig-cpu: registered to indicate activity on CPUs
[    0.745085] usbcore: registered new interface driver usbhid
[    0.751536] usbhid: USB HID core driver
[    0.758625] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
[    0.767760] NET: Registered protocol family 10
[    0.775301] Segment Routing with IPv6
[    0.781785] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    0.788874] NET: Registered protocol family 17
[    0.795399] can: controller area network core (rev 20170425 abi 9)
[    0.802013] NET: Registered protocol family 29
[    0.808495] can: raw protocol (rev 20170425)
[    0.814965] can: broadcast manager protocol (rev 20170425 t)
[    0.821447] can: netlink gateway (rev 20170425) max_hops=1
[    0.828317] Key type dns_resolver registered
[    0.835733] Registering SWP/SWPB emulation handler
[    0.842787] Loading compiled-in X.509 certificates
[    0.852989] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
[    0.862190] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[    0.868970] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-07-03 14:16
[    0.870688] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.872371] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[    0.875388] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[    0.897742] mmc0: host does not support reading read-only switch, assuming write-enable
[    0.906523] mmc0: new high speed SDHC card at address 1234
[    0.913738] mmcblk0: mmc0:1234 SA32G 29.3 GiB 
[    0.922210]  mmcblk0: p1 p2
[    0.928980] dwc2 3f980000.usb: 3f980000.usb supply vusb_d not found, using dummy regulator
[    0.935881] dwc2 3f980000.usb: 3f980000.usb supply vusb_a not found, using dummy regulator
[    0.993219] dwc2 3f980000.usb: DWC OTG Controller
[    0.999967] dwc2 3f980000.usb: new USB bus registered, assigned bus number 1
[    1.002026] mmc1: new high speed SDIO card at address 0001

Could you please also share your config?
Do you have a Raspberry Pi 3 B 1.2?
Did you check the function of the hardware before?

> >
> > Stefan
> >
> > _______________________________________________
> > linux-arm-kernel mailing list
> > linux-arm-kernel at lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

mmc1 timeout issue with rpi3

[Phil Elwell]

Hi Sergey,

On 17/01/2018 18:19, Stefan Wahren wrote:
> Hi Sergey,
> 
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 22:07 geschrieben:
>>
>>
>> sure, here you go
>>
>> https://pastebin.com/kAHUrb6m
>>
>>
>> On 01/16/2018 11:54 PM, Stefan Wahren wrote:
>>> Hi Sergey,
>>>
>>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 21:27 geschrieben:
>>>>
>>>>
>>>> Hi,
>>>> I still have the issue "mmc1 timeout" with mainline 4.15rc7, discussed here
>>>>
>>>> http://lists.infradead.org/pipermail/linux-rpi-kernel/2016-June/004003.html
>>>>
>>>> Is there any progress on this ?
>>>> Thanks
>>>>
>>> please provide the dmesg output.
> 
> first of all please avoid top-posting.
> 
> These mmc1 timeouts are unexpected for Raspberry Pi 3 with mailine kernel. I'm using multi_v7_defconfig and get the following:
> 
> [    0.730597] mmc1: SDHCI controller on 3f300000.sdhci [3f300000.sdhci] using PIO
> [    0.738238] ledtrig-cpu: registered to indicate activity on CPUs
> [    0.745085] usbcore: registered new interface driver usbhid
> [    0.751536] usbhid: USB HID core driver
> [    0.758625] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
> [    0.767760] NET: Registered protocol family 10
> [    0.775301] Segment Routing with IPv6
> [    0.781785] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> [    0.788874] NET: Registered protocol family 17
> [    0.795399] can: controller area network core (rev 20170425 abi 9)
> [    0.802013] NET: Registered protocol family 29
> [    0.808495] can: raw protocol (rev 20170425)
> [    0.814965] can: broadcast manager protocol (rev 20170425 t)
> [    0.821447] can: netlink gateway (rev 20170425) max_hops=1
> [    0.828317] Key type dns_resolver registered
> [    0.835733] Registering SWP/SWPB emulation handler
> [    0.842787] Loading compiled-in X.509 certificates
> [    0.852989] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
> [    0.862190] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
> [    0.868970] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-07-03 14:16
> [    0.870688] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
> [    0.872371] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
> [    0.875388] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
> [    0.897742] mmc0: host does not support reading read-only switch, assuming write-enable
> [    0.906523] mmc0: new high speed SDHC card at address 1234
> [    0.913738] mmcblk0: mmc0:1234 SA32G 29.3 GiB
> [    0.922210]  mmcblk0: p1 p2
> [    0.928980] dwc2 3f980000.usb: 3f980000.usb supply vusb_d not found, using dummy regulator
> [    0.935881] dwc2 3f980000.usb: 3f980000.usb supply vusb_a not found, using dummy regulator
> [    0.993219] dwc2 3f980000.usb: DWC OTG Controller
> [    0.999967] dwc2 3f980000.usb: new USB bus registered, assigned bus number 1
> [    1.002026] mmc1: new high speed SDIO card at address 0001
> 
> Could you please also share your config?
> Do you have a Raspberry Pi 3 B 1.2?
> Did you check the function of the hardware before?

To add to Stefan's questions, have you specifically checked that your power supply
is adequate? Issues like this during startup are often caused by a momentary undervoltage
triggered by increased current demands as many subsystems are started at once. We
recommend a 2.5A supply for Pi 3.

Phil

mmc1 timeout issue with rpi3

[Sergey Suloev]

Hi Stefan

wifi network was working fine when I used a raspbian image downloaded 
from official site.

Here is my config https://pastebin.com/7XRpmM0X? and cpuinfo 
https://pastebin.com/08Z6gDZ9

I have no idea about version you are talking about.

Thanks.


On 01/17/2018 09:19 PM, Stefan Wahren wrote:
> Hi Sergey,
>
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 22:07 geschrieben:
>>
>>
>> sure, here you go
>>
>> https://pastebin.com/kAHUrb6m
>>
>>
>> On 01/16/2018 11:54 PM, Stefan Wahren wrote:
>>> Hi Sergey,
>>>
>>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 21:27 geschrieben:
>>>>
>>>>
>>>> Hi,
>>>> I still have the issue "mmc1 timeout" with mainline 4.15rc7, discussed here
>>>>
>>>> http://lists.infradead.org/pipermail/linux-rpi-kernel/2016-June/004003.html
>>>>
>>>> Is there any progress on this ?
>>>> Thanks
>>>>
>>> please provide the dmesg output.
> first of all please avoid top-posting.
>
> These mmc1 timeouts are unexpected for Raspberry Pi 3 with mailine kernel. I'm using multi_v7_defconfig and get the following:
>
> [    0.730597] mmc1: SDHCI controller on 3f300000.sdhci [3f300000.sdhci] using PIO
> [    0.738238] ledtrig-cpu: registered to indicate activity on CPUs
> [    0.745085] usbcore: registered new interface driver usbhid
> [    0.751536] usbhid: USB HID core driver
> [    0.758625] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
> [    0.767760] NET: Registered protocol family 10
> [    0.775301] Segment Routing with IPv6
> [    0.781785] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
> [    0.788874] NET: Registered protocol family 17
> [    0.795399] can: controller area network core (rev 20170425 abi 9)
> [    0.802013] NET: Registered protocol family 29
> [    0.808495] can: raw protocol (rev 20170425)
> [    0.814965] can: broadcast manager protocol (rev 20170425 t)
> [    0.821447] can: netlink gateway (rev 20170425) max_hops=1
> [    0.828317] Key type dns_resolver registered
> [    0.835733] Registering SWP/SWPB emulation handler
> [    0.842787] Loading compiled-in X.509 certificates
> [    0.852989] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
> [    0.862190] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
> [    0.868970] raspberrypi-firmware soc:firmware: Attached to firmware from 2017-07-03 14:16
> [    0.870688] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
> [    0.872371] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
> [    0.875388] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
> [    0.897742] mmc0: host does not support reading read-only switch, assuming write-enable
> [    0.906523] mmc0: new high speed SDHC card at address 1234
> [    0.913738] mmcblk0: mmc0:1234 SA32G 29.3 GiB
> [    0.922210]  mmcblk0: p1 p2
> [    0.928980] dwc2 3f980000.usb: 3f980000.usb supply vusb_d not found, using dummy regulator
> [    0.935881] dwc2 3f980000.usb: 3f980000.usb supply vusb_a not found, using dummy regulator
> [    0.993219] dwc2 3f980000.usb: DWC OTG Controller
> [    0.999967] dwc2 3f980000.usb: new USB bus registered, assigned bus number 1
> [    1.002026] mmc1: new high speed SDIO card at address 0001
>
> Could you please also share your config?
> Do you have a Raspberry Pi 3 B 1.2?
> Did you check the function of the hardware before?
>
>>> Stefan
>>>
>>> _______________________________________________
>>> linux-arm-kernel mailing list
>>> linux-arm-kernel at lists.infradead.org
>>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

mmc1 timeout issue with rpi3

[Sergey Suloev]

Hi Phil

thank you for that detail. But I am using the same power supply that I 
have been always using for my rpi3. It worked with a raspbian image and 
I never had such issues.

Thanks


On 01/17/2018 09:47 PM, Phil Elwell wrote:
> Hi Sergey,
>
> On 17/01/2018 18:19, Stefan Wahren wrote:
>> Hi Sergey,
>>
>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 
>>> 22:07 geschrieben:
>>>
>>>
>>> sure, here you go
>>>
>>> https://pastebin.com/kAHUrb6m
>>>
>>>
>>> On 01/16/2018 11:54 PM, Stefan Wahren wrote:
>>>> Hi Sergey,
>>>>
>>>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 16. Januar 2018 um 
>>>>> 21:27 geschrieben:
>>>>>
>>>>>
>>>>> Hi,
>>>>> I still have the issue "mmc1 timeout" with mainline 4.15rc7, 
>>>>> discussed here
>>>>>
>>>>> http://lists.infradead.org/pipermail/linux-rpi-kernel/2016-June/004003.html 
>>>>>
>>>>>
>>>>> Is there any progress on this ?
>>>>> Thanks
>>>>>
>>>> please provide the dmesg output.
>>
>> first of all please avoid top-posting.
>>
>> These mmc1 timeouts are unexpected for Raspberry Pi 3 with mailine 
>> kernel. I'm using multi_v7_defconfig and get the following:
>>
>> [??? 0.730597] mmc1: SDHCI controller on 3f300000.sdhci 
>> [3f300000.sdhci] using PIO
>> [??? 0.738238] ledtrig-cpu: registered to indicate activity on CPUs
>> [??? 0.745085] usbcore: registered new interface driver usbhid
>> [??? 0.751536] usbhid: USB HID core driver
>> [??? 0.758625] bcm2835-mbox 3f00b880.mailbox: mailbox enabled
>> [??? 0.767760] NET: Registered protocol family 10
>> [??? 0.775301] Segment Routing with IPv6
>> [??? 0.781785] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
>> [??? 0.788874] NET: Registered protocol family 17
>> [??? 0.795399] can: controller area network core (rev 20170425 abi 9)
>> [??? 0.802013] NET: Registered protocol family 29
>> [??? 0.808495] can: raw protocol (rev 20170425)
>> [??? 0.814965] can: broadcast manager protocol (rev 20170425 t)
>> [??? 0.821447] can: netlink gateway (rev 20170425) max_hops=1
>> [??? 0.828317] Key type dns_resolver registered
>> [??? 0.835733] Registering SWP/SWPB emulation handler
>> [??? 0.842787] Loading compiled-in X.509 certificates
>> [??? 0.852989] 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, 
>> base_baud = 0) is a PL011 rev2
>> [??? 0.862190] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
>> [??? 0.868970] raspberrypi-firmware soc:firmware: Attached to 
>> firmware from 2017-07-03 14:16
>> [??? 0.870688] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
>> [??? 0.872371] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
>> [??? 0.875388] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
>> [??? 0.897742] mmc0: host does not support reading read-only switch, 
>> assuming write-enable
>> [??? 0.906523] mmc0: new high speed SDHC card at address 1234
>> [??? 0.913738] mmcblk0: mmc0:1234 SA32G 29.3 GiB
>> [??? 0.922210]? mmcblk0: p1 p2
>> [??? 0.928980] dwc2 3f980000.usb: 3f980000.usb supply vusb_d not 
>> found, using dummy regulator
>> [??? 0.935881] dwc2 3f980000.usb: 3f980000.usb supply vusb_a not 
>> found, using dummy regulator
>> [??? 0.993219] dwc2 3f980000.usb: DWC OTG Controller
>> [??? 0.999967] dwc2 3f980000.usb: new USB bus registered, assigned 
>> bus number 1
>> [??? 1.002026] mmc1: new high speed SDIO card at address 0001
>>
>> Could you please also share your config?
>> Do you have a Raspberry Pi 3 B 1.2?
>> Did you check the function of the hardware before?
>
> To add to Stefan's questions, have you specifically checked that your 
> power supply
> is adequate? Issues like this during startup are often caused by a 
> momentary undervoltage
> triggered by increased current demands as many subsystems are started 
> at once. We
> recommend a 2.5A supply for Pi 3.
>
> Phil

mmc1 timeout issue with rpi3

[Stefan Wahren]

Hi Sergey,

> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 19:49 geschrieben:
> 
> 
> Hi Stefan
> 
> wifi network was working fine when I used a raspbian image downloaded 
> from official site.
> 
> Here is my config https://pastebin.com/7XRpmM0X  and cpuinfo 
> https://pastebin.com/08Z6gDZ9
> 
> I have no idea about version you are talking about.

please stop top-posting.

I was talking about the board revision of your RPi. You can get this information by looking at the PCB.

I updated to the last firmware and your config but i'm unable to reproduce this issue.

Do you use U-Boot or only the Raspberry Pi bootloader?
What are your modifications to config.txt?

> 
> Thanks.
> 
>

mmc1 timeout issue with rpi3

[Phil Elwell]

Hi Sergey,

On 17/01/2018 18:52, Sergey Suloev wrote:
> Hi Phil
> 
> thank you for that detail. But I am using the same power supply that I have been always using for my rpi3. It worked with a raspbian image and I never had such issues.
> 
> Thanks

[ This is the "top posting" crime that Stefan was referring to. We are supposed to add comments inline
or at the end. ]

A different kernel will have different timing and current requirements. To rule out a
marginal supply, boot a standard Raspbian image and run "vcgencmd get_throttled". An
answer other than 0x0 (likely 0x50000, but possibly 0x50005) indicates that undervoltage
has occurred (and is possibly still ocurring). This may not be enough to trigger a
malfunction, but the potential is there.

Phil

> On 01/17/2018 09:47 PM, Phil Elwell wrote:
>> Hi Sergey,
>>
>> To add to Stefan's questions, have you specifically checked that your power supply
>> is adequate? Issues like this during startup are often caused by a momentary undervoltage
>> triggered by increased current demands as many subsystems are started at once. We
>> recommend a 2.5A supply for Pi 3.
>>
>> Phil
> 

mmc1 timeout issue with rpi3

[Sergey Suloev]

Hi Stefan,

On 01/17/2018 10:32 PM, Stefan Wahren wrote:
> Hi Sergey,
>
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 19:49 geschrieben:
>>
>>
>> Hi Stefan
>>
>> wifi network was working fine when I used a raspbian image downloaded
>> from official site.
>>
>> Here is my config https://pastebin.com/7XRpmM0X  and cpuinfo
>> https://pastebin.com/08Z6gDZ9
>>
>> I have no idea about version you are talking about.
> please stop top-posting.
>
> I was talking about the board revision of your RPi. You can get this information by looking at the PCB.
>
> I updated to the last firmware and your config but i'm unable to reproduce this issue.
>
> Do you use U-Boot or only the Raspberry Pi bootloader?
> What are your modifications to config.txt?
>
>> Thanks.
>>
>>
I am using u-boot tagged 2018.01.

Here is my config.txt https://pastebin.com/VXWuVGLB and? kernel args

dwc_otg.lpm_enable=0 root=/dev/mmcblk0p2 rootfstype=ext4 
rootflags=commit=100,data=writeback elevator=deadline rootwait 
console=tty1 cma=256M at 512M fbcon=map:10 console=ttyAMA0,115200 
kgdboc=ttyAMA0,115200 ipv6.disable=1 net.ifnames=0 init=/bin/systemd

Thanks

mmc1 timeout issue with rpi3

[Stefan Wahren]

Hi Sergey,

> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 21:04 geschrieben:
> 
> 
> Hi Stefan,
> 
> On 01/17/2018 10:32 PM, Stefan Wahren wrote:
> > Hi Sergey,
> >
> >> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 19:49 geschrieben:
> >>
> >>
> >> Hi Stefan
> >>
> >> wifi network was working fine when I used a raspbian image downloaded
> >> from official site.
> >>
> >> Here is my config https://pastebin.com/7XRpmM0X  and cpuinfo
> >> https://pastebin.com/08Z6gDZ9
> >>
> >> I have no idea about version you are talking about.
> > please stop top-posting.
> >
> > I was talking about the board revision of your RPi. You can get this information by looking at the PCB.
> >
> > I updated to the last firmware and your config but i'm unable to reproduce this issue.
> >
> > Do you use U-Boot or only the Raspberry Pi bootloader?
> > What are your modifications to config.txt?
> >
> >> Thanks.
> >>
> >>
> I am using u-boot tagged 2018.01.

interesting. I don't use u-boot as second stage bootloader. Maybe it messed up the pin configuration of the GPIO expander. Could you please try without u-boot?

mmc1 timeout issue with rpi3

[Sergey Suloev]

Hi, Stefan

On 01/18/2018 10:03 AM, Stefan Wahren wrote:
> Hi Sergey,
>
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 21:04 geschrieben:
>>
>>
>> Hi Stefan,
>>
>> On 01/17/2018 10:32 PM, Stefan Wahren wrote:
>>> Hi Sergey,
>>>
>>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 19:49 geschrieben:
>>>>
>>>>
>>>> Hi Stefan
>>>>
>>>> wifi network was working fine when I used a raspbian image downloaded
>>>> from official site.
>>>>
>>>> Here is my config https://pastebin.com/7XRpmM0X  and cpuinfo
>>>> https://pastebin.com/08Z6gDZ9
>>>>
>>>> I have no idea about version you are talking about.
>>> please stop top-posting.
>>>
>>> I was talking about the board revision of your RPi. You can get this information by looking at the PCB.
>>>
>>> I updated to the last firmware and your config but i'm unable to reproduce this issue.
>>>
>>> Do you use U-Boot or only the Raspberry Pi bootloader?
>>> What are your modifications to config.txt?
>>>
>>>> Thanks.
>>>>
>>>>
>> I am using u-boot tagged 2018.01.
> interesting. I don't use u-boot as second stage bootloader. Maybe it messed up the pin configuration of the GPIO expander. Could you please try without u-boot?

but how can u-boot influence that ? As far as I understand the error 
happens in a very late boot stage, actually in the end. At this time 
bcm2837-rpi-3-b device tree file from kernel is already loaded. Do you 
think this DTB is incorrect ?

Thanks

mmc1 timeout issue with rpi3

[Stefan Wahren]

Hi Sergey,


Am 18.01.2018 um 13:55 schrieb Sergey Suloev:
> Hi, Stefan
>
> On 01/18/2018 10:03 AM, Stefan Wahren wrote:
>> Hi Sergey,
>>
>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 
>>> 21:04 geschrieben:
>>>
>>>
>>> Hi Stefan,
>>>
>>> I am using u-boot tagged 2018.01.
>> interesting. I don't use u-boot as second stage bootloader. Maybe it 
>> messed up the pin configuration of the GPIO expander. Could you 
>> please try without u-boot?
>
> but how can u-boot influence that ? As far as I understand the error 
> happens in a very late boot stage, actually in the end. At this time 
> bcm2837-rpi-3-b device tree file from kernel is already loaded. Do you 
> think this DTB is incorrect ?

wild guessing doesn't help here. Did you test it without U-Boot? Did the 
issue still occur?

Stefan

>
> Thanks
>
>

mmc1 timeout issue with rpi3

[Sergey Suloev]

Hi, Stefan,

On 01/18/2018 07:55 PM, Stefan Wahren wrote:
> Hi Sergey,
>
>
> Am 18.01.2018 um 13:55 schrieb Sergey Suloev:
>> Hi, Stefan
>>
>> On 01/18/2018 10:03 AM, Stefan Wahren wrote:
>>> Hi Sergey,
>>>
>>>> Sergey Suloev <ssuloev@orpaltech.com> hat am 17. Januar 2018 um 
>>>> 21:04 geschrieben:
>>>>
>>>>
>>>> Hi Stefan,
>>>>
>>>> I am using u-boot tagged 2018.01.
>>> interesting. I don't use u-boot as second stage bootloader. Maybe it 
>>> messed up the pin configuration of the GPIO expander. Could you 
>>> please try without u-boot?
>>
>> but how can u-boot influence that ? As far as I understand the error 
>> happens in a very late boot stage, actually in the end. At this time 
>> bcm2837-rpi-3-b device tree file from kernel is already loaded. Do 
>> you think this DTB is incorrect ?
>
> wild guessing doesn't help here. Did you test it without U-Boot? Did 
> the issue still occur?
>
> Stefan
>
>>
>> Thanks
>>
>>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

no I haven't checked it yet. I'm going to find information about setting 
it up w/o u-boot since I've never tried it before.

mmc1 timeout issue with rpi3

[Stefan Wahren]

Hi Sergey,

> Sergey Suloev <ssuloev@orpaltech.com> hat am 18. Januar 2018 um 18:56 geschrieben:
> 
> 
> Hi, Stefan,
> 
> 
> no I haven't checked it yet. I'm going to find information about setting 
> it up w/o u-boot since I've never tried it before.
> 
> 

store the kernel zImage as /boot/kernel7.img

and define the DT within config.txt 

device_tree=bcm2837-rpi-3-b.dtb

mmc1 timeout issue with rpi3

[Phil Elwell]

On 18/01/2018 18:07, Stefan Wahren wrote:
> Hi Sergey,
> 
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 18. Januar 2018 um 18:56 geschrieben:
>>
>>
>> Hi, Stefan,
>>
>>
>> no I haven't checked it yet. I'm going to find information about setting 
>> it up w/o u-boot since I've never tried it before.
>>
>>
> 
> store the kernel zImage as /boot/kernel7.img
> 
> and define the DT within config.txt 
> 
> device_tree=bcm2837-rpi-3-b.dtb
> 

And comment out or delete:

#kernel=u-boot.bin

Phil

mmc1 timeout issue with rpi3

[Sergey Suloev]

Hi Stefan

On 01/18/2018 09:07 PM, Stefan Wahren wrote:
> Hi Sergey,
>
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 18. Januar 2018 um 18:56 geschrieben:
>>
>>
>> Hi, Stefan,
>>
>>
>> no I haven't checked it yet. I'm going to find information about setting
>> it up w/o u-boot since I've never tried it before.
>>
>>
> store the kernel zImage as /boot/kernel7.img
>
> and define the DT within config.txt
>
> device_tree=bcm2837-rpi-3-b.dtb

it isn't working that way. I am getting kernel panics.

Thanks

mmc1 timeout issue with rpi3

[Sergey Suloev]

Hi Stefan

On 01/18/2018 09:07 PM, Stefan Wahren wrote:
> Hi Sergey,
>
>> Sergey Suloev <ssuloev@orpaltech.com> hat am 18. Januar 2018 um 18:56 geschrieben:
>>
>>
>> Hi, Stefan,
>>
>>
>> no I haven't checked it yet. I'm going to find information about setting
>> it up w/o u-boot since I've never tried it before.
>>
>>
> store the kernel zImage as /boot/kernel7.img
>
> and define the DT within config.txt
>
> device_tree=bcm2837-rpi-3-b.dtb

ok, what I tried:

1) copied dtbs from firmware github repo

2) copied kernel and kernel7 files

3) modified config.txt? to add

device_tree=bcm2710-rpi-3-b.dtb

4) boot successful

5) here is my dmesg https://pastebin.com/CK33EcgD

Thanks