Hello ronjohnson, hello Matthias,
any news here? My device has exactly the same behaviour, even the LEDs are the same.
I came here by googling the Kernel panic, after several retries and tests.
I could provide complete logs, but they are "nearly exact" the same as ronjohnsons, even the timing is the same (same brick ;/ ).
any news here? My device has exactly the same behaviour, even the LEDs are the same.
I came here by googling the Kernel panic, after several retries and tests.
I could provide complete logs, but they are "nearly exact" the same as ronjohnsons, even the timing is the same (same brick ;/ ).
[ 0.000000] Linux version 3.3.8 (blogic@Debian-60-squeeze-64-minimal) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #1 Sun Nov 18 04:31:55 UTC 2012 ... [ 0.000000] Memory: 29008k/32768k available (2209k kernel code, 3760k reserved, 412k data, 212k init, 0k highmem) ... [ 0.490000] m25p80 spi0.0: unrecognized JEDEC id c84016 ... [ 1.070000] ag71xx ag71xx.0: eth0: connected to PHY at ag71xx-mdio.1:00 [uid=004dd041, driver=Generic PHY] [ 1.080000] TCP cubic registered [ 1.080000] NET: Registered protocol family 17 [ 1.090000] Bridge firewalling registered [ 1.090000] 8021q: 802.1Q VLAN Support v1.8 [ 1.100000] VFS: Cannot open root device "(null)" or unknown-block(0,0) [ 1.100000] Please append a correct "root=" boot option; here are the available partitions: [ 1.110000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)