Modify

Opened 5 years ago

Last modified 4 years ago

#13340 new defect

Open Mesh OM1P fails on boot with CONFIG_LEDS_GPIO enabled

Reported by: ben@… Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: kernel Version: Trunk
Keywords: gpio, leds, atheros, om1p Cc:

Description

An Open Mesh OM1P (Atheros AR2315) fails on boot with filesystem errors when the option CONFIG_LEDS_GPIO is enabled in target/linux/atheros/config-3.8. This was tested on trunk r36255.

Excerpts from the serial console on the failing OM1P:

[   29.000000] jffs2: Old JFFS2 bitmask found at 0x00106eb0
[   29.070000] jffs2: You cannot use older JFFS2 filesystems with newer kernels
[   29.270000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110000: 0xc816 instead
[   29.380000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110004: 0x8287 instead
[   29.500000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110008: 0x09c2 instead
[   29.610000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0011000c: 0x1996 instead
[   29.720000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110010: 0x22d7 instead
[   29.840000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110014: 0xcbd1 instead
[   29.950000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110018: 0x07d9 instead
[   30.070000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0011001c: 0x9a49 instead
[   30.180000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110020: 0xe7f5 instead
[   30.290000] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00110024: 0x3d41 instead
[   30.410000] jffs2: Further such events for this erase block will not be printed

...

[   36.300000] jffs2: Further such events for this erase block will not be printed
[   36.470000] jffs2: Empty flash at 0x00153dfc ends at 0x00156dd0
[   36.640000] jffs2: Empty flash at 0x00156dd4 ends at 0x0015eda8
[   37.000000] jffs2: Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes
[   37.100000] jffs2: empty_blocks 84, bad_blocks 0, c->nr_blocks 107
[   37.170000] VFS: Cannot open root device "(null)" or unknown-block(31,1): error -5
[   37.260000] Please append a correct "root=" boot option; here are the available partitions:
[   37.360000] 1f00             192 mtdblock0  (driver?)
[   37.430000] 1f01            6848 mtdblock1  (driver?)
[   37.490000] 1f02            4096 mtdblock2  (driver?)
[   37.550000] 1f03            1024 mtdblock3  (driver?)
[   37.610000] 1f04              60 mtdblock4  (driver?)
[   37.670000] 1f05               4 mtdblock5  (driver?)
[   37.730000] 1f06              64 mtdblock6  (driver?)
[   37.790000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1)

A workaround found is to disable GPIO LEDs in the target kernel (i.e. disable all soft LED control). Just disabling the kmod-leds-gpio package in menuconfig does not appear sufficient.

Index: target/linux/atheros/base-files/etc/uci-defaults/01_leds
===================================================================
--- target/linux/atheros/base-files/etc/uci-defaults/01_leds	(revision 36225)
+++ target/linux/atheros/base-files/etc/uci-defaults/01_leds	(working copy)
@@ -4,8 +4,8 @@
 
 . /lib/functions/uci-defaults.sh
 
-ucidef_set_led_netdev "wlan" "wlan" "wlan" "wlan0"
+#ucidef_set_led_netdev "wlan" "wlan" "wlan" "wlan0"
 
-ucidef_commit_leds
+#ucidef_commit_leds
 
 exit 0
Index: target/linux/atheros/config-3.8
===================================================================
--- target/linux/atheros/config-3.8	(revision 36225)
+++ target/linux/atheros/config-3.8	(working copy)
@@ -79,7 +79,8 @@
 CONFIG_IP17XX_PHY=y
 CONFIG_IRQ_CPU=y
 CONFIG_IRQ_FORCED_THREADING=y
-CONFIG_LEDS_GPIO=y
+#CONFIG_LEDS_GPIO=y
+CONFIG_LEDS_GPIO=n
 CONFIG_MDIO_BOARDINFO=y
 CONFIG_MIPS=y
 CONFIG_MIPS_L1_CACHE_SHIFT=5

These boot error appear to identical to ones also occurring on AR2315-based Engenius devices, described in this issue below. The assumed cause is that GPIO LED control is interfering with SPI flash chip select on these boards.
/ticket/11969.html

Attachments (0)

Change History (1)

comment:1 Changed 4 years ago by jow

  • Milestone changed from Attitude Adjustment 12.09 to Barrier Breaker 14.07

Milestone Attitude Adjustment 12.09 deleted

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.