Re: kern/57564 raspberry pi zero W also panic in linux (should be closed?)

To: gnats-bugs%netbsd.org@localhost
Subject: Re: kern/57564 raspberry pi zero W also panic in linux (should be closed?)
From: Ramiro Aceves <ea1abz%gmail.com@localhost>
Date: Fri, 22 Sep 2023 20:10:56 +0200

Hello

After several days of long and boring CVS/rm cycle tortureRaspberryPiZeroW testing, here we have the results.

As some people here suggested, first of all I wanted to discard afaulty power supply.

Using the USB power adaptor mentioned before, I connected my Flukevoltage tester to the GPIO 5V/GND RaspberryPi Zero W GPIO header pins inmax/min voltage measurement mode. After a CVS/rm torture test, max andmin voltage values were registered (VMAX= 5 .008V / Vmin= 4.986 V). Noproblem at all, voltage was good. Panics were present in raspbian at 1 GHz.

To definitely discard a power supply problem at all, I connected theRaspberryPi ZeroW to my laboratory linear power supply, feeding the Pithrough 5V/GND GPIO header pins (using two 5V pins and 2 GND pins tohave a better connection). 5V voltage and 5 A max current setting werestablished on the power supply. The panics showed up again in raspbianat 1 GHz máx frequency with a good power supply, so I definititelydiscarded a power supply issue.

So I burned again my previously saved copy of NetBSD in my new 64 GB SDcard and tested again both 1 GHz and 700 MHz fixed frequency. At 1 GHzfixed frequency and after a random number of few hours I got the usualkernel panics. I eventually got a slightly different kernel diagnosticassertion panic that failed at a different function:

Sep 12 02:26:30 raspa-netbsd syslogd[456]: restartSep 12 02:26:30 raspa-netbsd /netbsd: [22577.8104056] panic: kernel diagnostic assertion "!cpu_softintr_p()"failed: file "../../../../kern/subr_kmem.c", line 431Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8104056] cpu0: Begintraceback...Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8104056] 0xc8b3db54:netbsd:db_panic+0xc Sep 12 02:26:30 raspa-netbsd /netbsd: [22577.8104056] 0xc8b3db74: netbsd:vpanic+0xf4Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8104056] 0xc8b3db8c:netbsd:kern_assert+0x3cSep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8104056] 0xc8b3dbc4:netbsd:kmem_zalloc+0xd0Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8204366] 0xc8b3dbfc:netbsd:bwfm_proto_bcdc_set_dcmd+0x44Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8204366] 0xc8b3dc2c:netbsd:bwfm_start+0x1b4Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8204366] 0xc8b3dc54:netbsd:if_transmit+0x13cSep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8204366] 0xc8b3dc9c:netbsd:ether_output+0x2c0 Sep 12 02:26:30 raspa-netbsd /netbsd: [22577.8304615] 0xc8b3dce4: netbsd:arprequest+0x1d0Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8304615] 0xc8b3dd54:netbsd:arp_llinfo_output+0x158Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8304615] 0xc8b3dedc:netbsd:nd_timer+0x390 Sep 12 02:26:30 raspa-netbsd /netbsd: [22577.8404855] 0xc8b3df24: netbsd:callout_softclock+0xccSep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8404855] 0xc8b3dfac:netbsd:softint_dispatch+0x118Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8404855] 0xc96ede44:netbsd:softint_switch+0x5c Sep 12 02:26:30 raspa-netbsd /netbsd: [22577.8404855] 0xc96edec4: netbsd:irq_entry+0xacSep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8505045] 0xc96edf14:netbsd:mi_switch+0x2e4Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8505045] 0xc96edf44:netbsd:sleepq_block+0xb0Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8505045] 0xc96edf6c:netbsd:cv_wait+0x50Sep 12 02:26:30 raspa-netbsd /netbsd: [ 22577.8505045] 0xc96edfac: [1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,Sep 12 02:26:30 raspa-netbsd /netbsd: [ 1.0000000] 2004, 2005,2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,Sep 12 02:26:30 raspa-netbsd /netbsd: [ 1.0000000] 2014, 2015,2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023Sep 12 02:26:30 raspa-netbsd /netbsd: [ 1.0000000] The NetBSDFoundation, Inc. All rights reserved.

At 700 MHz there were no kernel panics. On the other hand, I gotfrequent WIFI failures with network stopped working. I connected a TVHDMI set to see what happened. The system was alive but could notrecover the network without a reboot.

I suspected that my Raspberry Pi Zero W did not work properly at highfrequency.

I have here another Raspberry pi Zero PCB that has been working withoutproblems during several years. So I started to run the tests in NetBSDand Raspbian to see if there was diferences among both RaspberryPis. Ihave called them "The Flaky" and "The Good" RaspberryPi Zero W.


The results of the comparison test between both Raspberries:

******** FLAKY RASPBERRY ZERO W **********

NetBSD @ 1 GHz
   AFTER RANDOM NUMBER OF FEW HOURS:

   KERNEL PANIC->IT REBOOTS
   OR
   WIFI FAILURE-> NO NETWORK
   ( SYSTEM ALIVE BUT NETWORK NOT   RECOVERALE WITHOUT REBOOT)


NetBSD @ 700 MHz

   AFTER RANDOM NUMBER OF FEW HOURS:

   NO KERNEL PANICS

   WIFI FAILURE-> NO NETWORK
   ( SYSTEM ALIVE BUT NETWORK NOT  RECOVERALE WITHOUT REBOOT)"


RASPBIAN @700-1000 MHz F SCALING
   AFTER RANDOM NUMBER OF FEW HOURS:

   KERNEL PANIC-> IT HANGS


RASPBIAN  @ 700-900 MHz F SCALING
   AFTER 72 DAYS RUNNING FINE:
   SD CARD DIED.

*************************************************

********* GOOD RASPBERRY PI ZERO W ********

NetBSD @ 1 GHz
   AFTER RANDOM NUMBER OF FEW HOURS:

   NO KERNEL PANICS

   WIFI FAILURE-> NO NETWORK
   ( SYSTEM ALIVE BUT NETWORK NOT RECOVERALE WITHOUT REBOOT)

NetBSD @ 700 MHz
   NOT TESTED

RASPBIAN @ 700-1000 MHz F SCALING
   RUNS JUST FINE (DURING 5 DAYS AND  I STOPPED THE TEST)


RASPBIAN @ 700-900 MHz F SCALING
   NOT TESTED

**************************************************

So my conclusion is that my Flaky Rpi does not work properly at 1 GHz inboth NetBSD and Raspbian. Some people in internet have experienced thesame behaviour. I do not know if there are a few faulty units or youare in luck if your RaspberryPiZeroW works at 1 GHz without problems.The problem arises when the system is stressed and the scaling algorithmselects the highest CPU speed. In a relaxed Rpi the issue is moredifficult to happen. On the other hand, on my NetBSD system with fixed 1GHz CPU speed, the issue is more likely to happen.

Also noticed that bwfm WIFI NetBSD driver does not work reliable (Ithink that more people complain about the driver in other platforms).That is odd because the system becomes unreachable very frequently andyou need to reboot it.


Please let me know what you think and  if this bug can be closed now.

Regards.
Ramiro

Follow-Ups:
- Re: kern/57564 raspberry pi zero W also panic in linux (should be closed?)
  - From: Mouse
- Re: kern/57564 raspberry pi zero W also panic in linux (should be closed?)
  - From: John Klos

Prev by Date: Re: wondering about Xilinx Zynq 7000 support
Next by Date: Re: kern/57564 raspberry pi zero W also panic in linux (should be closed?)
Previous by Thread: -current doesn't accept root=
Next by Thread: Re: kern/57564 raspberry pi zero W also panic in linux (should be closed?)
Indexes:

Home | Main Index | Thread Index | Old Index