3 added 151 characters in body
source | link

friendly forum!

I had just setup my 3B+ with ssh certificates and things(booting from a Sandisk Cruze 16GB, no other device connected, wifi internet) and was tinkering with the motd when I ran a

grep -rnw '/' -e 'The black cat ran across the floor'

causing the Pi to think for ten or so seconds, show a few matches or none, then:

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.377471] 3fe0: 00000000 7e84609c 0002f728 76e9453c 60000010 00000003 00000000 00000000

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.398610] Code: ebfac537 e5141004 e5142008 e0881001 (e5913000)

Segmentation fault

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.320014] Internal error: Oops: 17 [#1] SMP ARM

whereafter it stalls when attempting a reboot.

I have seen https://github.com/raspberrypi/linux/issues/2481 and run rpi-update (4.14 -> 4.19 ) , set sdram_freq=450 in config.txt and rebooted and tried the same grep: same result.

Flashed a twin Sandisk Cruze 16GB with the same raspbian lite november 2018 official image, booted, did the same grep immediately: just the same result.

The old 3B did not do that with an OWFS usb adapter and a USB memory attached (booting from an SD card). Something appears amiss - I expect to be able to find a string in the file system and then proceed to reboot the pi.

Edit. I just tried starting the old 3B from a "new" rasbian on one of the Sandisk USB memory sticks, which worked, then I did the same grep and...precisely the same Oops and it stalls after "Stopped dhcpcd on all interfaces" just like the 3b+. HmmSame with the other (identical official power source). Am going to try it on (Can't test the 3A now just because of that.can't use a keyboard while booting from a USB drive)

Any help mucho appreciated. (Don't currently have an extra SD card to try and repro it when not booted from a USB device but that seems the next logical step). Perhaps someone else with a Pi that boots via USB can try the same grep?

friendly forum!

I had just setup my 3B+ with ssh certificates and things(booting from a Sandisk Cruze 16GB, no other device connected, wifi internet) and was tinkering with the motd when I ran a

grep -rnw '/' -e 'The black cat ran across the floor'

causing the Pi to think for ten or so seconds, show a few matches or none, then:

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.377471] 3fe0: 00000000 7e84609c 0002f728 76e9453c 60000010 00000003 00000000 00000000

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.398610] Code: ebfac537 e5141004 e5142008 e0881001 (e5913000)

Segmentation fault

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.320014] Internal error: Oops: 17 [#1] SMP ARM

whereafter it stalls when attempting a reboot.

I have seen https://github.com/raspberrypi/linux/issues/2481 and run rpi-update (4.14 -> 4.19 ) , set sdram_freq=450 in config.txt and rebooted and tried the same grep: same result.

Flashed a twin Sandisk Cruze 16GB with the same raspbian lite november 2018 official image, booted, did the same grep immediately: just the same result.

The old 3B did not do that with an OWFS usb adapter and a USB memory attached (booting from an SD card). Something appears amiss - I expect to be able to find a string in the file system and then proceed to reboot the pi.

Edit. I just tried starting the old 3B from a "new" rasbian on one of the Sandisk USB memory sticks, which worked, then I did the same grep and...precisely the same Oops and it stalls after "Stopped dhcpcd on all interfaces" just like the 3b+. Hmm. Am going to try it on the 3A now just because of that.

Any help mucho appreciated. (Don't currently have an extra SD card to try and repro it when not booted from a USB device but that seems the next logical step)

friendly forum!

I had just setup my 3B+ with ssh certificates and things(booting from a Sandisk Cruze 16GB, no other device connected, wifi internet) and was tinkering with the motd when I ran a

grep -rnw '/' -e 'The black cat ran across the floor'

causing the Pi to think for ten or so seconds, show a few matches or none, then:

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.377471] 3fe0: 00000000 7e84609c 0002f728 76e9453c 60000010 00000003 00000000 00000000

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.398610] Code: ebfac537 e5141004 e5142008 e0881001 (e5913000)

Segmentation fault

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.320014] Internal error: Oops: 17 [#1] SMP ARM

whereafter it stalls when attempting a reboot.

I have seen https://github.com/raspberrypi/linux/issues/2481 and run rpi-update (4.14 -> 4.19 ) , set sdram_freq=450 in config.txt and rebooted and tried the same grep: same result.

Flashed a twin Sandisk Cruze 16GB with the same raspbian lite november 2018 official image, booted, did the same grep immediately: just the same result.

Something appears amiss - I expect to be able to find a string in the file system and then proceed to reboot the pi.

Edit. I just tried starting the old 3B from a "new" rasbian on one of the Sandisk USB memory sticks, which worked, then I did the same grep and...precisely the same Oops and it stalls after "Stopped dhcpcd on all interfaces" just like the 3b+. Same with the other (identical official power source). (Can't test the 3A because can't use a keyboard while booting from a USB drive)

Any help mucho appreciated. (Don't currently have an extra SD card to try and repro it when not booted from a USB device but that seems the next logical step). Perhaps someone else with a Pi that boots via USB can try the same grep?

2 added 307 characters in body
source | link

friendly forum!

I had just setup my 3B+ with ssh certificates and things(booting from a Sandisk Cruze 16GB, no other device connected, wifi internet) and was tinkering with the motd when I ran a

grep -rnw '/' -e 'The black cat ran across the floor'

causing the Pi to think for ten or so seconds, show a few matches or none, then:

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.377471] 3fe0: 00000000 7e84609c 0002f728 76e9453c 60000010 00000003 00000000 00000000

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.398610] Code: ebfac537 e5141004 e5142008 e0881001 (e5913000)

Segmentation fault

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.320014] Internal error: Oops: 17 [#1] SMP ARM

whereafter it stalls when attempting a reboot.

I have seen https://github.com/raspberrypi/linux/issues/2481 and run rpi-update (4.14 -> 4.19 ) , set sdram_freq=450 in config.txt and rebooted and tried the same grep: same result.

Flashed a twin Sandisk Cruze 16GB with the same raspbian lite november 2018 official image, booted, did the same grep immediately: just the same result.

The old 3B did not do that with an OWFS usb adapter and a USB memory attached (booting from an SD card). Something appears amiss - I expect to be able to find a string in the file system and then proceed to reboot the pi.

Edit. I just tried starting the old 3B from a "new" rasbian on one of the Sandisk USB memory sticks, which worked, then I did the same grep and...precisely the same Oops and it stalls after "Stopped dhcpcd on all interfaces" just like the 3b+. Hmm. Am going to try it on the 3A now just because of that.

Any help mucho appreciated. (Don't currently have an extra SD card to try and repro it when not booted from a USB device but that seems the next logical step)

friendly forum!

I had just setup my 3B+ with ssh certificates and things(booting from a Sandisk Cruze 16GB, no other device connected, wifi internet) and was tinkering with the motd when I ran a

grep -rnw '/' -e 'The black cat ran across the floor'

causing the Pi to think for ten or so seconds, show a few matches or none, then:

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.377471] 3fe0: 00000000 7e84609c 0002f728 76e9453c 60000010 00000003 00000000 00000000

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.398610] Code: ebfac537 e5141004 e5142008 e0881001 (e5913000)

Segmentation fault

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.320014] Internal error: Oops: 17 [#1] SMP ARM

whereafter it stalls when attempting a reboot.

I have seen https://github.com/raspberrypi/linux/issues/2481 and run rpi-update (4.14 -> 4.19 ) , set sdram_freq=450 in config.txt and rebooted and tried the same grep: same result.

Flashed a twin Sandisk Cruze 16GB with the same raspbian lite november 2018 official image, booted, did the same grep immediately: just the same result.

The old 3B did not do that with an OWFS usb adapter and a USB memory attached (booting from an SD card). Something appears amiss - I expect to be able to find a string in the file system and then proceed to reboot the pi.

Any help mucho appreciated. (Don't currently have an extra SD card to try and repro it when not booted from a USB device but that seems the next logical step)

friendly forum!

I had just setup my 3B+ with ssh certificates and things(booting from a Sandisk Cruze 16GB, no other device connected, wifi internet) and was tinkering with the motd when I ran a

grep -rnw '/' -e 'The black cat ran across the floor'

causing the Pi to think for ten or so seconds, show a few matches or none, then:

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.377471] 3fe0: 00000000 7e84609c 0002f728 76e9453c 60000010 00000003 00000000 00000000

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.398610] Code: ebfac537 e5141004 e5142008 e0881001 (e5913000)

Segmentation fault

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.320014] Internal error: Oops: 17 [#1] SMP ARM

whereafter it stalls when attempting a reboot.

I have seen https://github.com/raspberrypi/linux/issues/2481 and run rpi-update (4.14 -> 4.19 ) , set sdram_freq=450 in config.txt and rebooted and tried the same grep: same result.

Flashed a twin Sandisk Cruze 16GB with the same raspbian lite november 2018 official image, booted, did the same grep immediately: just the same result.

The old 3B did not do that with an OWFS usb adapter and a USB memory attached (booting from an SD card). Something appears amiss - I expect to be able to find a string in the file system and then proceed to reboot the pi.

Edit. I just tried starting the old 3B from a "new" rasbian on one of the Sandisk USB memory sticks, which worked, then I did the same grep and...precisely the same Oops and it stalls after "Stopped dhcpcd on all interfaces" just like the 3b+. Hmm. Am going to try it on the 3A now just because of that.

Any help mucho appreciated. (Don't currently have an extra SD card to try and repro it when not booted from a USB device but that seems the next logical step)

1
source | link

3B+ "Internal error: Oops: 17 [#1] SMP ARM" after system wide grep pattern matching

friendly forum!

I had just setup my 3B+ with ssh certificates and things(booting from a Sandisk Cruze 16GB, no other device connected, wifi internet) and was tinkering with the motd when I ran a

grep -rnw '/' -e 'The black cat ran across the floor'

causing the Pi to think for ten or so seconds, show a few matches or none, then:

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.377471] 3fe0: 00000000 7e84609c 0002f728 76e9453c 60000010 00000003 00000000 00000000

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.398610] Code: ebfac537 e5141004 e5142008 e0881001 (e5913000)

Segmentation fault

Message from syslogd@gra-owfs at Mar 31 18:14:11 ...

kernel:[ 240.320014] Internal error: Oops: 17 [#1] SMP ARM

whereafter it stalls when attempting a reboot.

I have seen https://github.com/raspberrypi/linux/issues/2481 and run rpi-update (4.14 -> 4.19 ) , set sdram_freq=450 in config.txt and rebooted and tried the same grep: same result.

Flashed a twin Sandisk Cruze 16GB with the same raspbian lite november 2018 official image, booted, did the same grep immediately: just the same result.

The old 3B did not do that with an OWFS usb adapter and a USB memory attached (booting from an SD card). Something appears amiss - I expect to be able to find a string in the file system and then proceed to reboot the pi.

Any help mucho appreciated. (Don't currently have an extra SD card to try and repro it when not booted from a USB device but that seems the next logical step)