Bug#890343: linux: make fq_codel default for default_qdisc
Hello. Not an expert nor kernel developer, etc., just simple sysadmin here, but will answer anyway since nobody did yet. I think we want the mq qdisc to distribute the load between cores, to support very high speed network cards or too slow CPUs. Also, if net.core.default_qdisc = fq_codel is used, it also has the mq qdisc and fq_codel childs for each CPU core, so that's the default behavior in other distros. I guess being under mq it could impact fq_codel's ability somewhat, but it's better to support all the hardware spectrum by default, otherwise we should use cake as default since it can handle up to 10Gbit/s without troubles; we don't, because Debian is a generic operating system so it should work on embedded devices, laptops, workstations and big iron servers... Also, I don't see a problem with statically linking fq_codel if we are using it as default, since it will probably get loaded anyway... Thanks for pushing this forward, doing these tests, etc.!!! Bye. El 7/1/21 a las 21:12, Noah Meyerhans escribió: On Thu, Apr 23, 2020 at 03:34:06PM -0700, Matt Taggart wrote: #890343 was originally opened against systemd asking to install the upstream systemd sysctl.d/50-default.conf file that sets: net.core.default_qdisc = fq_codel As explained in #950701 (and the systemd debian changelog) the debian systemd maintainers felt that systemd in debian should not be changing kernel policies (and I agree). So #890343 was reassigned to linux to consider changing the default. fq_codel is better in every way than pfifo_fast and I am unaware of any reason why it would not be a better default. (but don't trust me, ask the kernel networking experts) Can we change it? I strongly agree that we should make this change for the bullseye release. I'm looking into provding a patch to implement the switch to fq_codel by default, but it appears to require something more than just a kernel config change. I have tried the following with the 5.10 kernel from the current sid branch: CONFIG_NET_SCH_FQ_CODEL=m CONFIG_DEFAULT_FQ_CODEL=y CONFIG_DEFAULT_NET_SCH="fq_codel" Then we don't see any change at all to the qdisc in use: admin@ip-10-0-0-162:~$ grep -i fq_codel /boot/config-$(uname -r) CONFIG_NET_SCH_FQ_CODEL=m CONFIG_DEFAULT_FQ_CODEL=y CONFIG_DEFAULT_NET_SCH="fq_codel" admin@ip-10-0-0-162:~$ /sbin/sysctl net.core.default_qdisc net.core.default_qdisc = pfifo_fast admin@ip-10-0-0-162:~$ tc qdisc show dev ens5 qdisc mq 0: root qdisc pfifo_fast 0: parent :2 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 qdisc pfifo_fast 0: parent :1 bands 3 priomap 1 2 2 2 1 2 0 0 1 1 1 1 1 1 1 1 admin@ip-10-0-0-162:~$ ip link show dev ens5 2: ens5: mtu 9001 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 02:47:e2:7c:be:ff brd ff:ff:ff:ff:ff:ff altname enp0s5 If we statically link the fq_codel module into the kernel, then we see: admin@ip-10-0-0-162:~$ grep -i fq_codel /boot/config-$(uname -r) CONFIG_NET_SCH_FQ_CODEL=y CONFIG_DEFAULT_FQ_CODEL=y CONFIG_DEFAULT_NET_SCH="fq_codel" admin@ip-10-0-0-162:~$ /sbin/sysctl net.core.default_qdisc net.core.default_qdisc = fq_codel admin@ip-10-0-0-162:~$ /sbin/tc qdisc show dev ens5 qdisc mq 0: root qdisc fq_codel 0: parent :2 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64 qdisc fq_codel 0: parent :1 limit 10240p flows 1024 quantum 1514 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64 admin@ip-10-0-0-162:~$ ip link show dev ens5 2: ens5: mtu 9001 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 02:47:e2:7c:be:ff brd ff:ff:ff:ff:ff:ff altname enp0s5 So in this case, we have fq_codel configured, but not as the root qdisc for the interface. If we manually set it: admin@ip-10-0-0-162:~$ sudo /sbin/tc qdisc add root dev ens5 fq_codel Then we get the following configuration: admin@ip-10-0-0-162:~$ /sbin/tc qdisc show dev ens5 qdisc fq_codel 8001: root refcnt 3 limit 10240p flows 1024 quantum 9015 target 5ms interval 100ms memory_limit 32Mb ecn drop_batch 64 admin@ip-10-0-0-162:~$ ip link show dev ens5 2: ens5: mtu 9001 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 02:47:e2:7c:be:ff brd ff:ff:ff:ff:ff:ff altname enp0s5 I believe that this is what we want. Is that accurate? The recent thread at https://www.mail-archive.com/netdev@vger.kernel.org/msg380410.html also seems relevant. noah -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ Freelance C++/PHP programmer and GNU/Linux systems administrator. The sky is not the limit!
Bug#409271: Workaround
On Thu, 4 Aug 2016 17:54:10 -0500 "Timothy Pearson" < kb9...@pearsoncomputing.net> wrote: > For now, since klibc does not have NFSV4 support, the attached file works > around the problem (place in /usr/share/initramfs-tools/hooks/nfsv4). Thanks a lot for the workaround!!! Though it doesn't work with read-only NFSv4.1 and OverlayFS with TmpFS on Stretch, both kernels 4.9 and 4.19. Any ideas? In the hook I added your workaround and: manual_add_modules overlay Then on /etc/initramfs-tools/scripts/init-bottom/local: mkdir -m 700 /ovl mkdir /ovl/lower /ovl/ram /ovl/merged mount -n -o move $rootmnt /ovl/lower mount -n -t tmpfs -o 'mode=755,size=75%' tmpfs /ovl/ram mkdir /ovl/ram/upper /ovl/ram/work mount -n -t overlay -o "lowerdir=/ovl/lower,upperdir=/ovl/ram/upper,workdir=/ovl/ram/work,_netdev" overlay /ovl/merged mount -n -o move /ovl/merged $rootmnt mkdir -m 700 $rootmnt/ovl mkdir $rootmnt/ovl/lower $rootmnt/ovl/ram mount -n -o move /ovl/lower $rootmnt/ovl/lower mount -n -o move /ovl/ram $rootmnt/ovl/ram This works with NFSv3. Also, if I test it on an already booted system with mounting NFSv4.1 manually and doing the overlay it works. So, something in the initramfs is different to the booted up system that causes the problem, but couldn't find it. If anyone has any idea of things to try I can report back the results and try to provide a fully working solution afterwards. Thanks!
Bug#911727: initramfs-tools-core: configure_networking avoid panic and wait for at least one network interface.
Package: initramfs-tools-core
Version: 0.130
Severity: normal
Tags: patch
In stable/stretch if there are no interfaces yet and ip-config doesn't
configure anything we get a panic.
I am using this patch in production with good results, it waits for
network interfaces to show and avoids sourcing an inexistent file,
avoiding the panic.
This happens with a USB network card but it could happen with other
cards too.
Maybe it is too much for stable/stretch, but unstable/sid version
0.132 seems to have the same problem so can be applied there.
Here it is, hope you find it useful:
--- functions.old 2017-03-06 19:42:55.0 -0300
+++ functions 2018-10-23 19:20:26.726994846 -0300
@@ -182,6 +182,15 @@
configure_networking()
{
+ for device_wait_try in 5 4 3 2 1; do
+ for device in /sys/class/net/*; do
+ [ $device = /sys/class/net/lo ] && continue
+ break 2
+ done
+ sleep 1
+ done
+ [ $device_wait_try = 1 ] && log_warning_msg "No network device found"
+
if [ -n "${BOOTIF}" ]; then
# pxelinux sets BOOTIF to a value based on the mac address of
the
# network card used to PXE boot, so use this value for DEVICE
rather
@@ -269,10 +278,12 @@
if [ -n "${DEVICE}" ]; then
# source specific bootdevice
. /run/net-${DEVICE}.conf
- else
+ elif [ -e /run/net-*.conf ]; then
# source any interface...
# ipconfig should have quit after first response
. /run/net-*.conf
+ else
+ log_warning_msg "Network configuration failed, maybe
driver/module not loaded/initialized yet or cable/network problem"
fi
}
Thanks a lot!!!
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8),
LANGUAGE=es_UY.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages initramfs-tools-core depends on:
ii cpio 2.11+dfsg-6
ii klibc-utils 2.0.4-9
ii kmod 23-2
ii udev 232-25+deb9u4
Versions of packages initramfs-tools-core recommends:
ii busybox 1:1.22.0-19+b3
Versions of packages initramfs-tools-core suggests:
ii bash-completion 1:2.1-4.3
-- Configuration Files:
/etc/initramfs-tools/initramfs.conf changed:
MODULES=netboot
BUSYBOX=auto
KEYMAP=n
COMPRESS=xz
DEVICE=
NFSROOT=auto
BOOT=nfs
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/initramfs-tools/scripts/functions (from
initramfs-tools-core package)
Bug#905875: linux-image-amd64 outdated in jessie-backports
Package: linux-image-amd64 Version: 4.9+80+deb9u4~bpo8+1 Severity: normal Tags: security In Jessie Backports, linux-image-amd64 4.9+80+deb9u4~bpo8+1 depends on linux- image-4.9.0-0.bpo.6-amd64. A newer linux-image-amd64 should be backported to depend on linux- image-4.9.0-0.bpo.7-amd64 which currently has version 4.9.110-1~deb8u1. Thanks a lot!!! -- System Information: Debian Release: 8.11 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-0.bpo.6-amd64 (SMP w/4 CPU cores) Locale: LANG=es_UY.UTF-8, LC_CTYPE=es_UY.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-amd64 depends on: ii linux-image-4.9.0-0.bpo.6-amd64 4.9.88-1+deb9u1~bpo8+1 linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information
Re: Some Linux kernel config options
Hello. El 27/02/15 a las 00:21, Ben Hutchings escibió: CONFIG_PARAVIRT_SPINLOCKS The help text suggests it should be enabled - yet that's not the default! Unfortunately, enabling this will change the module ABI. This mismatch seems like a bug so I filled https://bugzilla.kernel.org/show_bug.cgi?id=94011 . I found a very good written article about this option (why is it needed, etc.) and benchmarks showing no impact on native performance: http://wiki.xen.org/wiki/Benchmarking_the_new_PV_ticketlock_implementation . And here shows big improvement when running one or two busy virtualized guests: https://lkml.org/lkml/2012/3/23/50 . Is it too late to enable it for Jessie? CONFIG_NFSD_V4_SECURITY_LABEL Help text says 'For now we recommend "Y" only for developers and testers.' Ouch! I looked in a different version of the kernel. Good thing in current kernels it is stable now. Thanks for your answer! Bye. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- 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/54f1ded9.8040...@adinet.com.uy
Some Linux kernel config options
Hello. I searched for the reasons for not using some Linux build configuration options but couldn't find them, maybe having a README.Debian and explaining some choices, etc. could be a good idea, I don't know. Here are some config options that I would like to know why are disabled: CONFIG_PARAVIRT_SPINLOCKS CONFIG_ZRAM_LZ4_COMPRESS CONFIG_DRM_QXL CONFIG_DRM_BOCHS CONFIG_FB_SAVAGE_I2C CONFIG_USB_UAS CONFIG_SQUASHFS_FILE_DIRECT CONFIG_SQUASHFS_DECOMP_MULTI CONFIG_NFSD_V4_SECURITY_LABEL Nothing special just curiosity. Thanks and have a great day! P.s.: I am not subscribed to the mailing list, please send a copy if you reply. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- 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/54efa36d.2070...@adinet.com.uy
Bug#600871: This bug could maybe be closed now?
Hello. This bug still applies? Maybe it could be closed now... Thanks. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- 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/517c1d92.6030...@adinet.com.uy
Bug#553634: README.Debian.nfsv4 needs update
Hello. The information from the README.Debian.nfsv4 file seems to be from 11 Oct 2006. The information regarding the server part should be based on whats actually in Wheeze, and information for clients should cover also Squeeze; everything else should be deleted because it is too old or not available in any currently maintained stable Debian version. I don't know if the problem of the original reporter currently applies. I am still using NFSv3 but considering a migration to NFSv4 but I don't know if it is stable for production use yet, it should be clarified in that file. Thanks for your help!!! Have a nice day. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- 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/517c1bd3.3020...@adinet.com.uy
Bug#705711: linux-image-2.6.32-5-686: AMD A6-3500 APU with Radeon HD 6530D not supported
Hello Ben. JFYI with apt-get install -t squeeze-backports linux-image-686 firmware-linux xorg libdrm2 libdrm-radeon1 libgl1-mesa-glx it worked although with the FBDEV driver; the Radeon driver loads first but doesn't say anything about not supporting it, it just unloads and then VESA refuses to load because it detects KMS, so then is the FBDEV turn that uses the FBDev API exposed by the KMS driver and it works. Is good enough for office work so I am ok. Maybe this info could help someone else with the same problem on Squeeze. If you know or have some tip to try to load the Radeon driver let me know, but it isn't too important for me at least. Thanks a lot! El 18/04/13 20:12, Ben Hutchings escribió: Control: tag -1 wontfix On Thu, Apr 18, 2013 at 07:09:03PM -0300, Ivan Baldo wrote: Package: linux-2.6 Version: 2.6.32-46 Severity: wishlist Tags: squeeze This is just to let you know. I don't know if a backport to support that driver is worthwhile or not, complex or trivial, etc... The VESA driver is unstable, sometimes X starts, sometimes not, when it starts it doesn't support the monitors native resolution. Thanks for your consideration! Happy hacking! Sorry, it won't be possible to add any new graphics hardware support to 'squeeze'. The kernel and X packages in squeeze-backports might support this hardware properly; otherwise try Debian 7.0 'wheezy' which will be released very shortly. Ben. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- 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/51713012.5020...@adinet.com.uy
Bug#705711: linux-image-2.6.32-5-686: AMD A6-3500 APU with Radeon HD 6530D not supported
Package: linux-2.6 Version: 2.6.32-46 Severity: wishlist Tags: squeeze This is just to let you know. I don't know if a backport to support that driver is worthwhile or not, complex or trivial, etc... The VESA driver is unstable, sometimes X starts, sometimes not, when it starts it doesn't support the monitors native resolution. Thanks for your consideration! Happy hacking! -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-46) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 09:49:36 UTC 2012 ** Command line: initrd=inteligentes/initrd.img fsprotect=50% nfsroot=/usr/local/terminales/inteligentes BOOT_IMAGE=inteligentes/vmlinuz ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [5.884366] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.887527] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.890714] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.895858] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.900191] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.903692] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.907855] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.912529] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.915711] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.919022] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.921823] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.925810] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.928731] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.932748] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.936422] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.940484] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.943392] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.947691] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.950899] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.956648] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.959580] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.963901] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.968694] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.972268] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.975335] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.978244] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.981024] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [5.984400] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [6.177528] usbcore: registered new interface driver usbserial [6.177586] USB Serial support registered for generic [6.177637] usbcore: registered new interface driver usbserial_generic [6.177686] usbserial: USB Serial Driver core [6.183778] USB Serial support registered for Handspring Visor / Palm OS [6.183836] USB Serial support registered for Sony Clie 3.5 [6.183979] USB Serial support registered for Sony Clie 5.0 [6.184098] usbcore: registered new interface driver visor [6.184135] visor: USB HandSpring Visor / Palm OS driver [7.641971] svc: failed to register lockdv1 RPC service (errno 97). [8.161350] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.163707] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.165977] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.168390] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.170707] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.173142] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.175449] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.178060] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.180347] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.182600] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.185019] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.187348] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.189682] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.191903] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8.194330] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback Volume) [8
Bug#517122: Maybe should be closed then.
Hello. Maybe this bug should be closed then, and reopened if the problem is found again. Maybe VNC was eating bandwidth or had some other misbehavior. HTH, bye! -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#494162: Maybe it is related to 517449!
Hello. I had this problem, I fixed it running fold...@home with nice 19 instead of SCHED_IDLE, the same should be possible for BOINC or other programs that stress the system. Maybe this is related (or the same) to bug #517449. Hope this helps. Thanks. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#498328: Maybe it is related to 517449!
Hello. I have this problem, I fixed it running fold...@home with nice 19 instead of SCHED_IDLE, the same should be possible for BOINC. Maybe this is related (or the same) to bug #517449. Hope this helps. Thanks. -- Ivan Baldo - iba...@adinet.com.uy - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: iba...@codigolibre.net - http://go.to/ibaldo -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#466942: use CONFIG_FAIR_CGROUP_SCHED instead of CONFIG_FAIR_GROUP_SCHED
Hello. Thanks for your answer! I got confused! I tried something like your example and yes, it works very well and as intended. Then after a more careful look I noticed that the kernel is using the CGROUPS infrastructure so what I said doesn't apply. Sorry for the noise. I have problems with bad interactivity of the system, it is not graphics specific, is not sound specific... If I have a couple of cpu intensive tasks running with nice 19, and then a couple running with nice 0, the system feels slow to react even on the console, and it doesn't happen with 2.6.24... I have compiled a kernel without CONFIG_FAIR_GROUP_SCHED, another without CONFIG_GROUP_SCHED and another with 1000HZ, CONFIG_SLUB, CONFIG_PREEMPT, CONFIG_PREEMPT_RCU and without CONFIG_CLASSIC_RCU, all this kernels had the same problem on my system (Athlon64x2 3Ghz DDR2-800 Dual Channel). If you have some suggestions on things to try I will appreciate it. Thanks! p.s.: BTW, this bug should be closed since the kernel doesn't use CONFIG_FAIR_USER_SCHED anymore. El 07/09/08 17:11, Bastian Blank escribió: On Sun, Sep 07, 2008 at 03:20:56PM -0300, Ivan Baldo wrote: The CGROUP infrastructure is the only way to allow runtime configuration on how the scheduler should work, so some simple DebConf questions could setup the system as the user wants it (even distribution between users, even distribution between groups, even distribution for all the processes without considering groups or users), and even after that, a user or sysadmin could further configure it. Which configuration option is removed due to the group scheduler? I fail to find any. Currently, the FAIR_GROUP_SCHED option is the worst choice, because of 2 things: 1 - it forces one behaviour and there is no other way but recompile the kernel to change it. No. It only extends the scheduler decision with another information. 2 - it changes a default behaviour used for many years! you may run a program with nice 19 and SCHED_IDLEPRIO and still consume a lot of CPU time and starve other processes. Users and sysadmins are used to the nice command to control priorities of processes without thinking about groupings by group or user id. Please show that behaviour. By default a system have only one group and within the group the default nice behaviour is used. Between groups the cpu is uniformly distributed. Proove: | $ ps ux | grep test | USER 15850 86.1 0.0 1740 336 pts/6RN 22:05 0:12 ./test-nice-10 | USER 15851 11.3 0.0 1740 336 pts/6RN 22:05 0:01 ./test-nice-19 | $ uname -a | Linux HOST 2.6.26-1-powerpc64 #1 SMP Mon Aug 25 00:33:17 UTC 2008 ppc64 GNU/Linux Both processes runs in a cgroup which is restricted to one cpu. Bastian -- Ivan Baldo - [EMAIL PROTECTED] - http://ibaldo.codigolibre.net/ From Montevideo, Uruguay, at the south of South America. Freelance programmer and GNU/Linux system administrator, hire me! Alternatives: [EMAIL PROTECTED] - http://go.to/ibaldo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#466942: use CONFIG_FAIR_CGROUP_SCHED instead of CONFIG_FAIR_GROUP_SCHED
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Followup-For: Bug #466942 The CGROUP infrastructure is the only way to allow runtime configuration on how the scheduler should work, so some simple DebConf questions could setup the system as the user wants it (even distribution between users, even distribution between groups, even distribution for all the processes without considering groups or users), and even after that, a user or sysadmin could further configure it. Currently, the FAIR_GROUP_SCHED option is the worst choice, because of 2 things: 1 - it forces one behaviour and there is no other way but recompile the kernel to change it. 2 - it changes a default behaviour used for many years! you may run a program with nice 19 and SCHED_IDLEPRIO and still consume a lot of CPU time and starve other processes. Users and sysadmins are used to the nice command to control priorities of processes without thinking about groupings by group or user id. With FAIR_CGROUP_SCHED and no configuration it runs as before, with the behaviour that everyone got used in all this years, yet allowing to set it to any other behaviour needed. I hope the kernel maintainers change their mind and switch this option, I would not like to recompile the kernel in all the computers I maintain... Thanks for your consideration. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 11:13:42 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-amd64 root=UUID=c662531d-951e-4c01-a372-3212249feb65 ro ** Tainted: P (1) ** Kernel log: [1.835922] sata_nv :00:08.0: version 3.5 [1.835922] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 20 [1.835922] ACPI: PCI Interrupt :00:08.0[A] -> Link [LSA0] -> GSI 20 (level, low) -> IRQ 20 [1.835922] PCI: Setting latency timer of device :00:08.0 to 64 [1.835922] scsi0 : sata_nv [1.835922] scsi1 : sata_nv [1.835922] ata1: SATA max UDMA/133 cmd 0xd400 ctl 0xd080 bmdma 0xc880 irq 20 [1.835922] ata2: SATA max UDMA/133 cmd 0xd000 ctl 0xcc00 bmdma 0xc888 irq 20 [2.308035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.319852] ata1.00: ATA-7: SAMSUNG HD160JJ, ZM100-47, max UDMA7 [2.319852] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) [2.363895] ata1.00: configured for UDMA/133 [2.690238] ata2: SATA link down (SStatus 0 SControl 300) [2.691836] isa bounce pool size: 16 pages [2.691836] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD160JJ ZM10 PQ: 0 ANSI: 5 [2.691836] ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 23 [2.691836] ACPI: PCI Interrupt :00:08.1[B] -> Link [LSA1] -> GSI 23 (level, low) -> IRQ 23 [2.691836] PCI: Setting latency timer of device :00:08.1 to 64 [2.691836] scsi2 : sata_nv [2.691836] scsi3 : sata_nv [2.695841] ata3: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc000 irq 23 [2.695841] ata4: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xc008 irq 23 [3.038155] ata3: SATA link down (SStatus 0 SControl 300) [3.378239] ata4: SATA link down (SStatus 0 SControl 300) [3.383847] Uniform Multi-Platform E-IDE driver [3.383886] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [3.384516] NFORCE-MCP61: :00:06.0 (rev a2) UDMA133 controller [3.384555] NFORCE-MCP61: IDE controller (0x10de:0x03ec rev 0xa2) at PCI slot :00:06.0 [3.384619] NFORCE-MCP61: not 100% native mode: will probe irqs later [3.389929] NFORCE-MCP61: BIOS didn't set cable bits correctly. Enabling workaround. [3.389976] NFORCE-MCP61: IDE port disabled [3.390011] ide0: BM-DMA at 0xffa0-0xffa7 [3.390045] Probing IDE interface ide0... [4.122240] hda: SONY DVD RW DRU-830A, ATAPI CD/DVD-ROM drive [4.794216] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [4.794542] hda: drive side 80-wire cable detection failed, limiting max speed to UDMA33 [4.794588] hda: UDMA/33 mode selected [4.794983] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [4.809828] Driver 'sd' needs updating - please use bus_type methods [4.809942] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.809987] sd 0:0:0:0: [sda] Write Protect is off [4.810021] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810031] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.810031] sd 0:0:0:0: [sda] Write Protect is off [4.810031] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810087] sda: sda1 sda2 sda3 <<6>hda: ATAPI 40X DVD-ROM DVD-R-RAM CD-R
Bug#494162: I guess this is related to 466942
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Followup-For: Bug #494162 It happens to me too, and to many others. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466942 - "use CONFIG_FAIR_CGROUP_SCHED instead of CONFIG_FAIR_USER_SCHED", though the kernel now is using CONFIG_FAIR_GROUP_SCHED but it causes the same bad effects. The CGROUP infrastructure is the only way to allow runtime configuration on how the scheduler should work, so some simple DebConf questions could setup the system as the user wants it (even distribution between users, even distribution between groups, even distribution for all the processes without considering groups or users), and even after that, a user or sysadmin could further configure it. Currently, the FAIR_GROUP_SCHED option is the worst choice, because of 2 things: 1 - it forces one behaviour and there is no other way but recompile the kernel to change it. 2 - it changes a default behaviour used for many years! you may run a program with nice 19 and SCHED_IDLEPRIO and still consume a lot of CPU time and starve other processes. Users and sysadmins are used to the nice command to control priorities of processes without thinking about groupings by group or user id. With FAIR_CGROUP_SCHED and no configuration it runs as before, with the behaviour that everyone got used in all this years, yet allowing to set it to any other behaviour needed. I hope the kernel maintainers change their mind and switch this option, I would not like to recompile the kernel in all the computers I maintain... Thanks for your consideration. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 11:13:42 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-amd64 root=UUID=c662531d-951e-4c01-a372-3212249feb65 ro ** Tainted: P (1) ** Kernel log: [1.835922] sata_nv :00:08.0: version 3.5 [1.835922] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 20 [1.835922] ACPI: PCI Interrupt :00:08.0[A] -> Link [LSA0] -> GSI 20 (level, low) -> IRQ 20 [1.835922] PCI: Setting latency timer of device :00:08.0 to 64 [1.835922] scsi0 : sata_nv [1.835922] scsi1 : sata_nv [1.835922] ata1: SATA max UDMA/133 cmd 0xd400 ctl 0xd080 bmdma 0xc880 irq 20 [1.835922] ata2: SATA max UDMA/133 cmd 0xd000 ctl 0xcc00 bmdma 0xc888 irq 20 [2.308035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.319852] ata1.00: ATA-7: SAMSUNG HD160JJ, ZM100-47, max UDMA7 [2.319852] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) [2.363895] ata1.00: configured for UDMA/133 [2.690238] ata2: SATA link down (SStatus 0 SControl 300) [2.691836] isa bounce pool size: 16 pages [2.691836] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD160JJ ZM10 PQ: 0 ANSI: 5 [2.691836] ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 23 [2.691836] ACPI: PCI Interrupt :00:08.1[B] -> Link [LSA1] -> GSI 23 (level, low) -> IRQ 23 [2.691836] PCI: Setting latency timer of device :00:08.1 to 64 [2.691836] scsi2 : sata_nv [2.691836] scsi3 : sata_nv [2.695841] ata3: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc000 irq 23 [2.695841] ata4: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xc008 irq 23 [3.038155] ata3: SATA link down (SStatus 0 SControl 300) [3.378239] ata4: SATA link down (SStatus 0 SControl 300) [3.383847] Uniform Multi-Platform E-IDE driver [3.383886] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [3.384516] NFORCE-MCP61: :00:06.0 (rev a2) UDMA133 controller [3.384555] NFORCE-MCP61: IDE controller (0x10de:0x03ec rev 0xa2) at PCI slot :00:06.0 [3.384619] NFORCE-MCP61: not 100% native mode: will probe irqs later [3.389929] NFORCE-MCP61: BIOS didn't set cable bits correctly. Enabling workaround. [3.389976] NFORCE-MCP61: IDE port disabled [3.390011] ide0: BM-DMA at 0xffa0-0xffa7 [3.390045] Probing IDE interface ide0... [4.122240] hda: SONY DVD RW DRU-830A, ATAPI CD/DVD-ROM drive [4.794216] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [4.794542] hda: drive side 80-wire cable detection failed, limiting max speed to UDMA33 [4.794588] hda: UDMA/33 mode selected [4.794983] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [4.809828] Driver 'sd' needs updating - please use bus_type methods [4.809942] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.809987] sd 0:0:0:0: [sda] Write Protect is off [4.810021] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810031] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.810031] sd 0:0:0:0
Bug#497755: FWIW, I second that!
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Followup-For: Bug #497755 See also bug "#496871 - please change the PREEMPT settings". The requirements for servers and desktops are different. Thanks for considering this! -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 11:13:42 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-amd64 root=UUID=c662531d-951e-4c01-a372-3212249feb65 ro ** Tainted: P (1) ** Kernel log: [1.307989] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61. [1.307989] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21 [1.307989] ACPI: PCI Interrupt :00:07.0[A] -> Link [LMAC] -> GSI 21 (level, low) -> IRQ 21 [1.307989] PCI: Setting latency timer of device :00:07.0 to 64 [1.835922] forcedeth :00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:66:73:08:b8 [1.835922] forcedeth :00:07.0: highdma pwrctl mgmt timirq lnktim msi desc-v3 [1.835922] sata_nv :00:08.0: version 3.5 [1.835922] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 20 [1.835922] ACPI: PCI Interrupt :00:08.0[A] -> Link [LSA0] -> GSI 20 (level, low) -> IRQ 20 [1.835922] PCI: Setting latency timer of device :00:08.0 to 64 [1.835922] scsi0 : sata_nv [1.835922] scsi1 : sata_nv [1.835922] ata1: SATA max UDMA/133 cmd 0xd400 ctl 0xd080 bmdma 0xc880 irq 20 [1.835922] ata2: SATA max UDMA/133 cmd 0xd000 ctl 0xcc00 bmdma 0xc888 irq 20 [2.308035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.319852] ata1.00: ATA-7: SAMSUNG HD160JJ, ZM100-47, max UDMA7 [2.319852] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) [2.363895] ata1.00: configured for UDMA/133 [2.690238] ata2: SATA link down (SStatus 0 SControl 300) [2.691836] isa bounce pool size: 16 pages [2.691836] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD160JJ ZM10 PQ: 0 ANSI: 5 [2.691836] ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 23 [2.691836] ACPI: PCI Interrupt :00:08.1[B] -> Link [LSA1] -> GSI 23 (level, low) -> IRQ 23 [2.691836] PCI: Setting latency timer of device :00:08.1 to 64 [2.691836] scsi2 : sata_nv [2.691836] scsi3 : sata_nv [2.695841] ata3: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc000 irq 23 [2.695841] ata4: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xc008 irq 23 [3.038155] ata3: SATA link down (SStatus 0 SControl 300) [3.378239] ata4: SATA link down (SStatus 0 SControl 300) [3.383847] Uniform Multi-Platform E-IDE driver [3.383886] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [3.384516] NFORCE-MCP61: :00:06.0 (rev a2) UDMA133 controller [3.384555] NFORCE-MCP61: IDE controller (0x10de:0x03ec rev 0xa2) at PCI slot :00:06.0 [3.384619] NFORCE-MCP61: not 100% native mode: will probe irqs later [3.389929] NFORCE-MCP61: BIOS didn't set cable bits correctly. Enabling workaround. [3.389976] NFORCE-MCP61: IDE port disabled [3.390011] ide0: BM-DMA at 0xffa0-0xffa7 [3.390045] Probing IDE interface ide0... [4.122240] hda: SONY DVD RW DRU-830A, ATAPI CD/DVD-ROM drive [4.794216] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [4.794542] hda: drive side 80-wire cable detection failed, limiting max speed to UDMA33 [4.794588] hda: UDMA/33 mode selected [4.794983] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [4.809828] Driver 'sd' needs updating - please use bus_type methods [4.809942] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.809987] sd 0:0:0:0: [sda] Write Protect is off [4.810021] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810031] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.810031] sd 0:0:0:0: [sda] Write Protect is off [4.810031] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810087] sda: sda1 sda2 sda3 <<6>hda: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache [4.826125] Uniform CD-ROM driver Revision: 3.20 [4.826125] sda5 sda6 sda7 sda8 > [4.858042] sd 0:0:0:0: [sda] Attached SCSI disk [5.186119] PM: Starting manual resume from disk [5.192007] ReiserFS: sda8: found reiserfs format "3.6" with standard journal [5.192052] ReiserFS: sda8: using ordered data mode [5.198127] ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [5.198127] ReiserFS: sda8: checking transaction log (sda8) [5.230248] ReiserFS: sda8: Using r5 hash to sort names [6.544272] udevd version 125 s
Bug#496871: I guess they are disabled for server performance reasons...
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Followup-For: Bug #496871 I guess the preemption settings are disabled for slowing down servers, it would be more apropriate to implement what is said on bug "#497755 - Separate desktop and server kernels". Would be nice to have something like that... Thanks!!! P.s.: maybe this bug should be merged with 497755. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 11:13:42 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-amd64 root=UUID=c662531d-951e-4c01-a372-3212249feb65 ro ** Tainted: P (1) ** Kernel log: [1.307989] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61. [1.307989] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21 [1.307989] ACPI: PCI Interrupt :00:07.0[A] -> Link [LMAC] -> GSI 21 (level, low) -> IRQ 21 [1.307989] PCI: Setting latency timer of device :00:07.0 to 64 [1.835922] forcedeth :00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:66:73:08:b8 [1.835922] forcedeth :00:07.0: highdma pwrctl mgmt timirq lnktim msi desc-v3 [1.835922] sata_nv :00:08.0: version 3.5 [1.835922] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 20 [1.835922] ACPI: PCI Interrupt :00:08.0[A] -> Link [LSA0] -> GSI 20 (level, low) -> IRQ 20 [1.835922] PCI: Setting latency timer of device :00:08.0 to 64 [1.835922] scsi0 : sata_nv [1.835922] scsi1 : sata_nv [1.835922] ata1: SATA max UDMA/133 cmd 0xd400 ctl 0xd080 bmdma 0xc880 irq 20 [1.835922] ata2: SATA max UDMA/133 cmd 0xd000 ctl 0xcc00 bmdma 0xc888 irq 20 [2.308035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.319852] ata1.00: ATA-7: SAMSUNG HD160JJ, ZM100-47, max UDMA7 [2.319852] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) [2.363895] ata1.00: configured for UDMA/133 [2.690238] ata2: SATA link down (SStatus 0 SControl 300) [2.691836] isa bounce pool size: 16 pages [2.691836] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD160JJ ZM10 PQ: 0 ANSI: 5 [2.691836] ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 23 [2.691836] ACPI: PCI Interrupt :00:08.1[B] -> Link [LSA1] -> GSI 23 (level, low) -> IRQ 23 [2.691836] PCI: Setting latency timer of device :00:08.1 to 64 [2.691836] scsi2 : sata_nv [2.691836] scsi3 : sata_nv [2.695841] ata3: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc000 irq 23 [2.695841] ata4: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xc008 irq 23 [3.038155] ata3: SATA link down (SStatus 0 SControl 300) [3.378239] ata4: SATA link down (SStatus 0 SControl 300) [3.383847] Uniform Multi-Platform E-IDE driver [3.383886] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [3.384516] NFORCE-MCP61: :00:06.0 (rev a2) UDMA133 controller [3.384555] NFORCE-MCP61: IDE controller (0x10de:0x03ec rev 0xa2) at PCI slot :00:06.0 [3.384619] NFORCE-MCP61: not 100% native mode: will probe irqs later [3.389929] NFORCE-MCP61: BIOS didn't set cable bits correctly. Enabling workaround. [3.389976] NFORCE-MCP61: IDE port disabled [3.390011] ide0: BM-DMA at 0xffa0-0xffa7 [3.390045] Probing IDE interface ide0... [4.122240] hda: SONY DVD RW DRU-830A, ATAPI CD/DVD-ROM drive [4.794216] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [4.794542] hda: drive side 80-wire cable detection failed, limiting max speed to UDMA33 [4.794588] hda: UDMA/33 mode selected [4.794983] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [4.809828] Driver 'sd' needs updating - please use bus_type methods [4.809942] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.809987] sd 0:0:0:0: [sda] Write Protect is off [4.810021] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810031] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.810031] sd 0:0:0:0: [sda] Write Protect is off [4.810031] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810087] sda: sda1 sda2 sda3 <<6>hda: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache [4.826125] Uniform CD-ROM driver Revision: 3.20 [4.826125] sda5 sda6 sda7 sda8 > [4.858042] sd 0:0:0:0: [sda] Attached SCSI disk [5.186119] PM: Starting manual resume from disk [5.192007] ReiserFS: sda8: found reiserfs format "3.6" with standard journal [5.192052] ReiserFS: sda8: using ordered data mode [5.198127] ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [5.198127] R
Bug#463295: Should mention why it is compiled with gcc 4.1 instead of 4.3.
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Followup-For: Bug #463295 There is no README.Debian in this package! There should be one and explain there some things, like why it is compiled with gcc 4.1 instead of 4.3 (yes, I guess there should be a good reason, I trust you, but would like to know anyway...). Thanks. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 11:13:42 UTC 2008 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.26-1-amd64 root=UUID=c662531d-951e-4c01-a372-3212249feb65 ro ** Tainted: P (1) ** Kernel log: [1.307989] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61. [1.307989] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21 [1.307989] ACPI: PCI Interrupt :00:07.0[A] -> Link [LMAC] -> GSI 21 (level, low) -> IRQ 21 [1.307989] PCI: Setting latency timer of device :00:07.0 to 64 [1.835922] forcedeth :00:07.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:19:66:73:08:b8 [1.835922] forcedeth :00:07.0: highdma pwrctl mgmt timirq lnktim msi desc-v3 [1.835922] sata_nv :00:08.0: version 3.5 [1.835922] ACPI: PCI Interrupt Link [LSA0] enabled at IRQ 20 [1.835922] ACPI: PCI Interrupt :00:08.0[A] -> Link [LSA0] -> GSI 20 (level, low) -> IRQ 20 [1.835922] PCI: Setting latency timer of device :00:08.0 to 64 [1.835922] scsi0 : sata_nv [1.835922] scsi1 : sata_nv [1.835922] ata1: SATA max UDMA/133 cmd 0xd400 ctl 0xd080 bmdma 0xc880 irq 20 [1.835922] ata2: SATA max UDMA/133 cmd 0xd000 ctl 0xcc00 bmdma 0xc888 irq 20 [2.308035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [2.319852] ata1.00: ATA-7: SAMSUNG HD160JJ, ZM100-47, max UDMA7 [2.319852] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) [2.363895] ata1.00: configured for UDMA/133 [2.690238] ata2: SATA link down (SStatus 0 SControl 300) [2.691836] isa bounce pool size: 16 pages [2.691836] scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD160JJ ZM10 PQ: 0 ANSI: 5 [2.691836] ACPI: PCI Interrupt Link [LSA1] enabled at IRQ 23 [2.691836] ACPI: PCI Interrupt :00:08.1[B] -> Link [LSA1] -> GSI 23 (level, low) -> IRQ 23 [2.691836] PCI: Setting latency timer of device :00:08.1 to 64 [2.691836] scsi2 : sata_nv [2.691836] scsi3 : sata_nv [2.695841] ata3: SATA max UDMA/133 cmd 0xc800 ctl 0xc480 bmdma 0xc000 irq 23 [2.695841] ata4: SATA max UDMA/133 cmd 0xc400 ctl 0xc080 bmdma 0xc008 irq 23 [3.038155] ata3: SATA link down (SStatus 0 SControl 300) [3.378239] ata4: SATA link down (SStatus 0 SControl 300) [3.383847] Uniform Multi-Platform E-IDE driver [3.383886] ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx [3.384516] NFORCE-MCP61: :00:06.0 (rev a2) UDMA133 controller [3.384555] NFORCE-MCP61: IDE controller (0x10de:0x03ec rev 0xa2) at PCI slot :00:06.0 [3.384619] NFORCE-MCP61: not 100% native mode: will probe irqs later [3.389929] NFORCE-MCP61: BIOS didn't set cable bits correctly. Enabling workaround. [3.389976] NFORCE-MCP61: IDE port disabled [3.390011] ide0: BM-DMA at 0xffa0-0xffa7 [3.390045] Probing IDE interface ide0... [4.122240] hda: SONY DVD RW DRU-830A, ATAPI CD/DVD-ROM drive [4.794216] hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4 [4.794542] hda: drive side 80-wire cable detection failed, limiting max speed to UDMA33 [4.794588] hda: UDMA/33 mode selected [4.794983] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [4.809828] Driver 'sd' needs updating - please use bus_type methods [4.809942] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.809987] sd 0:0:0:0: [sda] Write Protect is off [4.810021] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810031] sd 0:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB) [4.810031] sd 0:0:0:0: [sda] Write Protect is off [4.810031] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [4.810031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [4.810087] sda: sda1 sda2 sda3 <<6>hda: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache [4.826125] Uniform CD-ROM driver Revision: 3.20 [4.826125] sda5 sda6 sda7 sda8 > [4.858042] sd 0:0:0:0: [sda] Attached SCSI disk [5.186119] PM: Starting manual resume from disk [5.192007] ReiserFS: sda8: found reiserfs format "3.6" with standard journal [5.192052] ReiserFS: sda8: using ordered data mode [5.198127] ReiserFS: sda8: journal params: device sda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [5.198127] ReiserFS: sda8: checking transaction log (sda
