Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 22:54, schrieb g4sra via Dng:

How do you know the mount is failing ?


It's not mounted after mount command.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-15 05:11, schrieb spiralofhope:

I wonder if there's anything S.M.A.R.T. information can tell you.

There is a spinup time test, and I wonder if perhaps there is SMART
logging within the drive that could reveal a problem with the drive not
spinning up as quickly as it should, and maybe that is causing a
problem (somehow).


=== START OF INFORMATION SECTION ===
Model Family: WDC HGST Ultrastar He10
Device Model: WDC WD100EMAZ-00WJTA0
Serial Number:1EGNK46Z
LU WWN Device Id: 5 000cca 27ec957bf
Firmware Version: 83.H0A83
User Capacity:10.000.831.348.736 bytes [10,0 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate:5400 rpm
Form Factor:  3.5 inches
Device is:In smartctl database [for details use: -P show]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Mon Jun 15 06:23:41 2020 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: 
Enabled.
Self-test execution status:  (   0) The previous self-test routine 
completed
without error or no self-test 
has ever

been run.
Total time to complete Offline
data collection:(   93) seconds.
Offline data collection
capabilities:(0x5b) SMART execute Offline immediate.
Auto Offline data collection 
on/off support.
Suspend Offline collection upon 
new

command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test 
supported.

Selective Self-test supported.
SMART capabilities:(0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:(0x01) Error logging supported.
General Purpose Logging 
supported.

Short self-test routine
recommended polling time:(   2) minutes.
Extended self-test routine
recommended polling time:(1159) minutes.
SCT capabilities:  (0x003d) SCT Status supported.
SCT Error Recovery Control 
supported.

SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  
UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate 0x000b   100   100   016Pre-fail  Always 
  -   0
  2 Throughput_Performance  0x0004   130   130   054Old_age   
Offline  -   110
  3 Spin_Up_Time0x0007   194   194   024Pre-fail  Always 
  -   328 (Average 350)
  4 Start_Stop_Count0x0012   100   100   000Old_age   Always 
  -   394
  5 Reallocated_Sector_Ct   0x0033   100   100   005Pre-fail  Always 
  -   0
  7 Seek_Error_Rate 0x000a   100   100   067Old_age   Always 
  -   0
  8 Seek_Time_Performance   0x0004   128   128   020Old_age   
Offline  -   18
  9 Power_On_Hours  0x0012   100   100   000Old_age   Always 
  -   4610
 10 Spin_Retry_Count0x0012   100   100   060Old_age   Always 
  -   0
 12 Power_Cycle_Count   0x0032   100   100   000Old_age   Always 
  -   393
 22 Helium_Level0x0023   100   100   025Pre-fail  Always 
  -   100
192 Power-Off_Retract_Count 0x0032   100   100   000Old_age   Always 
  -   561
193 Load_Cycle_Count0x0012   100   100   000Old_age   Always 
  -   561
194 Temperature_Celsius 0x0002   180   180   000Old_age   Always 
  -   36 (Min/Max 12/48)
196 Reallocated_Event_Count 0x0032   100   100   000Old_age   Always 
  -   0
197 Current_Pending_Sector  0x0022   100   100   000Old_age   Always 
  -   0
198 Offline_Uncorrectable   0x0008   100   100   000Old_age   
Offline  -   0
199 UDMA_CRC_Error_Count0x000a   200   200   000Old_age   Always 
  -   0


SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No 

Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread spiralofhope
On Fri, 12 Jun 2020 17:01:14 +0200
"J. Fahrner via Dng"  wrote:

> When this disk is active in /etc/fstab the boot process hangs
> forever.

I wonder if there's anything S.M.A.R.T. information can tell you.

There is a spinup time test, and I wonder if perhaps there is SMART
logging within the drive that could reveal a problem with the drive not
spinning up as quickly as it should, and maybe that is causing a
problem (somehow).

Keep in mind that not all USB docks will properly support SMART.

--

This may sound dumb, but does the drive _sound_ different when first
powered with the system, and does the sound change when it is mounted?
Does it sound like it's "waking up" only when you manually mount it?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan 3 running hot

2020-06-14 Thread Gregory Nowak
On Sun, Jun 14, 2020 at 02:30:39PM +0200, d...@d404.nl wrote:
> Which is still quiet high. I would advise to renew the thermal paste on
> your processor. I can recommend Arctic Silver 5 AS5-3.5G Thermal Paste.
> Made a difference of another 20°C on idle on my old i5.

If the system ran cool before the upgrade, thermal paste shouldn't be
the problem. What happens if you run with a 5.x kernel from
beowulf-backports, for instance
linux-image-5.4.0-0.bpo.2-amd64-unsigned?

Greg


-- 
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.

--
Free domains: http://www.eu.org/ or mail dns-mana...@eu.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread Simon Hobson
J. Fahrner via Dng  wrote:

> I don't see why this parameter is so important. When I read the description, 
> this is the delay for scanning usb devices after power up. But as you can see 
> in the logs, the device is responding and telling its characteristics. Only 
> mounting the filesystem fails.

As I've read the thread, the delay is between querying the USB bus for devices 
and trying to read from them. In your case, the device is been seen on the bus, 
but the mount fails - one possible cause of that is that the USB bridge device 
and/or disk are not ready in time, i.e. that the chippery and/or disk between 
them are not read to read data within 5s (if that's the default) of the devices 
being enumerated.
So changing this parameter is to see if giving a longer time between 
enumerating the devices on the bus (at which point, the chippery and disk 
should initialise and spin up) and actually trying to read form the disk. If it 
does, great; if it doesn't then there's a different problem.

> A smaller disk is no option, since this is my media server at home. It is 
> filled with 66%.

I think the idea was simply to try a smaller disk and see if that works. It's 
all in an effort to narrow down the list of possible causes - e.g. if it still 
won't mount then it being a big disk isn't the problem; if it does mount then 
at least you know it's not the USB chippery in the drive case.
At present, there are a lot of possible causes, which makes fixing the problem 
tricky.


Simon

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 21:49:50 +0200
"J. Fahrner via Dng"  wrote:

> > And an earlier suggestion to copy important things to a smaller disk
> > and use that disk, does that probably solve the issue?
> 
> A smaller disk is no option, since this is my media server at home.
> It is filled with 66%.

I meant just to find out if a smaller disk was mounting correctly.

> My mount scripts seem to work around this problem, so I give up in 
> further investigating what is happening.

Ok, I understand that you get moreorless crazy of this issue.
Fortunately the nofail option brought you a bit further.

HAND

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread g4sra via Dng

-- snip --
> Only mounting the filesystem fails.

How do you know the mount is failing ?

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 21:25, schrieb richard lucassen via Dng:

Ok, I missed that, sorry. Maybe 5 is too low, try 10 or 15 I'd say.


I don't see why this parameter is so important. When I read the 
description, this is the delay for scanning usb devices after power up. 
But as you can see in the logs, the device is responding and telling its 
characteristics. Only mounting the filesystem fails.



And an earlier suggestion to copy important things to a smaller disk
and use that disk, does that probably solve the issue?


A smaller disk is no option, since this is my media server at home. It 
is filled with 66%.


My mount scripts seem to work around this problem, so I give up in 
further investigating what is happening.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 20:48, schrieb richard lucassen:

What happens if you change the content of that script:

#!/bin/dash
echo 5 > /sys/module/usb_storage/parameters/delay_use


For what reason? I had it in /boot/boot.ini and that worked. I looked up 
/sys/module/usb_storage/parameters/delay_use and it was 5. But did not 
change my mount problem.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 20:31:22 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-14 20:07, schrieb d...@d404.nl:
> > It is a kernel parameter not a module parameter. You have to add it
> > to your kernel boot line.
> 
> Ok, I found out how to do that. It's in /boot/boot.ini
> But that made no difference to my problem.
> 
> This is my current setup:
> /etc/fstab has the mount option nofail, so the boot does not hang on 
> mountall.
> 
> I have a additional init script mounthdd:

What happens if you change the content of that script:

#!/bin/dash
echo 5 > /sys/module/usb_storage/parameters/delay_use

in a script /etc/rcS.d/00test.sh, just for test, normally you must set
a link.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 20:07, schrieb d...@d404.nl:

It is a kernel parameter not a module parameter. You have to add it to
your kernel boot line.


Ok, I found out how to do that. It's in /boot/boot.ini
But that made no difference to my problem.

This is my current setup:
/etc/fstab has the mount option nofail, so the boot does not hang on 
mountall.


I have a additional init script mounthdd:

# Provides:  hdd
...
if mountpoint -q /hdd
then
  echo 'HDD is already mounted'
else
  echo 'HHD is not mounted'
  mount /hdd
  /usr/local/bin/wait4hdd
fi

and the wait4hdd script:

#!/bin/sh
while ! mountpoint -q /hdd
do
  echo "Waiting for hdd"
  sleep 10
  mount /hdd
done

Now the following messages in /var/log/boot:

Thu Jan  1 01:00:18 1970: HHD is not mounted
Thu Jan  1 01:00:18 1970: Waiting for hdd
Sun Jun 14 20:19:24 2020: Waiting for hdd

Success after several tries.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 19:51, schrieb Tomasz Torcz:

  Try files in /sys/module/usb_storage/parameters
Or you can put in kernel command line: usb_storage.parameter=…
as described at
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html


Something is wrong her:

root@Odroid2:~# modprobe usb_storage delay_use=3
root@Odroid2:~# cat /sys/module/usb_storage/parameters/delay_use
5

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread d...@d404.nl
On 14-06-2020 19:46, J. Fahrner via Dng wrote:
> Am 2020-06-14 19:39, schrieb d...@d404.nl:
>> Most likely the usb_storage module is compiled in the kernel.
>
> How can I set its parameters in this case?
> sysctl -a lists nothing about storage or usb. 


From what i am able to find the kernel parameter:

    usb-storage.delay_use=

[UMS] The delay in seconds before a new device is scanned for Logical
Units (default 5).


Grtz.

Nick




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread Tomasz Torcz
On Sun, Jun 14, 2020 at 07:46:57PM +0200, J. Fahrner via Dng wrote:
> Am 2020-06-14 19:39, schrieb d...@d404.nl:
> > Most likely the usb_storage module is compiled in the kernel.
> 
> How can I set its parameters in this case?

  Try files in /sys/module/usb_storage/parameters
Or you can put in kernel command line: usb_storage.parameter=…
as described at
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html

-- 
Tomasz Torcz “God, root, what's the difference?”
to...@pipebreaker.pl   “God is more forgiving.”

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 19:39, schrieb d...@d404.nl:

Most likely the usb_storage module is compiled in the kernel.


How can I set its parameters in this case?
sysctl -a lists nothing about storage or usb.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread d...@d404.nl
On 14-06-2020 19:36, J. Fahrner via Dng wrote:
> Am 2020-06-14 19:30, schrieb richard lucassen:
>> What tells "modinfo g_mass_storage"?
>
> $ sudo modinfo g_mass_storage
> filename:  
> /lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko
> license:    GPL
> author: Michal Nazarewicz
> description:    Mass Storage Gadget
> depends:    usb_f_mass_storage,libcomposite
> intree: Y
> vermagic:   3.16.82+ SMP preempt mod_unload aarch64
> parm:   idVendor:USB Vendor ID (ushort)
> parm:   idProduct:USB Product ID (ushort)
> parm:   bcdDevice:USB Device version (BCD) (ushort)
> parm:   iSerialNumber:SerialNumber string (charp)
> parm:   iManufacturer:USB Manufacturer string (charp)
> parm:   iProduct:USB Product string (charp)
> parm:   file:names of backing files or devices (array of charp)
> parm:   ro:true to force read-only (array of bool)
> parm:   removable:true to simulate removable media (array of
> bool)
> parm:   cdrom:true to simulate CD-ROM instead of disk (array
> of bool)
> parm:   nofua:true to ignore SCSI WRITE(10,12) FUA bit (array
> of bool)
> parm:   luns:number of LUNs (uint)
> parm:   stall:false to prevent bulk stalls (bool)
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

g_mass_storage is used in usb otg mode where the system mimicks a usb
gadget. Most likely the usb_storage module is compiled in the kernel.


Grtz.

Nick



signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 19:30, schrieb richard lucassen:

What tells "modinfo g_mass_storage"?


$ sudo modinfo g_mass_storage
filename:   
/lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko

license:GPL
author: Michal Nazarewicz
description:Mass Storage Gadget
depends:usb_f_mass_storage,libcomposite
intree: Y
vermagic:   3.16.82+ SMP preempt mod_unload aarch64
parm:   idVendor:USB Vendor ID (ushort)
parm:   idProduct:USB Product ID (ushort)
parm:   bcdDevice:USB Device version (BCD) (ushort)
parm:   iSerialNumber:SerialNumber string (charp)
parm:   iManufacturer:USB Manufacturer string (charp)
parm:   iProduct:USB Product string (charp)
parm:   file:names of backing files or devices (array of charp)
parm:   ro:true to force read-only (array of bool)
parm:   removable:true to simulate removable media (array of 
bool)
parm:   cdrom:true to simulate CD-ROM instead of disk (array of 
bool)
parm:   nofua:true to ignore SCSI WRITE(10,12) FUA bit (array of 
bool)

parm:   luns:number of LUNs (uint)
parm:   stall:false to prevent bulk stalls (bool)
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 19:11:38 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-14 19:07, schrieb J. Fahrner via Dng:
> > modinfo: ERROR: Module usb_storage not found.
> 
> Maybe they have their own drivers for usb?
> 
> # find /lib/modules/3.16.82+/kernel/drivers -name '*storage*'
> /lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko
> /lib/modules/3.16.82+/kernel/drivers/usb/gadget/usb_f_mass_storage.ko

$ find /lib/modules/5.6.0-2-amd64/kernel/drivers -name '*storage*'
/lib/modules/5.6.0-2-amd64/kernel/drivers/usb/storage
/lib/modules/5.6.0-2-amd64/kernel/drivers/usb/storage/usb-storage.ko
/lib/modules/5.6.0-2-amd64/kernel/drivers/usb/gadget/function/usb_f_mass_storage.ko

Or the module is built in the kernel.
What tells "modinfo g_mass_storage"? If it's the same module as
usb_storage having the same parameters, then:

echo "options g_mass_storage delay_use=5" > \
  /etc/modprobe.d/g_mass_storage.conf

It's a pretty old kernel, if it doesn't work and the module is built
in, one thing you might try is to put:

#!/bin/dash
echo 5 > /sys/module/usb_storage/parameters/delay_use

in a script /etc/rcS.d/00test.sh

HTH

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 19:07, schrieb J. Fahrner via Dng:

modinfo: ERROR: Module usb_storage not found.


Maybe they have their own drivers for usb?

# find /lib/modules/3.16.82+/kernel/drivers -name '*storage*'
/lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko
/lib/modules/3.16.82+/kernel/drivers/usb/gadget/usb_f_mass_storage.ko
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 19:05, schrieb richard lucassen:

That's rather strange. From "modinfo usb_storage":

parm: delay_use:seconds to delay before using a new device (uint)

And what happens if you load the module in advance?:

echo "usb_storage" >> /etc/modules


modinfo: ERROR: Module usb_storage not found.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 18:38:48 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-14 17:25, schrieb richard lucassen via Dng:
> > echo "options usb_storage delay_use=5" > 
> > /etc/modprobe.d/usb_storage.conf
> 
> seems not to work.
> 
> After boot:
> 
> cat /sys/module/usb_storage/parameters/delay_use
> 1

That's rather strange. From "modinfo usb_storage":

parm: delay_use:seconds to delay before using a new device (uint)

And what happens if you load the module in advance?:

echo "usb_storage" >> /etc/modules



-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 17:25, schrieb richard lucassen via Dng:
echo "options usb_storage delay_use=5" > 
/etc/modprobe.d/usb_storage.conf


seems not to work.

After boot:

cat /sys/module/usb_storage/parameters/delay_use
1
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 17:24:01 +0200
richard lucassen via Dng  wrote:

Oops:

echo "options usb_storage delay_use=5" /etc/modprobe.d/usb_storage.conf

must be:

echo "options usb_storage delay_use=5" > /etc/modprobe.d/usb_storage.conf

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 14:12:21 +0200
"J. Fahrner via Dng"  wrote:

> Very big device. Trying to use READ CAPACITY

You may try this:

echo "options usb_storage delay_use=5" /etc/modprobe.d/usb_storage.conf

https://bbs.archlinux.org/viewtopic.php?id=125831

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread Tito via Dng


On 6/14/20 4:44 PM, J. Fahrner via Dng wrote:
> Am 2020-06-14 15:09, schrieb Dr. Nikolaus Klepp:
>> Anno domini 2020 Sun, 14 Jun 14:12:21 +0200
>>  J. Fahrner via Dng scripsit:
>>> [   22.579214] sd 0:0:0:0: [sda] Attached SCSI disk
>>> [ 1145.246051] EXT4-fs (sda1): mounted filesystem with ordered data
>>
>> I see this on RPi, too, just the delay is smaller (~ 30 secs) - but
>> that's anoying, too.
> 
> That was my manual mount. The automatic mount did not happen.
Hi,
you could try to stick at various boot stages a little program like this:

__
#include 
#include 
#include 
#include 
#include 

int main(int argc, char ** argv)
{
/* Eventually adjust the args to your liking */
if (mount("/dev/sda1", "/hdd", "ext4", 0, NULL) == -1) {
fprintf(stderr, "%s: %s\n", "mymount", strerror(errno));
syslog(LOG_ERR, "%s", strerror(errno));
} else {
fprintf(stderr, "%s: %s\n", "mymount", strerror(errno));
syslog(LOG_INFO, "%s", strerror(errno));
}
return 0;
}
__

Compile with:
gcc -Wall mymount.c -o mymount

This will log error or success to syslog with some hopefully meaningful 
messages:

Jun 14 17:03:13 devuan kernel: EXT4-fs (sdm1): mounted filesystem with ordered 
data mode. Opts: (null)
Jun 14 17:03:13 devuan mymount: mymount: Success

Hope this helps.

Ciao,
Tito
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 15:09, schrieb Dr. Nikolaus Klepp:

Anno domini 2020 Sun, 14 Jun 14:12:21 +0200
 J. Fahrner via Dng scripsit:

[   22.579214] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1145.246051] EXT4-fs (sda1): mounted filesystem with ordered data


I see this on RPi, too, just the delay is smaller (~ 30 secs) - but
that's anoying, too.


That was my manual mount. The automatic mount did not happen.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread Dr. Nikolaus Klepp
Anno domini 2020 Sun, 14 Jun 14:12:21 +0200
 J. Fahrner via Dng scripsit:
> [   22.579214] sd 0:0:0:0: [sda] Attached SCSI disk
> [ 1145.246051] EXT4-fs (sda1): mounted filesystem with ordered data

I see this on RPi, too, just the delay is smaller (~ 30 secs) - but that's 
anoying, too.

Nik

-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan 3 running hot

2020-06-14 Thread d...@d404.nl
On 14-06-2020 14:14, Lars Noodén via Dng wrote:
> On 6/14/20 2:03 PM, d...@d404.nl wrote:
>> On 14-06-2020 12:53, Lars Noodén via Dng wrote:
>>> On 6/14/20 1:47 PM, d...@d404.nl wrote:
 On 14-06-2020 12:38, Lars Noodén via Dng wrote:
> An upgrade to Beowulf went very smoothly but since upgrading I notice
> that the fans are always running.  Although the air temperature is about
> 25°C the cores seem to run much hotter than necessary, pushing 70°C or
> hotter.  The system is not really under any load.  What should I be
> looking at to make corrections?
>
> -
>
> $ grep -i pretty /etc/os-release ; uname -sr
> PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
> Linux 4.19.0-9-amd64
>
>
 You can try to add  intel_pstate=disable to your startup line.
>>> Thanks.  It may already be disabled¹ though:
>>>
>>> # cat /sys/kernel/debug/tracing/events/power/pstate_sample/enable
>>> 0
>>>
>>> # cat /sys/kernel/debug/tracing/events/power/cpu_frequency/enable
>>> 0
>>>
>>> However, this is all an area I know nothing about.
>>>
>>> ¹ https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html
>>> ___
>> It is not my daily job either but what i understand when intel_pstate is
>> disabled acpi-cpufreq takes it over. (And most likely did in ASCII.)
>>
>> Give it a try and if it works add it to grub.
>>
> Seems to have made a difference of over 20°C.
>
>
> /Lars

Which is still quiet high. I would advise to renew the thermal paste on
your processor. I can recommend Arctic Silver 5 AS5-3.5G Thermal Paste.
Made a difference of another 20°C on idle on my old i5.

Grtz.

Nick




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan 3 running hot

2020-06-14 Thread Lars Noodén via Dng
On 6/14/20 2:03 PM, d...@d404.nl wrote:
> On 14-06-2020 12:53, Lars Noodén via Dng wrote:
>> On 6/14/20 1:47 PM, d...@d404.nl wrote:
>>> On 14-06-2020 12:38, Lars Noodén via Dng wrote:
 An upgrade to Beowulf went very smoothly but since upgrading I notice
 that the fans are always running.  Although the air temperature is about
 25°C the cores seem to run much hotter than necessary, pushing 70°C or
 hotter.  The system is not really under any load.  What should I be
 looking at to make corrections?

 -

 $ grep -i pretty /etc/os-release ; uname -sr
 PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
 Linux 4.19.0-9-amd64


>>> You can try to add  intel_pstate=disable to your startup line.
>> Thanks.  It may already be disabled¹ though:
>>
>> # cat /sys/kernel/debug/tracing/events/power/pstate_sample/enable
>> 0
>>
>> # cat /sys/kernel/debug/tracing/events/power/cpu_frequency/enable
>> 0
>>
>> However, this is all an area I know nothing about.
>>
>> ¹ https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html
>> ___
> 
> It is not my daily job either but what i understand when intel_pstate is
> disabled acpi-cpufreq takes it over. (And most likely did in ASCII.)
> 
> Give it a try and if it works add it to grub.
>

Seems to have made a difference of over 20°C.


/Lars
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 13:32, schrieb richard lucassen via Dng:

It's weird. What does "dmesg" tell?

dmesg > /tmp/dmesg

and look if there are any messages there


[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 3.16.82+ (root@odroid-stretch64) (gcc 
version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP PREEMPT Tue Mar 
17 18:33:26 CET 2020

[0.00] CPU: AArch64 Processor [410fd034] revision 4
[0.00] cma: CMA: reserved 8 MiB at 7f80
[0.00] On node 0 totalpages: 520192
[0.00]   Normal zone: 7112 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 520192 pages, LIFO batch:31
[0.00] psci: probing for conduit method from DT.
[0.00] psci: Using PSCI v0.1 Function IDs from DT
[0.00] PERCPU: Embedded 12 pages/cpu s19712 r8192 d21248 u49152
[0.00] pcpu-alloc: s19712 r8192 d21248 u49152 alloc=12*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  
Total pages: 513080
[0.00] Kernel command line: 
root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro 
consoleblank=0 console=ttyS0,115200n8 console=tty0 no_console_suspend 
hdmitx=cecf  hdmimode=1080p60hz m_bpp=32 vout= fsck.repair=yes 
elevator=noop disablehpd=true  max_freq=1536 maxcpus=4 
monitor_onoff=false disableuhs=false mmc_removable=true 
usbmulticam=false usbhid.quirks=0x0eef:0x0005:0x0004 net.ifnames=0

[0.00] logo: get hdmimode: 1080p60hz
[0.00] dvfs [get_max_freq] - max_freq : 153600
[0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[0.00] Dentry cache hash table entries: 262144 (order: 9, 
2097152 bytes)
[0.00] Inode-cache hash table entries: 131072 (order: 8, 1048576 
bytes)
[0.00] Memory: 2018152K/2080768K available (8530K kernel code, 
906K rwdata, 3120K rodata, 923K init, 4119K bss, 62616K reserved)

[0.00] Virtual kernel memory layout:
   vmalloc : 0xff80 - 0xffbb   
(245759 MB)
   vmemmap : 0xffbc - 0xffbc01c0   ( 
   28 MB)
   modules : 0xffbffc00 - 0xffc0   ( 
   64 MB)
   memory  : 0xffc0 - 0xffc08000   ( 
 2048 MB)
 .init : 0xffc001be2000 - 0xffc001cc8d00   ( 
  924 kB)
 .text : 0xffc00108 - 0xffc001be1804   ( 
11655 kB)
 .data : 0xffc001cc9000 - 0xffc001dabbb0   ( 
  907 kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, 
Nodes=1

[0.00] Preemptible hierarchical RCU implementation.
[0.00] NR_IRQS:64 nr_irqs:64 0
[0.06] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps 
every 2147483648000ns
[0.26] mclk->mux_reg =ff802990,mclk->reg 
=ff80a994
[0.72] local timer MESON TIMER-G mclk->mux_reg 
=ff802990,mclk->reg =ff80c998
[0.95] local timer MESON TIMER-H mclk->mux_reg 
=ff802990,mclk->reg =ff80e99c
[0.000116] local timer MESON TIMER-I mclk->mux_reg 
=ff802990,mclk->reg =ff8109a0

[0.000127] Switching to timer-based delay loop
[0.000358] Console: colour dummy device 80x25
[0.000676] console [tty0] enabled
[0.003001] allocated 8388608 bytes of page_cgroup
[0.003011] please try 'cgroup_disable=memory' option if you don't 
want memory cgroups
[0.003028] Calibrating delay loop (skipped), value calculated using 
timer frequency.. 2.00 BogoMIPS (lpj=1)

[0.003046] pid_max: default: 32768 minimum: 301
[0.003104] Security Framework initialized
[0.003131] AppArmor: AppArmor initialized
[0.003164] Mount-cache hash table entries: 4096 (order: 3, 32768 
bytes)
[0.003176] Mountpoint-cache hash table entries: 4096 (order: 3, 
32768 bytes)

[0.003649] Initializing cgroup subsys memory
[0.003724] Initializing cgroup subsys devices
[0.003749] Initializing cgroup subsys freezer
[0.003764] Initializing cgroup subsys net_cls
[0.003781] Initializing cgroup subsys blkio
[0.003797] Initializing cgroup subsys perf_event
[0.003809] Initializing cgroup subsys net_prio
[0.003833] Initializing cgroup subsys hugetlb
[0.003844] Initializing cgroup subsys debug
[0.003896] ftrace: allocating 30664 entries in 120 pages
[0.030888] hw perfevents: enabled with arm/armv8-pmuv3 PMU driver, 7 
counters available

[0.071902] Meson chip version = RevC (1F:C - 0:0)
[0.090840] CPU1: Booted secondary processor
[0.110817] CPU2: Booted secondary processor
[0.130814] CPU3: Booted secondary processor
[0.130856] Brought up 4 CPUs
[0.130889] SMP: Total of 4 processors activated.
[0.131354] devtmpfs: initialized
[

Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 13:23, schrieb Dr. Nikolaus Klepp:

Are you 100% absolutely sure your board is not stuck at the bootloader
stage before the kernel is started?


Yes. It responds to ping, so network is running.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 13:03:13 +0200
"J. Fahrner"  wrote:

> But if I do it interactively with "sudo mount /hdd" the drive gets 
> mounted and the waiting daemons are started.
> 
> I'm very confused...

When you mount it interactively the path is different and maybe it's
waiting for some input.

Try to add to the script:

PATH=${PATH}:/sbin:/usr/sbin

and

mount /dev/disk/ /mnt/mountpoint http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 13:03:13 +0200
"J. Fahrner"  wrote:

> But if I do it interactively with "sudo mount /hdd" the drive gets 
> mounted and the waiting daemons are started.
> 
> I'm very confused...

It's weird. What does "dmesg" tell?

dmesg > /tmp/dmesg

and look if there are any messages there

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread Dr. Nikolaus Klepp
Anno domini 2020 Sun, 14 Jun 13:03:13 +0200
 J. Fahrner via Dng scripsit:
> Am 2020-06-14 10:11, schrieb richard lucassen:
> > Did you format the disk with a newer system than the system you run it
> > on? So, I wonder what happens if you remove the huge_file option
> 
> I don't remember on which system I formatted that drive.
> After playing around the problem is very strange. It's not the 
> huge_files option.
> 
> With the "nofail" option in fstab the boot does not hang and I can 
> experiment a little bit.
> 
> I made a init script "mounthdd" which mounts the drive if it is not 
> already mounted, and execute it at several stages. Sometimes the mount 
> is successful, sometimes not. If I mount the drive interactively with 
> "sudo mount /hdd" I have 100% success. But if it's executed in 
> background, it mostly fails.
> 
> Next I wrote a little script "wait4hdd"
> 
> #!/bin/sh
> while ! mountpoint -q /hdd
> do
>sleep 10
> done
> 
> and inserted it in the init scripts for daemons that need the disk.
> Result: they are waiting endless.
> 
> Next I added a cronjob for root:
> */10 * * * * mountpoint -q /hdd || mount /hdd
> 
> That tries to mount the drive every 10 minutes if not already mounted.
> No success.
> 
> But if I do it interactively with "sudo mount /hdd" the drive gets 
> mounted and the waiting daemons are started.
> 
> I'm very confused...
> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
> 

Are you 100% absolutely sure your board is not stuck at the bootloader stage 
before the kernel is started?


-- 
Please do not email me anything that you are not comfortable also sharing with 
the NSA, CIA ...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Ascii to Beowulf upgrade - 32% slowdown !

2020-06-14 Thread Hendrik Boom
On Sun, Jun 14, 2020 at 08:46:48AM +0200, Riccardo Mottola via Dng wrote:
> Hi,
> 
> On 6/12/20 9:21 PM, Steve Litt wrote:
> > > Maybe try ;https://make-linux-fast-again.com/   kerneloptions to
> > > disable all spectre and meltdown stuff
> > I hope you mean the preceding as a diagnostic test and not as a
> > solution.
> 
> 
> first, diagnostic on what is slowing down and stealing performance in such a
> significant way.
> 
> second, it could be also acceptable as a solution: If a system like laptop
> is not running multi-user, no virtual machines and you consider the software
> running trusted, where are the risks? I think only in the browser which runs
> "unknown" and "untrusted" stuff: The only attack surface would be JavaScript
> (or Java, Flash or similar). If, from what I read, the browser removed high
> resolution timers, timing attacks needed to exploit these bugs are unlikely.
> 
> Am I simplifying too much and overseeing some holes?

Even if you will not run your system airgapped in production, it might 
be worth running it airgapped without mitigation as a diagnostic to see 
if mitigation is really the problem.  If it is, you know the situation 
and can restore mitigation before you connect to the world.  If it 
isn't, you know to look elsewhere.

-- hendrik

> 
> 
> Riccardo
> 

> ___
> Dng mailing list
> Dng@lists.dyne.org
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan 3 running hot

2020-06-14 Thread d...@d404.nl
On 14-06-2020 12:53, Lars Noodén via Dng wrote:
> On 6/14/20 1:47 PM, d...@d404.nl wrote:
>> On 14-06-2020 12:38, Lars Noodén via Dng wrote:
>>> An upgrade to Beowulf went very smoothly but since upgrading I notice
>>> that the fans are always running.  Although the air temperature is about
>>> 25°C the cores seem to run much hotter than necessary, pushing 70°C or
>>> hotter.  The system is not really under any load.  What should I be
>>> looking at to make corrections?
>>>
>>> -
>>>
>>> $ grep -i pretty /etc/os-release ; uname -sr
>>> PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
>>> Linux 4.19.0-9-amd64
>>>
>>>
>> You can try to add  intel_pstate=disable to your startup line.
> Thanks.  It may already be disabled¹ though:
>
> # cat /sys/kernel/debug/tracing/events/power/pstate_sample/enable
> 0
>
> # cat /sys/kernel/debug/tracing/events/power/cpu_frequency/enable
> 0
>
> However, this is all an area I know nothing about.
>
> ¹ https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html
> ___

It is not my daily job either but what i understand when intel_pstate is
disabled acpi-cpufreq takes it over. (And most likely did in ASCII.)

Give it a try and if it works add it to grub.


Grtz.


Nick




signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-14 10:11, schrieb richard lucassen:

Did you format the disk with a newer system than the system you run it
on? So, I wonder what happens if you remove the huge_file option


I don't remember on which system I formatted that drive.
After playing around the problem is very strange. It's not the 
huge_files option.


With the "nofail" option in fstab the boot does not hang and I can 
experiment a little bit.


I made a init script "mounthdd" which mounts the drive if it is not 
already mounted, and execute it at several stages. Sometimes the mount 
is successful, sometimes not. If I mount the drive interactively with 
"sudo mount /hdd" I have 100% success. But if it's executed in 
background, it mostly fails.


Next I wrote a little script "wait4hdd"

#!/bin/sh
while ! mountpoint -q /hdd
do
  sleep 10
done

and inserted it in the init scripts for daemons that need the disk.
Result: they are waiting endless.

Next I added a cronjob for root:
*/10 * * * * mountpoint -q /hdd || mount /hdd

That tries to mount the drive every 10 minutes if not already mounted.
No success.

But if I do it interactively with "sudo mount /hdd" the drive gets 
mounted and the waiting daemons are started.


I'm very confused...
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan 3 running hot

2020-06-14 Thread Lars Noodén via Dng
On 6/14/20 1:47 PM, d...@d404.nl wrote:
> On 14-06-2020 12:38, Lars Noodén via Dng wrote:
>> An upgrade to Beowulf went very smoothly but since upgrading I notice
>> that the fans are always running.  Although the air temperature is about
>> 25°C the cores seem to run much hotter than necessary, pushing 70°C or
>> hotter.  The system is not really under any load.  What should I be
>> looking at to make corrections?
>>
>> -
>>
>> $ grep -i pretty /etc/os-release ; uname -sr
>> PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
>> Linux 4.19.0-9-amd64
>>
>>
> You can try to add  intel_pstate=disable to your startup line.

Thanks.  It may already be disabled¹ though:

# cat /sys/kernel/debug/tracing/events/power/pstate_sample/enable
0

# cat /sys/kernel/debug/tracing/events/power/cpu_frequency/enable
0

However, this is all an area I know nothing about.

¹ https://www.kernel.org/doc/html/v4.12/admin-guide/pm/intel_pstate.html
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Devuan 3 running hot

2020-06-14 Thread d...@d404.nl
On 14-06-2020 12:38, Lars Noodén via Dng wrote:
> An upgrade to Beowulf went very smoothly but since upgrading I notice
> that the fans are always running.  Although the air temperature is about
> 25°C the cores seem to run much hotter than necessary, pushing 70°C or
> hotter.  The system is not really under any load.  What should I be
> looking at to make corrections?
>
> -
>
> $ grep -i pretty /etc/os-release ; uname -sr
> PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
> Linux 4.19.0-9-amd64
>
>
You can try to add  intel_pstate=disable to your startup line.

Grtz.


Nick





signature.asc
Description: OpenPGP digital signature
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] Error in repositories

2020-06-14 Thread J. Fahrner via Dng

On an "apt-get update" I get the following errors:

Err:10 http://pkgmaster.devuan.org/merged beowulf/main armhf Contents 
(deb)

  Hash Sum mismatch
  Hashes of expected file:
   - Filesize:31681725 [weak]
   - 
SHA256:04dda4a3166f89d6cd274bd662e29997a9c59c0015e3a29537c5918ff35edd01

  Hashes of received file:
   - 
SHA256:1a6257d5b3f955d4e5bb7b6c2d760734d5f3526a8469e55dbb0967f3235e3be3

   - Filesize:31681725 [weak]
  Last modification reported: Sat, 13 Jun 2020 23:25:25 +
  Release file created at: Sun, 14 Jun 2020 06:28:02 +

Err:26 http://pkgmaster.devuan.org/merged beowulf-updates/main armhf 
Contents (deb)

  Hash Sum mismatch
  Hashes of expected file:
   - Filesize:39165 [weak]
   - 
SHA256:7145f997c5a76b48594627eef3d031103b1dc64ac207f8d32f366de0d8507be1

  Hashes of received file:
   - 
SHA256:3dc42338c18b4a11cdaddb372147406907590635b921ac291e3dff3f02a52caa

   - Filesize:39165 [weak]
  Last modification reported: Sat, 13 Jun 2020 23:27:19 +
  Release file created at: Sun, 14 Jun 2020 08:32:01 +

Err:32 http://pkgmaster.devuan.org/merged beowulf-security/main arm64 
Contents (deb)

  Hash Sum mismatch
  Hashes of expected file:
   - Filesize:36 [weak]
   - 
SHA256:11ddecec635785e907e11a662850add534e38646eafa507b674f885ce1ce63eb

  Hashes of received file:
   - 
SHA256:5a4f741de9c8e09be68cecd014d109d97e6d0ba35395bb673770c7b5e388e302

   - Filesize:36 [weak]
  Last modification reported: Sat, 13 Jun 2020 23:21:42 +
  Release file created at: Sun, 14 Jun 2020 06:28:01 +

E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf/main/Contents-armhf.gz  
Hash Sum mismatch

   Hashes of expected file:
- Filesize:31681725 [weak]
- 
SHA256:04dda4a3166f89d6cd274bd662e29997a9c59c0015e3a29537c5918ff35edd01

   Hashes of received file:
- 
SHA256:1a6257d5b3f955d4e5bb7b6c2d760734d5f3526a8469e55dbb0967f3235e3be3

- Filesize:31681725 [weak]
   Last modification reported: Sat, 13 Jun 2020 23:25:25 +
   Release file created at: Sun, 14 Jun 2020 06:28:02 +
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf/main/Contents-arm64.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf/contrib/Contents-armhf.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf/contrib/Contents-arm64.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf/non-free/Contents-arm64.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf/non-free/Contents-armhf.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-updates/main/Contents-armhf.gz 
 Hash Sum mismatch

   Hashes of expected file:
- Filesize:39165 [weak]
- 
SHA256:7145f997c5a76b48594627eef3d031103b1dc64ac207f8d32f366de0d8507be1

   Hashes of received file:
- 
SHA256:3dc42338c18b4a11cdaddb372147406907590635b921ac291e3dff3f02a52caa

- Filesize:39165 [weak]
   Last modification reported: Sat, 13 Jun 2020 23:27:19 +
   Release file created at: Sun, 14 Jun 2020 08:32:01 +
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-updates/main/Contents-arm64.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-updates/contrib/Contents-armhf.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-updates/contrib/Contents-arm64.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-updates/non-free/Contents-armhf.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-updates/non-free/Contents-arm64.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-security/main/Contents-arm64.gz 
 Hash Sum mismatch

   Hashes of expected file:
- Filesize:36 [weak]
- 
SHA256:11ddecec635785e907e11a662850add534e38646eafa507b674f885ce1ce63eb

   Hashes of received file:
- 
SHA256:5a4f741de9c8e09be68cecd014d109d97e6d0ba35395bb673770c7b5e388e302

- Filesize:36 [weak]
   Last modification reported: Sat, 13 Jun 2020 23:21:42 +
   Release file created at: Sun, 14 Jun 2020 06:28:01 +
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-security/main/Contents-armhf.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-security/contrib/Contents-arm64.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-security/contrib/Contents-armhf.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-security/non-free/Contents-armhf.gz
E: Failed to fetch 
http://pkgmaster.devuan.org/merged/dists/beowulf-security/non-free/Contents-arm64.gz
E: Some index files failed to download. They have been ignored, or old 
ones used instead.

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] Devuan 3 running hot

2020-06-14 Thread Lars Noodén via Dng
An upgrade to Beowulf went very smoothly but since upgrading I notice
that the fans are always running.  Although the air temperature is about
25°C the cores seem to run much hotter than necessary, pushing 70°C or
hotter.  The system is not really under any load.  What should I be
looking at to make corrections?

-

$ grep -i pretty /etc/os-release ; uname -sr
PRETTY_NAME="Devuan GNU/Linux 3 (beowulf)"
Linux 4.19.0-9-amd64


-

coretemp-isa-
Adapter: ISA adapter
Package id 0:  +75.0°C  (high = +100.0°C, crit = +100.0°C)
Core 0:+75.0°C  (high = +100.0°C, crit = +100.0°C)
Core 1:+70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 2:+70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 3:+70.0°C  (high = +100.0°C, crit = +100.0°C)
Core 4:+69.0°C  (high = +100.0°C, crit = +100.0°C)
Core 5:+70.0°C  (high = +100.0°C, crit = +100.0°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:+73.0°C  (crit = +120.0°C)

iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:+44.0°C

pch_cannonlake-virtual-0
Adapter: Virtual device
temp1:+60.0°C

-

top - 13:32:45 up 21:00, 11 users,  load average: 0.90, 0.97, 0.99
Tasks: 309 total,   1 running, 308 sleeping,   0 stopped,   0 zombie
%Cpu(s):  0.1 us,  0.4 sy,  0.0 ni, 99.5 id,  0.0 wa,  0.0 hi,  0.0 si,
0.0 st
MiB Mem :  15752.8 total,   6909.7 free,   2698.7 used,   6144.4 buff/cache
MiB Swap:  15743.0 total,  15742.6 free,  0.4 used.  12197.7 avail Mem

  PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+
COMMAND

 2529 root  20   0  493780 133052  98824 S   4.7   0.8  21:21.22
Xorg

  291 root -51  19   0  0  0 D   3.7   0.0  20:10.16
irq/144-SYNA120

 2839 lars  20   0  520740  50288  33980 S   1.0   0.3   0:22.16
xfce4-terminal

29662 root  20   0   12236   3020   2400 R   0.3   0.0   0:13.18 top


1 root  20   07904   2064   1892 S   0.0   0.0   0:02.10
init

2 root  20   0   0  0  0 S   0.0   0.0   0:00.04
kthreadd

3 root   0 -20   0  0  0 I   0.0   0.0   0:00.00
rcu_gp
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] eudev-related problems after Beowulf upgrade

2020-06-14 Thread David Kuehling via Dng
> "fsmithred" == fsmithred via Dng  writes:

> On 6/12/20 10:05 AM, David Kuehling via Dng wrote:
>> 
[..]
>> 
>> - none of the alsa sound driver modules is loaded during boot, so I
>> end up with a Desktop that does not support audio
>> 
>> - the amdgpu module is not loaded, so not 3-D acceleration
>> 

> This problem was showing up in the live isos but only when booting
> from optical media. It didn't happen when booting from usb (except for
> the couple of times it did).

> Workaround for now is to put the following line in /etc/rc.local:

> /etc/init.d/eudev stop && /etc/init.d/eudev start

You are right, the system rights itself if I re-start eudev from the
console.  Seems that during normal boot it sometimes misses the "cold
plug" events required to load hardware drivers.  Will try to add some
boot automatism for eudev restart.

The bootup of the system is somewhat special and does have some
similarities to the live ISO boot: my system is disk-less and booting
via "pxelinux" which is a syslinux derivative.  Maybe the ISOs boot in a
similar way using isolinux?  Does eudev do things differently depending
on whether system boots via UEFI or not?

cheers,

David





___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 08:21:51 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-13 22:10, schrieb richard lucassen via Dng:
> > I have no idea. But mountall is in runlevel S, not 2. What if you
> > mount it explicitely in a temporary script
> > called /etc/rcS.d/99mount.sh ? That
> > is before runlevel 2 starts.
> 
> Looks like it has something to do with huge_file support:
> https://forums.gentoo.org/viewtopic-t-905312-start-0.html

Yes, I already ran into such an issue a few years ago. I mounted a disk
created ext4 with a newer Debian on a machine running an older Debian
and it would not mount (at all). I looked it up in a script I made and
for me it was the metadata_csum option that was inserted by the newer
Debian and the old one did not support this. So the trick was to format
the disk without that option:

-- 8< -

mkfs.ext4 -O '^metadata_csum' /dev/mmcblk0p3 https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Ascii to Beowulf upgrade - 32% slowdown !

2020-06-14 Thread Riccardo Mottola via Dng

Hi,

On 6/12/20 9:21 PM, Steve Litt wrote:

Maybe try ;https://make-linux-fast-again.com/   kerneloptions to
disable all spectre and meltdown stuff

I hope you mean the preceding as a diagnostic test and not as a
solution.



first, diagnostic on what is slowing down and stealing performance in 
such a significant way.


second, it could be also acceptable as a solution: If a system like 
laptop is not running multi-user, no virtual machines and you consider 
the software running trusted, where are the risks? I think only in the 
browser which runs "unknown" and "untrusted" stuff: The only attack 
surface would be JavaScript (or Java, Flash or similar). If, from what I 
read, the browser removed high resolution timers, timing attacks needed 
to exploit these bugs are unlikely.


Am I simplifying too much and overseeing some holes?


Riccardo

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Ascii to Beowulf upgrade - 32% slowdown !

2020-06-14 Thread Riccardo Mottola via Dng

Hi all,

On 6/13/20 12:24 PM, Patrick Erdmann wrote:

Just to be sure, try this line as kernel parameters:

noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off
nospec_store_bypass_disable no_stf_barrier mds=off tsx=on
tsx_async_abort=off mitigations=off


I tried all "noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off
nospec_store_bypass_disable no_stf_barrier mds=off tsx=on
tsx_async_abort=off" and here some results.

Laptop with i7 (4x parallel build):

ascii "standard": 30-31 minutes
beowulf "standard": 41 minutes
beowulf "fast": 34 minutes


Laptop with T7200 (2x parallel build):

ascii "standard": 63 minutes
ascii "fast": 61 minutes


From this we see that at least some mitigations were already "slowing 
down" ascii already and at least on another CPU I gained some speed 
back, but this makes the comparison even with beowulf!


We see that "fast" still is slower than previous ascii by about 10% 
(which we can estimate do be more, since I did not test the same 
configuration).


Something is still slowing down... it is not that my life changes with 
3minutes, but I hate to know tht just a plain "upgrade" robbed me 10-15% 
of speed. By the way, informal tests (not on the same hardware) show 
that this speed gain is the difference between an i5 and an i7, so like 
to say my CPU was downgraded :-P



What could be slowing down? some other kernel "settings" not related to 
mitigations.. cache handling, file system, scheduling?



Riccardo

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Ascii to Beowulf upgrade - 32% slowdown !

2020-06-14 Thread Riccardo Mottola via Dng

Hi,

On 6/13/20 7:45 PM, Harald Arnesen via Dng wrote:

Do you compile ArcticFox with the same compiler in both cases? GCC gets
slower for each release, it seems...



Yes, same version, gcc 6.5 - the highest I can use to compile.

I have issues compiling it with gcc 7 (actually, linking it...). Help 
fixing it welcome!



Also, informal tests have shown that there is no such big difference, 
probably it depends on the code.


Riccardo

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread J. Fahrner via Dng

Am 2020-06-13 22:10, schrieb richard lucassen via Dng:

I have no idea. But mountall is in runlevel S, not 2. What if you mount
it explicitely in a temporary script called /etc/rcS.d/99mount.sh ? 
That

is before runlevel 2 starts.


Looks like it has something to do with huge_file support:
https://forums.gentoo.org/viewtopic-t-905312-start-0.html
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng