Source: linux
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear Maintainer,
I saw that you recently enabled the tls module. Great! It would also be nice to
enable CONFIG_TLS_DEVICE, so that the kernel can offload TLS handling to the
hardware, when supported (like with some
tems with boars using the rtw88 firmware?
Andrea Palazzi
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.3.0-3-amd64 (SMP w/12 CPU cores)
Kernel ta
Through a lengthy I finally found this:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654448
Which hinted to the fact that "Heaphone Mic Boost" is to blame for this.
Issuing:
$ amixer -c 0 set 'Headphone Mic Boost',0 1
makes the problem totally disappear for me. But why it depends on wh
Issue still there under linux-image-5.3.0-2-amd64 == 5.3.9-3.
Currently, with the latest debian sid packages the kernel seems to be the
culprit: as the static noise is NOT present with linux-image-4.19.0-5-amd64
== 4.19.37-6.
Was this bug even reported upstream?
Cheers,
Andrea
Package: firmware-realtek
Version: 20190717-2
Followup-For: Bug #935969
Hi,
The cause of the bug is that the rules.gen file does not include the rtw88
firmware files.
The attached patch solves the problem (at least for me).
Kind regards,
Andrea Palazzi
-- System Information:
Debian Release
Package: src:linux
Version: 5.2.9-2
Severity: normal
I am experiencing heavy static noise through the headphone jack, while
the issue is completely absent when booting with linux-image-4.19.0-5-amd64.
When the media stops the static noise persists for a few seconds, I
guess until the driver goes i
This issue has been fixed upstream in the 5.x branch (see earlier link
to kernel bugzilla). I have tested 5.0.2 and 5.0.4 successfully.
As recommended by upstream bug 192231 I have rebuilt the kernel with a
debugging patch and here is the output of dmesg when triggering the issue.
[0.00] Linux version 4.19.0-1-amd64 (debian-kernel@lists.debian.org)
(gcc version 8.2.0 (Debian 8.2.0-14)) #1 SMP Debian 4.19.12-1a~test (2019-
It seems to be the case that the lid is the most visible breakage but
not the only one: when charging, the battery information is not updated.
Attaching the output of "acpi -V" with the kernel from stable and the
current one in unstable.
Battery 0: Charging, 86%, 00:21:57 until charged
Battery
Package: src:linux
Version: 4.19.13-1
Severity: normal
Dear Maintainer,
after the upgrade to Testing, the system is no longer able to detect a closed
lid to initiate suspend-to-ram; reinstalling the kernel from Stable (4.9.0-7),
while keeping the rest of the
system as is, brings the functionali
he broken dependency links described above.
Don't try to fix 4.11 kernel (it's EOL anyway), we should probably just
wait for 4.12 coming from experimental soon.
Hope this helps you folks!
Bests,
Andrea
RTL8105e and it works flawlessly
:-)
andrea@zbox:~$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev
02)
00:02.0 VGA compatible controller: Intel Corporation Core Processor
Integrated Graphics Controller (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series
ion.
Obviously this is just a workaround: so what is happening here?
Is my hardware not resetting the PCI bus on an ACPI poweroff event?
Should the kernel or driver do it?
Where is the best place to force a device PCI reset so that no problem could
arise on hibernate/suspend?
Best rega
My experience is similar to yours.
Please check https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838491 I
filed.
Do you also report crazy-high load averages?
Package: src:linux
Version: 4.7.4-2
Severity: normal
Since the kernel upgrade to 4.7 I have noticed considerable increase of boot
times. Even 4x times slower compared to the
boot sequence with previous 4.6 kernel. Older kernel is still installed on the
system and I can compare boot times
against
Waiting on the day I go home !
--
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/3e11223b-4098-4164-be2f-ca26118f8...@gmail.com
Waiting on the day I go home !
--
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/818a7978-671c-4db5-a166-d3d3dc23a...@gmail.com
Compiling zswap support would be much appreciated, especially on low memory
systems. Thanks.
ack.
Hope it's useful.
Andrea Cascio
Nucleus srl
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/20130404114323.12149...@zarquon.intranet.nucleus.it
minal) echo "1814 539b" > /sys/bus/pci/drivers/rt2800pci/new_id
2. recompiling wheezy kernel after adding device id as in [1]
Please consider backport commit [1] to the kernel shipped with wheezy.
Thanks in advance.
--
Andrea
[1] http://git.kernel.org/?p=linux/kernel/git/stable/l
ly on Linode and Amazon EC2?
> > >
> >
> > Originally, I was able to reproduce the issue easily with a RHEL5
> > host. Now, with this patch it's fixed.
>
> OK, so Tested-by: Andrew Jones..
> and from my perspective it looks good - so Acked-by: Konrad Rzeszutek Wilk
>
6 case, it is enough to read the low part of the
pmdval atomically to declare the pmd as "stable" and that's true for
THP and no THP, furthermore in the THP case we also have a barrier()
that will prevent any inconsistent pmdvals to be cached by a later
re-read of the *pmd.
Signed-
ret |= ((pmdval_t)*(tmp + 1)) << 32;
}
+#endif
return (pmd_t) { ret };
}
But it's not worth the extra complexity. It looks cleaner if we deal
with "good" pmds if they're later found pointing to a pte (even if we
discard them and force pte_off
Hi,
On Thu, Jun 07, 2012 at 11:56:47AM -0400, Konrad Rzeszutek Wilk wrote:
> then the high part. Why that would trip the hypervisor
> is not clear to me. Perhaps in the past it only read the
That is the CONFIG_TRANSPARENT_HUGEPAGE=n case and in fact it doesn't
trip the hypervisor. That was tested
te).
> [...]
> > Non-Xen boots proceed normally.
>
> Yeah, apparently[2] that's caused by
>
> commit 26c191788f18
> Author: Andrea Arcangeli
> Date: Tue May 29 15:06:49 2012 -0700
>
> mm: pmd_read_atomic: fix 32bit PAE pmd w
On Mon, Feb 27, 2012 at 12:56:45AM -0600, Jonathan Nieder wrote:
> Andrea Bolognani wrote:
>
> > Is this patch (or a similar one) enabled in Debian’s 3.2 kernels?
>
> Yes, the patch was part of upstream 3.2.3. As the top of [1] says:
>
> Found in versions 3.1.6-1, 3
.
>
> Perfect. Thanks, Stefan!
Is this patch (or a similar one) enabled in Debian’s 3.2 kernels?
I’ve been running 3.2 since it hit testing (I’m on 3.2.4-1 now) and
the boot has not hanged once so far.
--
Andrea Bolognani
Resistance is futile, you will be garbage collected.
signature.asc
Description: Digital signature
can can collect to help track this
down, please let me know.
--
Andrea Bolognani
Resistance is futile, you will be garbage collected.
signature.asc
Description: Digital signature
i, Sep 9, 2011 at 20:34:19 +0200, Andrea Cardaci wrote:
>
>> Package: linux-image-2.6.32-5-amd64
>> Version: 2.6.32-35squeeze1
>>
>> After an apt-get upgrade today, I wasn't able to boot anymore, lvm
>> complains that can't find libncurses.so.5, and it&
Just wanted to tell that the issue happened two more times in these
months (last one yesterday; same details). I'd like to have some info
about it.
--
Andrea Cardaci
http://behance.net/AndreaCardaci
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subje
-2.6.32-5-common:amd64 (2.6.32-35,
2.6.32-35squeeze1), linux-headers-2.6.32-5-amd64:amd64 (2.6.32-35,
2.6.32-35squeeze1), linux-base:amd64 (2.6.32-35, 2.6.32-35squeeze1),
linux-libc-dev:amd64 (2.6.32-35, 2.6.32-35squeeze1)
End-Date: 2011-09-09 15:44:21
--
Andrea Cardaci
http://behance.net/Andr
blacklisting the radeon driver?
If I blacklist the radeon driver, I don't get any GPFs anymore.
I did 10 reboots, and no problems.
Can I help you anymore in diagnosing the problem?
Thanks,
Andrea
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "u
blacklisted rtl8187,
and resulted in the other GPFs at boot time that are not logged.
Andrea
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d1c4bf0.5010...@gmail.com
Package: linux-2.6
Version: 2.6.32-29
Severity: critical
Justification: breaks the whole system
The system randomly (say, 2 times every 3 boots) shows General Protection Fault
errors at boot time. I don't get to multiuser init levels.
When those errors occur, I can't do anything, the system seem
works
post-down pkill wpa_supplicant
dns-nameservers 208.67.222.222 208.67.220.220
iface unitn inet dhcp
wireless-essid unitn
up /home/andrea/documents/unitn/wireless-login
post-down /home/andrea/documents/unitn/wireless-login -o
iface eth0 inet dhcp
dns-
er to enable MMC_SDHCI_PCI kernel option.
(just to remind ENE Controller has stopped to work since 2.6.26 kernel: see
bug #496485 :-) )
Regards,
Andrea
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I installed r12453 sid snapshot xen kernel.
It works: xen dom0 boots on all my 3 test PCs. Attached to this message
you can find Gigabyte P35-DS3L motherboard PC boot log.
Thanks for your support.
Original Message
Subject: Bug#502849: Possible fix
From: Ian Campbell <[EMAIL P
oard, VIA K8T890 chipset, Athlon64 3000+ CPU.
-> kernel starts normally
Original Message
Subject: Re: Bug#502849:
From: Bastian Blank <[EMAIL PROTECTED]>
To: Andrea Janna <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Date: 14/11/2008 17.01
Please provide complete message
le to handle kernel paging request)
From: [EMAIL PROTECTED] (Debian Bug Tracking System)
To: Andrea Janna <[EMAIL PROTECTED]>
Date: 20/10/2008 11.42
Thank you for filing a new Bug report with Debian.
This is an automatically generated reply to let you know your message
has been received.
You
ou and bye.
Andrea Lorenzetti
Ps: current thread on Debian-eeepc-devel mailing list:
http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2008-August/000656.html
-- Package-specific info:
** Version:
Linux version 2.6.26-1-686 (Debian 2.6.26-2) ([EMAIL PROTECTED]) (gcc version
4.1.3 20080623 (
as explained in
changelog:
* udev.rules: added a rtc symlink to rtc0.
Regards,
Andrea.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Thu, Apr 10, 2008 at 09:28:24AM +0200, Sven Luther wrote:
> What about non-x86 architectures, well i guess ia64 and
> powerpc/powerpc64 are the most interesting candidates.
It should be zero cost there too if it has been implemented
correctly. The only feature that initially generated a minimum
Hello,
The story about seccomp is that as long as there are users CPUShare
will support it because it's a more efficient and more secure
computing model.
About the seccomp overhead, that is zero. It adds zero overhead to the
fast path of the scheduler. It never added any overhead on x86-64. For
x
://www.daenische-hobbyhuren.com/
Und als besonderes Bonbon haben wir da auch noch ein paar Sex-Tipps für Männer
UND Frauen!
Also, würde mich freuen...
Küsschen,
deine Andrea
(von damals)
Vacuum
Best. Watches for your loved ones and people you like.Planet
shewgff.com.
Torch
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Same problem here with linux-image-2.6.18-3-amd64:
[EMAIL PROTECTED]:~$ uname -a
Linux marcopolo 2.6.18-3-amd64 #1 SMP Mon Dec 4 17:04:37 CET 2006
x86_64 GNU/Linux
t need the drivers in
/lib/modules/2.6.16-2-xen folder during the boot process, but if you use the
kernel packet you do.
In any case, I think that a linux-modules postinst script creating the proper
initrd file would be nice.Of course if that doesn't cause troubles I don't
see...
Regard
JFYI: today klive recorded this /proc/version:
Linux version 2.6.15-deb-reiser4 (2.6.15-deb-reiser4-10.00.Custom) ([EMAIL
PROTECTED]) (gcc-Version 4.0.3 20060115 (prerelease) (Debian 4.0.2-7)) #1
PREEMPT Wed Jan 25 17:56:04 CET 2006
This generated a new branch called 2.6.15-deb-reiser4-10.00.C
Package: initramfs-tools
Version: 0.46
Severity: minor
[EMAIL PROTECTED]:/usr/share/initramfs-tools/scripts# dpkg -S functions.swp
initramfs-tools: /usr/share/initramfs-tools/scripts/.functions.swp
[EMAIL PROTECTED]:/usr/share/initramfs-tools/scripts#
-- System Information:
Debian Release: test
On Sun, Jan 08, 2006 at 08:48:20AM +0100, Sven Luther wrote:
> You could simply add the two distro-specific information, the full package
> name (2.6.14-2-amd64-k8) and the distro version number (2.6.14-7). I guess
> in additional often-intrusive patches, and will probably use a meaningful
> name.
On Sun, Jan 08, 2006 at 08:31:50AM +0100, Sven Luther wrote:
> You are not interested in recordying the debian abi number, or the flavour as
> a subset of the architecture used ? This seems like interesting info.
KLive wasn't originally designed to track distro packages, but mainline
or/and self-b
On Sun, Jan 08, 2006 at 08:04:33AM +0100, Sven Luther wrote:
> -1 was both the abi number and the debian revision. I guess you need to fix
> your script again :)
The client sends a plain /proc/version, so fixing this is very easy to
fix this on the server side.
> And none of those is really a sub
On Wed, Sep 14, 2005 at 05:02:18PM +0200, Sven Luther wrote:
> On Wed, Sep 14, 2005 at 04:46:04PM +0200, Andrea Arcangeli wrote:
> > On Wed, Sep 14, 2005 at 11:18:46AM +0200, Sven Luther wrote:
> > > On Sat, Sep 10, 2005 at 05:19:07PM +0200, Andrea Arcangeli wrote:
> > >
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: grave
Justification: renders package unusable
Installing (or upgrading) the package linux-image-2.6.14-2-686 the
post-installation script returns error code 128.
"""
Configuro linux-image-2.6.14-2-686 (2.6.14-5) ...
Running depmod.
Fin
On Wed, Sep 14, 2005 at 11:18:46AM +0200, Sven Luther wrote:
> On Sat, Sep 10, 2005 at 05:19:07PM +0200, Andrea Arcangeli wrote:
> > On Sat, Sep 10, 2005 at 07:43:31AM +0200, Sven Luther wrote:
> > > Not a good idea. Why clutter the namespace of versions in order to adapt
On Sun, Sep 11, 2005 at 06:10:47PM +0200, Sven Luther wrote:
> Nope,; it works for debian packages. But you can match that to kernels.
not quite, you never know what kernel the system is running if you don't
call uname -r sorry. Note that klive is written for _mainline_ kernels,
see the homepage (
On Sun, Sep 11, 2005 at 07:35:02AM +0200, Sven Luther wrote:
> and report data ? If so, you may look into the popularity context package ?
Does that work for all distro out there? Could you post the url of
the equivalent of a klive.cpushare.com chart so we can compare? (google
pointed me to the pa
On Sat, Sep 10, 2005 at 09:42:17PM +0200, Sven Luther wrote:
> On Sat, Sep 10, 2005 at 08:02:38PM +0200, Sven Luther wrote:
> > On Sat, Sep 10, 2005 at 05:57:12PM +0200, Andrea Arcangeli wrote:
> > > On Sat, Sep 10, 2005 at 05:33:29PM +0200, Sven Luther wrote:
> > >
On Sat, Sep 10, 2005 at 05:35:56PM -0400, Andres Salomon wrote:
> Quite honestly, I don't think we deviate enough from the mainline kernels
> enough to warrant such a thing. The main patches we include are the stable
> kernel patches, misc fixes backported from linus' git repo, architecture
> patc
On Sat, Sep 10, 2005 at 05:33:29PM +0200, Sven Luther wrote:
> Sure, i am not stupid, i perfectly noticed that, now my question is why do you
> want to know that ?
That's for the klive project, I added two links in the first email just
check it again.
> Sure, it is a debian system, running a debi
On Sat, Sep 10, 2005 at 07:43:31AM +0200, Sven Luther wrote:
> Not a good idea. Why clutter the namespace of versions in order to adapt to
> non-debian needs. ? What is it you intent to do anyway ?
My intent is to be able to tell the "branch" of the kernel based on
`uname -r` (per subject). So if
Hello everyone,
I'm trying to detect a debian kernel from uname -r.
My suggestion would be to add a "-debian" at the end of the localversion
of kernels _patched_/modified by debian, and to leave the localversion
completely _empty_ (or an unchanged localversion compared to the
mainline defconfig)
mouse and filesystems are
locked and even pinging from a nearby computer won't get any answers.
If any other information is needed i will be glad to provide it.
Goodbye (and congratulations for the great work)
--
UoVoBW aka Andrea Lusuardi
Registered Linux User #364578
---
dead. Is this similar
> to what you are seeing ?
Yes, something like that. It hangs after ethernet resume I think (but
I can be wrong). Maybe it is related to usb drivers (i've read it
somewhere on the web), we should try to unload them before suspending.
Thanks & bye
--
Andre
On Mon, Oct 11, 2004 at 08:47:35AM +0200, Jens Schmalzing wrote:
> Thanks for the information. So I am closing this bug now. Andrea,
> please upgrade to 2.6.8. If you have any problems with the newer
> kernel or the upgrade itself, feel free to report them.
Yes, it's fixed in
Package: kernel-image-2.6.7-powerpc
Version: 2.6.7-5
Severity: normal
this is the oops. it happens at boot when hald starts.
kernel: kernel BUG in fill_read_buffer at fs/sysfs/file.c:92!
kernel: Oops: Exception in kernel mode, sig: 5 [#1]
kernel: NIP: C00955A4 LR: C0095598 SP: D605FEA0 REGS: d605
66 matches
Mail list logo
