Bug#1067858: reset SuperSpeed USB device number 2 using xhci_hcd

2024-05-28 Thread Pierre Tomon
Control: forwarded 1067858 https://bugzilla.kernel.org/show_bug.cgi?id=218890



Bug#1067858: reset SuperSpeed USB device number 2 using xhci_hcd

2024-04-07 Thread Pierre Tomon
Control: found 1067858 6.1.82+1
Control: notfound 1067858 6.1.76+1
Control: notfound 1067858 6.6.15+2

Stable-p-u is also affected by this bug.



Bug#1067858: reset SuperSpeed USB device number 2 using xhci_hcd

2024-03-27 Thread Pierre Tomon
Source: linux-signed-amd64
Version: 6.7.9+2
Severity: normal
X-Debbugs-CC: pierretom...@ik.me

Dear Maintainer,

Since kernel 6.7.7-1 to 6.7.9+2 (amd64), I got this message when turning on the 
external drive.
The device is accessible after about 1 minute, then I can mount it and access 
data.
Does not happen on kernel 6.6.15+2 and prior versions.

SATA/USB controller: Bus 006 Device 003: ID 174c:5106 ASMedia Technology Inc. 
ASM1051 SATA 3Gb/s bridge
SATA controler: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller 
(rev 01)

# dmesg
[   89.821220] usb 6-1: new SuperSpeed USB device number 2 using xhci_hcd
[   98.669813] usb 6-1: New USB device found, idVendor=174c, idProduct=5106, 
bcdDevice= 0.01
[   98.669829] usb 6-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[   98.669836] usb 6-1: Product: AS2105
[   98.669842] usb 6-1: Manufacturer: ASMedia
[   98.669847] usb 6-1: SerialNumber: 
[   98.702925] usb-storage 6-1:1.0: USB Mass Storage device detected
[   98.703186] scsi host10: usb-storage 6-1:1.0
[   98.703323] usbcore: registered new interface driver usb-storage
[   98.712000] usbcore: registered new interface driver uas
[   99.729263] scsi 10:0:0:0: Direct-Access ST3000DM 001-1CH166   CC29 
PQ: 0 ANSI: 0
[   99.729842] sd 10:0:0:0: Attached scsi generic sg3 type 0
[   99.730034] sd 10:0:0:0: [sdc] Very big device. Trying to use READ 
CAPACITY(16).
[  130.381128] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
[  130.401814] sd 10:0:0:0: [sdc] 5860533168 512-byte logical blocks: (3.00 
TB/2.73 TiB)
[  130.402173] sd 10:0:0:0: [sdc] Write Protect is off
[  130.402181] sd 10:0:0:0: [sdc] Mode Sense: 23 00 00 00
[  130.402486] sd 10:0:0:0: [sdc] No Caching mode page found
[  130.402493] sd 10:0:0:0: [sdc] Assuming drive cache: write through
[  130.403339] sd 10:0:0:0: [sdc] Very big device. Trying to use READ 
CAPACITY(16).
[  161.100747] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
[  161.395030]  sdc: sdc1 sdc2
[  161.395511] sd 10:0:0:0: [sdc] Attached SCSI disk



Bug#1066805: Package request: `lua-latest`

2024-03-13 Thread Pierre Tomon
Source: lua5.4
Version: 5.4.6-3+b1
Severity: wishlist

Dear Maintainer,

It would be handy, if a metapackage can be created, that always depends on the 
latest version of the Lua package.
e.g. `lua-latest` package will depend on the latest version, currently the 
`lua5.4` package.
This would make easier to install and upgrade automatically to the latest 
version.



Bug#1033385: Any progress?

2023-07-23 Thread Pierre Tomon
Le Sun, 23 Jul 2023 15:09:31 +0200,
justhate  a écrit :

> Same issue here as Karine explained.
> 
> The bug was reported 4 months ago and here we are, upgraded glib
> yesterday [libglib2.0-0:amd64 (2.74.6-2, 2.76.4-3)] and Openbox
> (3.6.1-10) is quite unusable.
> 
> Despite the icculus bug report seems to be a bit in an unknown state
> isn't the patch good enough to be applied?
> 

There is an updated package of Openbox, but it requires a sponsor:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041486



Bug#901919: nvidia-driver: black screen with the latest Linux kernel - general protection fault

2018-06-21 Thread Pierre Tomon
As a temporary workaround, we can add this paramater to the kernel:
slab_common.usercopy_fallback=Y
Worked for me.

See also https://devtalk.nvidia.com/default/topic/1031067



Bug#795749: Allow the user to delete email addresses

2017-08-07 Thread Pierre Tomon
Hello,

Same request as İsmail + the possibility to remove the whole account.

regards,

Pierre T.