Bug#968110: linux-image-5.7.0-2-amd64: USB 3 storage device not detected

2020-08-08 Thread Jörg-Volker Peetz 
Package: src:linux
Version: 5.7.10-1
Severity: normal

Dear Maintainer,

USB 3 storage devices (hdd and stick) are not detected. Nothing shows up in the
log files (messages, kern.log) and the command lsusb doesn't show the device.
The version 5.7.6-1 also doesn't work.

A USB 2 storage device and a USB mouse are detected and can be used.

Any ideas?
Regards,
Jörg.


** Model information
sys_vendor: Hewlett-Packard
product_name: HP ProBook 650 G1
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version:
bios_vendor: Hewlett-Packard
bios_version: L77 Ver. 01.21
board_vendor: Hewlett-Packard
board_name: 1993
board_version: KBC Version 16.39

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

2020-01-10 Thread Jörg-Volker Peetz 
These error messages also appear in the 'make modules_install' step when
building a standard Linux kernel.

Regards,
Jörg.

Bug#935094: linux-image-5.2.0-2-amd64: USB 3 storage device not detected

2019-08-19 Thread Jörg-Volker Peetz 
Package: src:linux
Version: 5.2.7-1
Severity: normal

Dear Maintainer,

USB 3 storage devices (hdd and stick) are not detected. Nothing shows up in the
log files (messages, kern.log) and the command lsusb doesn't show the device.
With kernel package linux-image-4.19.0-5-amd64 the same devices work.

A USB 2 storage device and a USB mouse are detected and can be used.

Any ideas?
Regards,
Jörg.


-- Package-specific info:
<#part type="text/plain" disposition=attachment description="Bug script output">
** Version:
Linux version 5.2.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0
(Debian 8.3.0-19)) #1 SMP Debian 5.2.7-1 (2019-08-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.2.0-2-amd64
root=UUID=fee4c872-c3ec-4b28-9951-0bf6507cae5f ro quiet scsi_mod.use_blk_mq=1

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ProBook 650 G1
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version:
bios_vendor: Hewlett-Packard
bios_version: L77 Ver. 01.21
board_vendor: Hewlett-Packard
board_name: 1993
board_version: KBC Version 16.39

** Loaded modules:
uas
usb_storage
hid_generic
usbhid
hid
bfq
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
crct10dif_pclmul
crc32_pclmul
arc4
ghash_clmulni_intel
btusb
btrtl
btbcm
btintel
bluetooth
snd_hda_codec_hdmi
iwldvm
mac80211
aesni_intel
snd_hda_codec_idt
aes_x86_64
crypto_simd
snd_hda_codec_generic
drbg
cryptd
glue_helper
iwlwifi
i915
ledtrig_audio
intel_cstate
drm_kms_helper
tpm_infineon
snd_hda_intel
ansi_cprng
intel_uncore
ppdev
cfg80211
snd_hda_codec
joydev
iTCO_wdt
tpm_tis
tpm_tis_core
rtsx_pci_ms
evdev
snd_hda_core
intel_rapl_perf
ecdh_generic
parport_pc
tpm
snd_hwdep
hp_wmi
pcspkr
ecc
sparse_keymap
serio_raw
wmi_bmof
memstick
snd_pcm
hp_accel
iTCO_vendor_support
sg
lis3lv02d
watchdog
parport
drm
input_polldev
rfkill
pcc_cpufreq
rng_core
battery
mei_me
snd_timer
hp_wireless
button
snd
soundcore
i2c_algo_bit
mei
ac
ie31200_edac
ext4
crc16
mbcache
jbd2
crc32c_generic
sr_mod
cdrom
sd_mod
rtsx_pci_sdmmc
mmc_core
ahci
libahci
libata
psmouse
rtsx_pci
ehci_pci
ehci_hcd
xhci_pci
xhci_hcd
scsi_mod
e1000e
lpc_ich
i2c_i801
crc32c_intel
usbcore
mfd_core
usb_common
wmi
video

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor DRAM Controller [8086:0c04] (rev 06)
Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core 
Processor DRAM
Controller [103c:1993]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: ie31200_edac

00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA
controller])
DeviceName: 32
Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics
Controller [103c:1993]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller [8086:0c0c] (rev 06)
Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core 
Processor HD
Audio Controller [103c:1993]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset
Family USB xHCI [8086:8c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Hewlett-Packard Company 8 Series/C220 Series Chipset Family 
USB xHCI
[103c:1993]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series
Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Hewlett-Packard Company 8 Series/C220 Series Chipset Family 
MEI
Controller [103c:1993]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping-
SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-V
[8086:153b] (rev 04)
Subsystem: Hewlett-Packard

Bug#841368: gcc-6 6.2.0-7 breaks kernel build if stack protection is enabled

2016-10-25 Thread Jörg-Volker Peetz 
On Thu, 20 Oct 2016 18:13:05 -0500 "S. R. Wright"  wrote:
> I agree.  When the version changes from 6.2.0-6 to 6.2.0-7,  only bug 
> fixes should be included,  not changes in functionality.  In this case 
> setting enable-default-pie essentially broke backwards compatibility.  
> Kernel code that built in -6 failed to build in -7.  That, I agree,  
> should be considered a bug,  and the change should be rolled back.
> 
> -- sRw

I support this statement about changing functionality of such an important tool.
At least a recipe how to get the old behavior should be documented.

> 
> On 10/20/2016 05:49 PM, Ben Hutchings wrote:
> > On Fri, 2016-10-21 at 01:21 +0300, Konstantin Demin wrote:
> >> It's not a GCC bug but kind of new feature.
> > It's a bug when a compiler fails to compile valid code.
> >
> > Ben.
> >
> >> Take a look at this changelog entry:
> >>   gcc-6 (6.2.0-7) unstable; urgency=medium
> >>
> >> [ Matthias Klose ]
> >> * Configure with --enable-default-pie and pass -z now when pie is 
> >> enabled;
> >>   on amd64 arm64 armel armhf i386 mips mipsel mips64el ppc64el s390x.
> >>   Closes: #835148.
> >>
> >> Starting at gcc 6.2.0-7 we must provide "-fno-PIE -fno-PIC" in
> >> beginning of CFLAGS to build kernel successfully.
> >>

But does this generate the same output as without -enable-default-pie?
Some parts of the kernel do use -fpic or -fPIC. Which directive prevails?

> >> I'm currently looking for correct way to do this trick.

Regards,
jvp.

Bug#785463: mount: remounting root file system with lazytime broken

2015-05-20 Thread Jörg-Volker Peetz 
Hello Andreas,

Andreas Henriksson wrote on 05/17/2015 21:39:
 Hello Jörg-Volker Peetz.
 
 Thanks for your bug report.
 
 On Sat, May 16, 2015 at 06:44:53PM +0200, Jörg-Volker Peetz wrote:
 Package: mount, util-linux
 Version: 2.26.2-2
 Severity: normal

 Dear Maintainer,

 since version 2.26 the remounting of the root file system with
 lazytime/nolazytime seems to be broken. The command

 # mount -o remount,lazytime /

 has no effect if lazytime is not set.
 
 Could you please check if commenting out the following row
 in debian/rules and rebuilding the package makes any difference
 for this issue?
 
 CONFOPTS += --enable-libmount-force-mountinfo
 
 Quick hints for rebuilding the package:
 cd /tmp
 apt-get source util-linux
 cd util-linux
 # edit debian/rules to comment or delete the row mentioned above.
 apt-get build-dep util-linux
 dpkg-buildpackage -uc -us
 dpkg -i ../libmount_*.deb ../mount_*.deb
 
 
 Maybe that change is completely unrelated to your issue, but would be
 appreciated if you could help me out with checking if so.
 
snip

Following your instructions, I re-built the util-linux package.
I installed the packages mount, libmount1, util-linux, and libfdisk1. Before
being able to do that, I had to update the sysvinit related packages.

Still, I'm not able to manipulate the lazytime mount option. The mount state is

$ grep -E '(root|sda)' /proc/mounts
/dev/root / ext4 rw,lazytime,relatime,nobarrier,errors=remount-ro 0 0
/dev/sda2 /home ext4 rw,lazytime,relatime,nobarrier,errors=remount-ro 0 0

As root I commanded

# strace -o /tmp/st  mount -o remount,nolazytime /
# grep ^mount /tmp/st
mount(/dev/sda1, /, 0xf00780, MS_MGC_VAL|MS_REMOUNT,
nobarrier,errors=remount-ro) = 0

But nothing changed in /proc/mounts.
-- 
Regards,
Jörg.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/555c6ecd.8040...@web.de