Bug#594189: initramfs-tools: environment variable to disable run_bootloader
On Wed, Aug 25, 2010 at 05:44:32AM +0100, Ben Hutchings wrote: On Tue, 2010-08-24 at 16:55 +0100, Colin Watson wrote: Actually, what I want is a consistent way to disable bootloader invocation for all bootloaders, without necessarily requiring the bootloader package not to be installed (since that's sometimes extremely awkward to arrange). Exactly where this goes I can't say I mind. If the result is an extension to the bootloader/kernel policy that needs to be implemented in each bootloader package, that would be fine too. [...] OK, so something like this: Boot loader packages must be installable on the filesystem in a disabled state where they will not write to the boot sector or other non-filesystem storage. While a boot loader is disabled, any kernel and initramfs hooks it includes must do nothing except (optionally) printing a warning that the boot loader is disabled, and must exit successfully. This is a good start, but it doesn't specify *how* boot loader packages are to be disabled. I think that this needs to be consistent across boot loaders. -- Colin Watson [cjwat...@debian.org] -- 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/20100828083541.gr12...@riva.ucam.org
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
Dear Ben, It seems that the kernel without firmware is not able to load any module. Probably, because the device I am using is 083a:a701 !! . Here is the answer of the things you asked for (after dpkg --purge firmware-ralink ): readlink /sys/class/net/wlan0/device/driver --- ../../../../../bus/usb/drivers/usb /sbin/modinfo rt2870sta --- filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/staging/rt2870/rt2870sta.ko version:2.1.0.0 license:GPL description:RT2870/RT3070 Wireless Lan Linux Driver author: Paul Lin paul_...@ralinktech.com firmware: rt3071.bin firmware: rt3070.bin firmware: rt2870.bin srcversion: 081365DAC3DB3AC17D83014 alias: usb:v2019pED14d*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3C0Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0077d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p003Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v203Dp1480d*dc*dsc*dp*ic*isc*ip* alias: usb:v04BBp0945d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0283d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p5257d*dc*dsc*dp*ic*isc*ip* alias: usb:v1D4Dp000Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v1D4Dp000Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v1EDAp2310d*dc*dsc*dp*ic*isc*ip* alias: usb:v1A32p0304d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7711d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3072d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3071d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3070d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pAB25d*dc*dsc*dp*ic*isc*ip* alias: usb:v1044p800Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v13D3p3273d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9706d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9705d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9703d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7511d*dc*dsc*dp*ic*isc*ip* alias: usb:v18C5p0012d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C12d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0042d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p003Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v0DB0p3820d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3072d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3071d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3070d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp815Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0411p00E8d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0071d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0070d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7717d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7718d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0282d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0280d*dc*dsc*dp*ic*isc*ip* alias: usb:v04E8p2018d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v1482p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp815Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp805Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v157Ep300Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v129Bp1828d*dc*dsc*dp*ic*isc*ip* alias: usb:v0E66p0003d*dc*dsc*dp*ic*isc*ip* alias: usb:v0E66p0001d*dc*dsc*dp*ic*isc*ip* alias: usb:v15C5p0008d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap6618d*dc*dsc*dp*ic*isc*ip* alias: usb:v13D3p3247d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C25d*dc*dsc*dp*ic*isc*ip* alias: usb:v0471p200Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9702d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9701d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CDEp0025d*dc*dsc*dp*ic*isc*ip* alias: usb:v0586p3416d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CDEp0022d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7522d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap8522d*dc*dsc*dp*ic*isc*ip* alias: usb:v083ApA618d*dc*dsc*dp*ic*isc*ip* alias: usb:v083ApB522d*dc*dsc*dp*ic*isc*ip* alias: usb:v15A9p0006d*dc*dsc*dp*ic*isc*ip* alias: usb:v1044p800Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp003Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp003Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp002Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C27d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C23d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp825Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp8053d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C07d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C11d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C09d*dc*dsc*dp*ic*isc*ip* alias:
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz (2)
Dear Ben, After reconfiguring kernel and rebooting and so on, results are different (??). Here is the answer: readlink /sys/class/net/wlan0/device/driver --- --- (nothing) /sbin/modinfo rt2870sta --- filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/staging/rt2870/rt2870sta.ko version:2.1.0.0 license:GPL description:RT2870/RT3070 Wireless Lan Linux Driver author: Paul Lin paul_...@ralinktech.com firmware: rt3071.bin firmware: rt3070.bin firmware: rt2870.bin srcversion: 081365DAC3DB3AC17D83014 alias: usb:v2019pED14d*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3C0Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0077d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p003Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v203Dp1480d*dc*dsc*dp*ic*isc*ip* alias: usb:v04BBp0945d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0283d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p5257d*dc*dsc*dp*ic*isc*ip* alias: usb:v1D4Dp000Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v1D4Dp000Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v1EDAp2310d*dc*dsc*dp*ic*isc*ip* alias: usb:v1A32p0304d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7711d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3072d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3071d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3070d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pAB25d*dc*dsc*dp*ic*isc*ip* alias: usb:v1044p800Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v13D3p3273d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9706d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9705d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9703d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7511d*dc*dsc*dp*ic*isc*ip* alias: usb:v18C5p0012d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C12d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0042d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p003Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v0DB0p3820d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3072d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3071d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3070d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp815Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0411p00E8d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0071d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0070d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7717d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7718d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0282d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0280d*dc*dsc*dp*ic*isc*ip* alias: usb:v04E8p2018d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v1482p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp815Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp805Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v157Ep300Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v129Bp1828d*dc*dsc*dp*ic*isc*ip* alias: usb:v0E66p0003d*dc*dsc*dp*ic*isc*ip* alias: usb:v0E66p0001d*dc*dsc*dp*ic*isc*ip* alias: usb:v15C5p0008d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap6618d*dc*dsc*dp*ic*isc*ip* alias: usb:v13D3p3247d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C25d*dc*dsc*dp*ic*isc*ip* alias: usb:v0471p200Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9702d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9701d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CDEp0025d*dc*dsc*dp*ic*isc*ip* alias: usb:v0586p3416d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CDEp0022d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7522d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap8522d*dc*dsc*dp*ic*isc*ip* alias: usb:v083ApA618d*dc*dsc*dp*ic*isc*ip* alias: usb:v083ApB522d*dc*dsc*dp*ic*isc*ip* alias: usb:v15A9p0006d*dc*dsc*dp*ic*isc*ip* alias: usb:v1044p800Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp003Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp003Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp002Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C27d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C23d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp825Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp8053d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C07d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C11d*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pED06d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C28d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C06d*dc*dsc*dp*ic*isc*ip* alias:
Bug#594676: linux-image-2.6-amd64: Files Download Pb with the atl1c module and my ReadyNAS
Package: linux-image-2.6-amd64 Version: 2.6.32+27~bpo50+1 Severity: normal Hi, I have an eeepc 1201n with debian stable lenny+backports. So I'm using the kernel 2.6.32-bpo.5-amd64. The Ethernet controller is driven by the module atl1c. I'm using firestarter as firewall. I have a file transfer problem between my NAS (readyNAS Duo from Netgear); at first the symptoms: - with firestarter installed (stopped or in use) I can connect my eeepc to my NAS through FTP, CIFS or NFS. For example I can list or go through my shares. But when I'm trying to download a file it is so slow. I get 12Ko in 10minutes... - I can upload files from my eeepc to the NAS without problem with full speed. - When I boot the eeepc under w7 I don't have any problem to download files. - I have two others computers on my LAN: a laptop with SID and the b44 module for the ethernet controller. With this laptop no problem at all to download files from my NAS with firestarter installed. The other one is a desktop station and I don't have any problem, too. Now what I have done with the help of the debian.user.french list: - the NAS has a MTU of 1500 (the software forces it). All the other computers have an mtu of 1492. I don't choose it, my Netgear router force it...When I set the mtu to 1500 on my eeepc with ip link set dev eth0 mtu 1500, then ip route flush cache, I can dowload files from my NAS without problem (firestarter installed and running). When I set the both devices (eeepc and NAS) with a mtu to 1492, it doesn't work at all. - I have tested with the driver from realtek website and I get exactly the same problem. - I did capture with tcpdump. Guys of the debian.user.french mailing list were surprised to see that lots of my packets were lost in my normal configuration (firestarter installed, NAS mtu set to 1500 and eeepc mtu set to 1492). And they see that my packets don't have a lot of the normal TCP options (timestamp, selective ACK, window scaling). So I check with sysctl if these options were enabled or not: net.ipv4.tcp_timestamps = 0 net.ipv4.tcp_sack = 0 net.ipv4.tcp_window_scaling = 0 so they are disable on my normal configuration. Then, I enable the options one by one and see that the net.ipv4.tcp_timestamps option is a part of my problem: with net.ipv4.tcp_timestamps = 0, eeepc_mtu=1492, NAS_mtu=1500 I get problem to download files. with net.ipv4.tcp_timestamps = 1, eeepc_mtu=1492, NAS_mtu=1500 I don't have any problem to download files. The program firestarter modifies the TCP options when it is installed. It seems there is a problem for the atl1c module with the timestamps option disabled and different mtus. On my other laptop with the b44 module, a mtu of 1492 and firestarter I don't have this problem between it and the NAS. Sorry for this lnnng bug report. I can provide tcpdump captures if necessary. Best regards, Guillaume -- System Information: Debian Release: 5.0.5 APT prefers stable APT policy: (987, 'stable'), (985, 'stable'), (500, 'lenny'), (195, 'unstable'), (95, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6-amd64 depends on: ii linux-image-2.6.32-bpo 2.6.32-20~bpo50+1 Linux 2.6.32 for 64-bit PCs linux-image-2.6-amd64 recommends no packages. linux-image-2.6-amd64 suggests no packages. -- debconf-show failed -- 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/20100828092323.6765.13397.report...@baal
Bug#594544: marked as done (initramfs-tools: LVM script too early tries to find volume groups, before partitons are available.)
Your message dated Sat, 28 Aug 2010 09:41:27 +0200 with message-id 20100828074127.gb2...@stro.at and subject line Re: Bug#594544: initramfs-tools: LVM script too early tries to find volume groups, before partitons are available. has caused the Debian Bug report #594544, regarding initramfs-tools: LVM script too early tries to find volume groups, before partitons are available. 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.) -- 594544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594544 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: initramfs-tools Version: 0.98 Severity: normal Tags: squeeze As in subject, megaraid_sas kernel module initializes long enough to crash booting. This problem is probably hardware-specific, in my case it is Dell PowerEdge 1950 with megaraid. As workaround i added sleep 5 command to /scripts/local-top/lvm -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 3.5M Aug 26 21:57 /boot/initrd.img-2.6.32-5-xen-amd64 -rw-r--r-- 1 root root 3.5M Aug 26 20:49 /boot/initrd.img-2.6.32-5-xen-amd64.back -rw-r--r-- 1 root root 4.4M Aug 27 00:49 /boot/initrd.img-2.6.32-5-xen-amd64.local -rw-r--r-- 1 root root 4.4M Aug 27 00:48 /boot/initrd.img-2.6.32-trunk-amd64 -- /proc/cmdline root=/dev/mapper/vg1-root2 ro quiet -- resume RESUME=UUID=53d78982-76ee-4480-900b-83ca8f8e946d -- /proc/filesystems ext4 ext3 -- lsmod Module Size Used by md_mod 73760 0 nf_conntrack_ipv4 9833 0 nf_defrag_ipv4 1139 1 nf_conntrack_ipv4 xt_state1303 0 nf_conntrack 46519 2 nf_conntrack_ipv4,xt_state xt_physdev 1508 0 iptable_filter 2258 0 ip_tables 13899 1 iptable_filter x_tables 12845 3 xt_state,xt_physdev,ip_tables ext3 106502 0 jbd37085 1 ext3 bridge 39630 0 stp 1440 1 bridge xen_evtchn 4339 1 xenfs 9600 1 loop 11783 0 usbhid 33260 0 hid62857 1 usbhid snd_pcm60519 0 snd_timer 15582 1 snd_pcm radeon572779 0 sg 18760 0 ttm40034 1 radeon drm_kms_helper 20065 1 radeon sr_mod 12602 0 snd46446 2 snd_pcm,snd_timer soundcore 4598 1 snd cdrom 29415 1 sr_mod drm 143553 3 radeon,ttm,drm_kms_helper ata_generic 2983 0 snd_page_alloc 6249 1 snd_pcm i5k_amb 4439 0 i2c_algo_bit4225 1 radeon i5000_edac 7284 0 ata_piix 20996 0 i2c_core 15712 4 radeon,drm_kms_helper,drm,i2c_algo_bit rng_core3006 0 bnx2 57321 0 uhci_hcd 18521 0 edac_core 29261 3 i5000_edac dcdbas 5048 0 pcspkr 1699 0 button 4650 0 ehci_hcd 31135 0 processor 36077 0 e1000e110015 0 usbcore 121943 4 usbhid,uhci_hcd,ehci_hcd libata133568 2 ata_generic,ata_piix ses 5128 0 evdev 7352 3 serio_raw 3752 0 psmouse49777 0 enclosure 5503 1 ses nls_base6377 1 usbcore acpi_processor 5087 1 processor,[permanent] ext4 288873 1 mbcache 5050 2 ext3,ext4 jbd2 67015 1 ext4 crc16 1319 1 ext4 dm_mod 53770 22 sd_mod 29761 2 crc_t10dif 1276 1 sd_mod megaraid_sas 29116 1 scsi_mod 122101 6 sg,sr_mod,libata,ses,sd_mod,megaraid_sas thermal11674 0 thermal_sys11942 2 processor,thermal shpchp 26264 0 pci_hotplug21203 1 shpchp -- /etc/kernel-img.conf # Kernel image management overrides # See kernel-img.conf(5) for details do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no -- /etc/initramfs-tools/initramfs.conf MODULES=most BUSYBOX=y KEYMAP=n COMPRESS=gzip BOOT=local DEVICE= NFSROOT=auto -- /etc/initramfs-tools/update-initramfs.conf update_initramfs=yes backup_initramfs=no -- /etc/crypttab # target name source device key file options -- /proc/mdstat Personalities : unused
Bug#594690: please include mptscsih ATA passthrough fix from upstream
Package: linux-2.6 Severity: wishlist Tags: patch I manage a machine that has a LSI SAS controller, reported by lspci as LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08) (lsiutil says model LSI Logic SAS1068E B3, firmware 1.26.00). With the squeeze kernel, I can trigger a controller hangup (and most of the times whole system hangup), by running smartctl on the attached drives (not every time, but a few dozens of smartctl calls seem to suffice). After applying the attached patch, the system works fine, so please consider it for the squeeze release, so I won't need to rebuild my kernel package every time :) Patch is from http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=2a1b7e575b80ceb19ea50bfa86ce0053ea57181d (it has the relevant LKML message in the commit log). -- Petre. From 2a1b7e575b80ceb19ea50bfa86ce0053ea57181d Mon Sep 17 00:00:00 2001 From: Ryan Kuester rkues...@kspace.net Date: Mon, 26 Apr 2010 18:11:54 -0500 Subject: [PATCH] [SCSI] mptsas: fix hangs caused by ATA pass-through I may have an explanation for the LSI 1068 HBA hangs provoked by ATA pass-through commands, in particular by smartctl. First, my version of the symptoms. On an LSI SAS1068E B3 HBA running 01.29.00.00 firmware, with SATA disks, and with smartd running, I'm seeing occasional task, bus, and host resets, some of which lead to hard faults of the HBA requiring a reboot. Abusively looping the smartctl command, # while true; do smartctl -a /dev/sdb /dev/null; done dramatically increases the frequency of these failures to nearly one per minute. A high IO load through the HBA while looping smartctl seems to improve the chance of a full scsi host reset or a non-recoverable hang. I reduced what smartctl was doing down to a simple test case which causes the hang with a single IO when pointed at the sd interface. See the code at the bottom of this e-mail. It uses an SG_IO ioctl to issue a single pass-through ATA identify device command. If the buffer userspace gives for the read data has certain alignments, the task is issued to the HBA but the HBA fails to respond. If run against the sg interface, neither the test code nor smartctl causes a hang. sd and sg handle the SG_IO ioctl slightly differently. Unless you specifically set a flag to do direct IO, sg passes a buffer of its own, which is page-aligned, to the block layer and later copies the result into the userspace buffer regardless of its alignment. sd, on the other hand, always does direct IO unless the userspace buffer fails an alignment test at block/blk-map.c line 57, in which case a page-aligned buffer is created and used for the transfer. The alignment test currently checks for word-alignment, the default setup by scsi_lib.c; therefore, userspace buffers of almost any alignment are given directly to the HBA as DMA targets. The LSI 1068 hardware doesn't seem to like at least a couple of the alignments which cross a page boundary (see the test code below). Curiously, many page-boundary-crossing alignments do work just fine. So, either the hardware has an bug handling certain alignments or the hardware has a stricter alignment requirement than the driver is advertising. If stricter alignment is required, then in no case should misaligned buffers from userspace be allowed through without being bounced or at least causing an error to be returned. It seems the mptsas driver could use blk_queue_dma_alignment() to advertise a stricter alignment requirement. If it does, sd does the right thing and bounces misaligned buffers (see block/blk-map.c line 57). The following patch to 2.6.34-rc5 makes my symptoms go away. I'm sure this is the wrong place for this code, but it gets my idea across. Acked-by: Desai, Kashyap kashyap.de...@lsi.com Signed-off-by: James Bottomley james.bottom...@suse.de --- drivers/message/fusion/mptscsih.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/message/fusion/mptscsih.c b/drivers/message/fusion/mptscsih.c index 5c53624..407cb84 100644 --- a/drivers/message/fusion/mptscsih.c +++ b/drivers/message/fusion/mptscsih.c @@ -2459,6 +2459,8 @@ mptscsih_slave_configure(struct scsi_device *sdev) ioc-name,sdev-tagged_supported, sdev-simple_tags, sdev-ordered_tags)); + blk_queue_dma_alignment (sdev-request_queue, 512 - 1); + return 0; } -- 1.7.2.2
Re: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
On Sat, Aug 28, 2010 at 00:36:31 +0200, Cesare Leonardi wrote: I've also tried (don't know if it make sense) with 2.6.34-1~expermental.2, always with i915.modeset=0: same freeze. OK, it's starting to sound like this 'legacy' experiment is a failure so far. On my 945GM, legacy crashes on UMS on gnome startup (gdm is ok) reporting a lockup. I don't have an i8xx board to play with. Could you guys test the driver pointed at http://lists.freedesktop.org/pipermail/intel-gfx/2010-August/007910.html? (probably with the 2.6.32-20 kernel) Cheers, Julien signature.asc Description: Digital signature
Bug#594697: Xen 4/Linux 2.6.32-5-xen (Squeeze testing): Bridged PV Guests Crash Upon Autostart
Package: linux-image-2.6.32-5-xen-amd64/xen-hypervisor-4.0-amd64/udev Version: 2.6.32-5/4.0.1-rc5/160 The curent Squeeze Xen versions do not work with the current Squeeze udev version. Paravirtualised guests do not autostart. In other words, after creating DomUs with xen-create-image and xm create, if you reboot Dom0, all DomUs will crash and consume maximum CPU time due to known Xen bug #1612. This is a significant limitation, since a system will never automatically reboot to its previous state. According to Xen bug #1612, one solution would be to significantly upgrade to a newer kernel version, or to otherwise path the kernel accordingly. The other solution would be to revert back to udev 151. See http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612 for reference. Thank you for all the work you do! -- GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 -- 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/20100828132754.24...@gmx.net
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
On Sat, 2010-08-28 at 10:35 +0200, Wenceslao González-Viñas wrote: Dear Ben, It seems that the kernel without firmware is not able to load any module. Probably, because the device I am using is 083a:a701 !! . Here is the answer of the things you asked for (after dpkg --purge firmware-ralink ): [...] Why did you do that? Do you still think firmware-ralink is a driver? It is not. You do need firmware-ralink installed. Reinstall it and run those commands again. 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: reassign 594561 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 594561 linux-2.6 2.6.32-20 Bug #594561 [firmware-ralink] firmware-ralink: fails to detect APs at frequency 2.472GHz Bug reassigned from package 'firmware-ralink' to 'linux-2.6'. Bug No longer marked as found in versions firmware-nonfree/0.26. Bug #594561 [linux-2.6] firmware-ralink: fails to detect APs at frequency 2.472GHz There is no source info for the package 'linux-2.6' at version '2.6.32-20' with architecture '' Unable to make a source version for version '2.6.32-20' Bug Marked as found in versions 2.6.32-20. thanks Stopping processing here. Please contact me if you need assistance. -- 594561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594561 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.128300240126730.transcr...@bugs.debian.org
Bug#594189: initramfs-tools: environment variable to disable run_bootloader
On Sat, 2010-08-28 at 09:35 +0100, Colin Watson wrote: On Wed, Aug 25, 2010 at 05:44:32AM +0100, Ben Hutchings wrote: On Tue, 2010-08-24 at 16:55 +0100, Colin Watson wrote: Actually, what I want is a consistent way to disable bootloader invocation for all bootloaders, without necessarily requiring the bootloader package not to be installed (since that's sometimes extremely awkward to arrange). Exactly where this goes I can't say I mind. If the result is an extension to the bootloader/kernel policy that needs to be implemented in each bootloader package, that would be fine too. [...] OK, so something like this: Boot loader packages must be installable on the filesystem in a disabled state where they will not write to the boot sector or other non-filesystem storage. While a boot loader is disabled, any kernel and initramfs hooks it includes must do nothing except (optionally) printing a warning that the boot loader is disabled, and must exit successfully. This is a good start, but it doesn't specify *how* boot loader packages are to be disabled. I think that this needs to be consistent across boot loaders. That would be good, but it is already a problem you have to deal with in creating a live distribution (e.g. you don't want an invocation of 'lilo' without arguments to install on some random disk chosen at build time). I believe it is out of scope for this policy. For what it's worth, I think the basic answer is 'don't create a configuration file'. However, elilo will do that on installation by default, so you need to set debconf variable elilo/runme to false. 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#594697: Xen 4/Linux 2.6.32-5-xen (Squeeze testing): Bridged PV Guests Crash Upon Autostart
On Sat, 2010-08-28 at 15:27 +0200, andr...@gmx.net wrote: Package: linux-image-2.6.32-5-xen-amd64/xen-hypervisor-4.0-amd64/udev Version: 2.6.32-5/4.0.1-rc5/160 The curent Squeeze Xen versions do not work with the current Squeeze udev version. Paravirtualised guests do not autostart. In other words, after creating DomUs with xen-create-image and xm create, if you reboot Dom0, all DomUs will crash and consume maximum CPU time due to known Xen bug #1612. This is a significant limitation, since a system will never automatically reboot to its previous state. According to Xen bug #1612, one solution would be to significantly upgrade to a newer kernel version, or to otherwise path the kernel accordingly. The other solution would be to revert back to udev 151. See http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1612 for reference. Thank you for all the work you do! I believe the fix for this is in the 2.6.32-21 kernel currently present in Sid. Ian. -- Ian Campbell knghtbrd: and the meek shall inherit k-mart signature.asc Description: This is a digitally signed message part
Bug#594189: initramfs-tools: environment variable to disable run_bootloader
On Sat, Aug 28, 2010 at 02:47:56PM +0100, Ben Hutchings wrote: On Sat, 2010-08-28 at 09:35 +0100, Colin Watson wrote: This is a good start, but it doesn't specify *how* boot loader packages are to be disabled. I think that this needs to be consistent across boot loaders. That would be good, but it is already a problem you have to deal with in creating a live distribution (e.g. you don't want an invocation of 'lilo' without arguments to install on some random disk chosen at build time). I believe it is out of scope for this policy. For what it's worth, I think the basic answer is 'don't create a configuration file'. However, elilo will do that on installation by default, so you need to set debconf variable elilo/runme to false. Speaking as the grub2 maintainer, this is not particularly helpful there as the packaging creates a configuration file on installation if requested based on debconf interaction. Of course I can invent some way to change this but I would like that to be consistent with other boot loaders - that being part of the point of this report! -- Colin Watson [cjwat...@debian.org] -- 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/20100828140039.gs12...@riva.ucam.org
Bug#594189: initramfs-tools: environment variable to disable run_bootloader
On Sat, 2010-08-28 at 15:00 +0100, Colin Watson wrote: On Sat, Aug 28, 2010 at 02:47:56PM +0100, Ben Hutchings wrote: On Sat, 2010-08-28 at 09:35 +0100, Colin Watson wrote: This is a good start, but it doesn't specify *how* boot loader packages are to be disabled. I think that this needs to be consistent across boot loaders. That would be good, but it is already a problem you have to deal with in creating a live distribution (e.g. you don't want an invocation of 'lilo' without arguments to install on some random disk chosen at build time). I believe it is out of scope for this policy. For what it's worth, I think the basic answer is 'don't create a configuration file'. However, elilo will do that on installation by default, so you need to set debconf variable elilo/runme to false. Speaking as the grub2 maintainer, this is not particularly helpful there as the packaging creates a configuration file on installation if requested based on debconf interaction. Of course I can invent some way to change this but I would like that to be consistent with other boot loaders - that being part of the point of this report! This doesn't apply to grub2 since it will only update its configuration and not reinstall into the boot sector. I hope I've made this clear when updating the kernel handbook; please review 7.2 and 7.3 of http://kernel-handbook.alioth.debian.org/ch-update-hooks.html. 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: reassign 594676 to linux-2.6, reassign 593549 to linux-2.6, reassign 594165 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 594676 linux-2.6 2.6.32-20~bpo50+1 Bug #594676 [linux-image-2.6-amd64] linux-image-2.6-amd64: Files Download Pb with the atl1c module and my ReadyNAS Bug reassigned from package 'linux-image-2.6-amd64' to 'linux-2.6'. Bug No longer marked as found in versions 2.6.32+27~bpo50+1. Bug #594676 [linux-2.6] linux-image-2.6-amd64: Files Download Pb with the atl1c module and my ReadyNAS There is no source info for the package 'linux-2.6' at version '2.6.32-20~bpo50+1' with architecture '' Unable to make a source version for version '2.6.32-20~bpo50+1' Bug Marked as found in versions 2.6.32-20~bpo50+1. reassign 593549 linux-2.6 2.6.32-18 Bug #593549 [linux-image-2.6-686] linux-image-2.6-686: Missing driver to SD card for toshiba m30 Bug reassigned from package 'linux-image-2.6-686' to 'linux-2.6'. Bug No longer marked as found in versions linux-latest-2.6/28. Bug #593549 [linux-2.6] linux-image-2.6-686: Missing driver to SD card for toshiba m30 There is no source info for the package 'linux-2.6' at version '2.6.32-18' with architecture '' Unable to make a source version for version '2.6.32-18' Bug Marked as found in versions 2.6.32-18. reassign 594165 linux-2.6 2.6.32-20 Bug #594165 [linux-image-2.6-686] linux-image-2.6-686: Kernel panics while transferring data through ethernet on compaq dx2000 ST/CT Bug reassigned from package 'linux-image-2.6-686' to 'linux-2.6'. Bug No longer marked as found in versions linux-latest-2.6/28. Bug #594165 [linux-2.6] linux-image-2.6-686: Kernel panics while transferring data through ethernet on compaq dx2000 ST/CT There is no source info for the package 'linux-2.6' at version '2.6.32-20' with architecture '' Unable to make a source version for version '2.6.32-20' Bug Marked as found in versions 2.6.32-20. thanks Stopping processing here. Please contact me if you need assistance. -- 594165: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594165 593549: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593549 594676: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594676 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.128300515816335.transcr...@bugs.debian.org
Bug#594690: please include mptscsih ATA passthrough fix from upstream
On Sat, 2010-08-28 at 14:49 +0300, Petru Ratiu wrote: Package: linux-2.6 Severity: wishlist Tags: patch Which version(s) does this apply to? 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: reassign 583933 to linux-2.6, reassign 587355 to linux-2.6, reassign 585962 to linux-2.6 ...
Processing commands for cont...@bugs.debian.org: reassign 583933 linux-2.6 Bug #583933 [linux-image-2.6.32-5-amd64] xserver-xorg-video-radeon: Latest radeon + KMS ASIC bug error message Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 'linux-2.6'. reassign 587355 linux-2.6 linux-2.6/2.6.32-15 Bug #587355 [linux-image-2.6.32-5-686] i915: X locks up when trying to play DVD on Thinkpad X40 Bug reassigned from package 'linux-image-2.6.32-5-686' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-15. Bug #587355 [linux-2.6] i915: X locks up when trying to play DVD on Thinkpad X40 Bug Marked as found in versions linux-2.6/2.6.32-15. reassign 585962 linux-2.6 linux-2.6/2.6.32-15 Bug #585962 [linux-image-2.6.32-5-686] Hangs during boot unless radeon.modeset=0 is used Bug reassigned from package 'linux-image-2.6.32-5-686' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-15. Bug #585962 [linux-2.6] Hangs during boot unless radeon.modeset=0 is used Bug Marked as found in versions linux-2.6/2.6.32-15. reassign 589558 linux-2.6 linux-2.6/2.6.32-17 Bug #589558 [linux-image-2.6.32-5-686] Miscalculation of used/available pages on kernel suspend to disk (not suspending) Bug reassigned from package 'linux-image-2.6.32-5-686' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-17. Bug #589558 [linux-2.6] Miscalculation of used/available pages on kernel suspend to disk (not suspending) Bug Marked as found in versions linux-2.6/2.6.32-17. reassign 583949 linux-2.6 2.6.32-5-amd64 Bug #583949 [linux-image-2.6.32-5-amd64] 2.6.32-3-amd64 can't read DVDs/CDs (sometimes) Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 'linux-2.6'. Bug No longer marked as found in versions 2.6.32-5-amd64. Bug #583949 [linux-2.6] 2.6.32-3-amd64 can't read DVDs/CDs (sometimes) There is no source info for the package 'linux-2.6' at version '2.6.32-5-amd64' with architecture '' Unable to make a source version for version '2.6.32-5-amd64' Bug Marked as found in versions 2.6.32-5-amd64. reassign 593679 linux-2.6 linux-2.6/2.6.32-18 Bug #593679 [linux-image-2.6.32-5-amd64] OCFS2: 2 node cluster, kernel BUG at fs/ocfs2/dlm/dlmthread.c:169! Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-18. Bug #593679 [linux-2.6] OCFS2: 2 node cluster, kernel BUG at fs/ocfs2/dlm/dlmthread.c:169! Bug Marked as found in versions linux-2.6/2.6.32-18. reassign 592640 linux-2.6 linux-2.6/2.6.32-18 Bug #592640 [linux-image-2.6.32-5-amd64] [linux-image-2.6.32-5-amd64] FTDI driver broken Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-18. Bug #592640 [linux-2.6] [linux-image-2.6.32-5-amd64] FTDI driver broken Bug Marked as found in versions linux-2.6/2.6.32-18. reassign 592662 linux-2.6 Bug #592662 [linux-image-2.6.32-5-486] cpufrequtils: Cannot set frequency range of policy to full hardware frequency range Bug reassigned from package 'linux-image-2.6.32-5-486' to 'linux-2.6'. reassign 588602 linux-2.6 Bug #588602 [linux-image-2.6.32-5-amd64] xserver-xorg-video-radeon: xpress 200m 5955 = resume from suspend fails with KMS enabled Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 'linux-2.6'. reassign 587215 linux-2.6 linux-2.6/2.6.32-15 Bug #587215 [linux-image-2.6.32-5-686] kernel module for usb ethernet ax8817x 0b95:1780 not working Bug reassigned from package 'linux-image-2.6.32-5-686' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-15 and 2.6.32-15. Bug #587215 [linux-2.6] kernel module for usb ethernet ax8817x 0b95:1780 not working Bug Marked as found in versions linux-2.6/2.6.32-15. found 587215 2.6.32-15 Bug #587215 [linux-2.6] kernel module for usb ethernet ax8817x 0b95:1780 not working There is no source info for the package 'linux-2.6' at version '2.6.32-15' with architecture '' Unable to make a source version for version '2.6.32-15' Bug Marked as found in versions 2.6.32-15. thanks Stopping processing here. Please contact me if you need assistance. -- 587215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587215 592640: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592640 593679: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593679 583933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583933 592662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592662 587355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587355 588602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588602 589558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589558 585962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585962 583949: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583949 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
Processed: tagging 594690
Processing commands for cont...@bugs.debian.org: tags 594690 + moreinfo Bug #594690 [linux-2.6] please include mptscsih ATA passthrough fix from upstream Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 594690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594690 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.128300548918826.transcr...@bugs.debian.org
Bug#594690: please include mptscsih ATA passthrough fix from upstream
On Sat, Aug 28, 2010 at 17:24, Ben Hutchings b...@decadent.org.uk wrote: On Sat, 2010-08-28 at 14:49 +0300, Petru Ratiu wrote: Package: linux-2.6 Severity: wishlist Tags: patch Which version(s) does this apply to? I applied it to 2.6.32-18 from squeeze without any hiccups. As far as i can tell that line made it into main kernel a bit before 2.6.35. The line numbers changed a bit, but that should be all. -- Petre. -- 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/aanlktimzzz_fehjyvgeywxtevjl2ip6z5hv3smdw3...@mail.gmail.com
Bug#594604: linux-image-2.6.32-5-sparc64-smp: Kernel panic - not syncing: Irrecoverable deferred error trap.
On Fri, Aug 27, 2010 at 07:29:13PM -0700, David Miller wrote: From: Josip Rodin j...@debbugs.entuzijast.net Date: Fri, 27 Aug 2010 21:31:37 +0200 David, can you please queue this sunxvr500.c post-2.6.32 bugfix to sta...@kernel.org? http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=bdd32ce95f79fb5cc964cd789d7ae4500bba7c6f Same story as the last one :) As you asked me to last week, I submitted this fix to all of the active branches of -stable earlier this week, so it should show up in the next round of -stable releases. :-) Oh, I'm sorry about that, I actually thought it was a different one. Oh well, better safe than sorry :) Thanks. -- 2. That which causes joy or happiness. -- 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/20100828150515.ga24...@entuzijast.net
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
Ok, I installed them again. Nothing happens (same results of last email) until I type the following (that I got from the internet): echo 'install rt2870sta modprobe --ignore-install rt2870sta ; /bin/echo 083a a701 /sys/bus/usb/drivers/rt2870/new_id' | tee /etc/modprobe.d/rt2870sta.conf depmod -ae update-initramfs -u modprobe rt2870sta After that ... wifi stick gets up, but does not work properly. Results of the commands below: readlink /sys/class/net/wlan0/device/driver --- ../../../../../bus/usb/drivers/usb /sbin/modinfo rt2870sta --- filename: /lib/modules/2.6.32-5-amd64/kernel/drivers/staging/rt2870/rt2870sta.ko version:2.1.0.0 license:GPL description:RT2870/RT3070 Wireless Lan Linux Driver author: Paul Lin paul_...@ralinktech.com firmware: rt3071.bin firmware: rt3070.bin firmware: rt2870.bin srcversion: 081365DAC3DB3AC17D83014 alias: usb:v2019pED14d*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3C0Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v2001p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0077d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p003Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v203Dp1480d*dc*dsc*dp*ic*isc*ip* alias: usb:v04BBp0945d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0283d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p5257d*dc*dsc*dp*ic*isc*ip* alias: usb:v1D4Dp000Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v1D4Dp000Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v07D1p3C0Ad*dc*dsc*dp*ic*isc*ip* alias: usb:v1EDAp2310d*dc*dsc*dp*ic*isc*ip* alias: usb:v1A32p0304d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7711d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3072d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3071d*dc*dsc*dp*ic*isc*ip* alias: usb:v07B8p3070d*dc*dsc*dp*ic*isc*ip* alias: usb:v2019pAB25d*dc*dsc*dp*ic*isc*ip* alias: usb:v1044p800Dd*dc*dsc*dp*ic*isc*ip* alias: usb:v13D3p3273d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9706d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9705d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9703d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7511d*dc*dsc*dp*ic*isc*ip* alias: usb:v18C5p0012d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C12d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p0042d*dc*dsc*dp*ic*isc*ip* alias: usb:v0DF6p003Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v0DB0p3820d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3072d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3071d*dc*dsc*dp*ic*isc*ip* alias: usb:v148Fp3070d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp815Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v0411p00E8d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0071d*dc*dsc*dp*ic*isc*ip* alias: usb:v1737p0070d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7717d*dc*dsc*dp*ic*isc*ip* alias: usb:v7392p7718d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0282d*dc*dsc*dp*ic*isc*ip* alias: usb:v5A57p0280d*dc*dsc*dp*ic*isc*ip* alias: usb:v04E8p2018d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v1482p3C09d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp815Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp805Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v157Ep300Ed*dc*dsc*dp*ic*isc*ip* alias: usb:v129Bp1828d*dc*dsc*dp*ic*isc*ip* alias: usb:v0E66p0003d*dc*dsc*dp*ic*isc*ip* alias: usb:v0E66p0001d*dc*dsc*dp*ic*isc*ip* alias: usb:v15C5p0008d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap6618d*dc*dsc*dp*ic*isc*ip* alias: usb:v13D3p3247d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C25d*dc*dsc*dp*ic*isc*ip* alias: usb:v0471p200Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9702d*dc*dsc*dp*ic*isc*ip* alias: usb:v1740p9701d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CDEp0025d*dc*dsc*dp*ic*isc*ip* alias: usb:v0586p3416d*dc*dsc*dp*ic*isc*ip* alias: usb:v0CDEp0022d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap7522d*dc*dsc*dp*ic*isc*ip* alias: usb:v083Ap8522d*dc*dsc*dp*ic*isc*ip* alias: usb:v083ApA618d*dc*dsc*dp*ic*isc*ip* alias: usb:v083ApB522d*dc*dsc*dp*ic*isc*ip* alias: usb:v15A9p0006d*dc*dsc*dp*ic*isc*ip* alias: usb:v1044p800Bd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp003Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp003Cd*dc*dsc*dp*ic*isc*ip* alias: usb:v07AAp002Fd*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C27d*dc*dsc*dp*ic*isc*ip* alias: usb:v14B2p3C23d*dc*dsc*dp*ic*isc*ip* alias: usb:v050Dp825Bd*dc*dsc*dp*ic*isc*ip* alias:
Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
On Fri, 2010-08-27 at 10:15 +0200, Uwe Kleine-König wrote: This might be related to http://thread.gmane.org/gmane.linux.debian.devel.kernel/54624/ ? Any news there? Kel Modderman seems to have disappeared, haven't heard from him in a long time. If anyone else wants to join pkg-wpa and step up to maintain the packaging for crda, I'd be happy to re-issue my offer of sponsorship to them if pkg-wpa doesn't have sufficient people capable of uploading directly to Debian. Those who want to test them can do the following: apt-get install build-essential devscripts debhelper libnl-dev libssl-dev pkg-config openssl python python-m2crypto svn co svn://svn.debian.org/pkg-wpa/crda/trunk crda cd crda/ uscan --download-current-version debuild sudo debi cd .. svn co svn://svn.debian.org/pkg-wpa/wireless-regdb/trunk wireless-regdb cd wireless-regdb/ uscan --download-current-version debuild sudo debi cd .. I've been using the crda/wireless-regdb packages Kel created for a while and they seem fine but they need someone to step up to maintain them and get them into Debian. I don't have time to do that myself but would be willing to help folks who are interested in doing that. I have not disappeared. Nothing was ever sponsored, though multiple permutations of working packages were produced and annoying problems were found and discussed to no avail. Kel. -- 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/51959.58.174.128.135.1283008910.squir...@webmail.otaku42.de
compache ramswap (new kernel images)
Debian contains new kernel image (2.6.35 in experimental). It supports new technology: compcache http://code.google.com/p/compcache/ =quote This project creates RAM based block device (named ramzswap) which acts as swap disk. Pages swapped to this disk are compressed and stored in memory itself. =end quote There was (is) an ITP to support this feature http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495386 I asked ITP owner (Daniel Baumann) to upload it when 2.6.33 was released eight months ago. He did upload, then he uploaded new version of this package. This package is in NEW stage for seven months: http://ftp-master.debian.org/new/compcache-tools_0.6-1.html I wrote a few mails to ftp-masters (now they are in CC, too), but there was no answer. Does anybody know why this package isn't approved? Today I've installed debian/linux kernel 2.6.35 and want to use this feature and I'm forced to build this package by hand. Why? -- ... mpd is off . ''`. Dmitry E. Oboukhov : :’ : email: un...@debian.org jabber://un...@uvw.ru `. `~’ GPGKey: 1024D / F8E26537 2006-11-21 `- 1B23 D4F8 8EC0 D902 0555 E438 AB8C 00CF F8E2 6537 signature.asc Description: Digital signature
Processed: tagging 549591
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 549591 + pending Bug #549591 [linux-latest-2.6] Bug scripts for image metapackages Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 549591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549591 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.12830162252384.transcr...@bugs.debian.org
Bug#549591: Bug scripts for image metapackages
On Sun, 2009-10-04 at 17:12 +0100, Ben Hutchings wrote: Package: linux-latest-2.6 Severity: wishlist Currently we get bug reports on e.g. linux-image-2.6-686 which do not include any of the useful information that is automatically gathered by bug scripts in the real image packages. The image metapackages should either link to the bug scripts for the real image packages they depend on, or include this control file which I think will have the same effect: Submit-As: linux-2.6 Report-With: real-image-package Unfortunately this doesn't work. reportbug will show some information about the image package, but: 1. It won't call the bug script (that's fixable; we can add a bug script to the meta package that exec's the one in the image package); 2. It won't show the extra related packages listed in the image package's bug control file; 3. It will still use the version number from the meta package (this is the killer). Therefore I have instead added a presubj file which directs users to report against the corresponding image 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
Re: compache ramswap (new kernel images)
On Sat, 2010-08-28 at 20:28 +0400, Dmitry E. Oboukhov wrote: [...] I asked ITP owner (Daniel Baumann) to upload it when 2.6.33 was released eight months ago. He did upload, then he uploaded new version of this package. This package is in NEW stage for seven months: http://ftp-master.debian.org/new/compcache-tools_0.6-1.html I wrote a few mails to ftp-masters (now they are in CC, too), but there was no answer. Does anybody know why this package isn't approved? Daniel Baumann has added or adopted a huge number of packages and apparently overstretched his ability to maintain them properly. I believe the FTP team is preventing him from adding more packages that he cannot be depended on to maintain. Today I've installed debian/linux kernel 2.6.35 and want to use this feature and I'm forced to build this package by hand. Why? If you are able to maintain or co-maintain this package then that might move the FTP team to accept it into the archive. 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: Bug#594623: xserver-xorg-video-intel: after upgrade to 2.12.0+legacy1-1 X freeze on gdm start
Julien Cristau wrote: On Sat, Aug 28, 2010 at 00:36:31 +0200, Cesare Leonardi wrote: I've also tried (don't know if it make sense) with 2.6.34-1~expermental.2, always with i915.modeset=0: same freeze. OK, it's starting to sound like this 'legacy' experiment is a failure so far. On my 965GM it's a huge improvement over the driver in testing which lasts seconds and is unusable. I've been running with it for some time now and only two crashes so far, no accelerated video is the thing I miss most. I'm running on 2.6.34-1 (2.6.35-rc5 was unstable) Regards, M -- 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/e039223b3e530b16bea7eabd1ebf6e6d.squir...@luminoussheep.net
Processed: tagging 594561
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 594561 + pending Bug #594561 [linux-2.6] firmware-ralink: fails to detect APs at frequency 2.472GHz Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 594561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594561 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.128304174425323.transcr...@bugs.debian.org
Processed: tagging 594690
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 594690 + pending Bug #594690 [linux-2.6] please include mptscsih ATA passthrough fix from upstream Added tag(s) pending. End of message, stopping processing here. Please contact me if you need assistance. -- 594690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594690 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.12830451489708.transcr...@bugs.debian.org
Re: Bug#594561: firmware-ralink: fails to detect APs at frequency 2.472GHz
On Sat, 2010-08-28 at 17:21 +0200, k...@otaku42.de wrote: I have not disappeared. My apologies, I hadn't received any RFS mail so I incorrectly assumed. Nothing was ever sponsored, though multiple permutations of working packages were produced and annoying problems were found and discussed to no avail. According to my memory, the packages were ready to upload, just waiting for you to commit to maintaining them and request that someone upload them. Would you like me to upload them? What about getting them into squeeze? -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
