Bug#510568: usb powersave?
Maybe is due to usb powersave? I turned off it on that port ( echo -1 /sys/bus/usb/devices/usb1/power/autosuspend ) to check it. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508173: Acknowledgement (fbdev/logo: Corrupted SPE penguins on PS3)
Hi Geert, Geert Uytterhoeven wrote: Patch available in http://lkml.org/lkml/2008/12/9/78 The bugzilla entry has been closed, but the patch doesn't appear in the current Linus git tree so far. What's the merge status? Patches need to be merged into mainline prior to inclusion in Debian. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#446964: linux-image-2.6.18-5-686: kernel BUG at fs/exec.c:1459!
On Wed, Oct 17, 2007 at 01:26:22AM +0200, Michal Pokrywka wrote: Package: linux-image-2.6.18-5-686 Version: 2.6.18.dfsg.1-13etch4 Severity: normal System was rebooted 2 days ago due to kernel security update, I was trying to read some mail using mutt when app crashed and kernel left info about some problem: Oct 16 21:31:30 server kernel: [ cut here ] Oct 16 21:31:30 server kernel: kernel BUG at fs/exec.c:1459! Oct 16 21:31:30 server kernel: invalid opcode: [#1] Oct 16 21:31:30 server kernel: SMP Oct 16 21:31:30 server kernel: Modules linked in: tcp_diag inet_diag act_police sch_ingress cls_fw cls_u32 sch_sfq sch_htb ipt_ULOG ipt_owner xt_CONNMARK xt_multiport xt_MARK xt_helper xt_mac ipt_LOG xt_limit ipt_REDIRECT xt_tcpudp ip_nat_sip ip_conntrack_sip ip_nat_irc ip_conntrack_irc ip_nat_h323 ip_conntrack_h323 ip_nat_ftp ip_conntrack_ftp iptable_mangle iptable_nat ip_nat iptable_filter ip_tables x_tables reiserfs raid0 md_mod w83781d hwmon_vid i2c_isa ip_conntrack nfnetlink parport_pc parport rtc floppy psmouse pcspkr serio_raw evdev ext3 jbd mbcache dm_mirror dm_snapshot dm_mod ide_disk 3c59x e100 mii siimage pdc202xx_old shpchp pci_hotplug piix uhci_hcd i2c_piix4 i2c_core usbcore generic ide_core intel_agp agpgart thermal processor fan Oct 16 21:31:30 server kernel: CPU:0 Oct 16 21:31:30 server kernel: EIP:0060:[c01636e6]Not tainted VLI Oct 16 21:31:30 server kernel: EFLAGS: 00010282 (2.6.18-5-686 #1) Oct 16 21:31:30 server kernel: EIP is at do_coredump+0x1da/0x4f8 Oct 16 21:31:30 server kernel: eax: d7bac5b4 ebx: c54c8aa0 ecx: d7bac580 edx: 0001 Oct 16 21:31:31 server kernel: esi: d7bac580 edi: c4809550 ebp: e90c2ec4 esp: cc0bde40 Oct 16 21:31:31 server kernel: ds: 007b es: 007b ss: 0068 Oct 16 21:31:31 server kernel: Process mutt (pid: 22432, ti=cc0bc000 task=c4809550 task.ti=cc0bc000) Oct 16 21:31:31 server kernel: Stack: cc0bdfbc 000b 000b 03e8 d7bac580 c02cdc70 Oct 16 21:31:31 server kernel: b7c74326 055c0073 bfa950d8 c011670b c4809550 c4809550 d24ce6e0 0082 Oct 16 21:31:31 server kernel: 0082 0046 c48099cc d7d07924 cc0bdf34 c0126258 000b 000b Oct 16 21:31:31 server kernel: Call Trace: Oct 16 21:31:31 server kernel: [c011670b] task_rq_lock+0x31/0x58 Oct 16 21:31:31 server kernel: [c0126258] __dequeue_signal+0x151/0x15c Oct 16 21:31:31 server kernel: [c0127429] dequeue_signal+0x15/0x9c Oct 16 21:31:31 server kernel: [c0127a66] get_signal_to_deliver+0x38e/0x3bc Oct 16 21:31:31 server kernel: [c011532c] do_page_fault+0x0/0x481 Oct 16 21:31:31 server kernel: [c01023a6] do_notify_resume+0x71/0x5d7 Oct 16 21:31:31 server kernel: [c01151f1] force_sig_info_fault+0x24/0x28 Oct 16 21:31:31 server kernel: [c027f00a] schedule+0x84e/0x8fe Oct 16 21:31:31 server kernel: [c01157a4] do_page_fault+0x478/0x481 Oct 16 21:31:31 server kernel: [c011532c] do_page_fault+0x0/0x481 Oct 16 21:31:31 server kernel: [c0102d0a] work_notifysig+0x13/0x19 Oct 16 21:31:31 server kernel: Code: 00 00 85 c0 74 0f c7 87 f8 00 00 00 00 00 00 00 e8 1c 2f fb ff 85 ed 74 09 8d 44 24 68 e8 f3 b9 11 00 83 be 8c 01 00 00 00 74 08 0f 0b b3 05 1e aa 29 c0 85 ed 0f 88 04 03 00 00 89 e0 25 00 e0 Oct 16 21:31:31 server kernel: EIP: [c01636e6] do_coredump+0x1da/0x4f8 SS:ESP 0068:cc0bde40 System worked without problems (and reboot) for last couple of months acting as network gateway doing NAT, proxy (squid), small web server and windows file server (samba). After this bug system seems to work ok, only there's this mutt process stuck in D state - few MB wasted, but there's plenty of ram left :) Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#447029: linux-image-2.6.22-2-686: unknown NMI on resume on thinkpad T60p
On Wed, Oct 17, 2007 at 03:14:07AM -0400, Jerry Quinn wrote: Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: normal When I resume after sleep, I get the following messages on consoles and in the kernel log: Message from sysl...@naga at Wed Oct 17 02:55:24 2007 ... naga kernel: Uhhuh. NMI received for unknown reason a0 on CPU 0. Message from sysl...@naga at Wed Oct 17 02:55:24 2007 ... naga kernel: You have some hardware problem, likely on the PCI bus. Message from sysl...@naga at Wed Oct 17 02:55:24 2007 ... naga kernel: Dazed and confused, but trying to continue The system appears to keep working normally despite the messages. This is a thinkpad T60p with 2G memory. I can reproduce this problem on an untainted kernel. The taint is from the madwifi driver. This bug has been present in kernels since 2.6.18. I'm pretty sure this is not due to the particular laptop being broken. I transferred my drive into an identical machine and the same problem happens there. Does this error still occur with more recent kernel versions? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#446323: mdadm: recovery in infinite loop
fOn Wed, Oct 17, 2007 at 04:16:39PM -0500, Lukasz Szybalski wrote: On 10/15/07, Neil Brown ne...@suse.de wrote: As you say, the devices are exactly the same size, thanks. On Monday October 15, szybal...@gmail.com wrote: how do I undo? mdadm /dev/md2 -f /dev/hda2 So I could try the sync in init 1 Lucas Well, you could: mdadm /dev/md2 -f /dev/hda2 mdadm /dev/md2 -r /dev/hda2 then when you are ready to try again mdadm /dev/md2 -a /dev/hda2 Ok, So I went into init 1 to get rid of any program that might want to access the hda2. I unmounted my '/files' which mounts my hda2 in '/' folder. I was watching it as it went for 30 min to sync the drives and suddenly I got unrecognizable error 5 i believe it was. Unable to read sector lba 88604764 on hdb1. I guess that showed up in stderr or something because I couldn't find reference to it anywhere other then a terminal screen. What would be the proper command for testing every single block on that hardrive using e2fsck I used e2fsck -acf /dev/hdb2 but that took all night and it still wasn't finished. I've canceled it. What would be the proper options for this command that would get me to clean this drive. The weird part is when I checked the drives last Thursday using knoppix nothing has shown any problems or bad sectors. I think there must be something odd happening with the drive or controller. I notice that the two devices are on the same IDE channel, which is sometimes a source of problems, though it should behave like this. If you feel up to patching the kernel, recompiling, and experimenting, I can send you a patch which should provide more detailed information on what is happening. Let me know what kernel version you will be working with. Never done recompiling of a kernel before, but I guess if everything fails then we can try it. For now let me clean this drive and we go from there. What's the status of this bug? Does this error still occur with more recent kernel versions? If you're running Etch, you could try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4: http://packages.qa.debian.org/l/linux-2.6.24.html Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: add firmware-ipw2x00 to lenny?
[Followup-To: header set to gmane.linux.debian.devel.release.] On 2009-01-04, Paul Wise p...@debian.org wrote: Hi all, Would it be possible to unblock firmware-nonfree 0.14 from unstable? This would add a firmware-ipw2x00 package so that users with old Intel wireless on their laptops can have it work out of the box. This is the kind of thing that might be added to lennyandahalf, but we may as well add it before the release IMO. I've verified that this makes the wireless work on an old thinkpad have with me. The changelog is this: firmware-nonfree (0.14) unstable; urgency=low . * Generate license acceptation prompt, based on sun-java5. (closes: #504668) * Add Intel Pro 2100 firwmare, version 1.3. (closes: #504671) * Add Intel Pro 2200/2915 firwmare, version 3.0. (closes: #449235) Indeed, it works very well with my ipw2200. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 509992 to linux-2.6
reassign 509992 linux-2.6 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510695: type in included config file for cman initscript
Package: cman Version: 2.20081102-1 Severity: normal The file /etc/init.d/cman contains an include statement for an options file in /etc/defaults/cman -- but I found /etc/default/cman on mine. I suspect this is a type in the initscript. -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.26-1-486 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 cman depends on: ii debconf [debconf-2.0] 1.5.24Debian configuration management sy ii libc6 2.7-16GNU C Library: Shared libraries ii libcman2 2.20081102-1 Red Hat cluster suite - cluster ma ii libdlm22.20081102-1 Red Hat cluster suite - distribute ii libnet-snmp-perl 5.2.0-1 Script SNMP connections ii libnet-telnet-perl 3.03-3Script telnetable connections ii libnss3-1d 3.12.0-5 Network Security Service libraries ii libopenais20.83-1Standards-based cluster framework ii libvirt0 0.4.6-10 library for interfacing with diffe ii libxml22.6.32.dfsg-5 GNOME XML library ii openais0.83-1Standards-based cluster framework ii python 2.5.2-3 An interactive high-level object-o ii python-pexpect 2.1-1 Python module for automating inter ii sg3-utils 1.24-2Utilities for working with generic cman recommends no packages. cman suggests no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#456339: lm-sensors: couldn't get subfeature on applesmc
On Sat, Dec 27, 2008 at 11:30:45PM +0100, Filippo Giunchedi wrote: On Sat, Dec 27, 2008 at 02:27:42PM +0100, Moritz Muehlenhoff wrote: [...] It really looks like it is a kernel problem. Reassigning the bug. Filippo, does this error still occur with more recent kernel versions? It doesn't, though I'm running 2.6.26.3 with mactel patches (from https://mactel-linux.svn.sourceforge.net/svnroot/mactel-linux/trunk/kernel ) which contain some changes to applesmc, I can try with a vanilla/debian kernel in the following days if needed. It does with 2.6.26-1-amd64 (package is at 2.6.26-12) go...@clamp:/sys/class/hwmon/hwmon2/device$ cat temp*_input cat: temp10_input: Input/output error 30750 cat: temp2_input: Input/output error 53000 cat: temp4_input: Input/output error 50500 cat: temp6_input: Input/output error 52750 cat: temp8_input: Input/output error 53250 go...@clamp:/sys/class/hwmon/hwmon2/device$ uname -a Linux clamp 2.6.26-1-amd64 #1 SMP Mon Dec 15 17:25:36 UTC 2008 x86_64 GNU/Linux but doesn't with 2.6.28 (applesmc moved to hwmon0) go...@clamp:/sys/class/hwmon/hwmon0/device$ cat temp*_input 53000 30750 54750 53250 51500 51000 58000 55500 52750 52750 go...@clamp:/sys/class/hwmon/hwmon0/device$ uname -a Linux clamp 2.6.28 #1 SMP Tue Dec 30 16:31:27 CET 2008 x86_64 GNU/Linux go...@clamp:/sys/class/hwmon/hwmon0/device$ thanks, filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: Everyone is entitled to his own opinion, but not his own facts. -- Daniel Patrick Moynihan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 375149
Processing commands for cont...@bugs.debian.org: tags 375149 + ipv6 Bug#375149: Linux kernel IPv6 : random TCP connection failure There were no tags set. Tags added: ipv6 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#375523: hdaps fails to read gyroscope after suspend/resume
On Sun, Dec 21, 2008 at 11:28:48AM +0100, Moritz Muehlenhoff wrote: Does this error still occur with more recent kernel versions? My thinkpad motherboard died last year, and it's beyond warranty and way too expensive to repair/replace, so I'm afraid I cannot test. --Jeroen -- Jeroen van Wolffelaar jer...@wolffelaar.nl (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 509992 to src:linux-2.6
reassign 509992 src:linux-2.6 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 510654
Processing commands for cont...@bugs.debian.org: # Fixed in debian kernel SVN tags 510654 patch pending Bug#510654: linux-2.6: [hppa] UP-optimized flush_tlb_mm is broken There were no tags set. Tags added: patch, 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#484593: linux-image-2.6.25-2-686: su gets stuck for root -- stty getting stuck in T state
On Thu, Jun 05, 2008 at 02:03:29PM +1000, Tim Connors wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal There's an upstream bug that has started affecting me. stty gets backgrounded, and you can only kill -9 it to get your shell back. A thread titled su gets stuck for root is on LKML with all the details, and when there's an eventual patch, it would be good to include it in the debian patchset. Does this error still occur with the Lenny kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#453382: linux-source-2.6.18: UDF filsystem driver report errors
On Thu, Nov 29, 2007 at 10:09:07AM +0100, Jean-Michel wrote: Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-12etch2 Severity: normal As some errors occurs in UDF filesystem, I recompiled this module to activate log/debug facility. Hereafter I detail first (1) user reported error, and second (2), logd error in syslog. Finally (3), the linux packages installed.. Does this error still occur with more recent kernel versions? Can you rule out a hardware error? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#461730: linux-2.6: Cannot pair with bluetooth headset with 2.6.21+
On Sun, Jan 20, 2008 at 05:12:29AM -0500, Frédéric Brière wrote: Package: linux-2.6 Version: 2.6.21-6 Severity: normal I recently tried and failed to pair with a bluetooth headset that used to work some time ago. Specifically, any attempt to establish a connection to the device (with hcitool cc) would appear to be successful, with hci_create_connection() returning 0, yet no connection could be found. After a few joyful hours of downgrading and rebooting, it turns out that the kernel is to blame. I'm getting this erratic behavior with 2.6.21-2-k7 and 2.6.23-1-686, but not with 2.6.18-5-k7. (I couldn't test 2.6.20-1-k7, due to the PATA bug.) I'm reluctant at this point to spend more time compiling/rebooting on my own if it may turn out to be useless after all. However, if you need more information and/or want me to try stuff out, I'd be glad to do my part. Just let me know how I should proceed from here. Does this error still occur with the Lenny kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#463498: b43: Selects wrong driver?
On Sun, Jan 04, 2009 at 06:20:46PM +0100, Moritz Muehlenhoff wrote: Is the kernel issue of detecting your card with the proper driver resolved in the Lenny kernel? (Leaving the udev rename issue referenced later aside) As far as I know, it was only the udev issue and never a kernel issue for me. Atleast, with the proper udev rules I have no problem anymore. But you could probably argue that the kernel shouldn't get into a wrong state because you did something on the wrong devicename. Kurt -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#463498: b43: Selects wrong driver?
On Fri, Feb 01, 2008 at 12:58:57AM +0100, Kurt Roeckx wrote: Package: linux-2.6 Version: 2.6.24-1 Hi, It seems that the kernel does not select the proper driver for me. When booting a 2.6.22 (and .23) kernel, I see: bcm43xx driver PCI: Enabling device :02:00.0 ( - 0002) ACPI: PCI Interrupt :02:00.0[A] - Link [LNKA] - GSI 10 (level, low) - IRQ 10 PCI: Setting latency timer of device :02:00.0 to 64 bcm43xx: Chip ID 0x4306, rev 0x3 bcm43xx: Number of cores: 5 bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243 bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243 bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243 bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off udev: renamed network interface eth1 to eth3 cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7 cs: IO port probe 0x800-0x8ff: clean. cs: IO port probe 0xc00-0xcff: clean. cs: IO port probe 0xa00-0xaff: clean. Adding 771080k swap on /dev/hda5. Priority:-1 extents:1 across:771080k b43-phy0: Broadcom 4306 WLAN found phy0: Selected rate control algorithm 'simple' udev: renamed network interface wmaster0 to eth3 Adding 771080k swap on /dev/hda5. Priority:-1 extents:1 across:771080k EXT3 FS on hda1, internal journal Driver 'sr' needs updating - please use bus_type methods device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-de...@redhat.com input: b43-phy0 as /class/input/input8 Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio But this b43 driver doesn't seem to be working for me. I notice some strange behaviours with this: - After the udev: renamed network interface wmaster0 to eth3 it hangs for several seconds before doing something else. At that point something prints done on the screen which doesn't come from the kernel. (Manual modprobing b43 doesn't seem to cause this problem.) - When looking at the interface list I see a eth3 that doesn't have wireless extentions, and a wlan0_rename that does. I also have 1 more device than I should. Reading http://linuxwireless.org/en/users/Drivers/b43 it says: 4306 and 4309 cards with a MAC core revision of 4 or less should also use b43legacy. [...] The kernel autoloader will automatically do the right thing and load the correct driver for your device. If I read the dmesg above right I have a 4306 with MAC core revision 3, so I should use b43legacy. It seems to me that it's not doing the right thing here. So I've tried rmmod b43 and modprobe b43legacy but that doesn't seem to be doing much. Is the kernel issue of detecting your card with the proper driver resolved in the Lenny kernel? (Leaving the udev rename issue referenced later aside) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#456219: xserver-xorg-video-intel: causes excessive interrupts with compiz
On Fri, Dec 14, 2007 at 11:21:06AM +0100, Michel Dänzer wrote: reassign 456219 linux-2.6 kthxbye On Thu, 2007-12-13 at 18:58 +, brian m. carlson wrote: According to [0], the graphics driver uses an interrupt for OpenGL compatibility. On my machine, that results in approximately 70 wakeups per second when idle, if I use compiz. Please fix the driver so it does not need this interrupt anymore, which will save power. I realize this will not be fixed immediately, but please report this upstream if it has not been already. A fix is already available in the upstream drm Git branch vblank-rework. It's almost ready to be merged to the master branch (and consequently to the Linux kernel) but there are still some issues to be worked out. I don't think the X driver can handle this better, so I'm reassigning to the kernel. The DRM changes have been merged in 2.6.27. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508108: Reopening, bug not fixed in 2.6.26-12
found 2.6.26-12 thanks Hi, Contrary to what 2.6.26-12 changelog says, the Sparc XVR framebuffer drivers (CONFIG_FB_XVR500, CONFIG_FB_XVR2500) were NOT enabled in it: ju...@droopy:~/tmp$ dpkg -x linux-image-2.6.26-1-sparc64-smp_2.6.26-12_sparc.deb tmp ju...@droopy:~/tmp$ grep -i xvr tmp/boot/config-2.6.26-1-sparc64-smp # CONFIG_FB_XVR500 is not set # CONFIG_FB_XVR2500 is not set Please enable them for the next upload (which will hopefully make it into lenny). Thanks. -- Jurij Smakov ju...@wooyd.org Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Reopening
Processing commands for cont...@bugs.debian.org: found 508108 2.6.26-12 Bug#508108: Please enable XVR-500 and XVR-2500 fb drivers for sparc Bug marked as found in version 2.6.26-12 and reopened. 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#496111: marked as done (linux-image-2.6.26-1-amd64: iwl-wifi dumps stacks)
Your message dated Sun, 4 Jan 2009 15:00:06 +0100 with message-id 20090104140006.gb3...@galadriel.inutil.org and subject line Re: linux-image-2.6.26-1-amd64: iwl-wifi dumps stacks has caused the Debian Bug report #496111, regarding linux-image-2.6.26-1-amd64: iwl-wifi dumps stacks 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.) -- 496111: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-2 Severity: normal With the latest kernels, my wifi card somehow floods the kern.log with backtraces. Though I've seen no problems with the network whatsoever. It's just that it floods quite a lot (I've put here a short excerpt). [83892.115716] wlan0: switched to short barker preamble (BSSID=00:1b:11:4e:42:c9) [83892.115716] [ cut here ] [83892.115716] WARNING: at include/../net/mac80211/rate.h:153 rs_get_rate+0xce/0x420 [iwl3945]() [83892.115716] Modules linked in: tun binfmt_misc rfcomm l2cap ipv6 cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_conservative microcode nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc xfs sha256_generic aes_x86_64 aes_generic cbc dm_crypt i915 drm snd_hda_intel snd_pcm_oss snd_mixer_oss arc4 ecb crypto_blkcipher snd_pcm hci_usb iwl3945 rng_core bluetooth mac80211 snd_timer i2c_i801 video output snd led_class yenta_socket rsrc_nonstatic iTCO_wdt joydev battery soundcore snd_page_alloc ac button psmouse serio_raw cfg80211 evdev intel_agp usbhid hid ff_memless reiserfs dm_mirror dm_log dm_snapshot dm_mod sg sr_mod sd_mod cdrom ide_pci_generic ide_core ata_piix b44 ata_generic libata scsi_mod dock ohci1394 ricoh_mmc ieee1394 sdhci mmc_core ssb pcmcia pcmcia_core firmware_class mii ehci_hcd uhci_hcd thermal fan intelfb i2c_algo_bit i2c_core coretemp acpi_cpufreq freq_table processor thermal_sys [83892.115716] Pid: 2025, comm: iwl3945 Not tainted 2.6.26-1-amd64 #1 [83892.115716] [83892.115716] Call Trace: [83892.115716] [80234878] warn_on_slowpath+0x51/0x7a [83892.115716] [8031f019] sprintf+0x51/0x59 [83892.115716] [8031ef7f] vsnprintf+0x568/0x5b1 [83892.115716] [a02b489f] :iwl3945:rs_get_rate+0xce/0x420 [83892.115716] [8024aab2] getnstimeofday+0x39/0x98 [83892.115716] [80228c50] update_curr+0x44/0x6f [83892.115716] [80248beb] ktime_get+0xc/0x41 [83892.115716] [a0278707] :mac80211:rate_control_get_rate+0x79/0xdd [83892.115716] [a027d4ee] :mac80211:ieee80211_tx_h_rate_ctrl+0x31/0xfa [83892.115716] [a027e260] :mac80211:ieee80211_master_start_xmit+0x1e8/0x39b [83892.115716] [803cbabf] __qdisc_run+0xc0/0x1b3 [83892.115716] [803bcdae] dev_queue_xmit+0x179/0x2b3 [83892.115716] [a02754d0] :mac80211:ieee80211_associated+0xe9/0x185 [83892.115716] [a026fb79] :mac80211:sta_info_insert+0x135/0x169 [83892.115716] [a0275ac9] :mac80211:ieee80211_rx_mgmt_assoc_resp+0x55d/0x56f [83892.115716] [a0276901] :mac80211:ieee80211_sta_rx_queued_mgmt+0x5fa/0xe8d [83892.115716] [a027dd88] :mac80211:__ieee80211_tx+0x88/0x131 [83892.115716] [a027e2f0] :mac80211:ieee80211_master_start_xmit+0x278/0x39b [83892.115716] [803199ed] __next_cpu+0x19/0x26 [83892.115716] [8022954d] find_busiest_group+0x254/0x6dc [83892.115716] [8020a857] __switch_to+0x96/0x35e [83892.115716] [a02778c5] :mac80211:ieee80211_sta_work+0x98/0x693 [83892.115716] [80428294] thread_return+0x6b/0xac [83892.115716] [a027782d] :mac80211:ieee80211_sta_work+0x0/0x693 [83892.115716] [80242f18] run_workqueue+0x82/0x111 [83892.115716] [802437e5] worker_thread+0xd5/0xe0 [83892.115716] [8024601d] autoremove_wake_function+0x0/0x2e [83892.115716] [80243710] worker_thread+0x0/0xe0 [83892.115716] [80245ef7] kthread+0x47/0x74 [83892.115716] [80230057] schedule_tail+0x27/0x5c [83892.115716] [8020cef8] child_rip+0xa/0x12 [83892.115716] [80245eb0] kthread+0x0/0x74 [83892.115716] [8020ceee] child_rip+0x0/0x12 [83892.115716] [83892.115716] ---[ end trace 052857ef0447c214 ]--- [83892.131362] wlan0: association frame received from 00:1b:11:4e:42:c9, but not in associate state - ignored [83898.646938] wlan0: RX
Bug#496111: linux-image-2.6.26-1-amd64: iwl-wifi dumps stacks
On Sat, Dec 27, 2008 at 06:03:44PM +, Moritz Muehlenhoff wrote: On Fri, Aug 22, 2008 at 08:16:17PM +0200, Pierre Habouzit wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-2 Severity: normal With the latest kernels, my wifi card somehow floods the kern.log with backtraces. Though I've seen no problems with the network whatsoever. It's just that it floods quite a lot (I've put here a short excerpt). [83892.115716] wlan0: switched to short barker preamble (BSSID=00:1b:11:4e:42:c9) [83892.115716] [ cut here ] [83892.115716] WARNING: at include/../net/mac80211/rate.h:153 rs_get_rate+0xce/0x420 [iwl3945]() [83892.115716] Modules linked in: tun binfmt_misc rfcomm l2cap ipv6 cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_ondemand cpufreq_conservative microcode nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc xfs sha256_generic aes_x86_64 aes_generic cbc dm_crypt i915 drm snd_hda_intel snd_pcm_oss snd_mixer_oss arc4 ecb crypto_blkcipher snd_pcm hci_usb iwl3945 rng_core bluetooth mac80211 snd_timer i2c_i801 video output snd led_class yenta_socket rsrc_nonstatic iTCO_wdt joydev battery soundcore snd_page_alloc ac button psmouse serio_raw cfg80211 evdev intel_agp usbhid hid ff_memless reiserfs dm_mirror dm_log dm_snapshot dm_mod sg sr_mod sd_mod cdrom ide_pci_generic ide_core ata_piix b44 ata_generic libata scsi_mod dock ohci1394 ricoh_mmc ieee1394 sdhci mmc_core ssb pcmcia pcmcia_core firmware_class mii ehci_hcd uhci_hcd thermal fan intelfb i2c_algo_bit i2c_core coretemp acpi_cpufreq freq_table processor thermal_sys [83892.115716] Pid: 2025, comm: iwl3945 Not tainted 2.6.26-1-amd64 #1 Does this error still occur with the Lenny versions of the kernel and firmware-iwlwifi? No it doesn't since the 10 last days at least, sorry I forgot to check. -- ·O· Pierre Habouzit ··Omadco...@debian.org OOOhttp://www.madism.org pgpVoawAGYqMG.pgp Description: PGP signature
Re: Removing pseudo package kernel
In gmane.linux.debian.devel.kernel, you wrote: On Sun, 28 Dec 2008, Don Armstrong wrote: On Sun, 28 Dec 2008, Moritz Muehlenhoff wrote: BTS administrators, all bugs have been reassigned to linux-2.6 Can you please disable the kernel pseudo package? If there are no objections, I'll remove this around the 1st of the year. I've gone ahead and removed the psuedopackage; there will be a bit of a delay before everything gets into sync, but that should happen shortly. I'd also appreciate it if one of you would occasionally check the kernel package to make sure that bugs aren't languishing there from releases of reportbugs which have kernel still listed as a valid psuedopackage. The reportbug maintainers told me that current reportbug redirects bugs filed against kernel against the pseudo package linux-image. This pseudo package doesn't even have debian-kernel@lists.debian.org listed as the maintainer: --- Debian Bug report logs - [1]#509992 linux-image: Kernel (amd64) frequent oopses and freezes [2]version graph Package: [3]linux-image; Maintainer for [4]linux-image is [5](unknown); Reported by: [6]Ioannis Ramfos i...@edu.demokritos.gr Date: Sun, 28 Dec 2008 12:24:02 UTC --- Fortunately there's only one bug filed against linux-image, which I'll reassign now. So, please remove the linux-image pseudo package as well. I'll check kernel and linux-image for some time manually. There's also people triaging bugs filed against unknown packages to close bugs against removed packages, so they should notice them as well. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Removing pseudo package kernel
On Sun, 28 Dec 2008, Don Armstrong wrote: On Sun, 28 Dec 2008, Moritz Muehlenhoff wrote: BTS administrators, all bugs have been reassigned to linux-2.6 Can you please disable the kernel pseudo package? If there are no objections, I'll remove this around the 1st of the year. I've gone ahead and removed the psuedopackage; there will be a bit of a delay before everything gets into sync, but that should happen shortly. I'd also appreciate it if one of you would occasionally check the kernel package to make sure that bugs aren't languishing there from releases of reportbugs which have kernel still listed as a valid psuedopackage. Don Armstrong -- Taxes are not levied for the benefit of the taxed. -- Robert Heinlein _Time Enough For Love_ p250 http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#375523: marked as done (hdaps fails to read gyroscope after suspend/resume)
Your message dated Sun, 4 Jan 2009 14:59:01 +0100 with message-id 20090104135901.ga3...@galadriel.inutil.org and subject line Re: hdaps fails to read gyroscope after suspend/resume has caused the Debian Bug report #375523, regarding hdaps fails to read gyroscope after suspend/resume 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.) -- 375523: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=375523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.15-8 I have a thinkpad t41 with gyroscope, readable via the hdaps module. However, after suspend/resuming, the module no longer works -- it yields the same data every time. Rebooting the computer then also doesn't work, I can only get it to work again after cold-booting the laptop without resume. Somehow, probably the resume or the suspend code is disabling the gyroscope or bringing it in a state that it can't bring it out of again. If you need more info, please ask, I don't know enough of kernels to know what kind of info is relevant -- I'm using a default etch system with no tweaking to the kernel or to the hdaps module. Thanks, --Jeroen -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.15-1-686 depends on: ii initramfs-tools [linux-initra 0.60 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo Versions of packages linux-image-2.6.15-1-686 recommends: pn libc6-i686none (no description available) -- debconf information excluded -- Jeroen van Wolffelaar jer...@wolffelaar.nl (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl ---End Message--- ---BeginMessage--- On Sun, Jan 04, 2009 at 02:44:39PM +0100, Jeroen van Wolffelaar wrote: On Sun, Dec 21, 2008 at 11:28:48AM +0100, Moritz Muehlenhoff wrote: Does this error still occur with more recent kernel versions? My thinkpad motherboard died last year, and it's beyond warranty and way too expensive to repair/replace, so I'm afraid I cannot test. Ok, closing the bug then. Cheers, Moritz ---End Message---
Bug#484593: linux-image-2.6.25-2-686: su gets stuck for root -- stty getting stuck in T state
On Sun, 4 Jan 2009, Moritz Muehlenhoff wrote: On Thu, Jun 05, 2008 at 02:03:29PM +1000, Tim Connors wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-4 Severity: normal There's an upstream bug that has started affecting me. stty gets backgrounded, and you can only kill -9 it to get your shell back. A thread titled su gets stuck for root is on LKML with all the details, and when there's an eventual patch, it would be good to include it in the debian patchset. Does this error still occur with the Lenny kernel? It did last time I used that machine, but it's since been decomissioned. Since this is a race condition that obviously depends strongly on timing (it was quite a slow machine), I'm not going to say the bug is gone. There was no more activity on that su gets stuck for root thread on LKML, so I doubt it's been deliberately fixed. -- TimC Seen in a sendmail HELO greeting (Leon Brooks): Commodore 64 (anti-spam cartridge loaded) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#510780: linux-image-2.6.24-1-486: sound card YMF-724F, firmware request failed
Processing commands for cont...@bugs.debian.org: reassign 510780 linux-2.6 Bug#510780: linux-image-2.6.24-1-486: sound card YMF-724F, firmware request failed Warning: Unknown package 'linux-image-2.6.24-1-486' Bug reassigned from package `linux-image-2.6.24-1-486' to `linux-2.6'. -- 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#510787: Closed #496188 appear again in 2.6.26-12 SID and Lenny
Package: linux-image-2.6.26-1-openvz-amd64 Version: 2.6.26-12 Severity: grave Justification: renders package unusable Hi, the closed bug #496188 appears again in 2.6.26-1 debian version 2.6.26-12 amd-64-openvz from SID as well as 686 version from Lenny/unstable Please reopen it. I already send the information to kernel.org by reopening bug 11519 -- Daniel -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#510780: linux-image-2.6.24-1-486: sound card YMF-724F, firmware request failed
Package: linux-image-2.6.24-1-486 Version: 2.6.24-4 Severity: important bug=466570 Hello! Installing the firmware is not enough, the modul soundcore.ko is still necessary. It would be fine to put some advice in the kernel documentation or to fix the bug, it is still present in version 2.6.26-12. I published advice for Yamaha hardware: http://www.jpberlin.de/st.pofahl/html/science-and-software/Gnu-Linux/alsa-sound.html Regards, Stefan -- Tel.: 0731-3805149 Ochsensteige 48 89075 Ulm
Bug#463498: marked as done (b43: master mode doesn't work)
Your message dated Sun, 4 Jan 2009 22:04:05 +0100 with message-id 20090104210405.gb3...@galadriel.inutil.org and subject line Re: b43: Selects wrong driver? has caused the Debian Bug report #463498, regarding b43: master mode doesn't work 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.) -- 463498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463498 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.24-1 Hi, It seems that the kernel does not select the proper driver for me. When booting a 2.6.22 (and .23) kernel, I see: bcm43xx driver PCI: Enabling device :02:00.0 ( - 0002) ACPI: PCI Interrupt :02:00.0[A] - Link [LNKA] - GSI 10 (level, low) - IRQ 10 PCI: Setting latency timer of device :02:00.0 to 64 bcm43xx: Chip ID 0x4306, rev 0x3 bcm43xx: Number of cores: 5 bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243 bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243 bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243 bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243 bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243 bcm43xx: PHY connected bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2 bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2) bcm43xx: Radio turned off bcm43xx: Radio turned off udev: renamed network interface eth1 to eth3 cs: IO port probe 0x100-0x4ff: excluding 0x4d0-0x4d7 cs: IO port probe 0x800-0x8ff: clean. cs: IO port probe 0xc00-0xcff: clean. cs: IO port probe 0xa00-0xaff: clean. Adding 771080k swap on /dev/hda5. Priority:-1 extents:1 across:771080k b43-phy0: Broadcom 4306 WLAN found phy0: Selected rate control algorithm 'simple' udev: renamed network interface wmaster0 to eth3 Adding 771080k swap on /dev/hda5. Priority:-1 extents:1 across:771080k EXT3 FS on hda1, internal journal Driver 'sr' needs updating - please use bus_type methods device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-de...@redhat.com input: b43-phy0 as /class/input/input8 Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio But this b43 driver doesn't seem to be working for me. I notice some strange behaviours with this: - After the udev: renamed network interface wmaster0 to eth3 it hangs for several seconds before doing something else. At that point something prints done on the screen which doesn't come from the kernel. (Manual modprobing b43 doesn't seem to cause this problem.) - When looking at the interface list I see a eth3 that doesn't have wireless extentions, and a wlan0_rename that does. I also have 1 more device than I should. Reading http://linuxwireless.org/en/users/Drivers/b43 it says: 4306 and 4309 cards with a MAC core revision of 4 or less should also use b43legacy. [...] The kernel autoloader will automatically do the right thing and load the correct driver for your device. If I read the dmesg above right I have a 4306 with MAC core revision 3, so I should use b43legacy. It seems to me that it's not doing the right thing here. So I've tried rmmod b43 and modprobe b43legacy but that doesn't seem to be doing much. Kurt ---End Message--- ---BeginMessage--- On Sun, Jan 04, 2009 at 06:35:01PM +0100, Kurt Roeckx wrote: On Sun, Jan 04, 2009 at 06:20:46PM +0100, Moritz Muehlenhoff wrote: Is the kernel issue of detecting your card with the proper driver resolved in the Lenny kernel? (Leaving the udev rename issue referenced later aside) As far as I know, it was only the udev issue and never a kernel issue for me. Atleast, with the proper udev rules I have no problem anymore. But you could probably argue that the kernel shouldn't get into a wrong state because you did something on the wrong devicename. Thanks, closing the bug then. Cheers, Moritz ---End Message---
Bug#446964: Re: linux-image-2.6.18-5-686: kernel BUG at fs/exec.c:1459!
Hi, Package: linux-image-2.6.18-5-686 Version: 2.6.18.dfsg.1-13etch4 Severity: normal [...] Oct 16 21:31:30 server kernel: kernel BUG at fs/exec.c:1459! Oct 16 21:31:30 server kernel: invalid opcode: [#1] [...] Does this error still occur with more recent kernel versions? I have not encountered any more occurrences of this bug. I still run stable distribution 2.6.18 kernel - it works, so I won't fix it. I sent this bug report to let interested parties know that there may be some problem - in this case looks like something with core dumping sometimes goes wrong. I haven't investigated it further, nor have any idea how to reproduce it. Maybe some skilled kernel hackers will know if fs/exec.c was fixed or maybe there is some local dos, but I won't mind you closing this bug. (and maybe forward it to www.kerneloops.org before) Regards, Michal Pokrywka -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#508527: 2.6.26-11 oops on initial NIC (via-velocity) setup
Thanks Moritz and junk mail for pointing out. I can confirm both ways do work. Taking via-velocity.* from git or 2.6.28 sources will fix this issue. I pulled the current version of via-velocity.* from git diffed and patched against linux-source-2.6.26. I did some basic testing like sending jumbo frames and putting some load to the NIC. It looks like the 2.6.28 kernel makes not use of the latest git version of via-velocity.* nevertheless it works too. Have fun Christoph -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Removing pseudo package kernel
On Sun, 04 Jan 2009, Moritz Muehlenhoff wrote: The reportbug maintainers told me that current reportbug redirects bugs filed against kernel against the pseudo package linux-image. There is no linux-image pseudopackage; it's a non-existant package. [Reassigning bugs to it is wrong.] What'd probably be reasonable is to assign those bugs to something like Source: linux-$(uname -r |cut -f1,2 -d.); instead. Don Armstrong -- A Democracy lead by politicians and political parties, fails. http://www.donarmstrong.com http://rzlab.ucr.edu -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: add firmware-ipw2x00 to lenny?
On Sun, Jan 4, 2009 at 11:45 PM, Moritz Muehlenhoff j...@inutil.org wrote: firmware-nonfree (0.14) unstable; urgency=low . * Generate license acceptation prompt, based on sun-java5. (closes: #504668) * Add Intel Pro 2100 firwmare, version 1.3. (closes: #504671) * Add Intel Pro 2200/2915 firwmare, version 3.0. (closes: #449235) Indeed, it works very well with my ipw2200. Unblocked by Maulkin :D -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: reopen 377152 Bug#377152: debian-installer: BootX of (hd-media|cdrom) vmlinux and initrd.gz fails; miBoot works Bug#379218: linux-image-2.6.16-2-powerpc: Can't boot with bootx on a beige G3 (oldworld) Bug reopened, originator not changed. -- 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#446323: mdadm: recovery in infinite loop
On Sun, Jan 4, 2009 at 8:55 AM, Moritz Muehlenhoff j...@inutil.org wrote: fOn Wed, Oct 17, 2007 at 04:16:39PM -0500, Lukasz Szybalski wrote: On 10/15/07, Neil Brown ne...@suse.de wrote: As you say, the devices are exactly the same size, thanks. On Monday October 15, szybal...@gmail.com wrote: how do I undo? mdadm /dev/md2 -f /dev/hda2 So I could try the sync in init 1 Lucas Well, you could: mdadm /dev/md2 -f /dev/hda2 mdadm /dev/md2 -r /dev/hda2 then when you are ready to try again mdadm /dev/md2 -a /dev/hda2 Ok, So I went into init 1 to get rid of any program that might want to access the hda2. I unmounted my '/files' which mounts my hda2 in '/' folder. I was watching it as it went for 30 min to sync the drives and suddenly I got unrecognizable error 5 i believe it was. Unable to read sector lba 88604764 on hdb1. I guess that showed up in stderr or something because I couldn't find reference to it anywhere other then a terminal screen. What would be the proper command for testing every single block on that hardrive using e2fsck I used e2fsck -acf /dev/hdb2 but that took all night and it still wasn't finished. I've canceled it. What would be the proper options for this command that would get me to clean this drive. The weird part is when I checked the drives last Thursday using knoppix nothing has shown any problems or bad sectors. I think there must be something odd happening with the drive or controller. I notice that the two devices are on the same IDE channel, which is sometimes a source of problems, though it should behave like this. If you feel up to patching the kernel, recompiling, and experimenting, I can send you a patch which should provide more detailed information on what is happening. Let me know what kernel version you will be working with. Never done recompiling of a kernel before, but I guess if everything fails then we can try it. For now let me clean this drive and we go from there. What's the status of this bug? Does this error still occur with more recent kernel versions? If you're running Etch, you could try to reproduce this bug with the 2.6.24 based kernel added in 4.0r4: http://packages.qa.debian.org/l/linux-2.6.24.html It still exists. I will upgrade this week and I will let you know. Lucas -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#377152: debian-installer: BootX of (hd-media|cdrom) vmlinux and initrd.gz fails; miBoot works
On Thu, 25 Dec 2008 23:20:05 +0100 Moritz Muehlenhoff j...@inutil.org wrote: Does this error still occur with more recent kernel versions? I will try later this week. Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore: http://www.wightman.ca/~cshore signature.asc Description: PGP signature
Bug#452353: I no longer have the motherboard to test this bug
The motherboard the exhibited the problem is no longer in my possession, therefore I have no means of testing the situation. Regards, Daniel -- And that's my crabbing done for the day. Got it out of the way early, now I have the rest of the afternoon to sniff fragrant tea-roses or strangle cute bunnies or something. -- Michael Devore GnuPG Key Fingerprint 86 F5 81 A5 D4 2E 1F 1C http://gnupg.org The C Shore: http://www.wightman.ca/~cshore signature.asc Description: PGP signature
Bug#377152: Please don't mark submitter bounces unless BTS says bounce
Hi, This is the second bug of mine you have closed for which the submitter works (else I wouldn't know about this message) but for which you closed the bug because of submitter bouncing. Please stop doing that. The BTS has a command that lets you change your submitter address when you email address changes and I have used it. That means bugs sent to the bug address (in this case 377...@bugs.debian.org) get to me and DO NOT BOUNCE. What bounces is the original email address in the bug report, which isn't the same thing. In future please don't close a bug on the grounds that the submitter address bounces unless you have looked through the bug log and verified that there is no newer submitter address. This can also happen if a developer changes the submitter address for some reason. In that case also, closing a bug because the original email address is not the same as the current submitter address (which works) is wrong. Please be more careful in the future. Regards, Daniel signature.asc Description: PGP signature
Processed: tagging 510607
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch1 tags 510607 + pending Bug#510607: linux-image-2.6.26-1-686: Bug in rt2500usb makes affected WLAN hardware useless Tags were: patch 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
Processed: tagging 506835
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.9.26etch1 tags 506835 + pending Bug#506835: linux-image-2.6.26-1-686: DPT SCSI controller module eata not automatically loaded, modprobe eata locks up 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#508108: Reopening, bug not fixed in 2.6.26-12
Quoting Jurij Smakov (ju...@wooyd.org): Please enable them for the next upload (which will hopefully make it into lenny). If we want to release lenny some day, maybe not. D-I RC2 was delayed partly because of -12. Now that everything is in place for a release to happen (including the D-I RM back from holidays), I'm not sure that another delay is really welcome. Could we document that issue in the errata? signature.asc Description: Digital signature
Processed: Re: Bug#510815: 2.6.26.11 oops on adding via-velocity NIC to bridge
Processing commands for cont...@bugs.debian.org: reassign 510815 linux-2.6 Bug#510815: 2.6.26.11 oops on adding via-velocity NIC to bridge Warning: Unknown package 'kernel' Bug reassigned from package `kernel' to `linux-2.6'. -- 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#510815: 2.6.26.11 oops on adding via-velocity NIC to bridge
Package: kernel Version: 2.6.26-12 Tags: lenny I am facing repeatable kernel oopses when adding a via-velocity driven NIC to a bridge. The conditions are: * bridge set up automatically by means of /etc/network/interfaces. ---8--- auto br0 iface br0 inet dhcp bridge_ports eth0 eth1 bridge_fd 4 bridge_hello 1 bridge_stp on ---8--- * eth0 is VT6120/VT6121/VT6122 Gigabit Ethernet Adapter (via-velocity) * as soon as eth0 is enslaved the kernel oops * the same issue occurs when setting up the bridge manually I am using a custom kernel to circumvent bug #508527 (BTS Bug ID). The via-velocity driver was diffed and patched against the current git version of via-velocity.* The kernel config is stock lenny. ---8--- [ 63.811501] Bridge firewalling registered [ 63.876011] br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. [ 64.020028] BUG: unable to handle kernel NULL pointer dereference at [ 64.020028] IP: [] [ 64.020028] *pde = [ 64.020028] Oops: [#1] SMP [ 64.020028] Modules linked in: bridge dm_crypt crypto_blkcipher raid1 md_mod dm_snapshot dm_mirror dm_log dm_mod via_rng rng_core loop tpm_infineon tpm tpm_bios snd_pcm snd_timer snd soundcore snd_page_alloc pcspkr i2c_viapro i2c_core button shpchp via_agp pci_hotplug agpgart evdev ext3 jbd mbcache ide_disk ide_pci_generic usb_storage sd_mod via82cxxx ide_core ehci_hcd uhci_hcd ata_generic ahci libata scsi_mod via_rhine mii usbcore dock via_velocity crc_ccitt thermal processor fan thermal_sys [ 64.020028] [ 64.020028] Pid: 2136, comm: brctl Not tainted (2.6.26viagitpatched #1) [ 64.020028] EIP: 0060:[] EFLAGS: 00010046 CPU: 0 [ 64.020028] EIP is at 0x0 [ 64.020028] EAX: 00a3 EBX: 3d20 ECX: 01bd8000 EDX: c0371940 [ 64.020028] ESI: c0371940 EDI: EBP: 00a3 ESP: f7aafd5c [ 64.020028] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 64.020028] Process brctl (pid: 2136, ti=f7aae000 task=f748f180 task.ti=f7aae000) [ 64.020028] Stack: c0105f8b 3218f23e 3218f227 c010434b 3218 f23e 01bd8000 [ 64.020028]004d 3218f227 3218f2bc 007b 007b 00d8 [ 64.020028]ff5c c01e42e1 0060 0246 03eb 00d7 b7fa2000 [ 64.020028] Call Trace: [ 64.020028] [c0105f8b] do_IRQ+0x4d/0x66 [ 64.020028] [c010434b] common_interrupt+0x23/0x28 [ 64.020028] [c01e42e1] delay_tsc+0x1d/0x50 [ 64.020028] [c01e434f] __const_udelay+0x29/0x2a [ 64.020028] [f884166f] velocity_mii_read+0x1a/0x6b [via_velocity] [ 64.020028] [f8841702] check_connection_type+0x42/0x8e [via_velocity] [ 64.020028] [f8841762] velocity_get_settings+0x14/0x63 [via_velocity] [ 64.020028] [f8d05ef7] port_cost+0x30/0xa2 [bridge] [ 64.020028] [f8d0619d] br_add_if+0xeb/0x23f [bridge] [ 64.020028] [f8d06796] add_del_if+0x3e/0x58 [bridge] [ 64.020028] [f8d067b0] br_dev_ioctl+0x0/0x572 [bridge] [ 64.020028] [f8d06d16] br_dev_ioctl+0x566/0x572 [bridge] [ 64.020028] [c0184e25] dput+0x16/0xdb [ 64.020028] [c0167516] __vma_link+0x51/0x5b [ 64.020028] [c0167ad2] vma_adjust+0x394/0x40e [ 64.020028] [c0115949] do_page_fault+0x0/0x637 [ 64.020028] [c01896de] mntput_no_expire+0x18/0xf3 [ 64.020028] [c025b702] __dev_get_by_name+0x60/0x6b [ 64.020028] [f8d067b0] br_dev_ioctl+0x0/0x572 [bridge] [ 64.020028] [c025e0e8] dev_ifsioc+0x262/0x27c [ 64.020028] [c025e5ef] dev_ioctl+0x4ed/0x586 [ 64.020028] [c02575b4] skb_dequeue+0x42/0x48 [ 64.020028] [c02524b7] sock_ioctl+0x19f/0x1c1 [ 64.020028] [c0252318] sock_ioctl+0x0/0x1c1 [ 64.020028] [c018066c] vfs_ioctl+0x1c/0x5f [ 64.020028] [c01808eb] do_vfs_ioctl+0x23c/0x24e [ 64.020028] [c018093e] sys_ioctl+0x41/0x5b [ 64.020028] [c01038f7] sysenter_past_esp+0x78/0xb1 [ 64.020028] === [ 64.020028] Code: Bad EIP value. [ 64.020028] EIP: [] 0x0 SS:ESP 0068:f7aafd5c [ 64.020028] Kernel panic - not syncing: Fatal exception in interrupt ---8--- Architecture: i686 Thanks in advance, Christoph -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
