Bug#529719: linux-2.6: please set CONFIG_IDE_TASK_IOCTL=y in Linux build configuration
forcemerge 390616 529719 thanks On Thu, 2009-05-21 at 12:27 +0200, maximilian attems wrote: i don't have the time right now, but irc this has been discussed before and it was disabled due to troubles in the ide core. it's worth to search d-kernel for this. Thanks for the info, merging with the old bug. Once I upgrade to sid again I'll try to test this option. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#529719: linux-2.6: please set CONFIG_IDE_TASK_IOCTL=y in Linux build configuration
Processing commands for cont...@bugs.debian.org: forcemerge 390616 529719 Bug#390616: linux-image-2.6.18: Enable ATA-Security for Sid kernels Bug#529719: linux-2.6: please set CONFIG_IDE_TASK_IOCTL=y in Linux build configuration Forcibly Merged 390616 529719. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529750: linux-image-2.6.26-1-amd64: coretemp reports too-high temperatures on E6600
Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: normal Hi; I had an ACPI critical temperature error which caused a reboot (probably a different bug to this one), and so started looking at my temperatures. Notably, my coretemp readings are worryingly high - on the stock cooler I currently have: CPU Temp:+49.5C (high = +80.0C, hyst = +75.0C) sensor = diode Core 0: +78.0C (high = +78.0C, crit = +100.0C) Core 1: +78.0C (high = +78.0C, crit = +100.0C) (Read while burnP6 is running twice and my big 120mm fan is blasting the CPU HSF.) The first is from w83627ehf sensor on my ABIT IB9 motherboard (i965). Worried about this, I tried the 2.6.25 kernel (same results). That kernel is not tainted by fglrx. BIOS seems to agree roughly with the CPU temp. Booting Windows and running SpeedFan also agrees with this, however Speedfan reports the core temperatures to be around 60-62C while running the Windows burnP6 twice under the same conditions. I theorise that coretemp is overestimating by 15-20C for some reason. I'm told that those temperatures should never be more than 15 or so degrees higher than the BIOS reported one. -- Package-specific info: ** Version: Linux version 2.6.26-1-amd64 (Debian 2.6.26-13) (wa...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-24)) #1 SMP Sat Jan 10 17:57:00 UTC 2009 ** Command line: root=/dev/sda5 ro irqpoll ** Tainted: P (1) ** Kernel log: [7.197309] usbcore: registered new interface driver hiddev [7.301716] scsi4 : SCSI emulation for USB Mass Storage devices [7.301716] usbcore: registered new interface driver usb-storage [7.301716] USB Mass Storage support registered. [7.310690] input: Microsoft Natural� Ergonomic Keyboard 4000 as /class/input/input2 [7.314683] usb-storage: device found at 8 [7.314685] usb-storage: waiting for device to settle before scanning [7.335539] input,hidraw0: USB HID v1.11 Keyboard [Microsoft Natural� Ergonomic Keyboard 4000] on usb-:00:1d.1-2 [7.357797] input: Microsoft Natural� Ergonomic Keyboard 4000 as /class/input/input3 [7.377135] input,hidraw1: USB HID v1.11 Device [Microsoft Natural� Ergonomic Keyboard 4000] on usb-:00:1d.1-2 [7.379225] input: Logitech USB Receiver as /class/input/input4 [7.389695] input,hidraw2: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:00:1d.7-2.1.2 [7.392358] input: Logitech USB Receiver as /class/input/input5 [7.405550] input,hiddev96,hidraw3: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:1d.7-2.1.2 [7.405756] usbcore: registered new interface driver usbhid [7.405786] usbhid: v2.6:USB HID core driver [7.498246] PM: Starting manual resume from disk [7.579877] kjournald starting. Commit interval 5 seconds [7.579877] EXT3-fs: mounted filesystem with ordered data mode. [8.710819] udevd version 125 started [9.466148] end_request: I/O error, dev sr0, sector 13734860 [9.466187] Buffer I/O error on device sr0, logical block 3433715 [9.469052] input: Power Button (FF) as /class/input/input6 [9.489900] end_request: I/O error, dev sr0, sector 13734860 [9.489900] Buffer I/O error on device sr0, logical block 3433715 [9.522180] ACPI: Power Button (FF) [PWRF] [9.524341] input: Power Button (CM) as /class/input/input7 [9.582130] ACPI: Power Button (CM) [PWRB] [ 10.193983] usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0027 [ 10.194050] usbcore: registered new interface driver usblp [ 10.203979] input: PC Speaker as /class/input/input8 [ 10.231979] ACPI: PCI Interrupt :00:1f.3[B] - GSI 19 (level, low) - IRQ 19 [ 10.247979] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008) [ 10.261371] iTCO_wdt: Found a ICH8 or ICH8R TCO device (Version=2, TCOBASE=0x0460) [ 10.261450] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 10.303291] gameport: EMU10K1 is pci:02:05.1/gameport0, io 0xde00, speed 1018kHz [ 10.325431] input: Wacom Bamboo as /class/input/input9 [ 10.379581] usbcore: registered new interface driver wacom [ 10.379617] wacom: v1.48:USB Wacom Graphire and Wacom Intuos tablet driver [ 10.441916] ACPI: PCI Interrupt :02:05.0[A] - GSI 22 (level, low) - IRQ 22 [ 10.441916] PCI: Setting latency timer of device :02:05.0 to 64 [ 10.446950] Installing spdif_bug patch: Audigy 2 ZS [SB0350] [ 10.624614] ACPI: PCI Interrupt :01:00.1[B] - GSI 17 (level, low) - IRQ 17 [ 10.624614] PCI: Setting latency timer of device :01:00.1 to 64 [ 12.338657] Adding 3911788k swap on /dev/sda6. Priority:-1 extents:1 across:3911788k [ 12.378561] usb-storage: device scan complete [ 12.382981] scsi 4:0:0:0: Direct-Access Generic Flash HS-CF 4.44 PQ: 0 ANSI: 0 [ 12.387258] scsi 4:0:0:1: Direct-Access Generic Flash HS-COMBO 4.44 PQ: 0 ANSI: 0 [ 12.391540] sd 4:0:0:0: [sdb] Attached SCSI removable disk [ 12.391540] sd
Bug#529719: linux-2.6: please set CONFIG_IDE_TASK_IOCTL=y in Linux build configuration
On Thu, 21 May 2009, Paul Wise wrote: 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 i don't have the time right now, but irc this has been discussed before and it was disabled due to troubles in the ide core. it's worth to search d-kernel for this. -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I was told that openais 0.83 is a buggy dev version
Hi, I was told not to use openais 0.83, and that openais 0.83 is a buggy dev version, and the real version is the 0.80.x -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523942: linux-image-2.6.26-2-s390 will not boot!
Yes, 15lenny2 was a security update. This fix is queued for 2.6.26-16 which should be included in Debian 5.0.2. Well, I guess that makes sense; since the kernel that is packaged with the Debian installer needs to be replaced too. Even s390x kernels, which are not affected by this bug, are installed with an s390-kernel- based installation system, which is affected by the bug. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529785: [regression] the entire bluetooth stack needs a restart after resume
Package: linux-image-2.6.29-2-amd64 Severity: important Version: 2.6.29-5 Hello, I installed the Debian sid kernel 2.6.29-2-amd64 and, just like the pristine kernels (see http://bugzilla.kernel.org/show_bug.cgi?id=12125), after a hibernate-resume cycle the entire bluetooth stack needs to be restarted in order to work again, while it works without issues in 2.6.26-2-amd64. By restart of the entire bluetooth status I mean I have to: - kill/close all applications using bluetooth (e.g.: gnome-obex-server, blueproximity) - invoke-rc.d bluetooth restart - start again the applications According to the upstream report and my observations it seems the regression appeared sometime during the development of 2.6.27 . Note that I was unable to make a git bisect since I wasn't able to recompile the official debian kernel 2.6.26-2-amd64 in such a way bluetooth worked. I am still confused how somebody should compile the debian kernel to obtain the same kernel as Debian (I tried using make-kpkg on the source from the linux-source-2.6.26 (2.6.26-15lenny2) package. Please tell me what can I do to help fixing this bug. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529697: linux-image-2.6.26-2-686: Crystal 4237b audio card not working and causing kernel freeze during boot
I had a similar problem installing Lenny on an IBM ThinkPad 600 Model 2645-51U, which also has a built-in Crystal Semiconductor CS4237B sound chip. You might want to check out my web site, http://www.wowway.com/~zlinuxman/tp600.htm, to see how I handled the problem. One thing in particular that I noticed is that you blacklisted snd-cs4232, which is good, but you did not blacklist snd-wavefront, which is bad. You need to blacklist snd-wavefront too. There are many other sound tips in there too, including how to get the FM synthesizer to work. Hope this helps. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 528860
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 528860 + pending Bug#528860: linux-image-2.6.26-2-amd64: Kernel panic, not syncing: Aiee, killing interrupt handler There were no tags set. Bug#529261: linux-image-2.6.26-2-686: kernel panic with option selinux=1 in to grub/menu.lst Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529850: Please include firmware for broadcom WLAN bcm43xx
Package: firmware-nonfree Severity: wishlist Version: 0.16 Please add the firmware for the broadcom WLAN bcm43xx series. The firmware can be found on: http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 The firmware has to be extracted with the firmware cutter. On my notebook with bcm4318, this firmware works fine. Regards Bernhard -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
[bts-link] source package linux-2.6
# # bts-link upstream status pull for source package linux-2.6 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #528533 # * http://bugzilla.openvz.org/show_bug.cgi?id=1269 # * remote status changed: (?) - NEW usertags 528533 + status-NEW thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529864: linux-image-2.6.26-1-686-bigmem: CDROM_GET_CAPABILITY ioctl on a xen block device does not return success for cdrom type devices
Package: linux-image-2.6.26-1-686-bigmem Version: 2.6.26-9 Severity: normal The xen block front device driver does not implement the CDROM_GET_CAPABILITY ioctl for virtual cd-rom devices. This prevents udev from correctly identifying such devices and creating a suitable /dev/cdrom symbolic link. Upstream changeset 440a01a7f46742400c74d9d346118523e81d188b (plus 62aa0054da220b8bbe6f23c0eb1d97a99005d0b3 for a small cleanup) implement this ioctl. -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-1-686-bigmem depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93 tools for generating an initramfs ii module-init-tools 3.7-pre9-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.26-1-686-bigmem recommends: ii libc6-i6862.9-6 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-1-686-bigmem suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- debconf information: linux-image-2.6.26-1-686-bigmem/preinst/elilo-initrd-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/postinst/create-kimage-link-2.6.26-1-686-bigmem: true shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-1-686-bigmem/preinst/overwriting-modules-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/postinst/depmod-error-initrd-2.6.26-1-686-bigmem: false linux-image-2.6.26-1-686-bigmem/prerm/would-invalidate-boot-loader-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/postinst/old-initrd-link-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/postinst/bootloader-error-2.6.26-1-686-bigmem: linux-image-2.6.26-1-686-bigmem/preinst/initrd-2.6.26-1-686-bigmem: linux-image-2.6.26-1-686-bigmem/postinst/depmod-error-2.6.26-1-686-bigmem: false linux-image-2.6.26-1-686-bigmem/postinst/old-dir-initrd-link-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/preinst/lilo-has-ramdisk: linux-image-2.6.26-1-686-bigmem/postinst/bootloader-test-error-2.6.26-1-686-bigmem: linux-image-2.6.26-1-686-bigmem/postinst/old-system-map-link-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/prerm/removing-running-kernel-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/postinst/kimage-is-a-directory: linux-image-2.6.26-1-686-bigmem/preinst/failed-to-move-modules-2.6.26-1-686-bigmem: linux-image-2.6.26-1-686-bigmem/preinst/abort-overwrite-2.6.26-1-686-bigmem: linux-image-2.6.26-1-686-bigmem/preinst/abort-install-2.6.26-1-686-bigmem: linux-image-2.6.26-1-686-bigmem/preinst/lilo-initrd-2.6.26-1-686-bigmem: true linux-image-2.6.26-1-686-bigmem/preinst/bootloader-initrd-2.6.26-1-686-bigmem: true -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#414287: me too
My box had lenny (installed in December, before the official release), I just did: apt-get dist-upgrade It upgraded the box from 2.6.26-1 to 2.6.26-2 I did a reboot to get the new kernel On booting, eth0 became eth0_rename_ren I looked at: /etc/udev/rules.d/70-persistent-net.rules and found each MAC listed multiple times, with variations of eth0_rename and eth0, etc I deleted the file completely, rebooted again, and found the interfaces eth1, eth0_rename, eth2_rename and eth3_rename on my system, and each of these describe once in /etc/udev/rules.d/70-persistent-net.rules I edited the file by hand, remove _rename from each of the names, rebooted again and now I have eth0, eth1, eth2, eth3 Now for another reboot - and I still have eth0, eth1, eth2, eth3 now. My biggest concern is that booting without any /etc/udev/rules.d/70-persistent-net.rules gave me three interfaces with _rename appended to their names. One other comment, not sure if it could be related to the issue in any way, but this is a Xen dom0 box, and Xen does it's usual tricks renaming interfaces, but not until after the udev setup. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 529864
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 529864 + pending Bug#529864: linux-image-2.6.26-1-686-bigmem: CDROM_GET_CAPABILITY ioctl on a xen block device does not return success for cdrom type devices There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#445849: can't seem to reproduce this
I performed the test as described with kernel 2.6.26-1-xen-amd64 and it worked OK. I couldn't test 2.6.26-2 due to other bugs, but unless there has been a regression (which I doubt) I think that this one is fixed. -- Russell Coker russ...@coker.com.au http://etbe.coker.com.au/ My Blog http://etbe.coker.com.au/category/security/ My Security blog posts http://www.coker.com.au/selinux/play.html My Play Machine, root PW SELINUX -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529870: linux-image-2.6.26-2-686: Kernel panic when using SE Linux
Package: linux-image-2.6.26-2-686 Version: 2.6.26-15lenny2 Severity: important In my tests the latest 2.6 kernels for i386 (both Xen and non-Xen) and for AMD64 Xen will crash if SE Linux is enabled. The crash occurs even if SE Linux is in permissive mode, so the kernel parameter selinux=0 is required to boot the machine after installing such a kernel. Here is a back-trace from an AMD64 system: [8.252947] kernel BUG at security/selinux/avc.c:883! [8.252954] invalid opcode: [1] SMP [8.252961] CPU 0 [8.252966] Modules linked in: ext3 jbd mbcache thermal_sys [8.252978] Pid: 0, comm: swapper Not tainted 2.6.26-2-xen-amd64 #1 [8.252985] RIP: e030:[802e61dd] [802e61dd] avc_has_perm_noaudit+0x26/0x379 [8.253002] RSP: e02b:80595a00 EFLAGS: 00010246 [8.253008] RAX: RBX: 0011 RCX: [8.253015] RDX: 0011 RSI: 0009 RDI: 0001 [8.253022] RBP: 0009 R08: R09: 80595ab0 [8.253028] R10: 0007 R11: 803e932b R12: 0011 [8.253034] R13: 0001 R14: 0009 R15: 80595b40 [8.253044] FS: 7f7e2649f6e0() GS:80539000() knlGS: [8.253053] CS: e033 DS: ES: [8.253059] DR0: DR1: DR2: [8.253066] DR3: DR6: 0ff0 DR7: 0400 [8.253073] Process swapper (pid: 0, threadinfo 80552000, task 804fe460) [8.253081] Stack: 80595ab0 0012 [8.253095] 00128812 0001000c 804fe460 [8.253106] 0001 80595b90 8026fe3e [8.253115] Call Trace: [8.253122] IRQ [8026fe3e] ? mod_zone_page_state+0x2c/0x5b [8.253135] [802e7049] ? avc_has_perm+0x2b/0x5b [8.253143] [802efd58] ? sel_netport_sid+0x13b/0x16b [8.253151] [802e9ec1] ? selinux_ip_postroute+0x1eb/0x38b [8.253160] [803dfab8] ? nf_iterate+0x41/0x7d [8.253168] [803e8e81] ? ip_finish_output+0x0/0x241 [8.253175] [803dfb51] ? nf_hook_slow+0x5d/0xbe [8.253182] [803e8e81] ? ip_finish_output+0x0/0x241 [8.253189] [803e93b4] ? ip_output+0x89/0xa1 [8.253196] [803e8b3d] ? ip_local_out+0x9/0x1f [8.253204] [803e8e12] ? ip_push_pending_frames+0x2bf/0x32e [8.253211] [804075b4] ? icmp_send+0x4fc/0x54b [8.253220] [8020e911] ? xen_clocksource_read+0xd/0x9c [8.253228] [8020e9f1] ? profile_pc+0x21/0x53 [8.253235] [803e08a8] ? ipv4_link_failure+0x15/0x45 [8.253242] [804051cb] ? arp_error_report+0x24/0x2d [8.253250] [803cdcb2] ? neigh_timer_handler+0x21d/0x313 [8.253257] [803cda95] ? neigh_timer_handler+0x0/0x313 [8.253264] [802356b7] ? run_timer_softirq+0x190/0x237 [8.253273] [80231ca0] ? __do_softirq+0x77/0x103 [8.253280] [8020c13c] ? call_softirq+0x1c/0x28 [8.253287] [8020e08a] ? do_softirq+0x55/0xbb [8.253294] [8020e16d] ? do_IRQ+0x7d/0x9a [8.253301] [8037d41c] ? evtchn_do_upcall+0x13c/0x1fc [8.253309] [8020bbde] ? do_hypervisor_callback+0x1e/0x30 [8.253315] EOI [8020e795] ? xen_safe_halt+0x90/0xa6 [8.253326] [8020a0c8] ? xen_idle+0x2e/0x66 [8.253332] [80209cd6] ? cpu_idle+0x97/0xb9 [8.253338] [8.253342] [8.253346] Code: 41 5e 41 5f c3 41 57 41 56 41 89 f6 41 55 41 89 fd 41 54 55 53 48 83 ec 68 85 c9 89 4c 24 18 44 89 44 24 14 4c 89 4c 24 08 75 04 0f 0b eb fe 0f b7 f2 48 c7 c0 50 f6 58 80 46 8d 24 b5 00 00 00 [8.253408] RIP [802e61dd] avc_has_perm_noaudit+0x26/0x379 [8.253417] RSP 80595a00 [8.253424] ---[ end trace a7e19496a9366ab4 ]--- [8.253431] Kernel panic - not syncing: Aiee, killing interrupt handler! I can provide i386 back-traces if desired. If you want a non-Xen back-trace I could do that too, but getting a serial console going would take a little time so I hope you can track this down without it. -- Package-specific info: -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-686 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.92o tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of
Bug#529850: Please include firmware for broadcom WLAN bcm43xx
On Thu, 2009-05-21 at 21:19 +0200, Bernhard wrote: Package: firmware-nonfree Severity: wishlist Version: 0.16 Please add the firmware for the broadcom WLAN bcm43xx series. The firmware can be found on: http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 The firmware has to be extracted with the firmware cutter. What? How? You'll have to be a bit more explicit. I don't see anything looking like a firmware blob in the C sources or any licence text applying to the object files. Ben. On my notebook with bcm4318, this firmware works fine. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Bug#525220:
Sorry Dominique, when i have hcid stopped i can't do nothing, i try with a tip, umount /proc/bus/usb works some times... but few minuts more later this stop to work too i still can't transfers files or do any thing. i hear some thing about in newer version of bluez this works... what do you know? Greetings! -- Maximiliano Augusto Castañón Araneda Santiago, Chile Linux user # 394821
Processed: reassign 529870 to linux-2.6, forcibly merging 528860 529870
Processing commands for cont...@bugs.debian.org: reassign 529870 linux-2.6 Bug#529870: linux-image-2.6.26-2-686: Kernel panic when using SE Linux Bug reassigned from package `linux-image-2.6.26-2-686' to `linux-2.6'. forcemerge 528860 529870 Bug#528860: linux-image-2.6.26-2-amd64: Kernel panic, not syncing: Aiee, killing interrupt handler Bug#529870: linux-image-2.6.26-2-686: Kernel panic when using SE Linux Bug#529261: linux-image-2.6.26-2-686: kernel panic with option selinux=1 in to grub/menu.lst Forcibly Merged 528860 529261 529870. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 529870 to linux-2.6, forcibly merging 528860 529870
reassign 529870 linux-2.6 forcemerge 528860 529870 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525220:
Dominique, you can try to to transfers files umount /proc/bus/usb http://osdir.com/ml/linux.bluez.user/2003-07/msg00129.html https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502 Greetings! -- Maximiliano Augusto Castañón Araneda Santiago, Chile Linux user # 394821
Bug#521279: Bug#521280: acpid does support netlink, so the problem only affects thinkpad-acpi
On Thu, Mar 26, 2009 at 12:44:32PM -0300, Henrique de Moraes Holschuh wrote: never had to look back at, before writing something. The non-hotkey events go over netlink, yes. But hotkeys go only over the input device, where they belong, and there is no driver switch to mess with that. Could anyone enlighten me please, where these events are to be found? acpid does not just read the netlink inteface but also the input layer and thus is *supposed* to also get events coming over an input device. You can use kacpimon to try it out. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: mes...@jabber.org Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529870: Confirmed on intel
I'm also getting this on a new intel server. The stack trace looked different and I (unfortunately) didn't have a way to save the crash dump but it said: *kernel BUG at security/selinux/avc.c:883* -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
