Erik van Konijnenburg [EMAIL PROTECTED] writes:
Just to avoid misunderstandings: did you add the ide-generic
to repair a non-booting system, or just by way of prevention?
If the amd74xx also fails to boot without ide-generic, I'll need
to prepare a modified yaird patch.
Here's what I've
Package: linux-image-2.6.14-2-k7
Version: 2.6.14-5
Severity: normal
Hello
Since I've updated my kernel from 2.6.11 to 2.6.14, my computer no
longer wakes up.
My motherboard is an Asus A7N8X deluxe with nforce2 chipset
All values reported by nvram-wakeup are normal. They fit with what's
Hello
With recent version of kernel 2.5.15-1, the wake-up problem is gone:
My computer wakes up normally. I don't really know what triggered the
problem and what solved it.
I think you can close this bug.
Cheers
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe.
Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-11
Severity: normal
Hello
I've launched a command to remove a massive amount of file on an usb
disk. Roughly speaking ~20 files for ~ 10Gb of data.
The command worked fine for several minutes, but now the rm process is
stuck:
$
Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-11
Followup-For: Bug #414689
Hello
I follow up on my bug report.
I've mounted the usb disk with default options:
/dev/sde1 /mnt/usb-160gb ext3 rw,noexec,nosuid,nodev,user=domi 0 0
A mv command is stuck after transferring about 36GB :
Hello
While digging the issue, I've found kernel bug 5894 [1] which looks
close to the problem I found.
Following the advice, I've changed the way my usb disks are plugged.
Before they were on 2 adjacents plugs which are on the same usb bus.
Now they are on 2 differents set of plugs and the
Hello
Despite USB cabling change on my machine, I'm still bothered by
lock-up every now and then.
Here's what I found so far:
Lock up are likely to happen :
- during heavy I/O on usb disk (like par2create on a 4GB file)
- when dvb-usb-nova-t-usb2 is loaded
In this case, my keyboards also
Hello
I've tested with a vanilla kernel 2.6.21 and still have problems with
the USB external disks. So I've logged a bug in buzilla:
http://bugzilla.kernel.org/show_bug.cgi?id=8692
I'll keep debian BTS posted in case of progress upstream.
Cheers
--
To UNSUBSCRIBE, email to [EMAIL
Hello
The USB disk hang problem has been solved with 2.6.25 kernel.
For details, see http://bugzilla.kernel.org/show_bug.cgi?id=8692
You can close this bug.
All the best.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hello
I have s similar issue with an old external USB drive:
[ 130.390889] usb 5-3: new high-speed USB device number 3 using ehci-pci
[ 130.523624] usb 5-3: New USB device found, idVendor=0d49, idProduct=7100
[ 130.523636] usb 5-3: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[
For the record, I have the same issue on a OlinuXino A20 LIME card.
See also https://www.danand.de/index.php/2016-03/allwinner-a20-kernel-4-5/
--
https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org
On Sat, 30 Apr 2016 00:08:34 +0200 Sven Hartge wrote:
> Only way to get the network back is to downgrade to 4.4.6-1.
Thanks for the hint.
It took me a while to figure out how to make the downgrade work.
Installing old linux-image package is not enough.
One must also run
Package: src:linux
Version: 4.9.2-2
Severity: important
Dear Maintainer,
DVB usb device fails to load with linux 4.9 with the following error:
Jan 29 20:58:12 gandalf kernel: [ 18.972611] Bluetooth: BNEP (Ethernet
Emulation) ver 1.3
Jan 29 20:58:12 gandalf kernel: [ 18.972613] Bluetooth:
Hello
No better with kernel 4.9.6-3 (2017-01-28)
Relevant logs are:
févr. 11 16:07:22 gandalf kernel: dvb_usb_dibusb_mc_common: module license
'unspecified' taints kernel.
févr. 11 16:07:22 gandalf kernel: Disabling lock debugging due to kernel taint
févr. 11 16:07:22 gandalf kernel:
Hello
I have a similar issue with Hauppauge WinTV-NOVA-T usb2 (note the wrong
Manufacturer shown in the traces):
févr. 26 12:33:23 gandalf kernel: usb 7-2: new high-speed USB device number 2
using ehci-pci
févr. 26 12:33:23 gandalf kernel: usb 7-2: New USB device found, idVendor=2040,
On Sunday, September 4, 2016 12:34:03 PM CEST you wrote:
> Maybe the real bug is that the signed package doesn't contain the
> DTBs.
Indeed. This issue has also been reported in #836255.
On the other hand the error message returned by flash-kernel could be
improved.
When the dtb is missing,
On Wednesday, 1 March 2017 15:48:10 CET Ben Hutchings wrote:
> media-dvb-usb-don-t-use-stack-for-firmware-load.patch
> media-dvb-usb-don-t-use-stack-for-reset-either.patch
It works better: the firmware is loaded and the device starts (red LED is on),
but the communication on usb bus
On mercredi 1 mars 2017 10:44:42 CET Arnaud Patard wrote:
> From a very quick search, I guess it's fixed by
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4
> 3fab9793c1f44e665b4f98035a14942edf03ddc.
>
> As said, I can't find my device so can't test that it's fixing
On mercredi 1 mars 2017 10:44:42 CET you wrote:
> > févr. 26 12:33:23 gandalf kernel: usb 7-2: Manufacturer: Hauppau攀
> > févr. 26 12:33:23 gandalf kernel: usb 7-2: SerialNumber: 9301-00-F008B260
> > févr. 26 12:33:23 gandalf kernel: dvb-usb: found a 'Hauppauge WinTV-NOVA-T
> > usb2' in cold
Package: src:linux
Version: 4.15.11-1
Severity: normal
Dear Maintainer,
While recording audio from line input (on motherboard, no usb involved), I've
noticed an increase of the memory used by the kernel.
I record audio with:
$ pasuspender audacity
After recording for about 1 hour, about 5GB of
On the other hand, once I closed the audacity windows, the kernel released
about 3BG of memory:
$ smem -tw
Area Used Cache Noncache
firmware/hardware 0 0 0
kernel image 0 0 0
kernel
Hi
The oops related to USB were due to a DVB device attached to a 5m cable. This
length
of cable is the max supported by USB and was ok with my previous ASUS mobo,
but leads to oops on this one.
I've removed kdeconnect and not the kernel log looks fine except for these
lines:
sp5100_tco:
On dimanche 25 mars 2018 17:50:22 CEST you wrote:
> According to this, your kernel is not in the best of states. Maybe you
> want to read the fulle kernel log and see where this started?
First oops is due to usb trouble:
Mar 25 12:48:25 gandalf kernel: [ 21.212996] CPU: 7 PID: 2178 Comm:
On Friday, 7 January 2022 12:29:21 CET Diederik de Haas wrote:
> You went to all that trouble to find a 7+ year old bug, with a title that
> doesn't convey a link with dkms compilation issue, unarchive the bug and
> respond to that, but you missed the (1st) response of a kernel maintainer?
Not
On Sat, 11 Oct 2014 21:44:53 -0600 David Zundel wrote:
> Attempted re-installation of linux-image-3.16-2-amd64 generates an error
> report:
> Error! Bad return status for module build on kernel: 3.16-2-amd64
> (x86_64)
> Consult
On Sunday, 20 February 2022 17:36:20 CET Salvatore Bonaccorso wrote:
> Okay great :). This commit landed in 5.16.8 for the 5.16.y series. I
> did upload 5.16.10-1 (but the signed packages are yet missing). Can
> you test this one to confirm the issue is fixed?
I confirm that suspend works fine
On Monday, 14 February 2022 22:52:27 CET Alex Deucher wrote:
> Does the system actually suspend?
Not really. The screens looks like it's going to suspend, but it does come
back after 10s or so. The light mounted in the middle of the power button does
not switch off.
> Is this system S0i3 or
Hi
On Monday, 21 March 2022 09:57:59 CET Thorsten Leemhuis wrote:
> Dominique/Salvatore/Eric, what's the status of this regression?
> According to the debian bug tracker the problem is solved with 5.16 and
> 5.17, but was 5.15 ever fixed?
I don't think so.
On kernel side, the commit fixing this
Package: src:linux
Version: 5.15.15-2
Severity: normal
Tags: upstream
Dear Maintainer,
Since upgrade to linux-image-5.15.0-3-amd6, suspending my machine no
longer works correctly: the screen goes blank as usual, but comes back
after 10s or so.
The most relevant kernel logs are:
[ 257.531771]
On Saturday, 5 February 2022 21:25:03 CET Salvatore Bonaccorso wrote:
> Does the issue persist if you upgrade to the most recent 5.16.y
> version? 5.16.4-1~exp1
yes
> (5.16.7-1 should land soon as well).
I'll try it when it's available
> Any chance
> you can bisect the commit introducing the
On Tuesday, 8 February 2022 08:11:46 CET Salvatore Bonaccorso wrote:
> > > (5.16.7-1 should land soon as well).
>
> > I'll try it when it's available
5.16.7-1 is also broken
> > > Any chance
> > > you can bisect the commit introducing the issue?
> Some help is here:
>
>
On Tuesday, 8 February 2022 08:11:46 CET Salvatore Bonaccorso wrote:
> Does this help?
It did:
$ git bisect good
3c196f0510912645c7c5d9107706003f67c3 is the first bad commit
commit 3c196f0510912645c7c5d9107706003f67c3
Author: Alex Deucher
Date: Fri Nov 12 11:25:30 2021 -0500
On Fri, 11 Feb 2022 08:58:51 +0100 Dominique Dumont wrote:
> Now I need to investigate whether the failed suspend or kernel message are
> related to my external usb device (a usb-c hub with LAN and HDMI output).
They are not.
I get the same behavior and kernel messages on 5.15.0-3 w
33 matches
Mail list logo