megoldásokról?
Üdvözlettel
Alex Nagy
Package: linux-image-amd64
Version: 6.10.3-1
Severity: important
X-Debbugs-Cc: tuk...@gmail.com
Hello! I ran into some trouble while casually trying to update `linux-image-
amd64` and `linux-headers-amd64` during a routine system update.
My current image is `linux-image-6.9.7` (6.9.7-1). There a
Source: linux
Severity: normal
Dear Maintainer,
I can't see why something which can be done with a kernel boot parameter or a
sysctl variable
needs to be forced in the source since 2011. Also, the very existence of this
new default is non-transparent for anyone relying on official kernel
document
cgi-bin/bugreport.cgi?bug=1054514
Signed-off-by: Alex Constantino
---
drivers/gpu/drm/qxl/qxl_release.c | 50 +++
include/linux/dma-fence.h | 7 +
2 files changed, 52 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/qxl/qxl_release.c
b
e reproduced"
exit 0
```
>From what I could find online it seems that users that have been affected
by this problem just tend to move from QXL to VirtIO, that is why this bug
has been hidding for over 3 years now.
This issue was initially reported by Timo 4 months ago but the discussion
see
Package: linux-source-6.4
Version: 6.4.4-3~bpo12+1
Severity: normal
Dear Maintainer,
a certain patch leads to a significant regression making AVX instructions
unusable in the CPUs having them:
https://lore.kernel.org/lkml/202307192135.203ac24e-oliver.s...@intel.com/
a fix is available upstream:
they've never been added to linux-firmware.git.
> More recently amdgpu added:
>
> MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes.bin");
> MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes_2.bin");
> MODULE_FIRMWARE("amdgpu/gc_11_0_3_mes1.bin");
>
> and these are also missing from linux-firmware.git.
>
> Is this firmware intended to be available to the public?
Yes, those will be available soon.
Alex
hing I can do to speed up this seemingly-last step, or anyone I
could politely ask to do this?
Thanks,
Alex Lieflander
On Mon, Feb 21, 2022 at 3:29 AM Eric Valette wrote:
>
> On 20/02/2022 16:48, Dominique Dumont wrote:
> > 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
On Wed, Feb 16, 2022 at 2:56 PM Eric Valette wrote:
>
> On Tue, 15 Feb 2022 15:42:27 -0500 Alex Deucher
> wrote:
> > What chip is this? Can you provide the full dmesg output?
>
> Its a a renoir chip with a second gpu : [Radeon RX 5500/5500M / Pro 5500M].
Thanks. Can
What chip is this? Can you provide the full dmesg output?
Alex
On Tue, Feb 15, 2022 at 1:15 PM Eric Valette wrote:
>
> Since I upgraded from 5.10 (own compiled kernel or debian kernel) to
> 5.15 (own compiled from same config or debian kernel) and even 5.16
> kernel from debian
On Sat, Feb 12, 2022 at 1:23 PM Salvatore Bonaccorso wrote:
>
> Hi Alex, hi all
>
> In Debian we got a regression report from Dominique Dumont, CC'ed in
> https://bugs.debian.org/1005005 that afer an update to 5.15.15 based
> kernel, his machine noe longer suspends correc
Package: linux-source-5.9
Version: 5.9.15-1~bpo10+1
Severity: important
Tags: upstream
Dear Maintainer,
5.9.15 crashes regularly with memory/paging related messages, like this:
=
Jan 15 17:25:09 host kernel: [125426.427889] BUG: unable to handle page fault
for address: 2500
Jan
Hi,
I am experiencing a similar problem as Gianluigi on my Lenovo X1 Extreme
Gen 2
running Debian Testing with Gnome where touchpad click is non-responsive
while
running kernel 5.10.
There is no response whatsoever to clicking the touchpad, and the pointer
does
not respond when one finger taps an
Interestingly enough, I had a (probably unrelated) issue where
WPA_Supplicant, plasmashell, and kworker were using 100% CPU, forcing me
to reboot. And now upon reboot my Bluetooth works perfectly fine. I
swear I didn't do anything else. Issue fixed on my end.
Package: firmware-realtek
Version: 20201118-1
Severity: important
Dear Maintainer,
Bluetooth doesn't work at all. It is not appearing as a device in bluetoothctl
or bluedevil.
>From what I can tell, `dmesg` even reports that the firmware loaded
>successfully.
[ 21.488979] bluetooth hci0: fir
fore stuff starts working again.
On Fri, 22 May 2020 at 15:36, Lukas Straub wrote:
>
> Hello Everyone,
> When will this fix be released?
>
> Regards,
> Lukas Straub
--
Alex Bennée
KVM/QEMU Hacker for Linaro
ebian/rules source
dpkg-buildpackage
Once I install the package I can build QEMU again.
>From eb53234b3feb45f26e0a8ff36779d49ca8965fbe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Alex=20Benn=C3=A9e?=
Date: Tue, 12 May 2020 11:36:37 +0100
Subject: [PATCH] uabi: fix breakage for compiling u
kernel: [4.355209] amdgpu :1a:00.0:
firmware: direct-loading firmware amdgpu/vega10_sdma1.bin
--
-Alex
from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 418.694] (==) Log file: "/home/alex/.local/share/xorg/Xorg.1.log", Time:
Mon Apr 29 09:14:51 2019
[ 418.694] (=
Package: initramfs-tools
Version: 0.127
Severity: normal
Dear Maintainer,
My nvme device in my laptop is a bit slow to enumerate its partitions
(it takes upto 0.3 sec). This causes the initramfs script to fail to
resume from hibernation. The resume script in local-premount just
checks if the resu
Package: src:linux
Version: 4.6.4-1
Severity: normal
--- Please enter the report below this line. ---
So I have an Intel Z87 based motherboard with i7-4770 CPU installed
and VT-d switched on and I'm tinkering with iommu, virtualisation and stuff,
putting intel_iommu=on as a boot parameter.
I als
In 3.19, the way the kernel handles that button was changed from
hardware to software. You'll need
options thinkpad_acpi software_mute=0
in modprobe.d/ to get the old behaviour back.
-Alex
Package: linux-image-amd64
--- Please enter the report below this line. ---
Actually, after some research and having run dozens of old kernel versions I
came to the conclusion that this LVM/RAID1 shit NEVER WORKED PROPERLY.
It's just unbelievable. This RAID1 feature was added to LVM2 in 2011. d
But then again, I guess md should get metadata from some backend provided by
lvm, not from the device directly? (Don't know for sure, didn't dive deep into
the driver yet.)
=sockets.target
--
Alex
Package: linux-image-amd64
Version: 4.2+68
--- Please enter the report below this line. ---
This seems to be a duplicate of #795772, which I've filed on src:linux months
ago. (I wonder why so little info on this bug available, like nobody else uses
LVM's RAID1 feature?)
--- System information.
Package: nfs-common
Version: 1:1.2.8-9
The system is used to nfs4 chroot, when you create a user in a chroot
environment on other clients nfs-common version: 1:1.2.6-4 files shadow,
passwd, group updated without any problems. But on the clients nfs-common
version: 1:1.2.8-9 cat: /mountnfs/etc/shad
Package: src:linux
Version: 4.1.3-1
Severity: important
--- Please enter the report below this line. ---
Kernel bug #100491 (https://bugzilla.kernel.org/show_bug.cgi?id=100491)
presents in this version, making the system with mirrored lvm volume
unbootable. Moreover, the patch posted in bugzill
the hw involved, this patch might help:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=66c2b84ba6256bc5399eed45582af9ebb3ba2c15
Alex
>
>Simon
>
> -- System Information:
> Debian Release: 8.0
> APT prefers testing
> APT policy: (990, 'testi
working
/var/log/pm-suspend.log below for debugging, if needed - I hope this helps.
Thanks and regards
Alex
Excerpt from /var/log/pm-suspend.log (post installation of file
"linux-image-3.2.0-4-amd64_3.2.65-1+deb7u1~test_amd64.deb" upgrade -
working) starts
<<
Initial commandline param
control: severity -1 important
thanks
So in terms of deep-freeze bug triage and cleanup, what do we want to do
with this?
It's been over a year, and there aren't any "me-too" here, even though
there are reports of a similar problem at suse and ubuntu. Regardless,
it doesn't seem to be a wide-s
As an update, I loaded 3.15-rc7-686-pae and the screen was completely black
Thanks
Alex Lindberg
--
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/140175
Package: src:linux
Version: 3.14.4-1
Severity: important
After upgrading from linux-image-3.13.1 to 3.14.1, the screen on my laptop (a
Dell D630) is very dim to almost black. Booting to the to image 3.13-1, using
grub, resolves the issue.
LSPCI:
00:02.0 VGA compatible controller: Intel Corporati
I have not experienced either of these issues with the 3.14 kernel
image. Brightness controls work as they should and the display manager
loads just fine.
Thank you for your reply though.
On 2014-05-08 9:24 PM, Matteo Cypriani wrote:
Hi Alex,
On Thu, 02 Jan 2014 19:33:04 -0500, Alex
Package: src:linux
Version: 3.13.5-1
Severity: important
Dear Maintainers,
after updating to linux-image-3.13-1 I am not able to reach disks attached to
LSI SAS1068E sas controller.
The issue is described here:
http://bugs.launchpad.net/ubuntu/+source/linux/+bug/1276705
Thank you,
Alex
Package: src:linux
Version: 3.13~rc6-1~exp1
Severity: important
Dear Maintainer,
This package (version 3.13~rc6-1~exp1) is exhibiting some symptoms that lead me
to believe it's buggy, namely:
1: My display manager (GDM) fails to start when the system finishes booting.
2: The Intel graphics drive
Just want to let you know this bug can be closed now, I haven't once had
the kernel crash due to Folding@Home since my last message and I've gone
through several work units since then, all of which had been resumed
several times through their progress. I think it's quite safe to say
whatever bu
Package: src:linux
Followup-For: Bug #719127
Dear Maintainer,
I am also experiencing what appears to be the same kernel panic. It happens
sporadically and unpredicatbly.
I am also on a Thinkpad (though mine is a T530).
When I had ArchLinux installed on this computer (with a 3.10 kernel), I also
I would like to report that this issue seems to have been resolved in
kernel 3.11-rc7, I am able to run Folding@Home without the kernel
crashing. I do currently appear to be working on a different type of
unit than I had been with the previous kernel, however, but it does
appear to be using the
(In reply to your earlier email) The problem is that I'm already using
version 1.5.4-1 from Unstable, and it's having that issue, so either
something's been changed in the recent kernel version that broke it
again, or makedumpfile has regressed since version 1.5.1-1. Either way
I've already fil
Well, I've discovered why makedumpfile continues to run even after the
dump files show up in the folder. It's failing to properly dump the
kernel log, and is continually appending the line "[ 0.00] " to the
dmesg file. I just ended up with a 3 GB file, nano ended up kaput trying
to open it
I've discovered that the kernel only crashes when the Folding@Home core
attempts to resume a work unit already in progress. After configuring
kdump-tools to not collect unused memory pages (something apparently
recommended if your system has a larger amount of memory), I attempted
to trigger a
Apparently having the kernel image debug package installed is a good
idea when trying to do anything with crash dumps... After installing the
~2GB (unpacked) package I was able to use the crash utility to analyze
(to a degree) the crash dump file made by kdump-tools, however I am
unable to extr
Ah, I didn't know exactly what you meant. Unfortunately I don't know how
to extract anything from the dump files I got with kdump-tools. There
are two files in the crash dump directory I made and pointed kdump-tools
to, dmesg.201308111839 (which is the 2.9 GB file) and dump.201308111839
(the 1.
I was unable to get a photo of the screen output, apparently neither of
the cameras I have available can take high enough resolution shots to
actually read the output even slightly, so I carefully wrote down
(nearly) everything that was displayed and carefully typed it out into a
text file (for
I have to ask: Is it normal for a crash dump (and, apparently, a dmesg
dump as well) to be several GB in size? I ask, because my dump file from
the crash is 1.5 GB and the dmesg dump is 2.9 GB.
I would like to submit these somehow but I don't think via email would
be the best way to do so, and
Oh, well, in that case, I guess reporting it was a good idea then. I can
probably capture a crash dump some time later, if you need it, right now
though I need to get some rest.
On 11/08/13 07:50 AM, Ben Hutchings wrote:
On Sun, 2013-08-11 at 07:40 -0400, Alex Vanderpol wrote:
So I figured
So I figured out what's crashing the kernel, apparently kernel 3.11-rc4
and Folding@Home (when run as a system service) don't get along. I
suspect this may be an issue with Folding@Home rather than the kernel, I
may need to get in touch with them and inform them of this issue so it
can be resol
It would seem the issue isn't so much that the kernel is causing the
display manager to fail to start, apparently the kernel is crashing
after the system finishes booting but before the display manager starts.
I attempted to boot the system using SysV on the off chance it was an
issue with the
Package: src:linux
Version: 3.11~rc4-1~exp1
Severity: important
Dear Maintainer,
It would seem that with the current RC of kernel 3.11 my display manager (GDM)
fails to start after the system finishes booting, and I am unable to switch to
any of the virtual consoles. It seems the system freezes u
notfound 712756 3.2.39-2
found 712756 3.2.46-1
fixed 712756 3.9.6-1~bpo70+1
thanks
Correcting earlier mistake plus:
Wheezy installer and current default 3.2 kernel exhibits this problem.
The wheezy-backports 3.9 kernel does not have the problem.
--
To UNSUBSCRIBE, email to debian-kernel-requ...
on finding a
minimal patch to fix the debian kernel!
That is all I have time for right now.
Alex Owen
Package: src:linux
Version: 3.8.3-1~experimental.1
Severity: important
Dear Maintainer,
Recently it was discovered in Ubuntu that version 3.8.3 of the linux kernel had
issues that caused xrandr to detect an external monitor connected to a laptop
with Intel integrated graphics when in fact no moni
(Resending after reopening bug.)
I encountered this bug in a fresh squeeze install this week. I believe
the problem was that my dom0 was using ext4 filesystems (and not
ext3), while my domU was using an ext3 root filesystem. Therefore, the
initramfs created for dom0 did not include the ext3 module
Package: linux-2.6
Version: 2.6.32-39squeeze1
Severity: normal
-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-39squeeze1) (da...@debian.org) (gcc
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 9 20:49:59 UTC 2012
** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6
On Tue, Nov 22, 2011 at 7:08 AM, Touko Korpela wrote:
> On Mon, Nov 21, 2011 at 09:33:28AM -0500, Alex Deucher wrote:
>> On Sun, Nov 20, 2011 at 10:12 PM, Ben Hutchings wrote:
>> > On Sun, 2011-11-20 at 19:02 -0600, Jonathan Nieder wrote:
>> >> reassign 649448 s
s apparently only required for 3D acceleration and both KMS and 2D
> acceleration of X worked without it, at least on those systems I tested
> (which were quite old, R100-R300 families). Therefore failure to load
> firmware would only result in DRM (3D acceleration support) being
> d
Package: linux-2.6
Version: 2.6.32-38
Severity: important
This bug was not present in 2.6.32-35squeeze2.
My setup: 64bit squeeze dom0, 32bit PV squeeze domU.
When kernel 2.6.32-38 is running in the domU, domU cant be saved/restored
successfuly.
VM is mostly freezed after restore. VM answers to
For me setting acpi=off in the kernel command line at grub solved a
similar issue
Regards
Alexander Täffner
--
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/4de62b3
2011/5/2 Lisandro Damián Nicanor Pérez Meyer :
> On Lun 02 May 2011 11:23:48 Alex Deucher escribió:
> [snip]
>> You might try the patch here:
>> https://bugs.freedesktop.org/show_bug.cgi?id=27708#c7
>>
>> If you are using a DVI or HDMI port, some TV's don'
rent ports if they have minor edid changes
for the port. Also, some hdmi receivers/switches mangle the edids.
Alex
> Kinds regards, Lisandro.
>
> --
> "One of the biggest wake-up calls of my career was when I saw a record
> contract.
> I said, 'Wait - you sell it for $18.98 a
Version 2.6.38-1 seems to have the same issue. Slightly modifed patch follows:
diff -U 3 -H -B -d -p -r -N -- a/drivers/media/video/saa7134/saa7134-input.c b/drivers/media/video/saa7134/saa7134-input.c
--- a/drivers/media/video/saa7134/saa7134-input.c 2011-03-15 06:20:32.0 +0500
+++ b/drive
Package: linux-2.6
Version: 2.6.37-2
Severity: normal
Tags: patch
--- Please enter the report below this line. ---
Hello.
Pinnacle PCTV 110i TV-tuner board has IR remote control, which was recognized
by kernel as input device before this (http://goo.gl/U3Fal) upstream patch.
Since then, ir-kbd-i
On Tue, Mar 01, 2011 at 12:55:19PM +, Ben Hutchings wrote:
> On Tue, 2011-03-01 at 12:28 +0100, Alex Bennee wrote:
> > Package: linux-base
> > Version: 2.6.32-30
> > Severity: important
> > Tags: upstream
> >
> >
> > Starting up rtorrent on a numb
Package: linux-base
Version: 2.6.32-30
Severity: important
Tags: upstream
Starting up rtorrent on a number of torrents causes my VPS to loose network
connectivity. Although conntrack only reports around 250 connections the kernel
oops and the network will not respond any further. I can shell onto
correctly
>
>
Are things any better with a newer kernel?
Alex
>
>
> -- Package-specific info:
> /var/lib/x11/X.roster does not exist.
>
> /var/lib/x11/X.md5sum does not exist.
>
> X server symlink status:
> lrwxrwxrwx 1 root root 13 Dec 27 2009 /etc/X11/X -> /u
On Mon, Oct 11, 2010 at 8:30 PM, Ben Hutchings wrote:
> On Mon, 2010-09-27 at 11:27 -0400, Alex Deucher wrote:
>> On Mon, Sep 27, 2010 at 11:19 AM, Cyril Brulebois wrote:
>> > Aaron Small (26/09/2010):
>> >> I'm having trouble applying these patches - the firs
On Sun, Sep 26, 2010 at 9:46 PM, Ben Hutchings wrote:
> Alex,
>
> Moorthi Pichumani reports that radeon crashes at startup in a Debian
> kernel. This has drm from 2.6.33 with backported fixes. The oops
> message shows it's trying to write through a null pointer in
> r60
On Fri, Aug 13, 2010 at 11:55 AM, intrigeri wrote:
> Hi,
>
> Alex Deucher wrote (13 Aug 2010 15:04:49 GMT) :
>> Are you using kms? If so, does the system hibernate ok without
>> radeon loaded?
>
> Works ok without KMS (radeon loaded + radeon.modeset=0), does no
gle user, rmmod ipw2200, echo disk > /sys/power/state
> 3. single user, rmmod ipw2200, start dbus, udev and hal, pm-hibernate
>
Are you using kms? If so, does the system hibernate ok without radeon loaded?
Alex
> Relevant packages:
>
> linux-image-2.6.32-5-686: 2.6.32-18
>
patch for qcserial and options modules to use a shared wwan module
http://thread.gmane.org/gmane.linux.usb.general/29707
here is a link for the patchs
is it possible to add it to the 2.6.34 build
Alex
-- Package-specific info:
** Version:
Linux version 2.6.34-1-amd64 (Debian 2.6.34-1~experim
l parameter.
The option you used is the correct one. Unfortunately, load detection
for tv-out is often unreliable. There's not a lot you can do to fix
it.
Alex
--
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/aanlktimpemgrzrtq954-4bagn95wxsiwxwjjpm8ud...@mail.gmail.com
I've seen this message often at boot, it appear randomically from zero to more
times (seen up to four).
Take a look to scripts/init-bottom/udev, to me looks like some udevd die
between test -x and readlink (as correctly reported in the comment following
readlink).
The attached patch just ignore
On Tue, Feb 16, 2010 at 05:58:52PM +0100, maximilian attems wrote:
> On Tue, 09 Feb 2010, Alex Samad wrote:
>
> > I have got 2.6.32-6-686 installed on the machine - same problem
> >
> > I can't seem to find a 2.6.32-2-686 (my amd64 is on -7)
>
> so later shoul
On Mon, Feb 08, 2010 at 11:19:16PM +, Ben Hutchings wrote:
> On Tue, 2010-02-09 at 07:37 +1100, Alex Samad wrote:
> > On Mon, Feb 08, 2010 at 01:49:28PM +0100, maximilian attems wrote:
> > > On Mon, Feb 08, 2010 at 09:41:46AM +1100, alex wrote:
> > > > Pack
On Mon, Feb 08, 2010 at 01:49:28PM +0100, maximilian attems wrote:
> On Mon, Feb 08, 2010 at 09:41:46AM +1100, alex wrote:
> > Package: linux-2.6
> > Version: 2.6.32-5
> > Severity: normal
>
> outdated please install newer from unstable.
> has many fixes.
Interest
-110 messages
Feb 3 12:52:13 alex-mini kernel: [ 1217.516249] qcserial: probe of 1-1:1.0
failed with error -110
Feb 3 12:54:36 alex-mini kernel: [ 1360.436267] qcserial: probe of 1-1:1.0
failed with error -110
Feb 3 12:59:28 alex-mini kernel: [ 1652.004171] qcserial: probe of 1-1:1.0
failed
I have a chat on the linux-kernel ml and basically you have to set both of
the redirects.
So you can close the bug.
Thanks
-Original Message-
From: maximilian attems [mailto:m...@stro.at]
Sent: Wednesday, 3 February 2010 8:50 AM
To: Alex Samad; 557...@bugs.debian.org
Subject: Re: Bug
ux-image-2.6.30-2-amd64 2.6.30-8
Linux 2.6.30 image on AMD64
Hope that helps.
Alex.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
.conf.all.secure_redirects = 1
All the other interface redirects set to 1
with another linux machine (alex-mini) on the wireless (192.168.10.0/24 - ip
via dhcp), I try and ssh to laptop - which fails.
When I look at the tcpdump on laptop I see the packets coming in but laptop is
trying to send the
-- System Information:
Debian Release: 5.0.2
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-amd64
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-6-amd64 depends on:
ii coreutils 5.97-5.3
Package: linux-image-2.6.18-6-amd64
Version: 2.6.18.dfsg.1-24etch2
Severity: grave
Justification: renders package unusable
NB- With my Gigabyte GA-K8NS rev 2 motherboard (nForce 3 platform),
the problem is reproducible in all available BIOS versions (F15, F19,
F21A).
Inserting a SonyEricsson W980
I just encountered this bug trying to upgrade from etch to lenny.
Kernel 2.6.26-2 fails to boot with the same error. I was able to
successfully boot with the old kernel (2.6.18-6).
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Con
Than you for a fast help.
:) Alex
Ben Hutchings wrote:
On Sat, 2009-06-06 at 01:16 +0200, Alex Dănilă wrote:
Package: firmware-linux
Version: 0.16
Severity: normal
This is a request for a new version of the firmware-linux package, for
kernels 2.6.30.
I need the file radeon/RV620_cp.bin
Package: firmware-linux
Version: 0.16
Severity: normal
This is a request for a new version of the firmware-linux package, for
kernels 2.6.30.
I need the file radeon/RV620_cp.bin containing new firmware for AMD
video cards, which is
shipped with the standard kernel.
Because of bug #523467 I
Hi
seems like there is a bugzilla for this now
http://bugzilla.kernel.org/show_bug.cgi?id=13375
Alex
signature.asc
Description: Digital signature
Hi
Yeah i am thinking its a xfs problem as well, most of the crashes I am
getting are when i touch XFS via nfs, doing local xfs stuff seems to be
okay - if i was to guess i would say also only on writes
I might try going back to 28.7
have you posted anything on the kernel mailing list
Alex
partitions !
I have upgrade to the latest linux-image 2.6.29-5
mike :- is you setup up xfs | ext3 on lvm on raid(1|5|6). have you done
any tuning with blockdev or raid cache stripes ?
alex
signature.asc
Description: Digital signature
don't see this problem.
I original had irqbalance running but I saw this when I had stop it as well.
Alex
-- Package-specific info:
** Version:
Linux version 2.6.29-1-amd64 (Debian 2.6.29-2) (wa...@debian.org) (gcc version
4.3.3 (Debian 4.3.3-5) ) #1 SMP Sat Apr 4 16:54:07 UTC 2009
** C
On Sat, Nov 08, 2008 at 01:11:38AM +0100, Moritz Muehlenhoff wrote:
> On Sun, Jun 29, 2008 at 06:18:10PM +1000, Alex Samad wrote:
> > Package: linux-image-2.6.25-2-amd64
> > Version: 2.6.25-5
> > Severity: normal
> >
> > I recently bought a gigabyte GA-MA7
Yup,
it solves it, and boots 15 sec. faster :) . Are there any grave problems
(like fs corruption)?, because I would stick with this kernel.
Alex.
maximilian attems wrote:
can you please check 2.6.29-rc7 from trunk, see apt lines
http://wiki.debian.org/DebianKernel
--
To UNSUBSCRIBE
27;t apply
both set of patches (rt and debian) without having to manually resolve
not few conflicts.
I must be missing something.
Alex
On Fri, Jan 23, 2009 at 4:54 PM, dann frazier wrote:
> On Fri, Jan 23, 2009 at 01:43:43PM +, Alex Gonzalez wrote:
>> Hi,
>>
>> Please
://ftp.de.debian.org/debian/pool/main/l/linux-2.6.24/
Debian patches from: http://ftp.uk.debian.org/debian/pool/main/l/linux-2.6.24/
Thanks in advance,
Alex
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: linux-image-2.6-amd64
Version: 2.6.26+17
Severity: important
An mplayer crash when playing specific files will trigger the kernel
error message that will be described. From that moment on, a range of
crashed/freezed processes can
be killed no more. Example of such unkillable processes
looks like Alan Cox's patch will be in 2.6.27, and in the meantime
you can achieve a work around by rebuilding your initrd to load
pata_marvell before ahci.
I hope this helps everyone who's been affected by this problem!
--alex
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Alex
-- Package-specific info:
** Version:
Linux version 2.6.26-1-amd64 (Debian 2.6.26-6) ([EMAIL PROTECTED]) (gcc version
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Sep 24 13:59:41 UTC
2008
** Command line:
root=/dev/mapper/vglocal-root ro vga=0x317
** Tainted: P (1)
** Kernel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi bastian,
now it works with other kernels.
thanks a lot,
alex
Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the linux-2.6 package:
>
> #394608: linux-image-
information was different from the
ip li information
I had
ip r a 192.168.11.10/32 dev eth0 mtu 9100
ip li set eth0 mtu 6144
since clearing these up I haven't had any problems, I was able to
previously reproduce the probem by coping over a 2G file
Alex
signature.asc
Description: Digital signature
01 00 00
there seems to be some talk on this thread
http://ubuntuforums.org/showthread.php?t=671614 of a r8168 module, which I
can't find in the source tree ?
Alex
-- Package-specific info:
** Version:
Linux version 2.6.25-2-amd64 (Debian 2.6.25-5) ([EMAIL PROTECTED]) (gcc version
4
1 - 100 of 146 matches
Mail list logo
