From: Alexander Shiyan <eagle.alexander923@gmail.com>
To: Sascha Hauer <sha@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: v2022.05.0
Date: Thu, 19 May 2022 11:11:06 +0300 [thread overview]
Message-ID: <CAP1tNvT6RpQ5P4ZX4z0cObdOxL0ZBw9y_N9MSQv_9vB1NpTfPA@mail.gmail.com> (raw)
In-Reply-To: <20220518125852.GS25578@pengutronix.de>
ср, 18 мая 2022 г. в 16:00, Sascha Hauer <sha@pengutronix.de>:
> Hi All,
> barebox-2022.05.0 is out.
Hello.
After updating to the new version, I found errors...
This is probably the result of the "gpio: allocate dynamic gpio
numbers top down" patch.
In the gpiochip_find_base function, it seems to me that we should
change the algorithm
if the chip exists, such as:
if (!chip) {
...
} else {
spare = 0;
i+= chip->ngpio - 1; // Should be: i -= chip->ngpio - 1; ???
}
Thanks!
barebox 2022.05.0-00506-g1ed17b742ede #59 Thu May 19 09:03:27 MSK 2022
Board: Mega-Milas Informer/Spider AM335x
cpsw-mdio 4a101000.mdio@1000.of: detected phy mask 0x10
mdio_bus: miibus0: probed
eth0: got preset MAC address: d0:03:eb:ef:c2:a6
i2c-omap 44e0b000.i2c@0.of: bus 0 rev0.11 at 400 kHz
omap-hsmmc 48060000.mmc@0.of: registered as mmc0
omap_wdt 44e35000.wdt@0.of: OMAP Watchdog Timer Rev 0x01
unable to handle paging request at address 0x3e0d0008
pc : [<8fe2b208>] lr : [<8fe2bf3f>]
sp : 8ffeff40 ip : 00000000 fp : 0003f4f4
r10: 0017a4d8 r9 : 8fe7d628 r8 : 00000000
r7 : 87f59cd0 r6 : 00000000 r5 : 87f5afbc r4 : 3e0d0000
r3 : 0000010c r2 : 00000001 r1 : 87eff048 r0 : 00000008
Flags: nzcv IRQs off FIQs on Mode SVC_32
WARNING: [<8fe2b208>] (gpiochip_add+0x80/0x294) from [<8fe2bf3f>]
(pca953x_probe+0x11b/0x158)
WARNING: [<8fe2bf3f>] (pca953x_probe+0x11b/0x158) from [<8fe0a901>]
(device_probe+0x2d/0xac)
WARNING: [<8fe0a901>] (device_probe+0x2d/0xac) from [<8fe0a9a7>]
(match+0x27/0x2c)
WARNING: [<8fe0a9a7>] (match+0x27/0x2c) from [<8fe0acf3>]
(register_driver+0x6b/0x88)
WARNING: [<8fe0acf3>] (register_driver+0x6b/0x88) from [<8fe00f09>]
(start_barebox+0x35/0x6c)
WARNING: [<8fe00f09>] (start_barebox+0x35/0x6c) from [<8fe46aa7>]
(barebox_non_pbl_start+0x127/0x16c)
WARNING: [<8fe46aa7>] (barebox_non_pbl_start+0x127/0x16c) from
[<8fe00005>] (__bare_init_start+0x1/0xc)
WARNING: [<8fe482dd>] (unwind_backtrace+0x1/0x78) from [<8fe01235>]
(panic+0x1d/0x20)
WARNING: [<8fe01235>] (panic+0x1d/0x20) from [<8fe46323>]
(do_exception+0xf/0x14)
WARNING: [<8fe46323>] (do_exception+0xf/0x14) from [<8fe46391>]
(do_data_abort+0x21/0x34)
WARNING: [<8fe46391>] (do_data_abort+0x21/0x34) from [<8fe460d4>]
(do_abort_6+0x48/0x54)
### ERROR ### Please RESET the board ###
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-05-19 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 12:58 v2022.05.0 Sascha Hauer
2022-05-19 8:11 ` Alexander Shiyan [this message]
2022-05-19 10:44 ` v2022.05.0 Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAP1tNvT6RpQ5P4ZX4z0cObdOxL0ZBw9y_N9MSQv_9vB1NpTfPA@mail.gmail.com \
--to=eagle.alexander923@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=sha@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox