Source: linux
Version: 4.9.30-2
Severity: normal
It seems dm-raid.ko isn't in md-modules.udeb, or any other udeb on
DVD-1. It'd be useful to have it there to allow install on LVM-RAID
(which otherwise just requires an lvcreate or two on the command line).
Also useful because it'd presumably
Package: src:linux
Version: 4.5.1-1
Severity: normal
File: /lib/modules/4.5.0-1-amd64/kernel/drivers/acpi/thermal.ko
thermal: module verification failed: signature and/or required key
missing - tainting kernel
thermal LNXTHERM:00: registered as thermal_zone0
ACPI: Thermal
Package: nfs-common
Followup-For: Bug #740491
I've had this happen on two machines I've upgrade so far.
It turns out that you get an error (sorry, didn't copy down the exact
message) when you try to run:
rpcinfo -d status 1
to un-register the service.
On a third machine, I ran that
02:06 PM, Jonathan Nieder wrote:
Hi Anthony,
Anthony DeRobertis wrote:
Under 3.1, the wirless works fine (0% packet loss). Under 3.2, ping
shows 25% packet loss pinging the local gateway. This is repeatable;
each time I boot 3.1, it works, each time I boot 3.2 it doesn't. I have
tried each
Package: linux-2.6
Version: 3.2.4-1
Severity: normal
File: /lib/modules/3.2.0-1-amd64/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko
Under 3.1, the wirless works fine (0% packet loss). Under 3.2, ping
shows 25% packet loss pinging the local gateway. This is repeatable;
each time I boot 3.1, it
I tested 2.6.35~rc6-1~experimental.1 and the power consumption is back
to 2.6.33 levels, or even a little better, once all of powertop's
suggestions (particularly wireless power save) are implemented.
I think I managed to send the correct command to cont...@.
--
To UNSUBSCRIBE, email to
Package: linux-2.6
Version: 2.6.34-1~experimental.1
Severity: normal
Attached is powertop from 2.6.33 and also from 2.6.34. This is on an
Asus UL30A-X5 which is:
- idle
- booted into an identical gnome desktop
- just a gnome-terminal open running powetop
- connected to the same (idle)
Package: linux-base
Version: 2.6.32-11
Severity: normal
┌───┤ Configuring linux-base ├───┐
││
│ These configuration files will be updated: │
│
On Fri, Apr 09, 2010 at 11:24:23AM +0100, Ben Hutchings wrote:
Right. And it is generally able to convert references to CD drives.
Please send the contents of /etc/udev/rules.d/70-persistent-cd.rules and
the output of 'ls -l /dev/disk/by-id'.
anth...@feynman:~$ cat
Sorry for taking so long to respond. Adding the model=auto option fixes it.
--
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/4b9e14db.9090...@derobert.net
Package: linux-2.6
Version: 2.6.33-1~experimental.2
Severity: normal
This is an Asus UL30A.
On 2.6.32, I get two Mic Boosts: One called Mic Boost and one called
Front Mic Boost. The Front Mic Boost is for the built-in microphone
mounted at the top of the display; the other is assumably the mic
On 03/09/2010 09:30 PM, maximilian attems wrote:
please sent output of alsa-info.sh of 2.6.32 and 2.6.3
Attached. I couldn't find an alsa-info.sh in any Debian package, so I
grabbed the one from here:
On Tue, Jan 26, 2010 at 11:26:33AM -0800, Greg KH wrote:
Please let me know when it hits Linus's tree and what the git commit id
is for it then.
I believe
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4bb950806f10bc3e249dd34375b4a4d6bfc0
means its now in
Package: linux-2.6
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Linux-next commit 4bb950806f10bc3e249dd34375b4a4d6bfc0 contains a
fix for this bug. I'd really appreciate it if you'd cherry-pick this for
2.6.32 (which I understand squeeze is going to release with). The diff
Package: linux-2.6
Version: 2.6.31-2
Severity: normal
This warning showed up in my kernel logs, as I either logged out or in
(to a e16/KDE desktop, logged in using gdm).
Dec 2 10:22:49 Tao kernel: [1124012.512054] [ cut here
]
Dec 2 10:22:49 Tao kernel:
Package: linux-2.6
Version: 2.6.30-8
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a Unitech MS-180 barcode reader, which acts as a USB HID
keyboard. It works perfectly with the attached patch, which just removes
it from the blacklist. Note that the patch
On Wed, Aug 01, 2007 at 01:42:39AM +0200, maximilian attems wrote:
tags 358502 moreinfo
stop
is that fixed with a newer alsa in sid linux image 2.6.22 ?
The machine is running etch. However, it does have a backported 2.6.22
installed; I'll check if the bug still exists ASAP (probably
maximilian attems wrote:
sounds like a strange hardware bug,
any update on it?
Machine hasn't crashed since, despite several reboots...
thanks
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
maximilian attems wrote:
is that bug still existent in 2.6.18 linux-image ?
I don't know; I replaced the VIA board with an nForce board...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: linux-2.6
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Example from apt-cache search:
linux-image-2.6.18-2-xen-vserver-686 - Linux 2.6.18 image on
PPro/Celeron/PII/PIII/P4
The version is specified in the package name, the package version, and
the short description;
OK, here are the results with iommu=force. All of these are copied down
by hand, so please forgive any transcription errors:
2.6.12[1]: Last line displayed on screen is ata1: dev 0 ATA max
UDMA/133 390721968 sectors, lba48. Then it sits there. Scrolling with
shift-pgup/pgdown works.
Andi Kleen wrote:
Is that a board with VIA chipset?
Yep.
VIA doesn't seem to support PCI accesses with addresses 4GB and they also
don't have a working GART IOMMU.
It will likely work with iommu=force
I'll give this a try I do get a line in dmesg which reads:
PCI-DMA: Disabling
Package: cramfsprogs
Version: 1.1-6
Severity: normal
File: /usr/sbin/mkcramfs
mkcramfs is useful to non-sysadmins --- software developers, in
particular. It should probably really be in /usr/bin.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500,
Package: linux-2.6
Followup-For: Bug #327355
Anything I can do to help track down this regression?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux
Package: linux-2.6
Followup-For: Bug #341801
Is there anything I can do to help get this fixed?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux
Package: linux-2.6
Followup-For: Bug #347412
This still isn't fixed in 2.6.17-2. What may I do to help get this
fixed?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Martin Michlmayr wrote:
* Anthony DeRobertis [EMAIL PROTECTED] [2006-07-03 02:15]:
Is there anything I can do to help get this fixed?
You could try latest -mm if you have time.
You mention 2.6.12 several times. Does that mean that Ethernet works
correclty with 2.6.12 even
Ugh, -mm6 and kernel-package seem to be on less than friendly terms :-(
Oh well, building it the non-Debian way.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Thu, Mar 30, 2006 at 05:48:17AM -0800, Kevin Brown wrote:
Hmm...2.6.16 is out now, so perhaps that works properly in SMP mode?
Nope, already tested :-(
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Jurij Smakov wrote:
Hi,
Is it a laptop? The first impression is that it is some kind of ACPI
problem. Could you please try some combinations of boot options
Well, I just tried to debug it, only to discover that the machine does
not wish to crash tonight, no matter what options I give it.
Package: linux-2.6
Followup-For: Bug #327355
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ide-tape: hdd - ht0: Seagate STT2A rev 8A51
ide-tape: hdd - ht0: 1000KBps, 6*54kB buffer, 9720kB pipeline, 110ms tDSC, DMA
Badness in dma_map_sg at include/asm/dma-mapping.h:47
[e083fa66]
Package: linux-2.6
Followup-For: Bug #347412
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It took a while to reproduce, but skge + sata_promise is still a no-go
on 2.6.16. SATA died this time...
It seems it might be harder to reproduce on 2.6.16 than on 2.6.15, but
it has always been random,
Anthony DeRobertis wrote:
Trying with sk98lin now.
Tried it; it doesn't work either. Back to 2.6.12 :-(
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Jurij Smakov wrote:
Hi,
Is it a laptop?
No. It's a mid-tower.
The first impression is that it is some kind of ACPI problem. Could
you please try some combinations of boot options
acpi=off
pci=norouteirq
pci=noacpi
I'll give these a try ASAP.
nolapic
The boot messages with 2.6.16 says
Package: linux-2.6
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I upgraded a machine (lspci attached) to linux-image-2.6.16-1-k7
(version 2.6.16-2) and this new kernel panics before even getting to the
initrd. It appears to break right after detecting the VGA console. Here
is
Martin Michlmayr wrote:
There now.
2.6.16 generally panics before even looking at the initrd. The one time
(out of like 10 tries) it booted, the ide-tape bug is still there.
There is an additional message, something along the lines of
dma_map_(something). It repeated a lot, starting when
Package: linux-2.6
Followup-For: Bug #358718
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached.
- -- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing'), (130, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Package: linux-image-2.6.16-1-686-smp
Version: 2.6.16-1
Severity: wishlist
Not sure if there is a way to fix this or if its just yeah, hardware
sucks but 2.6.16 makes snd_had_intel's position_fix=1 param quite
needed. [Actually there was a little static, every once and a while, in
previous kernel
Martin Michlmayr wrote:
Anthony, do you still see this bug with 2.6.15 or (better yet) 2.6.16?
(will be uploaded tomorrow).
2.6.15, yes. I'll check 2.6.16 when it hits unstable (I'm guessing,
though I still need to test, that the ide-tape cleanup in 2.6.9 borked it)
--
To UNSUBSCRIBE,
maximilian attems wrote:
that's wrong.
udevd in initramfs is killed before handover, init starts a new udevd
which processes the out of banded coming uevents.
Glad to hear that! So, then, should initramfs not be regenerated on udev
upgrades?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
posted mailed
Jonas Smedegaard wrote:
I believe udev cintained within ramdisk needs to match udev outside -
so if udev on the system is updated then (all!) initramfs-based
ramdisks needs to be regenerated in order to survive _next_ boot.
Ouch! If this is true, it'd seem that somehow, the
Jonas Smedegaard wrote:
Do you consider the following a reasonable resolution?:
Sounds fine to me. Though it looks like your changelog entry has been
mangled a little:
bug#345067 (thanks especially to Jurij Smakov [EMAIL PROTECTED]
bug#for
--
To UNSUBSCRIBE, email to [EMAIL
Adeodato Simó wrote:
when udev gets upgraded, the latest initram is regenerated via
udev's postinst.
This sounds to me to be a fundamentally bad idea. The current initrd
clearly works --- the system did, after all, boot --- why would you
want to regenerate it?
If there is some *really*
Jonas Smedegaard wrote:
I believe it is important for yaird to apply same strict logic to all
Linux kernels, official or not.
Seems perfectly reasonable to me.
I think the following has been discovered:
1. The ide-generic requirement was added by the modular IDE patch, which
Debian included
Sven Luther wrote:
That means that jonas's fear of breaking self-built kernels is vastly
unfunded, and that he should remove those hacks, include a mention of
the broken kernels in the README file, and maybe propose a fixed yaird
to stable-proposed-updates or something.
yaird is not in
Jurij Smakov wrote:
That patch has been dropped starting with the release of 2.6.15-1
Debian kernel packages, according to changelog.
I tested my 2.6.12 machine last night, and it does indeed require
ide-generic. My empirical results agree with your analysis.
--
To UNSUBSCRIBE, email to
Jurij Smakov wrote:
Looking at the code I cannot see how the
native drivers can depend in any way on the ide-generic being loaded
before them.
While I have not thoroughly tested 2.6.15 in this respect, in 2.6.8 and
2.6.12 some IDE drivers, on some hardware, absolutely does[0]. Maybe
this is
Sven Luther wrote:
While I have not thoroughly tested 2.6.15 in this respect, in 2.6.8
and 2.6.12 some IDE drivers, on some hardware, absolutely does[0].
Maybe this is fixed in 2.6.15/16.
Do you know why this happened ? I will look at the code in 2.6.12 this
evening to understand this.
posted mailed
Anthony DeRobertis wrote:
Actually, the machine I'm at right now has ide-generic in
its /etc/modules file, after piix; I added it there by hand for 2.6.8,
probably (this machine boots off SATA, so IDE is only needed after
boot for the e.g., DVD-RW). Its currently on 2.6.15
Kevin Brown wrote:
Could you test with the amd64-generic kernel to see if you get hangs
with the on-board Promise controller and ethernet? I was considering
putting another couple of disks in mine but don't want to spend the
cash if it'll just hang.
Well, I'm testing with the -k8 kernel,
Ok, I've tested and it definitely seems that
linux-image-2.6.15-1-amd64-k8 version 2.6.15-7 is not affected by the
network/SATA hang (bug #347412)
I haven't tested 2.6.15-7 SMP, but all the previous 2.6.15-X SMP
versions were affected, so...
[This is a dual-core athlon 4400, so it'd be nice to
Kevin Brown wrote:
Well, the main reason is that I didn't see any advantage, since I'm
running a non-SMP system.
Ok, so you don't see the ethernet/sata hangs, then? Are you using the
VIA SATA controller or the Promise one?
One other thing: I'm using ECC memory, and have ECC enabled.
Why
Kevin Brown wrote:
PS: Since you have the same hardware as me, I'm curious if you're able
to use kernels 2.6.12.
Yeah. I'm currently using 2.6.15. Note that I'm using the
amd64-generic kernel, not the amd64-k8 kernel. I don't expect that
makes any difference at all with respect to this
Kevin Brown wrote:
I can confirm this bug.
I'm running kernel 2.6.15-1-amd64-generic version 2.6.15-6, and see
the very same thing.
So I have to turn off the memory remapping feature that allows the
system to see all 4 gig of memory, and thus lose the use of about 200
megabytes of
Ok, I just tried with having only the 'skge' module loaded since boot.
Once again, ethernet died.
So, the summary is:
2.6.12, w/ sk98lin: Works
2.6.12 does not have skge.
2.6.15 w/ sk98lin skge (yes, you can load both[0]): Fails
2.6.15 w/ sk98lin: Fails
2.6.15 w/ skge: Fails
where fails means
Same problem. Network died.
I did notice that udev/discover were somehow loading both the skge and
sk98lin modules. The sk98lin test I just did was after confirming that
skge had never been loaded since boot.
I can test again with only skge loaded since boot, but it can take some
time to
Package: linux-image-2.6.15-1-amd64-k8-smp
Version: 2.6.15-1
Severity: grave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have an ASUS A8V motherboard. When I use both the on-board LAN, skge,
and the on-board Promise PDC20378 SATA controller, one or the other
dies. Ways to kill the machine
Package: linux-image-2.6.14-2-amd64-k8-smp
Version: 2.6.14-4
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a Asus A8V with 4GB of RAM. When I turn on the hardware memory
hole in the BIOS, the skge driver prints out this message:
skge hardware error detected
Package: linux-image-2.6.14-2-amd64-k8-smp
Version: 2.6.14-4
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Under 2.6.12-1-amd64-k8-smp my via82xx sound works fine (on-board sound
on Asus A8V). Under 2.6.14, I get:
kernel: cannot find the slot for index 0 (range 0-0)
kernel: VIA
Sven Luther wrote:
because i was thinking that the problem happened during boot time, and since
there where issues of read-only filesystems. ...
This is definitely at creation time.
BTW, erik, i am not sure to have the files in non-/tmp will help
security-wise, since it will only protect
Package: yaird
Version: 0.0.11-10
Severity: important
/boot is for static files of the boot loader according to the FHS.
yaird is attempting to use it as /tmp, and failing horribly as it runs
out of inodes:
anthony:/etc/yaird# df -i /boot
FilesystemInodes IUsed IFree IUse%
Package: kernel-image-2.6.8-2-k7
Version: 2.6.8-16
Severity: normal
This popped up during a little bit of NFS load:
[ cut here ]
kernel BUG at fs/jbd/journal.c:1824!
invalid operand: [#1]
PREEMPT
Modules linked in: nls_cp437 sch_ingress cls_u32 sch_sfq sch_prio
Horms wrote:
Hi Anthony,
I am forwarding this to the IDE Tape maintainer for his consideration.
Thank you. Please tell me if anything comes out of it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Oh, btw, it just died on a different tape tonight... I rebooted to
2.6.8, and it works fine there. So its definitely a regression from 2.6.8.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: linux-image-2.6.12-1-k7
Version: 2.6.12-6
Severity: important
amverify started, then shortly later (after the first thing was done
verifying, I think) these managed to make it to syslog. As you can see,
it got the bug message, then rebooted itself a few minutes later:
Sep 9 01:12:27
Christoph Hellwig wrote:
Best thing for 2TB disks is to use LVM anyway
At least as far as d-i is concerned (AFAICT), you have to put LVM on top
of an existing partition table; you can't just use the full /dev/sda or
whatever. (The command-line lets you get around this).
However, even if you do
66 matches
Mail list logo
