KingNovy/CWWK Mini PC Intel N305, running Debian (Proxmox) but very often reboots, suspecting a hardware/motherboard issue, how to investigate?

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

newsboost

New Member
Jul 15, 2022
11
2
3
Hi,

After reading this forum for some time, back in June I bought myself something that very much looks like CWWK / King Novy mini pc 12th Gen Intel i3 Alder Lake N305 - 32 GB RAM. Unfortunately I was very busy for some months but I installed Proxmox and pfSense back around November and replaced my older server with this much newer and more capable minipc so I was happy... I thought... Initially it ran fine, but lately it's rebooting more often than ever. I tried to ask in a reddit forum, but nobody has any clue about what's going on. So I thought, you people in here knows the hardware, motherboard etc better than in a general Linux forum, furthermore people who buy this hardware and has experience with it, is probably found here. Initially I thought it was a software problem, because nobody could explain it:

Code:
# last -x shutdown reboot
reboot   system boot  6.5.11-7-pve     Fri Jan 26 18:01   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 15:01   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 11:02   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 09:02   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 07:01   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 06:02   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 05:03   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 03:02   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 02:02   still running
reboot   system boot  6.5.11-7-pve     Fri Jan 26 01:03   still running
reboot   system boot  6.5.11-7-pve     Thu Jan 25 23:03   still running
reboot   system boot  6.5.11-7-pve     Thu Jan 25 22:02   still running
reboot   system boot  6.5.11-7-pve     Thu Jan 25 18:01   still running
reboot   system boot  6.5.11-7-pve     Wed Jan 24 23:48   still running
shutdown system down  6.5.11-7-pve     Wed Jan 24 23:48 - 23:48  (00:00)
reboot   system boot  6.5.11-7-pve     Wed Jan 24 20:02 - 23:48  (03:45)
reboot   system boot  6.5.11-7-pve     Wed Jan 24 14:03 - 23:48  (09:45)
reboot   system boot  6.5.11-7-pve     Wed Jan 24 08:02 - 23:48  (15:45)
reboot   system boot  6.5.11-7-pve     Wed Jan 24 04:03 - 23:48  (19:44)
reboot   system boot  6.5.11-7-pve     Tue Jan 23 18:02 - 23:48 (1+05:45)
reboot   system boot  6.5.11-7-pve     Mon Jan 22 06:01 - 23:48 (2+17:46)
reboot   system boot  6.5.11-7-pve     Sun Jan 21 18:02 - 23:48 (3+05:45)
reboot   system boot  6.5.11-7-pve     Sun Jan 21 12:01 - 23:48 (3+11:46)
...
Now I'm suspecting it's a hardware problem, triggered by something that happens a few minutes past the hour - but only sometimes...

It's for sure not a temperature issue because I've placed a big USB-fan on top of the cooling fins to help the heat dissipate (I noticed, it can actually be quite warm during a CPU stress test), furthermore I bought a 12V internal 8010 fan because I want my hardware to run cool, so it lasts for many, many years. Currently the CPU load is generally very/really low. I was also suspecting that perhaps the power supply isn't good enough, but if you look at the numbers, then most of this happens just 1-3 minutes past the hour so it also cannot be the power supply. Furthermore, just by looking at the PSU, it seems or looks big enough, physically (although, it's just my impression). The /etc/cron.hourly/ directory is empty. When I posted in reddit, usually I'll get quick feedback, ideas etc - but nothing at all here. You can download the journalctl output here Easyupload.io - Upload Files and Share Them Easily as a text file, if you wish, this includes the output for several of the reboots - I don't see anything suspicious immediately before the reboots happen... This is the hardware:

Code:
Hardware:
   product: CW-AD4L-N V1 (Default string)
    vendor: CWWK
    capabilities: smbios-3.5.0 dmi-3.5.0 smp vsyscall32
    configuration: boot=normal chassis=desktop family=Default string sku=Default string uuid=03000200-0400-0500-0006-000700080009
  *-core
       description: Motherboard
       product: CW-AD4L-N V1
       vendor: CWWK
     *-firmware
          description: BIOS
          vendor: American Megatrends International, LLC.
          version: 5.27
          date: 04/04/2023
     *-memory
          size: 32GiB
        *-bank:0
             description: SODIMM Synchronous 4800 MHz (0.2 ns)
             product: M425R4GA3BB0-CQKOD
             vendor: Micron Technology
             slot: Controller0-ChannelA-DIMM0
             size: 32GiB
             clock: 505MHz (2.0ns)
     *-cpu
          product: Intel(R) Core(TM) i3-N305
          version: 6.190.0
          size: 1002MHz
          capacity: 3800MHz

           *-network
                description: Ethernet controller
                product: Ethernet Controller I226-V
                vendor: Intel Corporation
                version: 04
                width: 32 bits
                clock: 33MHz
                capabilities: pm msi msix pciexpress bus_master cap_list
                configuration: driver=vfio-pci latency=0
                resources: irq:18 memory:80a00000-80afffff memory:80b00000-80b03fff

           *-nvme
                product: Fanxiang S500PRO 1TB
                vendor: MAXIO Technology (Hangzhou) Ltd.
                version: SN10613

           *-nvme
                product: KXG50PNV1T02 NVMe TOSHIBA 1024GB
                vendor: Toshiba Corporation
I'm really disappointed by CWWK / King Novy by this... I bought one of their top products, 32 GB RAM, one of the best CPU's - and then this happens, it cannot even run 24/7 for a day without rebooting and stopping my services. Luckily it resumes within 3-4 minutes, but if you're using the internet and this happens and you have to wait 3-4 minutes, it's just unacceptable. I obviously googled for this problem and found a guy who also was troubled by random reboots and he reduced the memory frequency, so I went into the BIOS: Chipset -> System Agent (SA) Configuration -> Memory Configuration -> Maximum Memory Frequency: Auto -> 2133 - but after that NOTHING worked, it took me many hours before I realized they've put a CMOS RESET button outside the chassis, which eventually enabled me to restore and run the server again - but probably not without several daily reboots...

Last time I interacted with the aliexpress seller, I was extremely disappointed (time to reply was incredibly slow and the answers were almost like "go f yourself" and it didn't help to followup with more questions). I'm considering if this is the last time I ever buy one of their products and how I should proceed. I would be grateful for any ideas, that can help solve this problem, because I've actually been happy about the hardware and very small size itself...

Thanks!
 

newsboost

New Member
Jul 15, 2022
11
2
3
Hi, I currently don't think. I currently think it's an issue with taking 12V from a pin on the motherboard, for driving a 8010 internal fan, because I like to keep my system as cool as possible so the hardware runs for as many years as possible. I never received any documentation for the motherboard - no PDF explaining the details about things on the motherboard. This crappy chinese vendor informed me that it's possible to install a 8010 internal 12V fan and I ordered one, also had to order the connector that fits over the pins and then I soldered the wires - you can see a picture here, as I think this is the best forum to ask for this specific hardware: image - now I'm wondering, if I used the wrong pins/connector? Anyone had better luck, connecting an internal fan - or maybe even similar experiences with random reboots, after connecting a 12V internal fan?

After asking the original question on reddit, I suspect this is the problem: reddit - so this made me disable the 8010 fan and uptime is currently almost 21 hours - which is good - but I'm first considering the mystery solved when it has been running for a week at least - hopefully at least a month (I'll probably write again if the problem really has been solved or not)..... Still, I would like to connect the internal fan, but of course if this is the problem, I'm very happy to have found some kind of explanation as I'm willing to run without an internal fan if that solves my crazy reboot-problem...
 

newsboost

New Member
Jul 15, 2022
11
2
3
Check your logs, could it be a nic driver issue?
Update: Okay, the problem has not been solved. Even after disabling the internal fan, I can see it sometimes reboots... Then I'm out of ideas, except the hardware is malfunctioning and I should probably never ever again buy CWWK / King Novy / Topton etc from AliExpress... Not only does it cost money - but also many, many hours, that things aren't working...