Re: Dropping 686 non-pae kernel
On Sun, Mar 13, 2011 at 03:57:56AM +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:34 +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:23 +0100, Bastian Blank wrote: [...] There are several possibilities to do this: * Change name of meta-package: - Breaks nothing - Needs manual intervention by anyone using it * Don't change the name: - Breaks some systems - No manual intervention by the rest I'm wavering on this. I don't like the idea of simply renaming '686-bigmem' to '686', given there are a fair number of 686-class systems without PAE, and I don't think users with a Pentium M are going to expect that '486' is the right choice. Please read again what I wrote. The distinctions between these two flavours will be: 1. One processor (min 486) with 386 page tables (currently '486') 2. One or more processors with PAE page tables (currently '686-bigmem') Will not hold forever and you need to integrate the other architectures into it. How about naming them 'up' and 'smp-pae'? It'll be a pain to transition the metapackages, but then we should never have to go through this again when raising the minimum processor requirement. No, this will not help. See above. Bastian -- There are certain things men must do to remain men. -- Kirk, The Ultimate Computer, stardate 4929.4 -- 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/20110313081831.gb19...@wavehammer.waldi.eu.org
Bug#605083: linux-2.6: MacBookAir3,* support: USB fixes
Ben Hutchings b...@decadent.org.uk wrote: Hi Ben, USB: ehci: disable LPM and PPCD for nVidia MCP89 chips I'll look at backporting this to squeeze as well. It appears that it is not needed in squeeze because these features were not used by the ehci driver in 2.6.32. Thanks for tracking this. There are HID patches for the new MacBook Pro, I'll file a wishlist for that later. JB. -- Julien BLACHE jbla...@debian.org | Debian, because code matters more Debian GNU/Linux Developer| http://www.debian.org Public key available on http://www.jblache.org - KeyID: F5D6 5169 GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169 -- 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/87vczn1jp6@sonic.technologeek.org
Re: Dropping 686 non-pae kernel
On Sun, Mar 13, 2011 at 09:18:31AM +0100, Bastian Blank wrote: On Sun, Mar 13, 2011 at 03:57:56AM +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:34 +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:23 +0100, Bastian Blank wrote: [...] There are several possibilities to do this: * Change name of meta-package: - Breaks nothing - Needs manual intervention by anyone using it * Don't change the name: - Breaks some systems - No manual intervention by the rest I'm wavering on this. I don't like the idea of simply renaming '686-bigmem' to '686', given there are a fair number of 686-class systems without PAE, and I don't think users with a Pentium M are going to expect that '486' is the right choice. Please read again what I wrote. Please provide 'where' and 'when'. The distinctions between these two flavours will be: 1. One processor (min 486) with 386 page tables (currently '486') 2. One or more processors with PAE page tables (currently '686-bigmem') Will not hold forever and you need to integrate the other architectures into it. How about naming them 'up' and 'smp-pae'? It'll be a pain to transition the metapackages, but then we should never have to go through this again when raising the minimum processor requirement. No, this will not help. See above. Bastian -- There are certain things men must do to remain men. -- Kirk, The Ultimate Computer, stardate 4929.4 A good thing to remain human, is willing to communicate with humans. Take time to explain why something is a good thing. Take even more time to explain why something is a bad thing. If the other side doesn't get the message, both sides should allow each other the freedom to do their thing. Groeten Geert Stappers -- And is there a policy on top-posting vs. bottom-posting? Yes. signature.asc Description: Digital signature
Bug#618006: Input support for MacBookPro8,*
Source: linux-2.6
Version: 2.6.32-30
Severity: wishlist
Tags: patch
Hi,
The attached commit, taken from Dmitry Torokhov's input tree, adds
input support for the MacBookPro8,* released in March 2011.
Ideally the patch should be applied to both 2.6.32 in Squeeze and
2.6.37/2.6.38 in Sid. It may need some backporting work for 2.6.32 for
the trackpad part, not sure about that, shouldn't be anything major,
though.
Thanks,
JB.
--
Julien BLACHE jbla...@debian.org | Debian, because code matters more
Debian GNU/Linux Developer| http://www.debian.org
Public key available on http://www.jblache.org - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
From 47340bd9fefb57136da942b5aee0e85e959c Mon Sep 17 00:00:00 2001
From: Andy Botting a...@andybotting.com
Date: Sat, 12 Mar 2011 20:27:22 -0800
Subject: [PATCH] Input: bcm5974 - add support for MacBookPro8
This patch add multitouch support for the MacBookPro8,1 and
MacBookPro8,2 models.
Cc: sta...@kernel.org
Signed-off-by: Andy Botting a...@andybotting.com
Signed-off-by: Henrik Rydberg rydb...@euromail.se
Acked-by: Jiri Kosina jkos...@suse.cz
Signed-off-by: Dmitry Torokhov d...@mail.ru
---
drivers/hid/hid-apple.c |6 ++
drivers/hid/hid-core.c|6 ++
drivers/hid/hid-ids.h |3 +++
drivers/input/mouse/bcm5974.c | 20
4 files changed, 35 insertions(+), 0 deletions(-)
diff --git a/drivers/hid/hid-apple.c b/drivers/hid/hid-apple.c
index 61aa712..b85744f 100644
--- a/drivers/hid/hid-apple.c
+++ b/drivers/hid/hid-apple.c
@@ -481,6 +481,12 @@ static const struct hid_device_id apple_devices[] = {
.driver_data = APPLE_HAS_FN | APPLE_ISO_KEYBOARD },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING4A_JIS),
.driver_data = APPLE_HAS_FN | APPLE_RDESC_JIS },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_ANSI),
+ .driver_data = APPLE_HAS_FN },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_ISO),
+ .driver_data = APPLE_HAS_FN | APPLE_ISO_KEYBOARD },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_JIS),
+ .driver_data = APPLE_HAS_FN | APPLE_RDESC_JIS },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ANSI),
.driver_data = APPLE_NUMLOCK_EMULATION | APPLE_HAS_FN },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ISO),
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index d678cf3..48a0a2f 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1302,6 +1302,9 @@ static const struct hid_device_id hid_have_special_driver[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING4A_ANSI) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING4A_ISO) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING4A_JIS) },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_ANSI) },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_ISO) },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_JIS) },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ANSI) },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ISO) },
{ HID_BLUETOOTH_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_JIS) },
@@ -1801,6 +1804,9 @@ static const struct hid_device_id hid_mouse_ignore_list[] = {
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING4A_ANSI) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING4A_ISO) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING4A_JIS) },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_ANSI) },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_ISO) },
+ { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_WELLSPRING5_JIS) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_FOUNTAIN_TP_ONLY) },
{ HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_GEYSER1_TP_ONLY) },
{ }
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index 92a0d61..ca32ecb 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -103,6 +103,9 @@
#define USB_DEVICE_ID_APPLE_WELLSPRING4A_ANSI 0x0242
#define USB_DEVICE_ID_APPLE_WELLSPRING4A_ISO 0x0243
#define USB_DEVICE_ID_APPLE_WELLSPRING4A_JIS 0x0244
+#define USB_DEVICE_ID_APPLE_WELLSPRING5_ANSI 0x0245
+#define USB_DEVICE_ID_APPLE_WELLSPRING5_ISO 0x0246
+#define USB_DEVICE_ID_APPLE_WELLSPRING5_JIS 0x0247
#define USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ANSI 0x0239
#define USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_ISO 0x023a
#define USB_DEVICE_ID_APPLE_ALU_WIRELESS_2009_JIS 0x023b
diff --git a/drivers/input/mouse/bcm5974.c b/drivers/input/mouse/bcm5974.c
index ee82851..3185314 100644
---
Bug#617866: uvesafb: cannot reserve video memory at 0xf0000000 and error -5
Hi! On Sat, Mar 12, 2011 at 10:08:54AM +0100, Julien Cristau wrote: On Sat, Mar 12, 2011 at 00:47:00 +0100, Gernot Kieseritzky wrote: I tried to load uvesafb in order to get frame buffer support for the native 1024x600 resolution of my JVC MP-XP731 laptop. So I added You should get that from the i915 kernel mode setting driver, not uvesafb. Okay, I'll try to activate KMS, which was off by default after base install of debian/squeeze. I guess, it only gets activated by the installer selecting tasksel desktop. Thanks, Gernot -- 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/20110312220830.GA20482@mininote
Bug#465161: marked as done (Reintroduce Maestro firmware)
Your message dated Sun, 13 Mar 2011 16:21:30 + with message-id 1300033290.4146.196.camel@localhost and subject line Re: Sound broken with linux-image-2.6.24-1-686 has caused the Debian Bug report #464191, regarding Reintroduce Maestro firmware to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 464191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: alsa-base Version: 1.0.15-4 Severity: normal This should be a followup to bug#458010, but it has already been closed and archived: The ALSA drivers are part of the kernel. Your kernel (2.6.23) provides version 1.0.14. What we are doing is to serve the actual ALSA drivers in the package aksa-source. Release candidates you can find in experimental (this belongs to the whimsy of the maintainer ;)) 2.6.24 will provide 1.0.15, while I suspect to have the next RC's at that time... I can't and won't verify why the 2.6.23 Debian Kernel binary doesn't work with your card. When using debian's 2.6.24 source, or using debians 2.6.24 compiled package, I still don't have a working maestro3 soundcard. 2.6.24 comes with alsa 1.0.15: Feb 11 00:25:37 scuzzie kernel: Maestro3: probe of :00:08.0 failed with error -2 On the other hand, 2.6.22-3-686 comes with version 1.0.14, and it does detect and work: cat /proc/asound/version Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). cat /proc/asound/cards 0 [PCI]: Maestro3 - ESS Maestro3 PCI ESS Maestro3 PCI at 0xd800, irq 5 -- Package-specific info: --- Begin additional package status --- Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== ii libasound2 1.0.15-3ALSA library --- End additional package status --- --- Begin /proc/asound/version --- Advanced Linux Sound Architecture Driver Version 1.0.14 (Thu May 31 09:03:25 2007 UTC). --- End /proc/asound/version --- --- Begin /proc/asound/cards --- 0 [PCI]: Maestro3 - ESS Maestro3 PCI ESS Maestro3 PCI at 0xd800, irq 5 --- End /proc/asound/cards --- --- Begin /dev/snd/ listing --- total 0 crw-rw 1 root audio 116, 0 Feb 11 00:27 controlC0 crw-rw 1 root audio 116, 24 Feb 11 00:27 pcmC0D0c crw-rw 1 root audio 116, 16 Feb 11 00:27 pcmC0D0p crw-rw 1 root audio 116, 33 Feb 11 00:27 timer --- End /dev/snd/ listing --- -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages alsa-base depends on: ii linux-sound-base 1.0.15-4 base package for ALSA and OSS soun ii lsof 4.78.dfsg.1-4 List open files ii module-init-tools 3.3-pre11-4 tools for managing Linux kernel mo Versions of packages alsa-base recommends: ii alsa-utils1.0.15-2 ALSA utilities Versions of packages libasound2 depends on: ii libc6 2.7-6 GNU C Library: Shared libraries -- no debconf information ---End Message--- ---BeginMessage--- On Tue, 2008-02-05 at 13:02 -0500, Rob Bochan wrote: Package: linux-image-2.6.24-1-686 Version: 2.6.24-2 Severity: normal With the upgrade to linux-image-2.6.24-1-686, sound no onger works on this machine. Strting KDE gives me the artsmessage Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or directory) It does work properly with the previous kernels, including 2.6.22-3-686. lspci lists: '$ lspci |grep audio 00:0d.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator' [...] As explained previously, we removed the firmware for this device because the licence does not allow us to distribute it. It is labelled as licenced under the GPLv2, but since no source code is provided we cannot fulfil the terms of that licence. Closing the bug, as it cannot be fixed. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is
Bug#464191: marked as done (Reintroduce Maestro firmware)
Your message dated Sun, 13 Mar 2011 16:21:30 + with message-id 1300033290.4146.196.camel@localhost and subject line Re: Sound broken with linux-image-2.6.24-1-686 has caused the Debian Bug report #464191, regarding Reintroduce Maestro firmware to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 464191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=464191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-2 Severity: normal With the upgrade to linux-image-2.6.24-1-686, sound no onger works on this machine. Strting KDE gives me the artsmessage Error while initializing the sound driver: device /dev/dsp can't be opened (No such file or directory) It does work properly with the previous kernels, including 2.6.22-3-686. lspci lists: '$ lspci |grep audio 00:0d.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio Accelerator' -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-2) (wa...@debian.org) (gcc version 4.1.3 20080114 (prerelease) (Debian 4.1.2-19)) #1 SMP Thu Jan 31 20:35:50 UTC 2008 ** Command line: root=/dev/hda2 ro vga=792 ** Not tainted ** Kernel log: ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10 ACPI: PCI Interrupt :00:07.2[D] - Link [LNKD] - GSI 10 (level, low) - IRQ 10 uhci_hcd :00:07.2: UHCI Host Controller uhci_hcd :00:07.2: new USB bus registered, assigned bus number 1 uhci_hcd :00:07.2: irq 10, io base 0x1880 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected PIIX4: IDE controller (0x8086:0x7111 rev 0x01) at PCI slot :00:07.1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x18a0-0x18a7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x18a8-0x18af, BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... usb 1-1: new low speed USB device using uhci_hcd and address 2 usb 1-1: configuration #1 chosen from 1 choice hda: IBM-DARA-218000, ATA DISK drive hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hda: UDMA/33 mode selected ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... SCSI subsystem initialized libata version 3.00 loaded. hda: max request size: 128KiB hda: 35433216 sectors (18141 MB) w/418KiB Cache, CHS=35152/16/63 hda: cache flushes not supported hda: hda1 hda2 hda3 usbcore: registered new interface driver hiddev input: Kensington Kensington USB/PS2 Wheel Mouse as /class/input/input1 input,hidraw0: USB HID v1.10 Mouse [Kensington Kensington USB/PS2 Wheel Mouse] on usb-:00:07.2-1 usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Attempting manual resume kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. input: PC Speaker as /class/input/input2 Real Time Clock Driver v1.12ac parport_pc 00:0a: reported by Plug and Play ACPI parport0: PC-style at 0x378 (0x778), irq 7, dma 3 [PCSPP,TRISTATE,COMPAT,ECP,DMA] Linux agpgart interface v0.102 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Yenta: CardBus bridge found at :00:0a.0 [103c:0010] Yenta: Enabling burst memory read transactions Yenta: Using INTVAL to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket :00:0a.0, mfunc 0x012c1272, devctl 0x66 Yenta: ISA IRQ mask 0x0838, PCI irq 10 Socket status: 3006 Yenta: CardBus bridge found at :00:0a.1 [103c:0010] Yenta: Using INTVAL to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket :00:0a.1, mfunc 0x012c1272, devctl 0x66 Yenta: ISA IRQ mask 0x0838, PCI irq 10 Socket status: 3006 agpgart: Detected an Intel 440BX Chipset. agpgart: AGP aperture is 64M @ 0xf800 piix4_smbus :00:07.3: Found :00:07.3 device ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5 PCI: setting IRQ 5 as level-triggered ACPI: PCI Interrupt :00:0d.0[A] - Link [LNKC] - GSI 5 (level, low) - IRQ 5 ACPI: PCI interrupt for device :00:0d.0 disabled Maestro3: probe of :00:0d.0 failed with error -2 input: Power Button (FF) as /class/input/input3 ACPI: Power Button (FF) [PWRF] input: Lid Switch as /class/input/input4 ACPI: Lid Switch [LID] input: Sleep Button (CM) as /class/input/input5 ACPI: Sleep Button (CM) [SLP] Synaptics Touchpad, model: 1, fw: 5.4, id: 0x9b54b1, caps: 0x844793/0x0 serio: Synaptics pass-through port at isa0060/serio1/input0 input: SynPS/2 Synaptics TouchPad as
Bug#617962: Network module b44 gets disconnected frequently
I have been using kernel 2.6.32 to get around this issue, but I am able to see the same problem in this kernel too. So it appears, lot of browsing triggers this. -- 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/201103140730.23228.vivek.peria...@gmail.com
Re: Dropping 686 non-pae kernel
On 13/03/2011 04:45, Ben Hutchings wrote:
This really ought to be checked on a Pentium M as well, though.
Ok, my notebook uses a Pentium M 725 (Dothan).
I've run the following script (it should be equivalent to yours) with
2.6.38-rc7 from experimental in recovery mode, both for 486 and 686.
Attached you can find the results.
#!/bin/bash
for i in {1..3}; do
netperf -H 192.168.10.1,4 -t TCP_STREAM -l 60
netperf -H 192.168.10.1,4 -t UDP_RR -l 60
done
The differences between 486 and 686 look very small, if not null.
If you want me to do some more tests, i'm available.
I've seen in the beginning of this thread you've reported the result of
a scripts elaborated by a program called ministat. I admit i've not
understood well neither the results nor the procedure. If you want me to
do that as well, please, explain a bit more the procedure.
Otherwise we can try to use some benchmark tools (no experience in this
field). I've seen that Phoronix is in Debian since few days.
Ciao.
Cesare.
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.10.1
(192.168.10.1) port 0 AF_INET : demo
Recv SendSend
Socket Socket Message Elapsed
Size SizeSize Time Throughput
bytes bytes bytessecs.10^6bits/sec
87380 16384 1638460.003499.79
87380 16384 1638460.003534.46
87380 16384 1638460.003495.89
UDP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.10.1
(192.168.10.1) port 0 AF_INET : demo
Local /Remote
Socket Size Request Resp. Elapsed Trans.
Send Recv Size SizeTime Rate
bytes Bytes bytesbytes secs.per sec
114688 114688 11 60.0064590.18
114688 114688
114688 114688 11 60.0064958.24
114688 114688
114688 114688 11 60.0064770.58
114688 114688
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.10.1
(192.168.10.1) port 0 AF_INET : demo
Recv SendSend
Socket Socket Message Elapsed
Size SizeSize Time Throughput
bytes bytes bytessecs.10^6bits/sec
87380 16384 1638460.003443.95
87380 16384 1638460.003450.00
87380 16384 1638460.003397.42
UDP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.10.1
(192.168.10.1) port 0 AF_INET : demo
Local /Remote
Socket Size Request Resp. Elapsed Trans.
Send Recv Size SizeTime Rate
bytes Bytes bytesbytes secs.per sec
114688 114688 11 60.0060308.29
114688 114688
114688 114688 11 60.0060628.59
114688 114688
114688 114688 11 60.0060599.16
114688 114688
Processed: tagging 612933
Processing commands for cont...@bugs.debian.org: tags 612933 + fixed-upstream Bug #612933 [nfs-common] nfs-common: 'mount -o remount' fails for mount.nfs Ignoring request to alter tags of bug #612933 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 612933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130003545928398.transcr...@bugs.debian.org
Bug#617866: uvesafb: cannot reserve video memory at 0xf0000000 and error -5
On Sat, 2011-03-12 at 23:08 +0100, gernotk wrote: Hi! On Sat, Mar 12, 2011 at 10:08:54AM +0100, Julien Cristau wrote: On Sat, Mar 12, 2011 at 00:47:00 +0100, Gernot Kieseritzky wrote: I tried to load uvesafb in order to get frame buffer support for the native 1024x600 resolution of my JVC MP-XP731 laptop. So I added You should get that from the i915 kernel mode setting driver, not uvesafb. Okay, I'll try to activate KMS, which was off by default after base install of debian/squeeze. I guess, it only gets activated by the installer selecting tasksel desktop. KMS is disabled by default in the kernel, so that it is possible to upgrade just the kernel in a 'lenny' installation without breaking X. The X drivers that can work with KMS then install configuration files to enable it in the corresponding kernel driver. You should create a similar configuration file in /etc/modprobe.d (the name must end in '.conf') with the text: options i915 modeset=1 Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Dropping 686 non-pae kernel
On Sun, 2011-03-13 at 17:47 +0100, Cesare Leonardi wrote:
On 13/03/2011 04:45, Ben Hutchings wrote:
This really ought to be checked on a Pentium M as well, though.
Ok, my notebook uses a Pentium M 725 (Dothan).
I think that one actually has PAE. /proc/cpuinfo will tell you for
sure.
I've run the following script (it should be equivalent to yours) with
2.6.38-rc7 from experimental in recovery mode, both for 486 and 686.
Attached you can find the results.
#!/bin/bash
for i in {1..3}; do
netperf -H 192.168.10.1,4 -t TCP_STREAM -l 60
netperf -H 192.168.10.1,4 -t UDP_RR -l 60
done
The differences between 486 and 686 look very small, if not null.
If you want me to do some more tests, i'm available.
You seem to have tested the loopback device - which has quite different
performance from real networking!
Actually my previous (not completely working) laptop has some kind of
Pentium M so I could do this testing myself.
I've seen in the beginning of this thread you've reported the result of
a scripts elaborated by a program called ministat. I admit i've not
understood well neither the results nor the procedure. If you want me to
do that as well, please, explain a bit more the procedure.
Otherwise we can try to use some benchmark tools (no experience in this
field). I've seen that Phoronix is in Debian since few days.
Put two sets of benchmark results in two files (one number per line).
ministat then calculates statistical measures of each set and a
comparison of the two sets.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
Re: Dropping 686 non-pae kernel
On Sun, 2011-03-13 at 09:18 +0100, Bastian Blank wrote: On Sun, Mar 13, 2011 at 03:57:56AM +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:34 +, Ben Hutchings wrote: On Mon, 2011-02-14 at 11:23 +0100, Bastian Blank wrote: [...] There are several possibilities to do this: * Change name of meta-package: - Breaks nothing - Needs manual intervention by anyone using it * Don't change the name: - Breaks some systems - No manual intervention by the rest I'm wavering on this. I don't like the idea of simply renaming '686-bigmem' to '686', given there are a fair number of 686-class systems without PAE, and I don't think users with a Pentium M are going to expect that '486' is the right choice. Please read again what I wrote. The fact that changing the metapackage name is disruptive? Ever heard of transitional packages? The distinctions between these two flavours will be: 1. One processor (min 486) with 386 page tables (currently '486') 2. One or more processors with PAE page tables (currently '686-bigmem') Will not hold forever and you need to integrate the other architectures into it. [...] I would expect the minimum processor for (1) to increase over time (hence my suggested name change), but other than that, what would need to change? Major new x86 features seem to be restricted to Long Mode only now. Why do other architectures matter to this? Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Re: Dropping 686 non-pae kernel
On 13/03/2011 18:07, Ben Hutchings wrote: I think that one actually has PAE. /proc/cpuinfo will tell you for sure. Unfortunately not. flags: fpu vme de pse tsc msr mce cx8 sep mtrr pge mca cmov clflush dts acpi mmx fxsr sse sse2 ss tm pbe up bts est tm2 In the past i read that there are different Dothan revisions: older have PAE disabled in hardware, like mine. :-( You seem to have tested the loopback device - which has quite different performance from real networking! Yes, silly me. At home i've no network to test, only my ADSL modem, and hoped that using loopback some differences could be seen. But i've forgotten to write that important detail, sorry. Put two sets of benchmark results in two files (one number per line). ministat then calculates statistical measures of each set and a comparison of the two sets. Ok, will do, thank you. Cesare. -- 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/4d7d0011.1010...@gmail.com
Processed: limit source to nfs-utils, tagging 612002
Processing commands for cont...@bugs.debian.org: #nfs-utils (1:1.2.2-5) UNRELEASED; urgency=low # # * nfs-common.init, nfs-kernel-server.init: Add warning when portmap is #not running (Closes: #612002) # limit source nfs-utils Limiting to bugs with field 'source' containing at least one of 'nfs-utils' Limit currently set to 'source':'nfs-utils' tags 612002 + pending Bug #612002 [nfs-common] Starting NFS common utilities failed Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 612002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130003926821864.transcr...@bugs.debian.org
Processed: tagging 457652
Processing commands for cont...@bugs.debian.org: tags 457652 - wontfix Bug #457652 [linux-2.6] linux-2.6: Please package lguest launcher Removed tag(s) wontfix. thanks Stopping processing here. Please contact me if you need assistance. -- 457652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=457652 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130003991924944.transcr...@bugs.debian.org
Bug#390616: marked as done (linux-image-2.6.18: Enable ATA-Security for Sid kernels)
Your message dated Sun, 13 Mar 2011 18:10:38 + with message-id 1300039838.4146.223.camel@localhost and subject line Re: linux-image-2.6.18: Enable ATA-Security for Sid kernels has caused the Debian Bug report #390616, regarding linux-image-2.6.18: Enable ATA-Security for Sid kernels to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 390616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.18-1-k7 Version: 2.6.18-1 Severity: important File: linux-image-2.6.18 tom1:/home/schorpp# hdlock /dev/hdc: Issuing SECURITY_SET_PASS command, password=xx, user=master, mode=max Problem issuing security command: Invalid argument Error: 22 You need to configure your kernel with CONFIG_IDE_TASK_IOCTL. (hdparm = 6.3) Pls enable CONFIG_IDE_TASK_IOCTL, it is stable since 2.6.16, thx. y tom -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (501, 'testing'), (101, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages linux-image-2.6.18-1-k7 depends on: ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD -- debconf information excluded ---End Message--- ---BeginMessage--- On Mon, 2006-10-02 at 09:48 +0200, schorpp wrote: Package: linux-image-2.6.18-1-k7 Version: 2.6.18-1 Severity: important File: linux-image-2.6.18 tom1:/home/schorpp# hdlock /dev/hdc: Issuing SECURITY_SET_PASS command, password=xx, user=master, mode=max Problem issuing security command: Invalid argument Error: 22 You need to configure your kernel with CONFIG_IDE_TASK_IOCTL. (hdparm = 6.3) Pls enable CONFIG_IDE_TASK_IOCTL, it is stable since 2.6.16, thx. This was rejected originally. Most old-style IDE drivers have now been disabled, so this now be pointless now. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#529719: marked as done (linux-2.6: please set CONFIG_IDE_TASK_IOCTL=y in Linux build configuration)
Your message dated Sun, 13 Mar 2011 18:10:38 + with message-id 1300039838.4146.223.camel@localhost and subject line Re: linux-image-2.6.18: Enable ATA-Security for Sid kernels has caused the Debian Bug report #390616, regarding linux-2.6: please set CONFIG_IDE_TASK_IOCTL=y in Linux build configuration to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 390616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=390616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Severity: wishlist According to the comments at the URLs below, CONFIG_IDE_TASK_IOCTL=y is needed to allow hdparm to issue the Secure Erase command to ATA hard drives. Please add it to the kernel build configuration. http://freshmeat.net/projects/hdparm/comments http://www.ocztechnologyforum.com/forum/showthread.php?t=55173 -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part ---End Message--- ---BeginMessage--- On Mon, 2006-10-02 at 09:48 +0200, schorpp wrote: Package: linux-image-2.6.18-1-k7 Version: 2.6.18-1 Severity: important File: linux-image-2.6.18 tom1:/home/schorpp# hdlock /dev/hdc: Issuing SECURITY_SET_PASS command, password=xx, user=master, mode=max Problem issuing security command: Invalid argument Error: 22 You need to configure your kernel with CONFIG_IDE_TASK_IOCTL. (hdparm = 6.3) Pls enable CONFIG_IDE_TASK_IOCTL, it is stable since 2.6.16, thx. This was rejected originally. Most old-style IDE drivers have now been disabled, so this now be pointless now. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#457652: linux-2.6: lguest launcher
On Fri, 2010-01-29 at 23:37 +0100, Moritz Muehlenhoff wrote: On Sat, Nov 14, 2009 at 11:30:37PM +0100, Frank Lin PIAT wrote: Hello, A quick note for those willing to play with lguest... I have been playing with lguest a little bit, for the fun. I don't believe that the lguest sample user land tools is worth being shipped and supported in Debian. E I concur. Now that we have the linux-tools packages, perhaps we could put it in there? We would need to make a separate linux-tools (unversioned name) package as well as the versioned packages for perf. The 'nosy' Firewire tools would also belong in linux-tools. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: limit source to nfs-utils, tagging 521084
Processing commands for cont...@bugs.debian.org: #nfs-utils (1:1.2.2-5) UNRELEASED; urgency=low # # * nfs-common.init: Add --pidfile for statd (Closes: #521084) # limit source nfs-utils Limiting to bugs with field 'source' containing at least one of 'nfs-utils' Limit currently set to 'source':'nfs-utils' tags 521084 + pending Bug #521084 [nfs-common] nfs-common: init.d-script should use pid files for statd and idmapd Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 521084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130004025726237.transcr...@bugs.debian.org
Processed: limit source to nfs-utils, tagging 524610
Processing commands for cont...@bugs.debian.org: #nfs-utils (1:1.2.2-5) UNRELEASED; urgency=low # # * nfs-common.init: Add statd to sendsigs.omit.d (Closes: #524610) # limit source nfs-utils Limiting to bugs with field 'source' containing at least one of 'nfs-utils' Limit currently set to 'source':'nfs-utils' tags 524610 + pending Bug #524610 [nfs-common] nfs-common: rpc.statd not running during umountnfs.sh at shutdown/reboot causes delay due to lockd timeout Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 524610: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524610 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130004100328922.transcr...@bugs.debian.org
Bug#496893: marked as done (Please export dm_disk symbol)
Your message dated Sun, 13 Mar 2011 18:31:34 + with message-id 1300041094.4146.236.camel@localhost and subject line Re: please add dm-raid45 module has caused the Debian Bug report #496893, regarding Please export dm_disk symbol to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 496893: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496893 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Please consider including dm-raid45 module. http://people.redhat.com/heinzm/sw/dm/dm-raid45/ dmraid debian package need it (#411172) Feature set: - This software extends device-mapper by RAID4 and RAID5 mappings. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAki2dXUACgkQNxpp46476arMbACfbbKQyIxJGLMFNz+QGfyhOnqL tMUAniJ3xfWI/wTGIxxUbJurYXBK05zj =sTdY -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- On Thu, 2008-08-28 at 11:52 +0200, Giuseppe Iuculano wrote: Package: linux-2.6 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Please consider including dm-raid45 module. http://people.redhat.com/heinzm/sw/dm/dm-raid45/ dmraid debian package need it (#411172) Feature set: - This software extends device-mapper by RAID4 and RAID5 mappings. The upstream kernel now has the dm-raid driver, which works on top of the existing (md) raid456 driver. However, it is still marked EXPERIMENTAL and I have no intention of enabling a RAID driver in such a state. Given that dm-raid can be built as a module, it follows that all the necessary symbols must now be exported, so you could, if you wish, build it out-of-tree. However, I would strongly recommend not providing this option to Debian users until the driver is known to be reliable. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Processed: unblock 411172 with 496893
Processing commands for cont...@bugs.debian.org: unblock 411172 with 496893 Bug #411172 [dmraid] dmraid is looking for the raid45 kernel module and not the raid456 modules. Was blocked by: 496893 504165 Removed blocking bug(s) of 411172: 496893 thanks Stopping processing here. Please contact me if you need assistance. -- 411172: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=411172 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130004115830322.transcr...@bugs.debian.org
Processed: tagging 528939
Processing commands for cont...@bugs.debian.org: # commit 30f05c8a tags 528939 + fixed-upstream Bug #528939 [nfs-kernel-server] nfs: server not responding Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 528939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528939 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130004124330728.transcr...@bugs.debian.org
Processed: closing 532276
Processing commands for cont...@bugs.debian.org: # bug submitter says it's fixed close 532276 Bug#532276: nfs-kernel-server stop doesn't 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Harald Dunkel harald.dun...@aixigo.de thanks Stopping processing here. Please contact me if you need assistance. -- 532276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=532276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.130004148032108.transcr...@bugs.debian.org
Processed: limit source to nfs-utils, tagging 561718
Processing commands for cont...@bugs.debian.org: #nfs-utils (1:1.2.2-5) UNRELEASED; urgency=low # # * nfs-common.init, nfs-kernel-server.init: Add warning when portmap is #not running (Closes: #612002,#561718) # limit source nfs-utils Limiting to bugs with field 'source' containing at least one of 'nfs-utils' Limit currently set to 'source':'nfs-utils' tags 561718 + pending Bug #561718 [nfs-common] subprocess installed post-installation script returned error exit status 1 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 561718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13000417681181.transcr...@bugs.debian.org
Bug#520668: marked as done (Enable syn cookies by default)
Your message dated Sun, 13 Mar 2011 18:41:16 + with message-id 1300041676.4146.238.camel@localhost and subject line Re: Enable syn cookies by default has caused the Debian Bug report #520668, regarding Enable syn cookies by default to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 520668: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: procps Version: 1:3.2.7-11 Severity: wishlist Hi, Could syn cookies be enabled by default? AFAIK syn cookies only get send when the half-open TCP connection queue is full. So stuff like window scaling should work fine in normal situations. Greetings, Olaf # Uncomment the next line to enable TCP/IP SYN cookies # This disables TCP Window Scaling (http://lkml.org/lkml/2008/2/5/167), # and is not recommended. #net.ipv4.tcp_syncookies=1 -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages procps depends on: ii libc6 2.7-18 GNU C Library: Shared libraries ii libncurses5 5.7+20081213-1 shared libraries for terminal hand ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip Versions of packages procps recommends: ii psmisc22.6-1 Utilities that use the proc filesy procps suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- SYN cookies have been enabled by default since 2.6.37. This was an upstream change, following enhancements to SYN cookies that addressed the problems they used to have. The default will not be changed in 'squeeze'. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Processed: limit source to nfs-utils, tagging 562737, tagging 561718
Processing commands for cont...@bugs.debian.org: #nfs-utils (1:1.2.2-5) UNRELEASED; urgency=low # # * nfs-common.init, nfs-kernel-server.init: Add warning when portmap is #not running (Closes: #612002,#561718,#562737) # limit source nfs-utils Limiting to bugs with field 'source' containing at least one of 'nfs-utils' Limit currently set to 'source':'nfs-utils' tags 562737 + pending Bug #562737 [nfs-common] installation failed with Starting NFS common utilities: statd failed! Added tag(s) pending. tags 561718 + pending Bug #561718 [nfs-common] subprocess installed post-installation script returned error exit status 1 Ignoring request to alter tags of bug #561718 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 561718: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561718 562737: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562737 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13000418541513.transcr...@bugs.debian.org
Bug#618258: linux-image-2.6.32-5-amd64: readd legacy /proc/scsi support
Package: linux-2.6 Version: 2.6.32-30 Severity: wishlist First and foremost, I've already browsed several bug reports dating back to 2008 that have requested this to be turned back on (mostly in the now nonexistent scsiadd package). The general attitude is bug your software vendor if they don't support sysfs but really, you can't expect this out of everyone. Especially a place like HighPoint who hasn't touched their drivers since 10/22/2009. I respect the position but, in my opinion, you're only hurting consumer level Debian users by turning extremely minor things like this off. I upgraded my home Linux server from lenny to squeeze last weekend via a fresh install onto a new drive and my final to-do item was fix the CLI interface for my common, consumer-level, current-gen, hardware RAID5 card: a HighPoint RocketRaid 2310. Their CLI client that can be configured to email me when the array degrades simply stopped working after the upgrade. Compiled fine, but when ran it didn't do anything but claim the driver wasn't loaded even though I was clearly using the RAID array and seeing it in dmesg. A tiny bit of Googling led me to this blog post from 1/12/2011: http://cosmicb.no/?p=136 which correctly explained hptraidconf was broken because Debian decided to turn legacy /proc/scsi support off in squeeze. I think it should be turned back on to continue to support devices that use it that are unlikely to see their kernel tainting drivers updated to not use /proc/scsi. Thanks and have a fine day. I sadly expect this to be quickly marked as wontfix with zero discussion because that's my experience with filing Debian bug reports. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Chassis Manufacture chassis_version: Chassis Version bios_vendor: Phoenix Technologies, LTD bios_version: ASUS A8N-SLI Premium ACPI BIOS Revision 1008 board_vendor: ASUSTeK Computer INC. board_name: A8N-SLI Premium board_version: 1.02 ** Network interface configuration: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth1 iface eth1 inet static address 172.16.31.2 netmask 255.255.255.0 broadcast 172.16.31.255 network 172.16.31.0 gateway 172.16.31.1 ** PCI devices: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a3) Subsystem: ASUSTeK Computer Inc. A8N-E Mainboard [1043:815a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Capabilities: access denied 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge [10de:0050] (rev a3) Subsystem: ASUSTeK Computer Inc. K8N4-E or A8N-E Mainboard [1043:815a] Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] (rev a2) Subsystem: ASUSTeK Computer Inc. K8N4-E or A8N-E Mainboard [1043:815a] Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 10 Region 0: I/O ports at dc00 [size=32] Region 4: I/O ports at 4c00 [size=64] Region 5: I/O ports at 4c40 [size=64] Capabilities: access denied Kernel driver in use: nForce2_smbus 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2) (prog-if 10 [OHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E or A8N-E Mainboard [1043:815a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 (750ns min, 250ns max) Interrupt: pin A routed to IRQ 20 Region 0: Memory at d6003000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied Kernel driver in use: ohci_hcd 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005b] (rev a3) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. K8N4-E or A8N-E Mainboard [1043:815a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR-
Processed: limit source to nfs-utils, tagging 593511
Processing commands for cont...@bugs.debian.org: #nfs-utils (1:1.2.2-5) UNRELEASED; urgency=low # # * nfs-common.default, nfs-kernel-server.default: Remove spurious question #mark in wiki url (Closes: #593511) # limit source nfs-utils Limiting to bugs with field 'source' containing at least one of 'nfs-utils' Limit currently set to 'source':'nfs-utils' tags 593511 + pending Bug #593511 [nfs-common] Lenny: typo in comments in /etc/default/nfs-common Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 593511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13000423273694.transcr...@bugs.debian.org
Bug#550358: marked as done (linux-image-2.6.30-2-686: Enable BOOTPARAM_HUNG_TASK_PANIC feature)
Your message dated Sun, 13 Mar 2011 18:55:43 +
with message-id 1300042543.4146.241.camel@localhost
and subject line Re: linux-image-2.6.30-2-686: Enable BOOTPARAM_HUNG_TASK_PANIC
feature
has caused the Debian Bug report #550358,
regarding linux-image-2.6.30-2-686: Enable BOOTPARAM_HUNG_TASK_PANIC feature
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
550358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.30-2-686
Version: 2.6.30-8
Severity: normal
Please enable the BOOTPARAM_HUNG_TASK_PANIC feature (Panic Reboot on
Hung Tasks).
The current kernel already has DETECT_HUNG_TASK enabled.
Adding this feature will help a lot in cases where a process goes hung
in 'DI' state and can't be killed. Currently, in those situations you
cannot shutdown your box because the kernel will not be able to kill the
process.
By enabling the above feature and then using it together with Reboot on
Panic, we can handle this catastrophic situation.
Here's the kernel description:
=
Say Y here to enable the kernel to panic on hung tasks,
which are bugs that cause the kernel to leave a task
stuck in uninterruptible D state.
The panic can be used in combination with panic_timeout,
to cause the system to reboot automatically after a hung task
has been detected. This feature is useful for high-availability
systems that have uptime guarantees and where a hung tasks must be
resolved ASAP.
-- Package-specific info:
** Version:
Linux version 2.6.30-2-686 (Debian 2.6.30-8) (wa...@debian.org) (gcc version
4.3.4 (Debian 4.3.4-3) ) #1 SMP Sat Sep 26 01:16:22 UTC 2009
** Command line:
BOOT_IMAGE=/vmlinuz-2.6.30-2-686 root=/dev/mapper/VgSd-ROOT ro
root=/dev/mapper/VgSd-ROOT ro audit=1 selinux=1 enforcing=0 quiet vga=788
** Not tainted
** Kernel log:
[ 15.247412] input: TPPS/2 IBM TrackPoint as
/devices/platform/i8042/serio1/serio2/input/input10
[ 18.265012] __ratelimit: 57 callbacks suppressed
[ 18.265021] type=1400 audit(1255023463.912:19): avc: denied { read } for
pid=698 comm=udevd path=anon_inode:[signalfd] dev=anon_inodefs ino=56
scontext=system_u:system_r:udev_t:s0-s0:c0.c1023
tcontext=system_u:object_r:anon_inodefs_t:s0 tclass=file
[ 18.265144] type=1300 audit(1255023463.912:19): arch=4003 syscall=3
success=yes exit=128 a0=7 a1=bfbf9688 a2=80 a3=bfbf97e8 items=0 ppid=1 pid=698
auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0
tty=(none) ses=4294967295 comm=udevd exe=/sbin/udevd
subj=system_u:system_r:udev_t:s0-s0:c0.c1023 key=(null)
[ 20.141987] type=1400 audit(1255023465.772:20): avc: denied { read write }
for pid=1314 comm=auditd name=tty1 dev=tmpfs ino=1357
scontext=system_u:system_r:auditd_t:s0
tcontext=system_u:object_r:tty_device_t:s0 tclass=chr_file
[ 20.142177] type=1300 audit(1255023465.772:20): arch=4003 syscall=11
success=yes exit=0 a0=bfbf0edf a1=bfbef180 a2=bfbef188 a3=bfbef180 items=0
ppid=1310 pid=1314 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0
sgid=0 fsgid=0 tty=tty1 ses=4294967295 comm=auditd exe=/sbin/auditd
subj=system_u:system_r:auditd_t:s0 key=(null)
[ 20.428724] type=1400 audit(1255023466.076:21): avc: denied { read } for
pid=1314 comm=auditd name=urandom dev=tmpfs ino=1159
scontext=system_u:system_r:auditd_t:s0
tcontext=system_u:object_r:urandom_device_t:s0 tclass=chr_file
[ 20.428755] type=1400 audit(1255023466.076:21): avc: denied { open } for
pid=1314 comm=auditd name=urandom dev=tmpfs ino=1159
scontext=system_u:system_r:auditd_t:s0
tcontext=system_u:object_r:urandom_device_t:s0 tclass=chr_file
[ 20.428796] type=1300 audit(1255023466.076:21): arch=4003 syscall=5
success=yes exit=3 a0=b7facbd9 a1=0 a2=b7c8b8f0 a3=bfc1b440 items=0 ppid=1310
pid=1314 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0
fsgid=0 tty=tty1 ses=4294967295 comm=auditd exe=/sbin/auditd
subj=system_u:system_r:auditd_t:s0 key=(null)
[ 20.575334] type=1400 audit(1255023466.220:22): avc: denied { read } for
pid=1317 comm=audispd name=urandom dev=tmpfs ino=1159
scontext=system_u:system_r:audisp_t:s0
tcontext=system_u:object_r:urandom_device_t:s0 tclass=chr_file
[ 20.575367] type=1400 audit(1255023466.220:22): avc: denied { open } for
pid=1317 comm=audispd name=urandom dev=tmpfs ino=1159
scontext=system_u:system_r:audisp_t:s0
tcontext=system_u:object_r:urandom_device_t:s0 tclass=chr_file
[ 20.575407] type=1300 audit(1255023466.220:22): arch=4003 syscall=5
success=yes
Bug#553472: marked as done (linux-libc-dev: Include linux/aufs_type.h for aufs2-utils?)
Your message dated Sun, 13 Mar 2011 18:57:09 + with message-id 1300042629.4146.242.camel@localhost and subject line Re: linux-libc-dev: Include linux/aufs_type.h for aufs2-utils? has caused the Debian Bug report #553472, regarding linux-libc-dev: Include linux/aufs_type.h for aufs2-utils? to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 553472: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553472 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-libc-dev Version: 2.6.31-1 Severity: wishlist Hi, would it be possible to get linux/aufs_type.h included in linux-libc-dev or a similar package? This header is needed to build the userspace tools of aufs, which include programs such as mount.aufs or auchk. Currently it is included in linux-headers-2.6.31-common but this package is versioned and would thus require changes to aufs-tools build-dependencies for every new kernel. Regards, Julian -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. ---End Message--- ---BeginMessage--- On Sat, 2009-10-31 at 17:50 +0100, Julian Andres Klode wrote: Package: linux-libc-dev Version: 2.6.31-1 Severity: wishlist Hi, would it be possible to get linux/aufs_type.h included in linux-libc-dev or a similar package? This header is needed to build the userspace tools of aufs, which include programs such as mount.aufs or auchk. Currently it is included in linux-headers-2.6.31-common but this package is versioned and would thus require changes to aufs-tools build-dependencies for every new kernel. As previously stated, the AUFS userland interface is not stable nor supported by the kernel team. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#556365: marked as done (Please enable CONFIG_MEMTEST)
Your message dated Sun, 13 Mar 2011 18:59:32 + with message-id 1300042772.4146.244.camel@localhost and subject line Re: Please enable CONFIG_MEMTEST has caused the Debian Bug report #556365, regarding Please enable CONFIG_MEMTEST to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 556365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.31-1 Severity: wishlist Please enable CONFIG_MEMTEST on x86. It shouldn't have any impact by default, and can be useful to boot a system with bad ram. -- Romain Francoise rfranco...@debian.org http://people.debian.org/~rfrancoise/ ---End Message--- ---BeginMessage--- On Sun, 2009-11-15 at 16:05 +0100, Romain Francoise wrote: Package: linux-2.6 Version: 2.6.31-1 Severity: wishlist Please enable CONFIG_MEMTEST on x86. It shouldn't have any impact by default, and can be useful to boot a system with bad ram. As previously stated, this is a very poor test and redundant with the memtest86+ package. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part ---End Message---
Re: Dropping 686 non-pae kernel
On 13/03/2011 18:07, Ben Hutchings wrote: Put two sets of benchmark results in two files (one number per line). ministat then calculates statistical measures of each set and a comparison of the two sets. I've run the following in recovery mode (to avoid interference from other programs/daemons): for i in $(seq 0 100); do \time find /usr /dev/null; done Every results is composed by two line: i kept only the lines containing user and system time. Then discarded the first line to keep only data from cache. Then extrated only the columns containing system time. The two file (1 for 486, 1 for 686) were passed to ministat, which produced the attached file. Ciao. Cesare. x ministat-486.mod.txt + ministat-686.mod.txt ++ | +| |x +| |x +| |x +| |x +| |x +| |x +| |x +| |x +| | x x +| | x x +| | x x x + + | | x x x x + + + | | x x x x + + + | | x x x x + + + | | x * x x + + + | | x * x x + + + | | x * x * + + + | | x * x * + + + | | x * * * + + + | | x x * * * * + + | |x x x * * * * + + | |x x * * * * * + + | |x x * * * * * + + +| |x x * * * * * * + +| |x x * * * * * * * + +| |* * * * * * * * * + +| ||A__M_| | | |__A_M| | ++ N Min MaxMedian AvgStddev x 100 0.2 0.28 0.240.2349 0.018062462 + 101 0.2 0.3 0.260.25752475 0.021043096 Difference at 95.0% confidence 0.0226248 +/- 0.00542407 9.63165% +/- 2.3091% (Student's t, pooled s = 0.019617)
Bug#618261: linux-2.6: Please enable CONFIG_FB_UDL on all architectures
Package: linux-2.6 Severity: wishlist CONFIG_FB_UDL enables the udlfb framebuffer driver, for a USB-to-DVI display adapter. The Debian kernels have this driver enabled on an armel kernel, but not in general. As a USB device, this seems like a perfect candidate for enabling (=m) on all architectures. Thanks, Josh Triplett -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.37-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20110313194615.22578.33449.reportbug@feather
Bug#618258: linux-image-2.6.32-5-amd64: readd legacy /proc/scsi support
On Sun, 2011-03-13 at 11:31 -0700, Tyler wrote: Package: linux-2.6 Version: 2.6.32-30 Severity: wishlist First and foremost, I've already browsed several bug reports dating back to 2008 that have requested this to be turned back on (mostly in the now nonexistent scsiadd package). There are sysfs files you can poke to add SCSI devices. The general attitude is bug your software vendor if they don't support sysfs but really, you can't expect this out of everyone. Especially a place like HighPoint who hasn't touched their drivers since 10/22/2009. I respect the position but, in my opinion, you're only hurting consumer level Debian users by turning extremely minor things like this off. It is not the responsibility of the kernel team to support out-of-tree drivers. I would strongly discourage anyone from buying hardware that does not have in-tree drivers. But it sounds like you are conflating the driver and the utilities. The driver surely does not depend on /proc/scsi/scsi. [...] I think it should be turned back on to continue to support devices that use it that are unlikely to see their kernel tainting drivers updated to not use /proc/scsi. [...] Given that the upstream default is still Y, you may be right. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#618261: linux-2.6: Please enable CONFIG_FB_UDL on all architectures
On Sun, 2011-03-13 at 12:46 -0700, Josh Triplett wrote: Package: linux-2.6 Severity: wishlist CONFIG_FB_UDL enables the udlfb framebuffer driver, for a USB-to-DVI display adapter. The Debian kernels have this driver enabled on an armel kernel, but not in general. As a USB device, this seems like a perfect candidate for enabling (=m) on all architectures. It does seem to make sense, but we need to be sure that consoles won't move to the DisplayLink adapter when udlfb is loaded on a system where it is a secondary adapter. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#618279: linux-image-2.6.32-5-686.deb: WIFI Usb adapter REALTEK RTL8188S not work
Processing commands for cont...@bugs.debian.org: reassign 618279 linux-2.6 Bug #618279 [linux-image-2.6.32-5-686.deb] linux-image-2.6.32-5-686.deb: WIFI Usb adapter REALTEK RTL8188S not work Warning: Unknown package 'linux-image-2.6.32-5-686.deb' Bug reassigned from package 'linux-image-2.6.32-5-686.deb' to 'linux-2.6'. Bug No longer marked as found in versions 2.6.32-ieee1394.deb. -- Stopping processing here. Please contact me if you need assistance. -- 618279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618279 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13000579895401.transcr...@bugs.debian.org
Bug#618279: linux-image-2.6.32-5-686.deb: WIFI Usb adapter REALTEK RTL8188S not work
Package: linux-image-2.6.32-5-686.deb Version: 2.6.32-ieee1394.deb Severity: important Morning sir, I try to install an USB WIFI adapter, manufacturer Realtek idvendor 0bda, Product id= 8171. Linux driver used is RTL8192, firmware: requesting RTL8192SU/rtl8192sfw.bin, done. At this point all thing seam done, and the rtl819xU:Firmware Download Success!! The problem is this message : ADDRCONF(NETDEV_UP): wlan1: link is not ready [15376.945960] =rtl8192SU_link_change 1 [15376.950043] =rtl8192SU_link_change 2 You will find here under a log file of the messages : root@Soleil:~# dmesg ... [15371.584010] usb 2-1: new high speed USB device using ehci_hcd and address 8 [15371.652250] hub 2-0:1.0: unable to enumerate USB device on port 1 [15371.976007] usb 6-1: new full speed USB device using uhci_hcd and address 2 [15372.171034] usb 6-1: not running at top speed; connect to a high speed hub [15372.199034] usb 6-1: New USB device found, idVendor=0bda, idProduct=8171 [15372.199037] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [15372.199039] usb 6-1: Product: RTL8188S WLAN Adapter [15372.199042] usb 6-1: Manufacturer: Manufacturer Realtek [15372.199044] usb 6-1: SerialNumber: 00e04c01 [15372.199146] usb 6-1: configuration #1 chosen from 1 choice [15372.309564] r8192s_usb: module is from the staging directory, the quality is unknown, you have been warned. [15372.314066] ieee80211_crypt: registered algorithm 'NULL' [15372.314068] ieee80211_crypt: registered algorithm 'TKIP' [15372.314070] ieee80211_crypt: registered algorithm 'CCMP' [15372.314072] ieee80211_crypt: registered algorithm 'WEP' [15372.314074] [15372.314074] Linux kernel driver for RTL8192 based WLAN cards [15372.314076] Copyright (c) 2007-2008, Realsil Wlan [15372.314259] ==ep_num:4, in_ep_num:1, out_ep_num:3 [15372.314260] ==RtInPipes:3 [15372.314262] ==RtOutPipes:4 6 13 [15372.314265] ==txqueue_to_outpipemap for BK, BE, VI, VO, HCCA, TXCMD, MGNT, HIGH, BEACON: [15372.314268] 1 1 0 0 2 2 2 2 2 [15373.402043] Dot11d_Init() [15373.402805] usbcore: registered new interface driver rtl819xU [15373.416400] udev[651]: renamed network interface wlan0 to wlan1 [15373.464036] rtl819xU: ---FirmwareDownload92S() [15373.464039] [15373.464043] usb 6-1: firmware: requesting RTL8192SU/rtl8192sfw.bin [15373.477353] rtl819xU:signature:8192, version:902b, size:30, imemsize:7408, sram size:9688 [15373.477356] [15373.477394] rtl819xU:---FirmwareDownloadCode() [15373.477395] [15373.477472] rtl819xU:---FirmwareCheckReady(): LoadStaus(1), [15373.508043] rtl819xU:---FirmwareCheckReady(): LoadFWStatus(1), rtStatus(0) [15373.508045] [15373.508048] rtl819xU:---FirmwareDownloadCode() [15373.508049] [15373.508131] rtl819xU:---FirmwareCheckReady(): LoadStaus(2), [15373.547039] rtl819xU:--FirmwareEnableCPU() [15373.547041] [15373.553039] rtl819xU:IMEM Ready after CPU has refilled. [15373.553041] [15373.553043] rtl819xU:--FirmwareEnableCPU(): rtStatus(0x0) [15373.553044] [15373.553046] rtl819xU:---FirmwareCheckReady(): LoadFWStatus(2), rtStatus(0) [15373.553047] [15373.553049] rtl819xU:---FirmwareDownloadCode() [15373.553050] [15373.553055] rtl819xU:---FirmwareCheckReady(): LoadStaus(3), [15373.554037] rtl819xU:DMEM code download success, CPUStatus(0x3f) [15373.554038] [15373.556037] rtl819xU:Polling Load Firmware ready, CPUStatus(ff) [15373.556039] [15373.560037] rtl819xU:FirmwareCheckReady(): Current RCR settings(0x157e20e) [15373.560039] [15373.561040] rtl819xU:---FirmwareCheckReady(): LoadFWStatus(3), rtStatus(0) [15373.561041] [15373.561043] rtl819xU:Firmware Download Success!! [15373.561044] [15376.880436] ADDRCONF(NETDEV_UP): wlan1: link is not ready [15376.945960] =rtl8192SU_link_change 1 [15376.950043] =rtl8192SU_link_change 2 root@Soleil:~# lsmod | grep rt exportfs2554 1 nfsd rt2800usb 21151 0 rt2x00usb 5491 1 rt2800usb rt2x00lib 18557 2 rt2800usb,rt2x00usb led_class 1761 1 rt2x00lib mac80211 119802 2 rt2x00usb,rt2x00lib cfg80211 83870 2 rt2x00lib,mac80211 crc_ccitt 1035 1 rt2800usb gameport5929 2 emu10k1_gp parport_pc 15581 1 parport22346 3 ppdev,lp,parport_pc usbcore95846 8 r8192s_usb,rt2800usb,rt2x00usb,usbhid,usb_storage,uhci_hcd,ehci_hcd root@Soleil:~# lsmod | grep r r8192s_usb263968 0 bridge 32383 0 stp 1008 1 bridge rfcomm 24020 0 l2cap 21473 6 bnep,rfcomm crc16 1023 1 l2cap bluetooth 34653 6 sco,bnep,rfcomm,l2cap acpi_cpufreq4797 0 cpufreq_stats 1930 0 cpufreq_userspace 1380 0 cpufreq_powersave602 0 cpufreq_conservative 4058 0 exportfs2554 1 nfsd auth_rpcgss24729 2 nfsd,nfs sunrpc132466 12
Bug#618261: linux-2.6: Please enable CONFIG_FB_UDL on all architectures
On Sun, Mar 13, 2011 at 07:56:17PM +, Ben Hutchings wrote: On Sun, 2011-03-13 at 12:46 -0700, Josh Triplett wrote: Package: linux-2.6 Severity: wishlist CONFIG_FB_UDL enables the udlfb framebuffer driver, for a USB-to-DVI display adapter. The Debian kernels have this driver enabled on an armel kernel, but not in general. As a USB device, this seems like a perfect candidate for enabling (=m) on all architectures. It does seem to make sense, but we need to be sure that consoles won't move to the DisplayLink adapter when udlfb is loaded on a system where it is a secondary adapter. Fair enough. - Josh Triplett -- 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/20110314010635.GB25516@feather
Re: Dropping 686 non-pae kernel
On Sun, 2011-03-13 at 17:07 +, Ben Hutchings wrote:
On Sun, 2011-03-13 at 17:47 +0100, Cesare Leonardi wrote:
On 13/03/2011 04:45, Ben Hutchings wrote:
This really ought to be checked on a Pentium M as well, though.
Ok, my notebook uses a Pentium M 725 (Dothan).
I think that one actually has PAE. /proc/cpuinfo will tell you for
sure.
I've run the following script (it should be equivalent to yours) with
2.6.38-rc7 from experimental in recovery mode, both for 486 and 686.
Attached you can find the results.
#!/bin/bash
for i in {1..3}; do
netperf -H 192.168.10.1,4 -t TCP_STREAM -l 60
netperf -H 192.168.10.1,4 -t UDP_RR -l 60
done
The differences between 486 and 686 look very small, if not null.
If you want me to do some more tests, i'm available.
You seem to have tested the loopback device - which has quite different
performance from real networking!
Actually my previous (not completely working) laptop has some kind of
Pentium M so I could do this testing myself.
Done. That laptop is a Thinkpad T42 with a Pentium M model 745, which
does not have PAE.
I turned off interrupt moderation for the UDP_RR tests (so far as
ethtool says; personally I can't believe the transaction rate can be so
low with moderation completely off, but then I'm spoiled).
With the 686 flavour:
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.2.250
(192.168.2.250) port 0 AF_INET : demo
Recv SendSend
Socket Socket Message Elapsed
Size SizeSize Time Throughput
bytes bytes bytessecs.10^6bits/sec
87380 16384 1638460.04 751.58
87380 16384 1638460.03 751.20
87380 16384 1638460.04 751.42
UDP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
192.168.2.250 (192.168.2.250) port 0 AF_INET : demo
Local /Remote
Socket Size Request Resp. Elapsed Trans.
Send Recv Size SizeTime Rate
bytes Bytes bytesbytes secs.per sec
126976 126976 11 60.009774.93
114688 114688
126976 126976 11 60.009856.57
114688 114688
126976 126976 11 60.009840.54
114688 114688
With the 486 flavour:
TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.2.250
(192.168.2.250) port 0 AF_INET : demo
Recv SendSend
Socket Socket Message Elapsed
Size SizeSize Time Throughput
bytes bytes bytessecs.10^6bits/sec
87380 16384 1638460.03 751.29
87380 16384 1638460.03 751.08
87380 16384 1638460.03 751.22
UDP REQUEST/RESPONSE TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to
192.168.2.250 (192.168.2.250) port 0 AF_INET : demo
Local /Remote
Socket Size Request Resp. Elapsed Trans.
Send Recv Size SizeTime Rate
bytes Bytes bytesbytes secs.per sec
126976 126976 11 60.009846.26
114688 114688
126976 126976 11 60.009854.01
114688 114688
126976 126976 11 60.009867.24
114688 114688
Looks very marginally slower on the TCP_STREAM test, but all the results
for that are so close together that I suspect that the PCI bus on the
T42 is the bottleneck. (The other side of these tests is a T61 whose
Ethernet adapter is attached with PCI Express, so it should not be a
bottleneck.)
All in all, I'm convinced that using the current '486' configuration for
all PAE-incapable systems is unlikely to hurt their performance and will
generally improve it slightly.
As for the PAE-capable systems currently not using PAE, there is a cost:
approximately twice as much RAM needed for page tables, and twice as
much memory traffic required to read and write them in batches. But I
doubt it's significant. As benefits, we get more systems using the
NX/XD bit and fewer with RAM above 4 GB accidentally disabled.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
Re: Re: 3g usb wireless modem
Hi, 3G HSDPA/HSUPA/EVDO USB Wireless Modem, factory, OEM service. Kind regards, Tinty Sunrise Tech Group Limited www.sunrisechina.biz T: +86-755-28894365 23943658 F: +86-755-29014855 E: ti...@sunrisechina.biz
