Hi YunQiang,
Could you try the following kernel patch & let me know if it works for
you?
My theory is that this is fallout from commit 517e1fbeb65f
("mm/usercopy: Drop extra is_vmalloc_or_module() check") which went into
Linux v4.12. I guess this shows our test systems don't have hardened
On 11 March 2012 21:06, Holger Jeromin jero...@hitnet.rwth-aachen.de wrote:
Jonathan Nieder schrieb am 11.03.2012 20:36:
Holger Jeromin wrote:
The patch (e1000e: workaround for packet drop on 82579 at 100Mbps)
hit mainline in v3.1-rc4. Are squeeze 2.6.32.y kernels affected?
As you can see
Regarding possible support for the Intel 82579LM and 82579V in Squeeze:
Many (but not all) devices including an Intel 82579 series NIC have a
hardware fault at 100Mbps that results in packet loss that is worked
around by the following recent patch:
http://patchwork.ozlabs.org/patch/109926/
Package: linux-2.6
Source: linux-2.6
Version: 3.0.0-3
Severity: normal
Tags: patch
Many (but not all) devices including an Intel 82579LM NIC have a
hardware fault that results in packet loss at 100Mbps that is worked
around by the following recent patch:
http://patchwork.ozlabs.org/patch/109926/
Package: linux-image-2.6.26-1-iop32x
Version: 2.6.26-10
Severity: normal
With 2.6.26 running ifplugd causes the kernel to assert:
[42949526.36] BUG: scheduling while atomic: swapper/0/0x0100
It appears that the cause is the new LED driver, when ifplugd drives to beep.
-- System
Package: linux-image-2.6.25-2-iop32x
Version: 2.6.25-5
Severity: normal
I have a NAS (Thecus N2100, IOP32x based) connected to my network using the
r8169 driver. When I start avahi-daemon on the NAS, the rest of the network
sees the multicast zeroconf announce packets being sent. If I wait five
Martin,
I don't want to pester, but is there any progress from Intel on this?
The current disk speed is pretty poor, considering my n2100 is meant to
be a NAS. :/
Ross
--
Ross Burton mail: [EMAIL PROTECTED]
jabber: [EMAIL
Package: linux-2.6
Severity: wishlist
Please package a bigmem version of the vserver kernel. People using vserver may
well be doing so on server hardware with 4gb of ram (I am).
Thanks,
Richard.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500,
Package: linux-image-2.6.18-1-686
Version: 2.6.18-3
Severity: important
Module compat has been broken between this version and the previous.
This should not happen when the package name is being kept the same, if
module compat needs to be broken the package should become
tags 394974 - moreinfo
thanks
Please show the breakage.
Oops, forgot to paste some in. Here are examples from 2 boxes:
boot.0:Tue Oct 24 08:16:57 2006: nvidia
boot.0:Tue Oct 24 08:16:57 2006: FATAL: Error inserting nvidia
(/lib/modules/2.6.18-1-686/nvidia/nvidia.ko): Invalid module
Package: linux-image-2.6.17-2-686
Version: 2.6.17-6
Severity: normal
Wake on lan doesn't work with the tg3 driver. WOL was enabled with the ethtool,
and confirmed as on with the same tool. After shutdown the computer cannot be
woken (works fine when bcm5700 driver is used instead).
This is not a
Package: linux-image-2.6.16-1-686
Version: 2.6.16-7
Severity: important
After installing new 2.6.16-7 packages no custom modules would load, appears
module compatibility has been broken.
e.g.
kernel: bcm5700: disagrees about version of symbol struct_module
Module compat shouldn't be broken on a
Richard, you said you were able to build fglrx. Did you make something
special ?
I also tried without module-assistant, but cannot figure out why it is
looking
for Makefile.lib.c file.
That module builds fine for me, in fact so far it's the only one that does
against 2.6.16.
bcm5700
Package: linux-image-2.6-vserver-686
Severity: minor
Hi,
The new linux-image-X-vserver-Y packages all appear to have short and
long descriptions that are identical to the corresponding non-vserver
linux-image-X-Y packages. (I have only verified this for
linux-image-2.6-vserver-686 and
Package: linux-2.6
Severity: important
Unable to build some modules against the new 2.6.16 headers package. Here is the
top of the output from trying to build the tp_smapi module against 2.6.15 16:
[EMAIL PROTECTED]:~/tp_smapi-0.17# make install
make -C /lib/modules/2.6.15-1-686/build
This appears to be a duplicate of #330081, but since this one is marked
'confirmed' and has a different urgency, I'll leave it to the
maintainers to combine as they see fit.
Yes, it does seem to be the same problem. As it looks to have been fixed now
they should ideally be merged and closed -
It appears that this has now been fixed in 2.6.15-3, the localversion file
is now installed with the headers. I have tested it with the zaptel module
and it now installs to the correct location.
Can this bug be closed, or has it been left open for a reason?
Richard.
--
To UNSUBSCRIBE,
Package: linux-2.6
Version: 2.6.15
When using make module_install with the makefile that comes with the kernel
(/lib/modules/2.6.15-1-686/build/Makefile) modules are not installed into
the correct location in /lib/modules. They build fine but are then installed
to /lib/modules/2.6.15 instead
Congratulations, you are the first to file a bug report against linux
2.6.15 :)
Yay ;-)
Could you tell us exactly what you do to build the module, and check if
this
is not a bug in m-a or your module ?
The official recomended way of building modules is to build inside the
module
tree
KDIR := /lib/modules/$(KVER)/build
modules: $(patsubst %.o,%.c,$(TP_MODULES))
$(MAKE) -C $(KDIR) M=$(PWD) modules
...
install: modules
rm -f /lib/modules/$(KVER)/kernel/$(MDIR)/{tp_base,tp_smapi}.ko
$(MAKE) -C $(KDIR) M=$(PWD) modules_install
We use $(MAKE)
Calling 'make -C /lib/modules/2.6.15-1-686/build kernelrelease' shows
the
kernel release as 2.6.15, but shouldn't this show 2.6.15-1-686, (which
is
defined for UTS_RELEASE in version.h)?
can you give the output of :
dpkg -l | grep linux-header
[EMAIL PROTECTED]:~$ dpkg -l | grep
On Tue, 8 Nov 2005 15:34:48 +0100, Sven Luther wrote [typo corrected]:
You can now, just need to add
Recommends: blah to the arch/arch/defines entry.
Now the capability has been added, any chance you could pop this extra line
in? I'd be happy to do it myself, but of course I can't.
Richard.
2.6.8 is frozen solid for sarge. IF there is interest in having this
added for the etch kernels, can you please reasign it to linux-2.6
I think it should become a permanent addition to all 686 class kernels going
forward, but I don't mind what point that starts at - unstable would be fine
for
Confirmed fix working. Thanks guys.
Richard.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel-images 2.6.x-686 and 2.6.x-k7 shoud recommend libc6-i686,
because libc6-686 improves system performance when running with
2.6.x-686 and 2.6.x-k7 kernel-images.
Thanks for the clarification.
I now agree with your suggestion.
I will get it into the tree, but
my TODO list is rather long
As Sven said vesafb isn't a module at 2.6.14. So for =2.6.14 you need
both,
for 2.6.14 you only need to add fbcon to the conf file.
I'm sure you all spotted it - there is a slight error in the above
statement, so for the record it should read:
As Sven said vesafb isn't a module at 2.6.14. So
Package: linux-image-2.6.14-1-686
Version: 2.6.14-1
Severity: normal
When booting with vga=795 option at the point it should switch video mode the
screen simply goes black. Continues to boot fine and I am able to login blind.
Same kernel option worked fine at 2.6.12. Here is my grub conf:
title
Package: linux-headers-2.6.14-1
Version: 2.6.14-1
Followup-For: Bug #336295
I'm also hitting this problem, maybe what's missing is made a little clearer by
the comparison between 2.6.12 2.6.14:
lrwxrwxrwx 1 root root8 Sep 30 19:44
./linux-headers-2.6.12-1-686/include/asm - asm-i386
This could be changes to video drivers in the kernel. Please describe
your graphics card used.
Oops, I did intened to mention that. It's an Nvidia GeForce 6600GT 128MB
(generic unbranded reference board).
Please try the following:
1) add ramdisk = /usr/sbin/mkinitrd.yaird to
Nvidia. Ok (or ok is perhaps an exageration: problems with this
specific hardware vendor is not really a surprise to me...)
Yeah, but it plays native Linux Quake 4 very nicely!
You did remember to uninstall yaird before regenerating the ramdisk?
Yep, and to confirm it I checked the size of
Try editing /etc/yaird/Default.cfg and add the following:
MODULE vesafb
Ok, that got the vesafb loaded, but that didn't give me video. Added MODULE
fbcon as well and that did the job. This testing was all on the 2.6.12.
As Sven said vesafb isn't a module at 2.6.14. So for =2.6.14 you need
Things people need for feeling better.
http://VTWcwOHDfaks.t6i.net/p/sevy/wa.html
Burton
My name is Julie :)
Most of the time I like to do something I've never done before.. so I decided
to have my first website featuring me (pics and videos). My girlfriends want
to join me to on my website. -) Verify your age and connect to my webcam today
-)
Come I want to share my life
Imagine having debt no more!
For the rest of the story about destroying debt, visit us here
http://qog.e2.coolproductmessage.com/e3/
Student loans or tax liens? Discharge these debts quickly, painlessly,
legally and without damaging your report.
po box in link above and you can say no thank
maks attems wrote:
tags 260971 moreinfo
thanks
On Thu, 22 Jul 2004, Daniel Burton wrote:
..
My system stops and becomes completely unresponsive, both locally and
over the network at random times, usually within two hours of booting on
this kernel version. It is okay on version 2.6.5-1-k7
35 matches
Mail list logo