Bug#563605: marked as done (linux-image-2.6.32-trunk-amd64: Intel VT flags missing on Q45 chipset)
Your message dated Mon, 1 Feb 2010 08:47:07 + with message-id 20100201084707.ga4...@lupin.powdarrmonkey.net and subject line Re: Bug#563605: linux-image-2.6.32-trunk-amd64: Intel VT flags missing on Q45 chipset has caused the Debian Bug report #563605, regarding linux-image-2.6.32-trunk-amd64: Intel VT flags missing on Q45 chipset 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.) -- 563605: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-3 Severity: normal I don't seem to have the CPU flags for Intel virtualisation from the processor to run KVM, Xen and friends. I double-checked the BIOS and virtualisation is enabled (it's a Q45 chipset with a Core2Duo E7400 processor, and a recent BIOS). I'm happy to include other information or try things if you direct me, since my kernel experience is limited. I did wonder if I needed to load a module. Thanks. -- Package-specific info: ** Version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-3) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sat Dec 26 17:13:29 UTC 2009 ** Command line: BOOT_IMAGE=//vmlinuz-2.6.32-trunk-amd64 root=UUID=674d09bc-8ab6-4744-8b4f-b1e5c3a61e54 ro quiet ** Not tainted ** Kernel log: [4.788413] EXT3-fs: mounted filesystem with ordered data mode. [5.806669] udev: starting version 149 [6.013774] input: PC Speaker as /devices/platform/pcspkr/input/input6 [6.123250] ACPI: SSDT bd94cc18 002CC (v01AMI IST 0001 MSFT 0301) [6.123774] Marking TSC unstable due to TSC halts in idle [6.123848] processor LNXCPU:00: registered as cooling_device0 [6.124084] processor LNXCPU:01: registered as cooling_device1 [6.124387] Switching to clocksource acpi_pm [6.329255] cfg80211: Using static regulatory domain info [6.329257] cfg80211: Regulatory domain: US [6.329258] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [6.329260] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [6.329262] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.329264] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.329266] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.329267] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.329269] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [6.329405] cfg80211: Calling CRDA for country: US [6.353684] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [6.560504] b43-phy0: Broadcom 4306 WLAN found (core revision 5) [6.631671] phy0: Selected rate control algorithm 'minstrel' [6.632129] Registered led device: b43-phy0::tx [6.632141] Registered led device: b43-phy0::rx [6.632153] Registered led device: b43-phy0::radio [6.632193] Broadcom 43xx driver loaded [ Features: PML, Firmware-ID: FW13 ] [6.822503] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [6.822559] HDA Intel :00:1b.0: setting latency timer to 64 [7.248960] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input7 [7.682349] EXT3 FS on sdb2, internal journal [7.752849] loop: module loaded [7.975459] kjournald starting. Commit interval 5 seconds [7.975619] EXT3 FS on sda1, internal journal [7.975625] EXT3-fs: mounted filesystem with ordered data mode. [8.049323] kjournald starting. Commit interval 5 seconds [8.049473] EXT3 FS on sdb5, internal journal [8.049477] EXT3-fs: mounted filesystem with ordered data mode. [8.072441] kjournald starting. Commit interval 5 seconds [8.072669] EXT3 FS on sdb6, internal journal [8.072673] EXT3-fs: mounted filesystem with ordered data mode. [8.112049] kjournald starting. Commit interval 5 seconds [8.112062] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [8.112271] EXT3 FS on sdb7, internal journal [8.112274] EXT3-fs: mounted filesystem with ordered data mode. [8.145522] kjournald starting. Commit interval 5 seconds [8.145773] EXT3 FS on sdb8, internal journal [8.145775] EXT3-fs: mounted filesystem with ordered data mode. [9.524042] b43 ssb0:0: firmware: requesting b43/ucode5.fw [9.564087] b43 ssb0:0: firmware: requesting b43/pcm5.fw [9.572774] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw [9.576175] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw [9.700047] b43-phy0: Loading
Bug#563605: linux-image-2.6.32-trunk-amd64: Intel VT flags missing on Q45 chipset
On Mon, 2010-02-01 at 08:47 +, Jonathan Wiltshire wrote: On Tue, Jan 05, 2010 at 02:53:57AM +, Ben Hutchings wrote: According to http://ark.intel.com/Product.aspx?id=36500#specs, there are some variants of the E7400 which do not support VT-x. These are distinguished by 'Ordering Code' and 'SPEC Code'; I assume one or both of these codes are shown on the processor packaging. Please check whether you have one of these variants. Sadly I can't find the original box (I suspect it's been thrown away in a fit of tidying over the holiday) so I can't be sure about which processor I have, but looking at the original invoice there's a good chance it's the cheapest of the lot, which doesn't have vmx. Thanks for the specs page, which I hadn't seen, and sorry for wasting your time, There is another thing you could check. Apparently on some BIOSes you need to enable Trusted Execution for VT-x to work. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Processing of linux-2.6_2.6.32-6_multi.changes
linux-image-2.6.32-1-486_2.6.32-6_i386.deb has incorrect size; deleting it Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#550975: OpenVZ - deb-packages
Processing commands for cont...@bugs.debian.org: tags 550975 -patch Bug #550975 [linux-2.6] linux-2.6: Add ppp support in openvz flavor Removed tag(s) patch. stop 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: severity of 563941 is important
Processing commands for cont...@bugs.debian.org: severity 563941 important Bug #563941 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: unexpected system hangups Severity set to 'important' from 'grave' 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#497706: marked as done (boot halts on the eeepc 701 with SD card in slot)
Your message dated Mon, 1 Feb 2010 14:29:10 +0100 with message-id 20100201132910.gg9...@stro.at and subject line Re: Bug#497706: eeepc 701 boot halts when SD card is inside slot has caused the Debian Bug report #497706, regarding boot halts on the eeepc 701 with SD card in slot 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.) -- 497706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26+15 I run debian testing on my eee pc 701. The box has one sd slot, and I have a transcend 16Gb sd card on it. When the card was new and empty, the system would boot with no problems with the card inside the slot. However, after I started writing to it, when I boot the system, it halts after udev starts with a read error on the card, and a hard boot is required. If I boot without the card in, everything goes fine. My first guess was a bad sd card. I reformated it, used badblocks -w on it, and no problems were found. After the card was formated (and empty), the system would boot without problems. However, as soon as I started writing to it, when I reboot I get the same read errors again. If, however, I plug the card after system boot, I can use it without problems. I just tried to read it all to make sure: gapski at revo:~$ dd bs=1024 if=/dev/sdb of=/dev/null 15694336+0 records in 15694336+0 records out 1607164 bytes (16 GB) copied, 967.822 s, 16.6 MB/s A later post on the debian eeepc mailing list seems to identify the issue and point to a patch: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2008-August/000829.html Can this patch be included into debian kernels? regards, Pedro ---End Message--- ---BeginMessage--- Version: 2.6.32-1 On Tue, 28 Jul 2009, Pedro Bulach Gapski wrote: Hello Moritz, [...] Can this patch be included into debian kernels? The upstream commit points to the attached patch. Could you test it against the Lenny kernel if it fixes your problem? Cheers, Moritz I have migrated to newer kernels in sid mainly because of this issue, and indeed the problem is solved. thanks for the feedback, thus closing the bug reports. ---End Message---
Bug#473398: marked as done (new linux-image-2.6.24-1-amd64 does not boot anymore (semmes to be a problem with kernel-module ata_generic))
Your message dated Mon, 1 Feb 2010 14:27:16 +0100 with message-id 20100201132716.gf9...@stro.at and subject line Re: Bug#473398: new linux-image-2.6.24-1-amd64 does not boot anymore (semmes to be a problem with kernel-module ata_generic) has caused the Debian Bug report #473398, regarding new linux-image-2.6.24-1-amd64 does not boot anymore (semmes to be a problem with kernel-module ata_generic) 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.) -- 473398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473398 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-5 After a normal apt-get update apt-get upgrade under deban sid it wanted to update my installed 2.6.24-kernel (amd64). After rebooting the machine the upgraded kernel told me that /dev/sda2 - my partition where debian is installed - can't be found. After removing the quiet option I saw a lot of unknown symbol-strings coming up from the ata_generic-module. One of them is (if you need the whole screen-output just tell me, but it's no fun to copy everything manually, because copypasting is not possible): ata_generic: Unknown symbol ata_scsi_slave_config My Harddisk is a SATA-disk and my setup is a cryptsetup on /dev/sda2 (dm-crypt/luks) and a LVM on the crypt (/dev/sda2_crypt). Everything was working fine with the prior 2.6.24-image and the still being installed 2.6.22 is also working fine. This whole setup was made with the normal debian-installer - I didn't change anything of the setup manually. Seems that the ata_generic-driver is broken which is needed to recognize the paritition table of ma SATA-Device. A CC was also sent to debian-kernel@lists.debian.org Even if the E-mail-address is a spam-email-address i'll check the account for any non-spam-mail's so i'll read responses for sure. Regards Mirko (d...@ten) ---End Message--- ---BeginMessage--- On Fri, 14 Aug 2009, Moritz Muehlenhoff wrote: On Sun, Mar 30, 2008 at 02:22:44PM +0200, foobar wrote: Package: linux-image-2.6.24-1-amd64 Version: 2.6.24-5 After a normal apt-get update apt-get upgrade under deban sid it wanted to update my installed 2.6.24-kernel (amd64). After rebooting the machine the upgraded kernel told me that /dev/sda2 - my partition where debian is installed - can't be found. After removing the quiet option I saw a lot of unknown symbol-strings coming up from the ata_generic-module. One of them is (if you need the whole screen-output just tell me, but it's no fun to copy everything manually, because copypasting is not possible): ata_generic: Unknown symbol ata_scsi_slave_config My Harddisk is a SATA-disk and my setup is a cryptsetup on /dev/sda2 (dm-crypt/luks) and a LVM on the crypt (/dev/sda2_crypt). Everything was working fine with the prior 2.6.24-image and the still being installed 2.6.22 is also working fine. This whole setup was made with the normal debian-installer - I didn't change anything of the setup manually. Seems that the ata_generic-driver is broken which is needed to recognize the paritition table of ma SATA-Device. A CC was also sent to debian-kernel@lists.debian.org Even if the E-mail-address is a spam-email-address i'll check the account for any non-spam-mail's so i'll read responses for sure. Does it work with more recent kernels? closing as no answer since. if the bug can be reproduced with recent linux-2.6 this can be reopened. thanks for the report ---End Message---
Bug#496540: marked as done (eeepc 701 boot halts when SD card is inside slot)
Your message dated Mon, 1 Feb 2010 14:29:10 +0100 with message-id 20100201132910.gg9...@stro.at and subject line Re: Bug#497706: eeepc 701 boot halts when SD card is inside slot has caused the Debian Bug report #497706, regarding eeepc 701 boot halts when SD card is inside slot 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.) -- 497706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 I run debian testing on my eee pc 701. The box has one sd slot, and I have a transcend 16Gb sd card on it. When the card was new and empty, the system would boot with no problems with the card inside the slot. However, after I started writing to it, when I boot the system, it halts after udev starts with a read error on the card, and a hard boot is required. If I boot without the card in, everything goes fine. My first guess was a bad sd card. I reformated it, used badblocks -w on it, and no problems were found. After the card was formated (and empty), the system would boot without problems. However, as soon as I started writing to it, when I reboot I get the same read errors again. If, however, I plug the card after system boot, I can use it without problems. I just tried to read it all to make sure: gapski at revo:~$ dd bs=1024 if=/dev/sdb of=/dev/null 15694336+0 records in 15694336+0 records out 1607164 bytes (16 GB) copied, 967.822 s, 16.6 MB/s A later post on the debian eeepc mailing list seems to identify the issue and point to a patch: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2008-August/000829.html Can this patch be included into debian kernels? regards, Pedro ---End Message--- ---BeginMessage--- Version: 2.6.32-1 On Tue, 28 Jul 2009, Pedro Bulach Gapski wrote: Hello Moritz, [...] Can this patch be included into debian kernels? The upstream commit points to the attached patch. Could you test it against the Lenny kernel if it fixes your problem? Cheers, Moritz I have migrated to newer kernels in sid mainly because of this issue, and indeed the problem is solved. thanks for the feedback, thus closing the bug reports. ---End Message---
Bug#496540: marked as done (eeepc 701 boot halts when SD card is inside slot)
Your message dated Mon, 1 Feb 2010 14:29:10 +0100 with message-id 20100201132910.gg9...@stro.at and subject line Re: Bug#497706: eeepc 701 boot halts when SD card is inside slot has caused the Debian Bug report #496540, regarding eeepc 701 boot halts when SD card is inside slot 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.) -- 496540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 I run debian testing on my eee pc 701. The box has one sd slot, and I have a transcend 16Gb sd card on it. When the card was new and empty, the system would boot with no problems with the card inside the slot. However, after I started writing to it, when I boot the system, it halts after udev starts with a read error on the card, and a hard boot is required. If I boot without the card in, everything goes fine. My first guess was a bad sd card. I reformated it, used badblocks -w on it, and no problems were found. After the card was formated (and empty), the system would boot without problems. However, as soon as I started writing to it, when I reboot I get the same read errors again. If, however, I plug the card after system boot, I can use it without problems. I just tried to read it all to make sure: gapski at revo:~$ dd bs=1024 if=/dev/sdb of=/dev/null 15694336+0 records in 15694336+0 records out 1607164 bytes (16 GB) copied, 967.822 s, 16.6 MB/s A later post on the debian eeepc mailing list seems to identify the issue and point to a patch: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2008-August/000829.html Can this patch be included into debian kernels? regards, Pedro ---End Message--- ---BeginMessage--- Version: 2.6.32-1 On Tue, 28 Jul 2009, Pedro Bulach Gapski wrote: Hello Moritz, [...] Can this patch be included into debian kernels? The upstream commit points to the attached patch. Could you test it against the Lenny kernel if it fixes your problem? Cheers, Moritz I have migrated to newer kernels in sid mainly because of this issue, and indeed the problem is solved. thanks for the feedback, thus closing the bug reports. ---End Message---
Bug#497706: marked as done (boot halts on the eeepc 701 with SD card in slot)
Your message dated Mon, 1 Feb 2010 14:29:10 +0100 with message-id 20100201132910.gg9...@stro.at and subject line Re: Bug#497706: eeepc 701 boot halts when SD card is inside slot has caused the Debian Bug report #496540, regarding boot halts on the eeepc 701 with SD card in slot 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.) -- 496540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26+15 I run debian testing on my eee pc 701. The box has one sd slot, and I have a transcend 16Gb sd card on it. When the card was new and empty, the system would boot with no problems with the card inside the slot. However, after I started writing to it, when I boot the system, it halts after udev starts with a read error on the card, and a hard boot is required. If I boot without the card in, everything goes fine. My first guess was a bad sd card. I reformated it, used badblocks -w on it, and no problems were found. After the card was formated (and empty), the system would boot without problems. However, as soon as I started writing to it, when I reboot I get the same read errors again. If, however, I plug the card after system boot, I can use it without problems. I just tried to read it all to make sure: gapski at revo:~$ dd bs=1024 if=/dev/sdb of=/dev/null 15694336+0 records in 15694336+0 records out 1607164 bytes (16 GB) copied, 967.822 s, 16.6 MB/s A later post on the debian eeepc mailing list seems to identify the issue and point to a patch: http://lists.alioth.debian.org/pipermail/debian-eeepc-devel/2008-August/000829.html Can this patch be included into debian kernels? regards, Pedro ---End Message--- ---BeginMessage--- Version: 2.6.32-1 On Tue, 28 Jul 2009, Pedro Bulach Gapski wrote: Hello Moritz, [...] Can this patch be included into debian kernels? The upstream commit points to the attached patch. Could you test it against the Lenny kernel if it fixes your problem? Cheers, Moritz I have migrated to newer kernels in sid mainly because of this issue, and indeed the problem is solved. thanks for the feedback, thus closing the bug reports. ---End Message---
Bug#550975: OpenVZ - deb-packages
tags 550975 -patch stop no patch on top of our 2.6.26 lenny openvz got integrated got posted, nor did upstream in openvz 2.6.26 branch a patch appear. as at this point we won't integrate new features for lenny, thus i guess this bug report can be closed soon. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563941: Additional information
On Wed, 06 Jan 2010, irb250 irb250 wrote: Jan 5 22:49:01 localhost kernel: [17744.647218] [ cut here ] Jan 5 22:49:01 localhost kernel: [17744.647230] WARNING: at lib/kref.c:43 kref_get+0x17/0x1c() Jan 5 22:49:01 localhost kernel: [17744.647233] Modules linked in: nls_utf8 nls_cp437 vfat fat nls_base sd_mod usb_storage usbhid hid ff_memless xt_TCPMSS xt_tcpmss xt_tcpudp iptable_mangle ip_tables x_tables pppoe pppox ppp_generic slhc radeon drm ppdev lp acpi_cpufreq speedstep_lib cpufreq_userspace cpufreq_conservative cpufreq_stats cpufreq_ondemand freq_table cpufreq_powersave ipv6 fuse loop joydev pcmcia firmware_class parport_pc parport serio_raw psmouse video output bay pcspkr battery snd_ali5451 snd_ac97_codec ac97_bus container snd_pcm snd_timer snd snd_page_alloc yenta_socket rsrc_nonstatic pcmcia_core ac trident i2c_ali1535 i2c_ali15x3 gameport button soundcore ac97_codec i2c_core shpchp pci_hotplug ali_agp agpgart evdev ext3 jbd mbcache ide_cd_mod cdrom ide_disk ata_generic libata scsi_mod ide_pci_generic floppy alim15x3 ide_core 8139cp 8139too mii dock ohci_hcd usbcore thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] Jan 5 22:49:01 localhost kernel: [17744.647341] Pid: 3377, comm: Xorg Tainted: GW 2.6.26-2-686 #1 can you reproduce with 2.6.26-21 that got pushed that weekend? it has several fixes. also we can't help with tainted kernel. is it reproducible without? thanks for the report -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: longer boot time without reason
Processing commands for cont...@bugs.debian.org: tags 522156 moreinfo Bug #522156 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: Longer boot time without reason Added tag(s) moreinfo. stop 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: Re: Bug#521548: linux-image-2.6.29-1-amd64: laptop toshiba qosmio g30 fails to boot with 2.6.28 and 2.6.29 kernels
Processing commands for cont...@bugs.debian.org: tags 521548 moreinfo Bug #521548 [linux-2.6] linux-image-2.6.29-1-amd64: laptop toshiba qosmio g30 fails to boot with 2.6.28 and 2.6.29 kernels Added tag(s) moreinfo. stop 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#551733: linux-image-2.6.26-2-686: Cannot boot kernel 2.6.26-2-686
[ please keep bug report on cc, otherwise your mail may get lost, thanks ] On Wed, 21 Oct 2009, Bruce Ward wrote: please post output of: sh -x mkinitramfs -o /dev/null How do I do that? Simple redirection (sh -x mkinitramfs -o /dev/null mkramfs) gives a zero length file. include stderr in redirect: sh -x mkinitramfs -o /dev/null/ initramfs.log 21 can you still reproduce the original bug? sorry for late reply but your mail got really lost.. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523761: marked as done (linux-image-2.6.29-1-amd64: /boot partition not mountable)
Your message dated Mon, 1 Feb 2010 14:15:26 +0100 with message-id 20100201131526.gd9...@stro.at and subject line Re: Bug#523761: linux-image-2.6.29-1-amd64: /boot partition not mountable has caused the Debian Bug report #523761, regarding linux-image-2.6.29-1-amd64: /boot partition not mountable 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.) -- 523761: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523761 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.29-1-amd64 Version: 2.6.29-2 Severity: important When booting a 2.6.29 kernel, the /boot filesystem is not accessible after booting. When trying to mount the partition with mount -t ext3 /dev/sdd1 /boot I get the error message: mount: /dev/sdd1 already mounted or /boot busy but mount and df show that the partition is not mounted yet. Booting a 2.6.26 kernel does not show this behaviour. Kind regards, Felix -- Package-specific info: ** Version: Linux version 2.6.29-1-amd64 (Debian 2.6.29-2) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-5) ) #1 SMP Sat Apr 4 16:54:07 UTC 2009 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.29-1-amd64 root=/dev/mapper/jupisdd-root ro ** Tainted: P (1) ** Kernel log: [ 10.709412] input: PC Speaker as /devices/platform/pcspkr/input/input4 [ 10.725761] i801_smbus :00:1f.3: PCI INT C - GSI 18 (level, low) - IRQ 18 [ 10.734666] sn9c102: V4L2 driver for SN9C1xx PC Camera Controllers v1:1.47pre49 [ 10.737861] usb 3-1: SN9C105 PC Camera Controller detected (vid:pid 0x0471:0x0327) [ 10.791889] alloc irq_desc for 22 on cpu 0 node 0 [ 10.791891] alloc kstat_irqs on cpu 0 node 0 [ 10.791898] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 10.792147] HDA Intel :00:1b.0: setting latency timer to 64 [ 10.834715] hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... [ 10.855562] usb 3-1: No supported image sensor detected for this bridge [ 10.855658] usbcore: registered new interface driver sn9c102 [ 10.885748] usbcore: registered new interface driver snd-usb-audio [ 10.903216] logips2pp: Detected unknown logitech mouse model 62 [ 11.415091] input: ImExPS/2 Logitech Explorer Mouse as /devices/platform/i8042/serio1/input/input5 [ 11.766970] Adding 25165816k swap on /dev/mapper/jupiter-swap1. Priority:-1 extents:1 across:25165816k [ 11.785298] EXT3 FS on dm-0, internal journal [ 12.795887] loop: module loaded [ 60.501412] fuse init (API version 7.11) [ 60.551649] kjournald starting. Commit interval 5 seconds [ 60.624769] EXT3 FS on dm-4, internal journal [ 60.624866] EXT3-fs: mounted filesystem with ordered data mode. [ 60.626220] kjournald starting. Commit interval 5 seconds [ 60.626288] EXT3 FS on dm-1, internal journal [ 60.626379] EXT3-fs: mounted filesystem with ordered data mode. [ 60.674771] kjournald starting. Commit interval 5 seconds [ 60.678267] EXT3 FS on dm-10, internal journal [ 60.678365] EXT3-fs: mounted filesystem with ordered data mode. [ 60.730985] kjournald starting. Commit interval 5 seconds [ 60.738542] EXT3 FS on dm-3, internal journal [ 60.738640] EXT3-fs: mounted filesystem with ordered data mode. [ 60.808325] kjournald starting. Commit interval 5 seconds [ 60.818590] EXT3 FS on dm-5, internal journal [ 60.818688] EXT3-fs: mounted filesystem with ordered data mode. [ 60.868724] kjournald starting. Commit interval 5 seconds [ 60.888342] EXT3 FS on dm-7, internal journal [ 60.888439] EXT3-fs: mounted filesystem with ordered data mode. [ 60.919486] kjournald starting. Commit interval 5 seconds [ 60.930016] EXT3 FS on dm-6, internal journal [ 60.930113] EXT3-fs: mounted filesystem with ordered data mode. [ 61.006864] kjournald starting. Commit interval 5 seconds [ 61.025240] EXT3 FS on dm-8, internal journal [ 61.025335] EXT3-fs: mounted filesystem with ordered data mode. [ 61.043330] kjournald starting. Commit interval 5 seconds [ 61.052968] EXT3 FS on dm-9, internal journal [ 61.053062] EXT3-fs: mounted filesystem with ordered data mode. [ 61.604877] Bridge firewalling registered [ 61.609310] device eth0 entered promiscuous mode [ 61.610068] r8169: eth0: link up [ 61.610125] r8169: eth0: link up [ 61.614220] br0: port 1(eth0) entering learning state [ 70.612005] br0: topology change detected, propagating [ 70.612068] br0: port 1(eth0) entering forwarding state [ 70.759307] NET: Registered protocol family 10 [ 70.759697] lo: Disabled Privacy Extensions [ 76.661616] RPC: Registered udp transport
Processed: tagging 529697
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 529697 + pending Bug #529697 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: Crystal 4237b audio card not working and causing kernel freeze during boot Added tag(s) 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: Re: Bug#563134: Info received (IDE hard drive not seen by Debian kernel packages since 2.6.31)
Processing commands for cont...@bugs.debian.org: tags 563134 moreinfo Bug #563134 [linux-2.6] boot hard drive IDE interface not found; no ide-gd driver found in dmesg Added tag(s) moreinfo. stop 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: Re: Bug#533885: [linux-image-2.6.30-1-amd64] Stops booting with message that it cannot load av7110/bootcode.bin
Processing commands for cont...@bugs.debian.org: tags 533885 moreinfo Bug #533885 [linux-2.6] [linux-image-2.6.30-1-amd64] Stops booting with message that it cannot load av7110/bootcode.bin Added tag(s) moreinfo. stop 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: Re: Bug#529471:
Processing commands for cont...@bugs.debian.org: tags 529471 moreinfo Bug #529471 [linux-2.6] kvm fails to boot Win XP after update to linux-image-2.6.29-2-686 Added tag(s) moreinfo. stop 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#522156: longer boot time without reason
tags 522156 moreinfo stop can you still reproduce with latest pushed out stable update? 2.6.26-21 also a search on which patch caused the problem if it is still reproducible might be the best. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521548: linux-image-2.6.29-1-amd64: laptop toshiba qosmio g30 fails to boot with 2.6.28 and 2.6.29 kernels
tags 521548 moreinfo stop On Mon, 27 Jul 2009, Fathi Boudra (Debian) wrote: I have started each script by hand and hal script (rc2.d) triggers the bug. is this fixed with 2.6.32 and/or newer hal? -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#527250: marked as done (linux-image-2.6.26-2-686: Occasional superblock read failure at boot)
Your message dated Mon, 1 Feb 2010 14:51:53 +0100 with message-id 20100201135153.gm9...@stro.at and subject line Re: Bug#527250: (no subject) has caused the Debian Bug report #527250, regarding linux-image-2.6.26-2-686: Occasional superblock read failure at boot 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.) -- 527250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-15 Severity: important Hi, I'm using Debian testing. Recently, my computer shows an error-message at boot, resulting in a stop of the boot-proces. Here's the message: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 device This message refers to my hda2-partition. Here's an output of fstab: # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/hda1 / ext3errors=remount-ro 0 1 /dev/hda2 /home ext3defaults0 2 /dev/hda3 noneswapsw 0 0 /dev/hdb/media/cdrom0 udf,iso9660 user,noauto 0 0 I also get the choise to continu the boot-proces by pressing ctrl+D. After that, everything works fine. I have the possibility to log on as root to give some mainentance-commands. But, the proposed command doesn't do anything, nor does the -p option with fsck.ext3. When I restart the computer with kernel 2.6.26-1, everything is normal. I don't get any error-messages. This is /var/log/fsch/checkfs after a boot with 2.6.26-1: fsck 1.41.3 (12-Oct-2008) /dev/hda2: clean, 36983/3973120 files, 4149665/15868203 blocks I tested my harddrive with smartmontools and it doenst give any problem. This is also strange: It doesn't appear every time I boot with kernel 2.6.26-2, only in the minority of the cases. Greetings Steven -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) 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 linux-image-2.6.26-2-686 depends on: ii debconf [debconf-2.0] 1.5.26 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.2 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-2-686 recommends: ii libc6-i6862.9-4 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.26-2-686 suggests: ii grub 0.97-53GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none (no description available) -- debconf information: linux-image-2.6.26-2-686/postinst/bootloader-error-2.6.26-2-686: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-686/postinst/old-dir-initrd-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/overwriting-modules-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/bootloader-test-error-2.6.26-2-686: linux-image-2.6.26-2-686/postinst/depmod-error-2.6.26-2-686: false linux-image-2.6.26-2-686/preinst/bootloader-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/abort-overwrite-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/abort-install-2.6.26-2-686: linux-image-2.6.26-2-686/postinst/depmod-error-initrd-2.6.26-2-686: false linux-image-2.6.26-2-686/postinst/create-kimage-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/failed-to-move-modules-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/initrd-2.6.26-2-686: linux-image-2.6.26-2-686/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-686/prerm/would-invalidate-boot-loader-2.6.26-2-686: true linux-image-2.6.26-2-686/postinst/kimage-is-a-directory: linux-image-2.6.26-2-686/postinst/old-initrd-link-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/elilo-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/preinst/lilo-initrd-2.6.26-2-686: true linux-image-2.6.26-2-686/prerm/removing-running-kernel-2.6.26-2-686: true
Processed: Re: Processed: reassign 514805 to linux-2.6
Processing commands for cont...@bugs.debian.org: tags 514805 moreinfo Bug #514805 [linux-2.6] Error message pcspkr on boot from hard disk Added tag(s) moreinfo. stop 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#533885: [linux-image-2.6.30-1-amd64] Stops booting with message that it cannot load av7110/bootcode.bin
tags 533885 moreinfo stop On Sun, 21 Jun 2009, Resul Cetin wrote: Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-1 Severity: normal I have a Technotrend Premium C-2300 Hybrid and wanted to boot the new linux 2.6.30 kernel. This boot process stops when it loads the modules. I think it said Could not load av7110/bootcode.bin (only took a note with the name of the firmware and not the rest. sry). It is really disturbing that the whole boot process stops and not only the module stops working. I think this has to be fixed when debian strips the firmware blobs. can you still reproduce with 2.6.32 from testing/sid ? thanks for the report. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529471:
tags 529471 moreinfo stop On Tue, 30 Jun 2009, z...@bluemonk.de wrote: P.S. No success with linux-image-2.6.30-1-686 either, which reached Debian/sid. When I start the Windows XP image in kvm with virt-manager, the virtual BIOS appears and I can choose with F12 the boot medium, but the Win XP splash logo does not appear. The console window remains dark. It is possible, that XP is running in the background, because I see no error message - but if so, I have no graphics output. - When I boot with linux-image-2.6.28-1-686, XP starts, how it should. A few weeks past, and I have no idea. what about 2.6.32 that is now in testing? thanks for the feedback -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563134: Info received (IDE hard drive not seen by Debian kernel packages since 2.6.31)
tags 563134 moreinfo stop On Sat, 23 Jan 2010, Bryan Cebuliak wrote: Note to self: Is this Ubuntu kernel bug relevant? Sure sounds familiar: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294123 can you still reproduce with 2.6.32 testing/unstable linux images? do you know of http://wiki.debian.org/InitramfsDebug ?? thanks for the report. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516968: marked as done (base: SATA drive is resumed at boot, even if not used)
Your message dated Mon, 1 Feb 2010 14:55:38 +0100 with message-id 20100201135538.go9...@stro.at and subject line Re: SATA drive usage has caused the Debian Bug report #516968, regarding base: SATA drive is resumed at boot, even if not used 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.) -- 516968: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516968 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: base Severity: important i have extra SATA disk which i use rarely. so to reduce some power consumption and noise - i put the disk to 'start in sleep state'. i've done it with hdparam -s /dev/sdX. obviously i have removed all links in fstab to that drive. to prevent any auto mount. motor of the disk is no longer starting when bios is booting-up the machine, but unfortunetly it does when system starts INIT section (after initrd finishes it's job). i cannot discover what exactly makes disk to start it's motor but it's possibly sata_nv driver - motor begins to work near logs from this driver. i would like to start my extra disks on demand - when they are needed, but as for now i can't do that. Mark -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- just add your small hdparam snipped in /etc/rc.local anyway not a kernel bug, but just a userspace policy, thus closing. ---End Message---
Processed: Re: Bug#541656: linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img
Processing commands for cont...@bugs.debian.org: tags 541656 moreinfo Bug #541656 [linux-2.6] linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img Added tag(s) moreinfo. stop 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#499307: marked as done (base: System hangs on boot when using 2.6.26-1-686)
Your message dated Mon, 1 Feb 2010 15:13:12 +0100 with message-id 20100201141312.gs9...@stro.at and subject line Re: Bug#499307: dpkg information as requsted has caused the Debian Bug report #499307, regarding base: System hangs on boot when using 2.6.26-1-686 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.) -- 499307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=499307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: base Severity: normal If i try to boot up with the latest headers it gets to 'getting console screen modes and fonts' and just hangs. I can only boot up the system if i select 2.6.24-1-686. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On Sun, 26 Jul 2009, Moritz Muehlenhoff wrote: On Thu, Sep 18, 2008 at 05:45:44PM +0100, Aimee Daniells wrote: $ dpkg -l linux-image-2.6.26-1-686 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii linux-image-2. 2.6.26-4 Linux 2.6.26 image on PPro/Celeron/PII/PIII/ Does the error still occur with more recent kernels? Cheers, Moritz closing as no followup since. if you can reproduce with recent testing linux 2.6.32 let us know and the bug will be reopened. thanks for the report. ---End Message---
Bug#555526: marked as done (linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot)
Your message dated Mon, 1 Feb 2010 15:11:08 +0100 with message-id 20100201141108.gr9...@stro.at and subject line Re: Bug#26: linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot has caused the Debian Bug report #26, regarding linux-image-2.6.26-2-686: 2.6.26-19lenny2 with serial console hangs on boot 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.) -- 26: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=26 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal Hello, I upgraded from (I think) 2.6.26-19lenny1 to 2.6.26-19lenny2 with the latest security update and I found my system would hang during the boot. By 'hang' I mean that the boot process seems to stop -- no further messages on the console and the network never came up. The system would not respond to ctrl-alt-del but does respond to the alt-sysrq-cmd keys. The last messages on the console before hang were: ide_generic: please use probe_mask=0x3f module parameter for probing all legacy ISA IDE ports ide_generic: I/O resource 0x1F0-0x1F7 not free. ide_generic: I/O resource 0x170-0x177 not free. I tried various combinations of things like probe_mask=0x3f and ide.probe_mask=0x3f and probe_mask=0x00 and probe_mask=0x30 on the kernel command line and nothing helped. I also moved the hd to a different box (the one I'm reporting this on now) and got the same behavior. (Both before and afger rebuilding the initramfs.) The grub stanza that causes the hang reads: title Debian GNU/Linux, kernel 2.6.26-2-686 root(hd0,0) kernel /vmlinuz-2.6.26-2-686 root=/dev/mapper/vg00-root ro console=tty0 console=ttyS0,9600n8 initrd /initrd.img-2.6.26-2-686 The system boots successfully after changing this to: title Debian GNU/Linux, kernel 2.6.26-2-686 root(hd0,0) kernel /vmlinuz-2.6.26-2-686 root=/dev/mapper/vg00-root ro initrd /initrd.img-2.6.26-2-686 (But then of course I don't have a serial console, afaict.) -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-19lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed Nov 4 20:45:37 UTC 2009 ** Command line: root=/dev/mapper/vg00-root ro ** Not tainted ** Kernel log: [4.316922] ide0: BM-DMA at 0xffa0-0xffa7 [4.316987] ide1: BM-DMA at 0xffa8-0xffaf [4.317044] Probing IDE interface ide0... [4.620228] hda: WDC WD3000JB-00KFA0, ATA DISK drive [5.100921] Floppy drive(s): fd0 is 1.44M [5.118551] FDC 0 is a National Semiconductor PC87306 [5.292172] hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [5.292264] hda: host side 80-wire cable detection failed, limiting max speed to UDMA33 [5.292339] hda: UDMA/33 mode selected [5.292483] Probing IDE interface ide1... [6.028165] hdc: CRD-8482B, ATAPI CD/DVD-ROM drive [6.700146] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [6.700259] hdc: Disabling (U)DMA for CRD-8482B (blacklisted) [6.700327] hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 [6.700449] ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 [6.700583] ide1 at 0x170-0x177,0x376 on irq 15 [6.701727] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 [6.701788] PCI: setting IRQ 10 as level-triggered [6.701797] ACPI: PCI Interrupt :02:08.0[A] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 [6.701944] 3c59x: Donald Becker and others. [6.702002] :02:08.0: 3Com PCI 3c905C Tornado at d0814c00. [6.724852] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5 [6.724911] PCI: setting IRQ 5 as level-triggered [6.724919] ACPI: PCI Interrupt :02:0c.0[A] - Link [LNKC] - GSI 5 (level, low) - IRQ 5 [6.725070] :02:0c.0: 3Com PCI 3c905C Tornado at d0816800. [6.756588] No dock devices found. [6.803585] SCSI subsystem initialized [6.860416] libata version 3.00 loaded. [6.966478] hda: max request size: 512KiB [6.984508] hda: 586072368 sectors (300069 MB) w/8192KiB Cache, CHS=36481/255/63 [6.984791] hda: cache flushes supported [6.984959] hda: hda1 hda2 hda5 [6.998812] hdc: ATAPI 48X CD-ROM drive, 128kB Cache [6.999008] Uniform CD-ROM driver Revision: 3.20 [7.329486] device-mapper: uevent: version 1.0.3 [7.331621] device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-de...@redhat.com [8.154160] PM: Starting manual resume from disk [8.259325] kjournald
Processed: Re: Bug#541656: linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img
Processing commands for cont...@bugs.debian.org: tags 541656 moreinfo Bug #541656 [linux-2.6] linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img Ignoring request to alter tags of bug #541656 to the same tags previously set stop 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#514805: Processed: reassign 514805 to linux-2.6
tags 514805 moreinfo stop can you still reproduce with more recent linux images like 2.6.32 from squeeze? thanks for report. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: first boot hangs
Processing commands for cont...@bugs.debian.org: tags 537173 moreinfo Bug #537173 [linux-2.6] first boot hangs Added tag(s) moreinfo. stop 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
Processing of linux-2.6_2.6.32-6_multi.changes
linux-2.6_2.6.32-6_multi.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.32-6.dsc linux-2.6_2.6.32-6.diff.gz linux-support-2.6.32-1_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb firmware-linux-free_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb linux-doc-2.6.32_2.6.32-6_all.deb linux-manual-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#539209: marked as done (linux-2.6.30-1-686: Please enable preemption)
Your message dated Mon, 1 Feb 2010 15:27:03 +0100 with message-id 20100201142703.gv9...@stro.at and subject line Re: please add CONFIG_PREEMPT has caused the Debian Bug report #311185, regarding linux-2.6.30-1-686: Please enable preemption 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.) -- 311185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6.30-1-686 Severity: normal I just discovered that the Debian kernel packages do not have preemption enabled: CONFIG_PREEMPT_NONE=y # CONFIG_PREEMPT is not set Some checking suggests that this choice dates back to the very early 2.6 kernel days, when preemption still represented an experimental option and much kernel code still needed fixing to work properly with it. That has not held true for a very long time, and CONFIG_PREEMPT now represents the more common kernel configuration. Please consider switching from CONFIG_PREEMPT_NONE to CONFIG_PREEMPT. - Josh Triplett -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Version: 2.6.32-1 enable in latest linux images, thus closing. ---End Message---
Bug#496871: marked as done (linux-2.6: please change the PREEMPT settings)
Your message dated Mon, 1 Feb 2010 15:27:03 +0100 with message-id 20100201142703.gv9...@stro.at and subject line Re: please add CONFIG_PREEMPT has caused the Debian Bug report #311185, regarding linux-2.6: please change the PREEMPT settings 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.) -- 311185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: normal Hi, Bugs #292061 and #311185 are contradictory. One asks for it to be disabled, the other enabled. I spoke with Simon Horman and he said: wildfire horms, why doesn't the debian linux kernel set preempt to on? horms wildfire: nfi horms i believe back in my day it was too experimental horms but i have no idea why it is still off We also checked a few other distributions: Ubuntu (feisty): CONFIG_PREEMPT_VOLUNTARY=y/CONFIG_PREEMPT_BKL=y RHEL 5.1: CONFIG_PREEMPT_VOLUNTARY=y, CONFIG_PREEMPT_BKL=y master.kernel.org: CONFIG_PREEMPT_NOTIFIERS=y, CONFIG_PREEMPT_VOLUNTARY=y (all machines are either ia64 or x86_64) So the censensus would seem to be to set: CONFIG_PREEMPT_VOLUNTARY=y CONFIG_PREEMPT_BKL=y CONFIG_PREEMPT_NOTIFIERS=y (already set in Debian) Could you please make it so, and close out the two above-mentioned reports? Thanks, Anand -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (1, 'experimental') 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=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Version: 2.6.32-1 enable in latest linux images, thus closing. ---End Message---
Bug#311185: marked as done (kernel-image-2.6.11-powerpc: please add CONFIG_PREEMPT)
Your message dated Mon, 1 Feb 2010 15:27:03 +0100 with message-id 20100201142703.gv9...@stro.at and subject line Re: please add CONFIG_PREEMPT has caused the Debian Bug report #311185, regarding kernel-image-2.6.11-powerpc: please add CONFIG_PREEMPT 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.) -- 311185: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel-image-2.6.11-powerpc Version: 2.6.11-2 Severity: normal please add CONFIG_PREEMPT to kernel configuration -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages kernel-image-2.6.11-powerpc depends on: ii initrd-tools 0.1.81.1 tools to create initrd image for p ii mkvmlinuz 13 create a kernel to boot a PowerPC ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.6.32-1 enable in latest linux images, thus closing. ---End Message---
Bug#398362: marked as done (please enable backwards compatibility)
Your message dated Mon, 1 Feb 2010 15:30:07 +0100 with message-id 20100201143007.gw9...@stro.at and subject line please enable backwards compat has caused the Debian Bug report #398362, regarding please enable backwards compatibility 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.) -- 398362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: squashfs-modules-2.6.17-2-686 Severity: wishlist Trying to mount an 1.0 filesystem, I get this error (in dmesg): SQUASHFS error: Major/Minor mismatch, Squashfs 1.0 filesystems are unsupported SQUASHFS error: Please recompile with Squashfs 1.0 support enabled Please can you enable compatibility with older filesystems? I think the following options will do: CONFIG_SQUASHFS_1_0_COMPATIBILITY CONFIG_SQUASHFS_2_0_COMPATIBILITY Thanks! -- Robert Millan ACK STORM, S.L. - http://www.ackstorm.es/ ---End Message--- ---BeginMessage--- squashfs is enabled with the features present in linux-2.6 backwards compat for old format is not included and thus can't be enabled. closing. ---End Message---
Bug#507725: marked as done (squashfs-modules-2.6-686: please enable SquashFS 1.0 support)
Your message dated Mon, 1 Feb 2010 15:30:07 +0100 with message-id 20100201143007.gw9...@stro.at and subject line please enable backwards compat has caused the Debian Bug report #398362, regarding squashfs-modules-2.6-686: please enable SquashFS 1.0 support 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.) -- 398362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=398362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: squashfs-modules-2.6-686 Version: 2:2.6.26-4 Severity: wishlist mas...@bagnat:~/EMINENT$ sudo mount -t squashfs -o loop 0 /mnt/ mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so mas...@bagnat:~/EMINENT$ dmesg |tail -n2 [43287.986603] SQUASHFS error: Major/Minor mismatch, Squashfs 1.0 filesystems are unsupported [43287.986619] SQUASHFS error: Please recompile with Squashfs 1.0 support enabled Would it be possible to do so by default? Thanks in advance. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages squashfs-modules-2.6-686 depends on: ii linux-image-2.6-686 [linux- 2.6.26+16Linux 2.6 image on PPro/Celeron/PI ii squashfs-modules-2.6.26-1-6 2.6.26+3.3-4 Compression filesystem for Linux 2 squashfs-modules-2.6-686 recommends no packages. squashfs-modules-2.6-686 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- squashfs is enabled with the features present in linux-2.6 backwards compat for old format is not included and thus can't be enabled. closing. ---End Message---
Bug#541656: linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img
maximilian attems wrote, on 02/02/10 00:38: tags 541656 moreinfo stop On Sat, 15 Aug 2009, Arthur Marsh wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-6~snapshot.14108 Severity: normal When attempting to upgrade I get: Setting up linux-image-2.6.30-1-686 (2.6.30-6~snapshot.14108) ... Running depmod. Running update-initramfs. Other valid candidates: update-initramfs mkinitrd.yaird update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img. dpkg: error processing linux-image-2.6.30-1-686 (--configure): subprocess installed post-installation script returned error exit status 17 can you still reproduce with 2.6.32 in squeeze/sid? No, it works fine now: $ ls -al /|grep init* lrwxrwxrwx 1 root root 32 Dec 10 22:50 initrd.img - boot/initrd.img-2.6.32-trunk-686 what is the output of cat /etc/kernel-img.conf $ cat /etc/kernel-img.conf # Do not create symbolic links in / do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in_boot = no postinst_hook = /usr/sbin/update-grub postrm_hook = /usr/sbin/update-grub sorry for the late answer, thanks for the report. Feel free to close this bug if you want. Arthur. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541656: linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img
tags 541656 moreinfo stop On Sat, 15 Aug 2009, Arthur Marsh wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-6~snapshot.14108 Severity: normal When attempting to upgrade I get: Setting up linux-image-2.6.30-1-686 (2.6.30-6~snapshot.14108) ... Running depmod. Running update-initramfs. Other valid candidates: update-initramfs mkinitrd.yaird update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img. dpkg: error processing linux-image-2.6.30-1-686 (--configure): subprocess installed post-installation script returned error exit status 17 can you still reproduce with 2.6.32 in squeeze/sid? what is the output of cat /etc/kernel-img.conf sorry for the late answer, thanks for the report. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540413: marked as done (cpufreq_ondemand no longer works with Pentium 4)
Your message dated Mon, 1 Feb 2010 15:37:54 +0100 with message-id 20100201143754.gx9...@stro.at and subject line Re: Bug#540413: linux-image-2.6.30-bpo.1-686: ondemand cpu frequency scaling not working has caused the Debian Bug report #540413, regarding cpufreq_ondemand no longer works with Pentium 4 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.) -- 540413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-bpo.1-686 Version: 2.6.30-3~bpo50+1 Severity: important The ondemand cpu frequency scaling governor doesn't work (or is not built in the kernel). I had no problem with previous kernel versions (up to 2.6.29). The frequency scaling works if I use a different governor (powersave, userspace, etc) but it doesn't change the frequency automatically anymore. Sorry if I reported the bug the bug incorrectly or more then once, it's the first time I use the reportbug tool. Have a nice day, Paolo. -- Package-specific info: ** Version: Linux version 2.6.30-bpo.1-686 (Debian 2.6.30-3~bpo50+1) (no...@debian.org) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 SMP Sat Jul 18 22:19:04 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.30-bpo.1-686 root=UUID=73b2ff46-a22b-42af-bfb4-27226a224927 ro ** Tainted: P (1) ** Kernel log: [ 115.616261] usb-storage: waiting for device to settle before scanning [ 118.376224] ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready [ 120.616176] usb-storage: device scan complete [ 120.617538] scsi 1:0:0:0: Direct-Access RIM BlackBerry SD0002 PQ: 0 ANSI: 0 CCS [ 120.720082] Driver 'sd' needs updating - please use bus_type methods [ 120.724978] sd 1:0:0:0: [sda] Attached SCSI removable disk [ 128.528024] ath0: no IPv6 routers present [ 129.805419] ACPI: EC: GPE storm detected, transactions will use polling mode [ 162.460024] ath0: no IPv6 routers present [ 713.520044] usb 3-2: reset high speed USB device using ehci_hcd and address 4 [ 713.663163] scsi2 : SCSI emulation for USB Mass Storage devices [ 713.685053] usb-storage: device found at 4 [ 713.685055] usb-storage: waiting for device to settle before scanning [ 718.684136] usb-storage: device scan complete [ 718.684693] scsi 2:0:0:0: Direct-Access RIM BlackBerry SD0002 PQ: 0 ANSI: 0 CCS [ 718.700567] sd 2:0:0:0: [sda] Attached SCSI removable disk [ 1316.472034] usb 3-2: reset high speed USB device using ehci_hcd and address 4 [ 1316.615263] scsi3 : SCSI emulation for USB Mass Storage devices [ 1316.637337] usb-storage: device found at 4 [ 1316.637338] usb-storage: waiting for device to settle before scanning [ 1321.636122] usb-storage: device scan complete [ 1321.636628] scsi 3:0:0:0: Direct-Access RIM BlackBerry SD0002 PQ: 0 ANSI: 0 CCS [ 1321.648826] sd 3:0:0:0: [sda] Attached SCSI removable disk [ 6751.060033] usb 3-2: reset high speed USB device using ehci_hcd and address 4 [ 6751.203232] scsi4 : SCSI emulation for USB Mass Storage devices [ 6751.220448] usb-storage: device found at 4 [ 6751.220450] usb-storage: waiting for device to settle before scanning [ 7076.948040] usb 3-2: reset high speed USB device using ehci_hcd and address 4 [ 7077.091368] scsi5 : SCSI emulation for USB Mass Storage devices [ 7077.117362] usb-storage: device found at 4 [ 7077.117364] usb-storage: waiting for device to settle before scanning [ 7082.116192] usb-storage: device scan complete [ 7082.117674] scsi 5:0:0:0: Direct-Access RIM BlackBerry SD0002 PQ: 0 ANSI: 0 CCS [ 7082.124292] sd 5:0:0:0: [sda] Attached SCSI removable disk [ 9683.383499] usb 3-2: USB disconnect, address 4 [15046.789431] vboxdrv: Trying to deactivate the NMI watchdog permanently... [15046.789434] vboxdrv: Successfully done. [15046.789434] vboxdrv: Found 1 processor cores. [15046.789504] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [15046.792051] vboxdrv: Successfully loaded version 3.0.4 (interface 0x000e). [16197.276054] usb 3-2: new high speed USB device using ehci_hcd and address 5 [16197.409416] usb 3-2: New USB device found, idVendor=0fca, idProduct=8004 [16197.409419] usb 3-2: New USB device strings: Mfr=1, Product=5, SerialNumber=3 [16197.409421] usb 3-2: Product: RIM Composite Device [16197.409422] usb 3-2: Manufacturer: Research In Motion [16197.409423] usb 3-2: SerialNumber: 81B7BA9CA77FA873820D7CC7905BF019F38F [16197.409489] usb 3-2: configuration #1 chosen from 1 choice [16197.417704] scsi6 : SCSI emulation for USB Mass Storage devices [16197.417897]
Bug#537173: first boot hangs
tags 537173 moreinfo stop can you still reproduce with the latest linux-2.6 images that reached either testing or stable? thanks for the report -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551786: marked as done (linux-image-2.6.26-2-686-bigmem: disk write performance regression)
Your message dated Mon, 1 Feb 2010 15:40:00 +0100 with message-id 20100201144000.gy9...@stro.at and subject line Re: Bug#551786: linux-image-2.6.26-2-686-bigmem: disk write performance regression has caused the Debian Bug report #551786, regarding linux-image-2.6.26-2-686-bigmem: disk write performance regression 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.) -- 551786: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=551786 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686-bigmem Version: 2.6.26-19 Severity: normal File: /boot/vmlinuz-2.6.26-2-686-bigmem Tags: patch We encountered a serious disk write performance regression after upgrading from the etch kernel (2.6.18) to the etchnhalf kernel (2.6.24). Co-workers of mine stumbled over the issue using OpenLDAP (with the Berkeley DB backend) while restoring about 60,000 medium-sized records with slapadd. As soon as they define an index with sub in their slapd.conf, the restore performance goes south and the load increases dramatically. The restore won't be finished after half an hour, while it's done within a few minutes when runnning 2.6.18. We were able to reproduce the problem on systems running lenny (with the stock 2.6.26 kernel), on different hardware, with different file systems, and with different OpenLDAP versions (we tested this with OpenLDAP 2.3.30, 2.4.13, 2.4.16, 2.4.18, and 2.4.19). However, I'm not aware of another way to trigger the issue, sorry. The problem is not Debian-specific. It was introduced with the kernel Git commit v2.6.21-1-g07db59b, which lowered the default dirty-writeback limits; and has been fixed with commit v2.6.29-4-g1b5e62b, which raised these settings again (though not to the original values). Backporting the new settings from v2.6.29-4-g1b5e62b fixes the problem for us. The attached patch should be applicable to both 2.6.26 from lenny and 2.6.24 from etchnhalf. --- a/mm/page-writeback.c +++ b/mm/page-writeback.c @@ -66,7 +66,7 @@ static inline long sync_writeback_pages(void) /* * Start background writeback (via pdflush) at this percentage */ -int dirty_background_ratio = 5; +int dirty_background_ratio = 10; /* * free highmem will not be subtracted from the total free memory @@ -77,7 +77,7 @@ int vm_highmem_is_dirtyable; /* * The generator of dirty data starts writeback at this percentage */ -int vm_dirty_ratio = 10; +int vm_dirty_ratio = 20; /* * The interval between `kupdate'-style writebacks, in jiffies ---End Message--- ---BeginMessage--- On Wed, 21 Oct 2009, Ben Hutchings wrote: On Tue, 2009-10-20 at 19:03 +0200, Holger Weiss wrote: Package: linux-image-2.6.26-2-686-bigmem Version: 2.6.26-19 Severity: normal File: /boot/vmlinuz-2.6.26-2-686-bigmem Tags: patch We encountered a serious disk write performance regression after upgrading from the etch kernel (2.6.18) to the etchnhalf kernel (2.6.24). [...] The attached patch should be applicable to both 2.6.26 from lenny and 2.6.24 from etchnhalf. Although it is apparently beneficial for your workload, it might have negative effects on others. This change has not been applied to the 2.6.27 stable series so I'm not convinced that it is suitable material for a Debian stable update either. These variables can be changed by sysctl, so I recommend that instead of patching your kernel you add these lines to /etc/sysctl.conf: vm.dirty_background_ratio = 10 vm.dirty_ratio = 20 thanks for you report, closing as no further testings or benchmarks, gave a strong hint that this patch is indeed backportable. ---End Message---
Bug#541656: marked as done (linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img )
Your message dated Mon, 1 Feb 2010 15:36:43 +0100 with message-id 20100201143642.gr9...@baikonur.stro.at and subject line Re: Bug#541656: linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img has caused the Debian Bug report #541656, regarding linux-image-2.6.30-1-686: Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img 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.) -- 541656: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-686 Version: 2.6.30-6~snapshot.14108 Severity: normal When attempting to upgrade I get: Setting up linux-image-2.6.30-1-686 (2.6.30-6~snapshot.14108) ... Running depmod. Running update-initramfs. Other valid candidates: update-initramfs mkinitrd.yaird update-initramfs: Generating /boot/initrd.img-2.6.30-1-686 Failed to symbolic-link boot/initrd.img-2.6.30-1-686 to initrd.img. dpkg: error processing linux-image-2.6.30-1-686 (--configure): subprocess installed post-installation script returned error exit status 17 -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.31-rc5 (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.30-1-686 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.13-5 Yet Another mkInitRD Versions of packages linux-image-2.6.30-1-686 recommends: ii libc6-i6862.9-24 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.30-1-686 suggests: ii grub-pc [grub] 1.96+20090808-2 GRand Unified Bootloader, version pn linux-doc-2.6.30 none (no description available) -- debconf-show failed ---End Message--- ---BeginMessage--- On Tue, Feb 02, 2010 at 12:52:11AM +1030, Arthur Marsh wrote: sorry for the late answer, thanks for the report. Feel free to close this bug if you want. thanks for the quick feedback, doing so. ---End Message---
Bug#531273: marked as done (linux-image-2.6.26-2-amd64: not powering off: boot CPU gets halted)
Your message dated Mon, 1 Feb 2010 15:21:23 +0100 with message-id 20100201142122.gt9...@stro.at and subject line Re: Processed: Re: Bug#531273 closed by Bastian Blank wa...@debian.org has caused the Debian Bug report #531273, regarding linux-image-2.6.26-2-amd64: not powering off: boot CPU gets halted 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.) -- 531273: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=531273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15lenny2 Severity: normal Often, but not always my desktop refuses to power down. The last messages are (copied manually): [34709.779040] ACPI: Preparing to enter system sleep state S5 [34709.779040] Disabling non-boot CPUs ... [34709.779040] CPU0 attach NULL sched-domain. [34709.779040] CPU1 attach NULL sched-domain. -- Package-specific info: ** Version: Linux version 2.6.26-2-amd64 (Debian 2.6.26-15lenny2) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Wed May 13 15:37:46 UTC 2009 ** Command line: root=/dev/twin_vg/root rootflags=data=journal ro usbcore.autosuspend=1 nomsi ** Tainted: P (1) ** Kernel log: [ 32.668128] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.668128] EXT3 FS on dm-3, internal journal [ 32.668128] EXT3-fs: mounted filesystem with journal data mode. [ 32.741477] kjournald starting. Commit interval 30 seconds [ 32.745475] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.745475] EXT3 FS on dm-6, internal journal [ 32.745475] EXT3-fs: mounted filesystem with journal data mode. [ 32.819547] kjournald starting. Commit interval 30 seconds [ 32.819547] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.819547] EXT3 FS on dm-7, internal journal [ 32.819547] EXT3-fs: mounted filesystem with journal data mode. [ 32.955547] kjournald starting. Commit interval 30 seconds [ 32.955667] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 32.955667] EXT3 FS on dm-9, internal journal [ 32.955667] EXT3-fs: mounted filesystem with journal data mode. [ 33.096664] kjournald starting. Commit interval 30 seconds [ 33.099579] EXT3-fs warning: mounting fs with errors, running e2fsck is recommended [ 33.099843] EXT3 FS on dm-1, internal journal [ 33.099916] EXT3-fs: mounted filesystem with journal data mode. [ 33.174490] kjournald starting. Commit interval 30 seconds [ 33.174490] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 33.175538] EXT3 FS on dm-4, internal journal [ 33.175612] EXT3-fs: mounted filesystem with journal data mode. [ 33.339127] kjournald starting. Commit interval 30 seconds [ 33.340966] EXT3 FS on dm-19, internal journal [ 33.340966] EXT3-fs: mounted filesystem with journal data mode. [ 33.610890] kjournald starting. Commit interval 30 seconds [ 33.615114] EXT3-fs warning: maximal mount count reached, running e2fsck is recommended [ 33.615114] EXT3 FS on dm-11, internal journal [ 33.615114] EXT3-fs: mounted filesystem with journal data mode. [ 33.995726] Adding 4194296k swap on /dev/mapper/twin_vg-swap. Priority:-1 extents:1 across:4194296k [ 35.700773] NET: Registered protocol family 15 [ 37.710104] ip_tables: (C) 2000-2006 Netfilter Core Team [ 37.757428] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [ 38.029337] r8169: eth0: link down [ 38.080927] device eth0 entered promiscuous mode [ 38.922927] NET: Registered protocol family 10 [ 38.923630] lo: Disabled Privacy Extensions [ 38.924375] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 40.933439] powernow-k8: Found 1 AMD Athlon(tm) X2 Dual Core Processor BE-2300 processors (2 cpu cores) (version 2.20.00) [ 40.933439] powernow-k8:0 : fid 0xb (1900 MHz), vid 0xc [ 40.933444] powernow-k8:1 : fid 0xa (1800 MHz), vid 0xd [ 40.933447] powernow-k8:2 : fid 0x2 (1000 MHz), vid 0x16 [ 56.287861] pnp: the driver 'parport_pc' has been registered [ 56.290395] lp: driver loaded but no devices found [ 56.353332] ppdev: user-space parallel port driver [ 57.202148] Clocksource tsc unstable (delta = -125107490 ns) [ 65.094860] Bluetooth: Core ver 2.11 [ 65.096894] NET: Registered protocol family 31 [ 65.096924] Bluetooth: HCI device and connection manager initialized [ 65.096951] Bluetooth: HCI socket layer initialized [ 65.126865] Bluetooth: L2CAP ver 2.9 [ 65.126865] Bluetooth:
Bug#565789: marked as done (say what the current Thinkpad BIOS/Firmware should be)
Your message dated Mon, 1 Feb 2010 16:08:22 +0100 with message-id 20100201150822.gz9...@stro.at and subject line Re: Bug#565789: [ltp] Re: Bug#565789: say what the current Thinkpad BIOS/Firmware should be has caused the Debian Bug report #565789, regarding say what the current Thinkpad BIOS/Firmware should be 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.) -- 565789: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565789 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-5 Severity: wishlist File: /lib/modules/2.6.32-trunk-686/kernel/drivers/platform/x86/thinkpad_acpi.ko X-debbugs-Cc: ibm-acpi-de...@lists.sourceforge.net, linux-think...@linux-thinkpad.org We see ThinkPad ACPI Extras v0.23 http://ibm-acpi.sf.net/ ThinkPad BIOS 1WET88WW (2.08 ), EC 1VHT28WW-1.04 IBM ThinkPad R50e, model 1834NV1 WARNING: Outdated ThinkPad BIOS/EC firmware WARNING: This firmware may be missing critical bug fixes and/or important features Perhaps it could mention what it believes the current versions should be, so we can check the IBM website before decide we have send the unit back to IBM to get whatever it is that is bothering it updated (as we Linux users can't update the BIOS ourselves.) Also it could mention perhaps some URLs on where it got its information about what is current from. ---End Message--- ---BeginMessage--- On Thu, 21 Jan 2010, Yves-Alexis Perez wrote: On jeu., 2010-01-21 at 13:29 +0800, jida...@jidanni.org wrote: SM == Shannon McMackin smcmac...@gmail.com writes: SM I think it's wonderful that the current version at least knows what SM the current BIOS rev is, that in itself is a huge amount of work to SM add in considering the variety of ThinkPad models. upstream decided not to add the requested addtional info. It seems more appropriate to ask Lenovo for better Linux support. as this beyond a debian bug, closing. thanks for the report. ---End Message---
Bug#567965: i915: KMS framebuffer fails to work, only X works
Package: linux-2.6 Version: 2.6.32-5 Severity: important Since a few days, my screen stays black except for VT7 where X is running. As soon as the kernel is loaded, the screen turns black until X is loaded. When X is loaded, switching to anything else than VT7 just causes the mouse pointer to disappear, but the image from X is still displayed. I don't know when exactly this started to happen, but I know that my last kernel update was 2.6.32-3 = 2.6.32-5. -- Package-specific info: ** Version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-amd64 root=UUID=67091a05-bf38-4136-b876-09e4b81a44bc ro quiet ** Not tainted ** Kernel log: [ 17.289425] HDA Intel :00:1b.0: power state changed by ACPI to D0 [ 17.289440] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 17.289494] HDA Intel :00:1b.0: setting latency timer to 64 [ 17.335801] Bluetooth: Core ver 2.15 [ 17.338847] NET: Registered protocol family 31 [ 17.338850] Bluetooth: HCI device and connection manager initialized [ 17.338853] Bluetooth: HCI socket layer initialized [ 17.343023] Bluetooth: Generic Bluetooth USB driver ver 0.6 [ 17.343167] usbcore: registered new interface driver btusb [ 17.356896] phy0: Selected rate control algorithm 'iwl-3945-rs' [ 17.397928] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1a0b1, caps: 0xa04713/0x20 [ 17.415983] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input7 [ 17.438975] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input8 [ 17.843912] name_count maxed, losing inode data: dev=00:07, inode=4547 [ 17.843928] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.843934] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.844612] name_count maxed, losing inode data: dev=00:07, inode=8 [ 17.844617] name_count maxed, losing inode data: dev=00:07, inode=4552 [ 17.844633] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.844640] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.845425] name_count maxed, losing inode data: dev=00:07, inode=8 [ 17.845430] name_count maxed, losing inode data: dev=00:07, inode=4558 [ 17.845446] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.845453] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.847392] name_count maxed, losing inode data: dev=00:07, inode=8 [ 17.847398] name_count maxed, losing inode data: dev=00:07, inode=4576 [ 17.847417] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.847424] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.848419] name_count maxed, losing inode data: dev=00:07, inode=8 [ 17.848425] name_count maxed, losing inode data: dev=00:07, inode=4588 [ 17.848443] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.848450] name_count maxed, losing inode data: dev=00:05, inode=4 [ 17.849787] name_count maxed, losing inode data: dev=00:07, inode=8 [ 17.849793] name_count maxed, losing inode data: dev=00:07, inode=4600 [ 17.849800] loop: module loaded [ 17.859646] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 18.133588] EXT4-fs (sda5): mounted filesystem with ordered data mode [ 18.216617] Adding 1024280k swap on /swap. Priority:-1 extents:39 across:9918340k [ 19.612777] vboxdrv: Trying to deactivate the NMI watchdog permanently... [ 19.612782] vboxdrv: Warning: 2.6.31+ kernel detected. Most likely the hardware performance [ 19.612784] vboxdrv: counter framework which can generate NMIs is active. You have to prevent [ 19.612786] vboxdrv: the usage of hardware performance counters by [ 19.612787] vboxdrv: echo 2 /proc/sys/kernel/perf_counter_paranoid [ 19.617905] vboxdrv: Found 2 processor cores. [ 19.617973] VBoxDrv: dbg - g_abExecMemory=a04e41a0 [ 19.617996] vboxdrv: fAsync=0 offMin=0x150 offMax=0x1440 [ 19.618045] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 19.618048] vboxdrv: Successfully loaded version 3.1.2_OSE (interface 0x0011). [ 19.659880] vboxNetAdpOpen returns 0 [ 19.717301] e1000e :00:19.0: irq 27 for MSI/MSI-X [ 19.772104] e1000e :00:19.0: irq 27 for MSI/MSI-X [ 19.772398] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 20.046493] fuse init (API version 7.13) [ 20.257436] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input9 [ 27.665352] Bluetooth: L2CAP ver 2.14 [ 27.665358] Bluetooth: L2CAP socket layer initialized [ 27.672809] Bluetooth: RFCOMM TTY layer initialized [ 27.672814] Bluetooth: RFCOMM socket layer initialized [ 27.672816] Bluetooth: RFCOMM ver 1.11 [ 27.778921] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 27.778924] Bluetooth: BNEP filters: protocol multicast [ 27.787495] Bridge firewalling registered [
Processed: Re: HAL deamon locks computer on boot,
Processing commands for cont...@bugs.debian.org: tags 542772 moreinfo Bug #542772 [linux-2.6] hal: HAL deamon locks computer on boot, needs powercycling to recover Ignoring request to alter tags of bug #542772 to the same tags previously set stop 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#567204: serious filesystem corruption with bigmem kernels
Package: linux-image-686-bigmem Severity: normal i started a reportbug run with the real kernel name. this is the outcome: Subject: linux-image-2.6.32-trunk-686-bigmem: mockup report for fscorruption Package: linux-2.6 Version: 2.6.32-5 Justification: causes non-serious data loss Severity: grave -- Package-specific info: ** Version: Linux version 2.6.32-trunk-686-bigmem (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 07:12:17 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-686-bigmem root=UUID=fbdfdf29-80a2-47f7-9996-a8be95c9ad59 ro acpi_osi=Linux quiet ** Not tainted ** Kernel log: [6.158433] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.158435] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [6.158438] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [6.158668] cfg80211: Calling CRDA for country: US [6.181926] usbcore: registered new interface driver cdc_ether [6.216764] usbcore: registered new interface driver zaurus [6.320600] uvcvideo: Found UVC 1.00 device unnamed (17ef:4807) [6.322069] input: UVC Camera (17ef:4807) as /devices/pci:00/:00:1a.7/usb1/1-6/1-6:1.0/input/input7 [6.322130] usbcore: registered new interface driver uvcvideo [6.322232] USB Video Class driver (v0.1.0) [6.332030] usbcore: registered new interface driver hiddev [6.334766] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:1a.7/usb1/1-5/1-5.3/1-5.3:1.0/input/input8 [6.334836] generic-usb 0003:046D:C03E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1a.7-5.3/input0 [6.334853] usbcore: registered new interface driver usbhid [6.334855] usbhid: v2.6:USB HID core driver [6.396051] usb 4-2: new full speed USB device using uhci_hcd and address 3 [6.549439] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [6.551241] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [6.551942] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [6.552523] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [6.553274] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [6.569065] usb 4-2: New USB device found, idVendor=0a5c, idProduct=2145 [6.569068] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.569072] usb 4-2: Product: ThinkPad Bluetooth with Enhanced Data Rate II [6.569075] usb 4-2: Manufacturer: Lenovo Computer Corp [6.569173] usb 4-2: configuration #1 chosen from 1 choice [6.644184] Bluetooth: Core ver 2.15 [6.644216] NET: Registered protocol family 31 [6.644217] Bluetooth: HCI device and connection manager initialized [6.644219] Bluetooth: HCI socket layer initialized [6.786581] Bluetooth: Generic Bluetooth USB driver ver 0.6 [6.786662] usbcore: registered new interface driver btusb [6.906438] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks [6.906440] iwlagn: Copyright(c) 2003-2009 Intel Corporation [6.906490] iwlagn :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [6.906498] iwlagn :03:00.0: setting latency timer to 64 [6.906526] iwlagn :03:00.0: Detected Intel Wireless WiFi Link 5100AGN REV=0x54 [6.945601] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [6.945674] iwlagn :03:00.0: irq 30 for MSI/MSI-X [6.993939] phy0: Selected rate control algorithm 'iwl-agn-rs' [7.217236] HDA Intel :00:1b.0: PCI INT B - GSI 17 (level, low) - IRQ 17 [7.217264] HDA Intel :00:1b.0: setting latency timer to 64 [7.285683] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [7.285757] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input10 [7.285802] input: HDA Intel Mic as /devices/pci:00/:00:1b.0/sound/card0/input11 [7.285846] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input12 [8.415533] Adding 4939976k swap on /dev/sda2. Priority:-1 extents:1 across:4939976k [8.612920] EXT3 FS on sda1, internal journal [8.755456] loop: module loaded [ 11.284861] input: PS/2 Generic Mouse as /devices/platform/i8042/serio1/serio2/input/input13 [ 11.960043] usb 2-4: new high speed USB device using
Bug#542772: HAL deamon locks computer on boot,
tags 542772 moreinfo stop Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core) can you reproduce aboves with current 2.6.32 in Testing / sid?? thanks for the report. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565353: Info received (Bug#565353: Offer of testing)
Transferred about a terabyte over NFS over 3 days whilst under disk/CPU load - with no apparent problems, thanks. Tim. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6_2.6.32-6_multi.changes is NEW
firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb (new) linux-headers-2.6.32-1-486_2.6.32-6_i386.deb optional kernel Header files for Linux 2.6.32-1-486 This package provides the architecture-specific kernel header files for Linux kernel 2.6.32-1-486, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.32-1-486, and can be used for building modules that load into the kernel provided by the linux-image-2.6.32-1-486 package. (new) linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb optional kernel Header files for Linux 2.6.32-1-686-bigmem This package provides the architecture-specific kernel header files for Linux kernel 2.6.32-1-686-bigmem, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.32-1-686-bigmem, and can be used for building modules that load into the kernel provided by the linux-image-2.6.32-1-686-bigmem package. (new) linux-headers-2.6.32-1-686_2.6.32-6_i386.deb optional kernel Header files for Linux 2.6.32-1-686 This package provides the architecture-specific kernel header files for Linux kernel 2.6.32-1-686, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.32-1-686, and can be used for building modules that load into the kernel provided by the linux-image-2.6.32-1-686 package. (new) linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb optional kernel All header files for Linux 2.6.32 This package depends against all architecture-specific kernel header files for Linux kernel version 2.6.32, generally used for building out-of-tree kernel modules. (new) linux-headers-2.6.32-1-all_2.6.32-6_i386.deb optional kernel All header files for Linux 2.6.32 This package depends against all architecture-specific kernel header files for Linux kernel version 2.6.32, generally used for building out-of-tree kernel modules. (new) linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb optional kernel Header files for Linux 2.6.32-1-amd64 This package provides the architecture-specific kernel header files for Linux kernel 2.6.32-1-amd64, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.32-1-amd64, and can be used for building modules that load into the kernel provided by the linux-image-2.6.32-1-amd64 package. (new) linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb optional kernel Common header files for Linux 2.6.32-1-vserver This package provides the architecture-specific common kernel header files for Linux kernel version 2.6.32-1-vserver, generally used for building out-of-tree kernel modules. To obtain a complete set of headers you also need to install the linux-headers-2.6.32-1-(flavour) package, matching the flavour of the kernel you intend the build for. (new) linux-headers-2.6.32-1-common_2.6.32-6_i386.deb optional kernel Common header files for Linux 2.6.32-1 This package provides the architecture-specific common kernel header files for Linux kernel version 2.6.32-1, generally used for building out-of-tree kernel modules. To obtain a complete set of headers you also need to install the linux-headers-2.6.32-1-(flavour) package, matching the flavour of the kernel you intend the build for. (new) linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb optional kernel Header files for Linux 2.6.32-1-vserver-686-bigmem This package provides the architecture-specific kernel header files for Linux kernel 2.6.32-1-vserver-686-bigmem, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.32-1-vserver-686-bigmem, and can be used for building modules that load into the kernel provided by the linux-image-2.6.32-1-vserver-686-bigmem package. (new) linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb optional kernel Header files for Linux 2.6.32-1-vserver-686 This package provides the architecture-specific kernel header files for Linux kernel 2.6.32-1-vserver-686, generally used for building out-of-tree kernel modules. These files are going to be installed into /usr/src/linux-headers-2.6.32-1-vserver-686, and can be used for building modules that load into the kernel provided by the linux-image-2.6.32-1-vserver-686 package. (new) linux-image-2.6.32-1-486_2.6.32-6_i386.deb optional kernel Linux 2.6.32 for old PCs The Linux kernel 2.6.32 and modules for use on PCs with a 486, Pentium or compatible processor. (new) linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb optional kernel Linux 2.6.32 for PCs with 4GB+ RAM
Unable to find a kernel build server
I was previously using: kernel-archive.buildserver.net to build install pre-built kernels on my Debian Box. This made management easy, without the need to compile it myself. From a few threads from around the web I noticed they suffered a huge UPS failure last September. I was wondering if anyone knows of an alternative or if they will be back at any time as this is an invaluable resource. Thanks! Robin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 567689
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 567689 + pending Bug #567689 [linux-2.6] linux-image-2.6.26-2-amd64: cdc_ether driver fails to communicate with Sphairon Turbolink 1203 DSL modem Ignoring request to alter tags of bug #567689 to the same tags previously set 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 567689
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 567689 + pending Bug #567689 [linux-2.6] linux-image-2.6.26-2-amd64: cdc_ether driver fails to communicate with Sphairon Turbolink 1203 DSL modem Ignoring request to alter tags of bug #567689 to the same tags previously set 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#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used
Package: linux-source-2.6.32 Version: 2.6.32-5 Severity: important --- Please enter the report below this line. --- I get a kerneloops on 2.6.32 kernels unless CONFIG_LBDAF is yes. This is on a Lenovo W500 thinkpad that only has a 150G hard drive so there shouldn't be any need for LBDAF. The kerneloops is very early in the boot process. I always build my own kernels. I copied the 2.6.30 kernel config for my current kernel to the 2.6.32 source directory and did a make oldconfig. The resulting 2.6.32 kernel gave the kerneloops. After a long process of narrowing down what was causing the problem. I found that LBDAF had to be used for the kernel to boot. --- System information. --- Architecture: i386 Kernel: Linux 2.6.32.100131 Debian Release: squeeze/sid 500 testing www.debian-multimedia.org 500 testing security.debian.org 500 testing debian.linux.ibm.com 500 jaunty ppa.launchpad.net --- Package information. --- Depends (Version) | Installed ===-+-=== binutils| 2.20-5 bzip2 | 1.0.5-4 Recommends (Version) | Installed =-+-=== libc6-dev | 2.10.2-2 OR libc-dev | gcc | 4:4.3.4-1 make | 3.81-7 Suggests(Version) | Installed =-+-=== libncurses-dev| OR ncurses-dev | kernel-package| 12.032 libqt3-mt-dev | 3:3.3.8b-6 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6_2.6.32-6_multi.changes ACCEPTED
Accepted: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb linux-support-2.6.32-1_2.6.32-6_all.deb to main/l/linux-2.6/linux-support-2.6.32-1_2.6.32-6_all.deb Override entries for your package: firmware-linux-free_2.6.32-6_all.deb - optional kernel linux-2.6_2.6.32-6.dsc - source devel linux-doc-2.6.32_2.6.32-6_all.deb - optional doc linux-headers-2.6.32-1-486_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-686_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-all_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-common_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb - optional kernel linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb - optional kernel linux-image-2.6.32-1-486_2.6.32-6_i386.deb - optional kernel linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb - optional kernel linux-image-2.6.32-1-686_2.6.32-6_i386.deb - optional kernel linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb - optional kernel linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb - optional kernel linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb - optional kernel linux-libc-dev_2.6.32-6_i386.deb - optional devel linux-manual-2.6.32_2.6.32-6_all.deb - optional doc linux-patch-debian-2.6.32_2.6.32-6_all.deb - optional kernel linux-source-2.6.32_2.6.32-6_all.deb - optional kernel linux-support-2.6.32-1_2.6.32-6_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 478315 510593 525232 528834 545417 558237 561552 561880 562815 562975 563161 563847 564743 564807 565494 566213 566532 566539 566547 567352 567391 567689 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#563161: marked as done (Provide way to distinguish remove and purge in postrm hooks)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-lq...@ries.debian.org and subject line Bug#563161: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #563161, regarding Provide way to distinguish remove and purge in postrm hooks 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.) -- 563161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.30-2 Severity: wishlist Hi, if a kernel package is purged, the scripts in /etc/kernel/postrm.d are run twice. Once for `remove' and once for `purge'. There is no way, however, to find out the current phase and to prevent running the script twice. A kernel built with kernel-package sets the variable `DEB_MAINT_PARAMS' to `remove' and `purge', respectively. Something similar should also be supported by official kernel builds (preferably kernel-package and official builds should agree on the way to do this). Cheers, harry signature.asc Description: PGP signature ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb linux-support-2.6.32-1_2.6.32-6_all.deb to main/l/linux-2.6/linux-support-2.6.32-1_2.6.32-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 563...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing
Bug#562815: marked as done (Bug in kernel audit code makes system crash)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-ly...@ries.debian.org and subject line Bug#562815: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #562815, regarding Bug in kernel audit code makes system crash 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.) -- 562815: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562815 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6 Version: 2.6.26-2-686, 2.6.26-2-amd64, 2.6.26-2-openvz-amd64, 2.6.26-2-xen-amd64 My system crashes when I do auditctl -R audit.rules. I have figured out that the problem occurs after unloading and then loading some certain rules that include -F dir=/dev or -F dir=/lib, or some other directory watch. For example: # auditctl -a exit,always -F arch=b64 -S creat -F dir=/lib # auditctl -d exit,always -F arch=b64 -S creat -F dir=/lib # auditctl -a exit,always -F arch=b64 -S creat -F dir=/lib result in [ 154.715581] [ cut here ] [ 154.715581] kernel BUG at fs/inode.c:1152! [ 154.715581] invalid opcode: [1] SMP [ 154.715581] CPU 0 [ 154.715581] Modules linked in: ipv6 evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod thermal_sys [ 154.715581] Pid: 1256, comm: audit_prune_tre Not tainted 2.6.26-2-xen-amd64 #1 [ 154.715581] RIP: e030:[8029ceb0] [8029ceb0] iput+0x13/0x60 [ 154.715581] RSP: e02b:88007dd4fe80 EFLAGS: 00010246 [ 154.715581] RAX: 88007da63701 RBX: 88007da63748 RCX: 0001 [ 154.715581] RDX: 1414 RSI: 0001 RDI: 88007da63748 [ 154.715581] RBP: 88007fd9e440 R08: 0003 R09: 88007e94f220 [ 154.715581] R10: 88007e2c9840 R11: 80285a7a R12: 0002 [ 154.715581] R13: 88007e94f180 R14: 88007e94f190 R15: [ 154.715581] FS: 7f5a80f176e0() GS:8053a000() knlGS: [ 154.715581] CS: e033 DS: ES: [ 154.715581] DR0: DR1: DR2: [ 154.715581] DR3: DR6: 0ff0 DR7: 0400 [ 154.715581] Process audit_prune_tre (pid: 1256, threadinfo 88007dd4e000, task 88007fd39040) [ 154.715581] Stack: 88007e94f190 802b43ff 88007e94f190 88007ddc4000 [ 154.715581] 88007e94f220 802b4604 88007e2c9840 8025d69c [ 154.715581] 0003 88007e2c9840 80255bdd 88007eb898a8 [ 154.715581] Call Trace: [ 154.715581] [802b43ff] ? put_inotify_watch+0x21/0x4d [ 154.715581] [802b4604] ? unpin_inotify_watch+0x11/0x1a [ 154.715581] [8025d69c] ? untag_chunk+0x3e6/0x40a [ 154.715581] [80255bdd] ? prune_tree_thread+0x0/0x26 [ 154.715581] [8025d6db] ? prune_one+0x1b/0x66 [ 154.715581] [8025d756] ? audit_prune_trees+0x30/0x59 [ 154.715581] [80255bf2] ? prune_tree_thread+0x15/0x26 [ 154.715581] [80255bdd] ? prune_tree_thread+0x0/0x26 [ 154.715581] [8023f593] ? kthread+0x47/0x74 [ 154.715581] [8020be28] ? child_rip+0xa/0x12 [ 154.715581] [8023f54c] ? kthread+0x0/0x74 [ 154.715581] [8020be1e] ? child_rip+0x0/0x12 [ 154.715581] [ 154.715581] [ 154.715581] Code: 08 02 00 00 77 ff ff ff eb df 48 83 ec 08 e8 d5 76 19 00 41 59 31 c0 c3 48 85 ff 53 48 89 fb 74 55 48 83 bf 08 02 00 00 40 75 04 0f 0b eb fe 48 8d 7f 48 48 c7 c6 20 41 5f 80 e8 a4 0f 07 00 85 [ 154.715581] RIP [8029ceb0] iput+0x13/0x60 [ 154.715581] RSP 88007dd4fe80 [ 154.715581] ---[ end trace f46939304c84baf0 ]--- I run Debian 5.0.3 on HP Proliant DL180 G6 (Intel Xeon CPU). Audit package version is 1.7.4-1. The problem was first discovered in Xen domU (2.6.26-2-xen-amd64). Then I was able to reproduce it in dom0 and even in non-xen-enabled kernel 2.6.26-2-amd64 and 2.6.26-2-686, openvz version is also affected. I wrote a letter to kernel audit code developers Steve Grubb, Miloslav Trmac and Alexander Viro. They asked me to try to reproduce this error with a more recent kernel to check if this crash was already fixed. So here follows what I did. 1. Installed linux-image-2.6.30-bpo.2-686 from Debian backports repository and booted it. Not using Xen for this time. 2. On one console I ran # while [ 1 == 1 ]; do /bin/ls /bin; done to produce some system load. 3. On another console I ran # while [ 1 == 1 ]; do pidof auditctl || auditctl -R /etc/audit/audit.rules; done to reproduce the error. I use
Bug#566376: marked as done (linux-image-2.6.32-trunk-amd64: X unconditionally hangs up on bootup)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-lm...@ries.debian.org and subject line Bug#558237: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #558237, regarding linux-image-2.6.32-trunk-amd64: X unconditionally hangs up on bootup 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.) -- 558237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-5 Severity: grave Justification: renders package unusable None of the linux-image-2.6.32-trunk-amd64 packages, since they reached unstable, ever booted successfully on my laptop. X system darkens the screen and hangs the computer completely (i.e. cannot even switch to the console via Ctrl-Alt-F1), as soon as the booting process reaches KDM; Alt-SysRq-B works though. Please tell me what logs should be included to debug this problem, I'll help as much as I can. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: LENOVO product_name: 7762WHW product_version: ThinkPad X61 Tablet chassis_vendor: LENOVO chassis_version: Not Available bios_vendor: LENOVO bios_version: 7SET34WW (1.20 ) board_vendor: LENOVO board_name: 7762WHW board_version: Not Available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) Subsystem: Lenovo T61 [17aa:20b3] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo T61 [17aa:20b5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 29 Region 0: Memory at f810 (64-bit, non-prefetchable) [size=1M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at 1800 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) Subsystem: Lenovo T61 [17aa:20b5] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at f820 (64-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:19.0 Ethernet controller [0200]: Intel Corporation 82566MM Gigabit Network Connection [8086:1049] (rev 03) Subsystem: Lenovo Device [17aa:20de] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 26 Region 0: Memory at fe00 (32-bit, non-prefetchable) [size=128K] Region 1: Memory at fe225000 (32-bit, non-prefetchable) [size=4K] Region 2: I/O ports at 1840 [size=32] Capabilities: access denied Kernel driver in use: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo ThinkPad T61 [17aa:20aa] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 20 Region 4: I/O ports at 1860 [size=32] Kernel driver in use: uhci_hcd 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo ThinkPad T60 [17aa:20aa] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Bug#566539: marked as done (linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-mp...@ries.debian.org and subject line Bug#566539: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #566539, regarding linux-image-2.6.32-trunk-486: Minor formatting issue on info screen during update 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.) -- 566539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-5 Severity: minor During the upgrade process, apt-get causes a message to display that starts with this text: │ Required firmware files may be missing│ │ │ │ This system is currently running Linux 2.6.30-2-686 and you are │ │ installing Linux 2.6.32-trunk-486. In the new version some of the│ │ drivers used on this system may require additional firmware files:│ While scrolling down, I noticed the following: │ radeon/RV630_me.bin, radeon/RV630_pfp.bin, radeon/RV610_me.bin, │ │ radeon/RV610_pfp.bin, radeon/R600_me.bin, radeon/R600_pfp.bin\nr8169: │ │ rtl8168d-2.fw, rtl8168d-1.fw │ I don't think that \n is supposed to be there. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] [1106:0691] (rev c4) Subsystem: ASUSTeK Computer Inc. Device [1043:8038] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR+ INTx- Latency: 0 Region 0: Memory at fc00 (32-bit, prefetchable) [size=32M] Capabilities: access denied Kernel driver in use: agpgart-via 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] [1106:8598] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: d000-dfff Memory behind bridge: de80-dfdf Prefetchable memory behind bridge: e000-fbff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied 00:04.0 ISA bridge [0601]: VIA Technologies, Inc. VT82C686 [Apollo Super South] [1106:0686] (rev 40) Subsystem: ASUSTeK Computer Inc. Device [1043:8038] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: parport_pc 00:04.1 IDE interface [0101]: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE [1106:0571] (rev 06) (prog-if 8a [Master SecP PriP]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 Region 0: [virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8] Region 1: [virtual] Memory at 03f0 (type 3, non-prefetchable) [size=1] Region 2: [virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8] Region 3: [virtual] Memory at 0370 (type 3, non-prefetchable) [size=1] Region 4: I/O ports at b800 [size=16] Capabilities: access denied Kernel driver in use: VIA_IDE 00:04.2 USB Controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 16) (prog-if 00 [UHCI]) Subsystem: First International Computer, Inc. VA-502 Mainboard [0925:1234] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status:
Bug#565494: marked as done (linux-image-2.6.26-2-amd64: does not include CONFIG_INFINIBAND_IPOIB_CM infiniband connected mode)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-ma...@ries.debian.org and subject line Bug#565494: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #565494, regarding linux-image-2.6.26-2-amd64: does not include CONFIG_INFINIBAND_IPOIB_CM infiniband connected mode 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.) -- 565494: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-19lenny2 Severity: wishlist Hi, On infiniband kernel 2.6.32-trunk-686 from debian, /sys/class/net/ib0/mode is missing to toggle infiniband connected mode it is usefull to size up MTU to boost IPoIB network traffic performance, Can you please add CONFIG_INFINIBAND_IPOIB_CM=y to default kernel ? http://www.mail-archive.com/linux-r...@vger.kernel.org/msg02127.html Regards. Nicolas -- Package-specific info: -- System Information: Debian Release: 5.0.3 APT prefers stable APT policy: (999, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo linux-image-2.6.26-2-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to
Bug#564861: marked as done (2.6.32-trunk-amd64: oopses if quota enabled)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-mm...@ries.debian.org and subject line Bug#566532: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #566532, regarding 2.6.32-trunk-amd64: oopses if quota enabled 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.) -- 566532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-5 Severity: normal Subject almost says it all. I have quota enabled on my /home partition but opening a file on / in vi and releasing it again makes the kernel oops: Jan 12 10:54:20 feivel kernel: [ 147.999029] kernel BUG at /build/buildd-linux-2.6_2.6.32-5-amd64-9RvY2G/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/quota/dquot.c:1398! Jan 12 10:54:20 feivel kernel: [ 147.999037] invalid opcode: [#1] SMP Jan 12 10:54:20 feivel kernel: [ 147.999042] last sysfs file: /sys/devices/pci:00/:00:1c.5/:0b:00.0/net/eth0/carrier Jan 12 10:54:20 feivel kernel: [ 147.999047] CPU 7 Jan 12 10:54:20 feivel kernel: [ 147.999050] Modules linked in: radeon ttm drm_kms_helper drm agpgart i2c_algo_bit sco bridge stp bnep rfcomm l2cap crc16 ppdev lp parport advantechwdt acpi_cpufreq cpufreq_stats cpufreq_conservative cpufreq_powersave cpufreq_userspace kvm_intel kvm uinput quota_v2 quota_tree fuse loop firewire_sbp2 btusb snd_hda_codec_atihdmi joydev bluetooth snd_hda_codec_idt snd_hda_intel snd_hda_codec arc4 ecb snd_hwdep uvcvideo snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi iwlagn snd_rawmidi snd_seq_midi_event snd_seq iwlcore videodev v4l1_compat v4l2_compat_ioctl32 mac80211 snd_timer snd_seq_device i2c_i801 snd cfg80211 soundcore psmouse evdev dell_laptop serio_raw pcspkr snd_page_alloc wmi i2c_core dcdbas rfkill processor battery ac ext3 jbd mbcache sha256_generic cryptd aes_x86_64 aes_generic cbc dm_crypt dm_mod usbhid hid sg sr_mod sd_mod cdrom crc_t10dif sdhci_pci firewire_ohci sdhci ahci video mmc_core libata firewire_core output scsi_mod ehci_hcd crc_itu_t led_class r8169 mii usbcore Jan 12 10:54:20 feivel kernel: nls_base button thermal fan thermal_sys [last unloaded: scsi_wait_scan] Jan 12 10:54:20 feivel kernel: [ 147.999193] Pid: 2683, comm: vi Not tainted 2.6.32-trunk-amd64 #1 Studio 1557 Jan 12 10:54:20 feivel kernel: [ 147.999198] RIP: 0010:[8112b43d] [8112b43d] dquot_transfer+0x123/0x49d Jan 12 10:54:20 feivel kernel: [ 147.999213] RSP: 0018:880134ecdd98 EFLAGS: 00010246 Jan 12 10:54:20 feivel kernel: [ 147.999217] RAX: RBX: 88012cb61d50 RCX: 7fd1a3bb9000 Jan 12 10:54:20 feivel kernel: [ 147.999222] RDX: 0002 RSI: RDI: 88012cb61d50 Jan 12 10:54:20 feivel kernel: [ 147.999227] RBP: 88012cb61ca0 R08: R09: 880134ecdee8 Jan 12 10:54:20 feivel kernel: [ 147.999232] R10: 0051 R11: R12: 0001 Jan 12 10:54:20 feivel kernel: [ 147.999236] R13: R14: 1846 R15: Jan 12 10:54:20 feivel kernel: [ 147.999242] FS: 7fd1a3b9e790() GS:8800055c() knlGS: Jan 12 10:54:20 feivel kernel: [ 147.999248] CS: 0010 DS: ES: CR0: 80050033 Jan 12 10:54:20 feivel kernel: [ 147.999252] CR2: 0044aab0 CR3: 000133919000 CR4: 26e0 Jan 12 10:54:20 feivel kernel: [ 147.999257] DR0: DR1: DR2: Jan 12 10:54:20 feivel kernel: [ 147.999262] DR3: DR6: 0ff0 DR7: 0400 Jan 12 10:54:20 feivel kernel: [ 147.999268] Process vi (pid: 2683, threadinfo 880134ecc000, task 8801349ba350) Jan 12 10:54:20 feivel kernel: [ 147.999272] Stack: Jan 12 10:54:20 feivel kernel: [ 147.999274] 8801376ca000 8801360b8068 88012cb64000 Jan 12 10:54:20 feivel kernel: [ 147.999281] 0 8801360bd800 8112a3ad Jan 12 10:54:20 feivel kernel: [ 147.999289] 0 88012cb61ca0 8801360bd800 8112b8be Jan 12 10:54:20 feivel kernel: [ 147.999297] Call Trace: Jan 12 10:54:20 feivel kernel: [ 147.999304] [8112a3ad] ? dqput+0x89/0x21a Jan 12 10:54:20 feivel kernel: [ 147.999311] [8112b8be] ? dquot_initialize+0x107/0x115 Jan 12 10:54:20 feivel kernel: [ 147.999318] [8112856e] ? vfs_dq_transfer+0x6a/0x86 Jan 12 10:54:20 feivel kernel: [ 147.999334]
Bug#566213: marked as done (linux-image-2.6.32-trunk-vserver-686-bigmem: vserver_686-bigmem is not bigmem)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-mf...@ries.debian.org and subject line Bug#566213: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #566213, regarding linux-image-2.6.32-trunk-vserver-686-bigmem: vserver_686-bigmem is not bigmem 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.) -- 566213: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-5 Severity: important vserver_686-bigmem is not bigmem because the bigmem config file reference is missing in debian/rules.gen. IOW vserver_686-bigmem=vserver_686. You can verify this in the respective /boot/configs* of the two packages. Adding the bigmem config ref in rules.gen gives me the bigmem kernel I need, but I think rules.gen is generated by a script so the bug ultimately needs to be fixed upstream of this file? -- Package-specific info: ** Version: Linux version 2.6.32-trunk-vserver-686-bigmem (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 09:10:46 UTC 2010 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-trunk-vserver-686-bigmem root=UUID=8c05ba16-4fe2-4ba6-bc50-2d078cf627a7 ro quiet ** Not tainted -- System Information: Debian Release: squeeze/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable'), (100, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-vserver-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.32-trunk-vserver-686-bigmem depends on: ii debconf [debconf-2.0] 1.5.28 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.11-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.32-trunk-vserver-686-bigmem recommends: ii firmware-linux-free 2.6.32-5 Binary firmware for various driver ii libc6-i6862.10.2-5 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.32-trunk-vserver-686-bigmem suggests: pn grub | lilo none (no description available) pn linux-doc-2.6.32 none (no description available) Versions of packages linux-image-2.6.32-trunk-vserver-686-bigmem is related to: pn firmware-bnx2 none (no description available) pn firmware-bnx2xnone (no description available) pn firmware-ipw2x00 none (no description available) pn firmware-ivtv none (no description available) pn firmware-iwlwifi none (no description available) ii firmware-linux0.22 Binary firmware for various driver ii firmware-linux-nonfree0.22 Binary firmware for various driver pn firmware-qlogic none (no description available) pn firmware-ralink none (no description available) -- debconf information excluded ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb
Bug#478315: marked as done (please enable CONFIG_PM_TRACE for easier debugging of suspend to ram)
Your message dated Mon, 01 Feb 2010 17:56:53 + with message-id e1nc0w5-l4...@ries.debian.org and subject line Bug#478315: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #478315, regarding please enable CONFIG_PM_TRACE for easier debugging of suspend to ram 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.) -- 478315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.24-1-686 Version: 2.6.24-6 Severity: wishlist Please enable the CONFIG_PM_TRACE option in the standard kernel builds (it may only work on 32-bit i386, I'm not sure, but anyway that's most of the laptops out there). This has no effect under normal circumstances but allows people to enable a special mode for debugging suspend-to-ram by writing to a file in sysfs. See http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-advanced.html for a description of the debugging process that would be possible with this config option. -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-6) (wa...@debian.org) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Sat Apr 19 00:37:55 UTC 2008 ** Command line: BOOT_IMAGE=(hd0,1)/boot/vmlinuz-2.6.24-1-686 root=/dev/hda1 ro ** Tainted: P (1) ** Kernel log: Clocksource tsc unstable (delta = -422216038 ns) hdc: MATSHITADVD-RAM UJ-841S, ATAPI CD/DVD-ROM drive hdc: host max PIO4 wanted PIO255(auto-tune) selected PIO4 hdc: UDMA/33 mode selected ide1 at 0x170-0x177,0x376 on irq 15 udev: renamed network interface eth0 to eth1 SCSI subsystem initialized libata version 3.00 loaded. hda: max request size: 512KiB hda: 156301488 sectors (80026 MB) w/7539KiB Cache, CHS=16383/255/63 hda: cache flushes supported hda: hda1 hda2 hda3 hdc: ATAPI 24X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 Attempting manual resume swsusp: Marking nosave pages: 0009e000 - 0010 swsusp: Basic memory bitmaps created swsusp: Basic memory bitmaps freed kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. Real Time Clock Driver v1.12ac input: PC Speaker as /class/input/input1 pci_hotplug: PCI Hot Plug PCI Core version: 0.5 shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 Linux agpgart interface v0.102 piix4_smbus :00:14.0: Found :00:14.0 device input: Power Button (FF) as /class/input/input2 ACPI: Power Button (FF) [PWRF] input: Lid Switch as /class/input/input3 ACPI: Lid Switch [LID] input: Power Button (CM) as /class/input/input4 input: PS/2 Mouse as /class/input/input5 ACPI: Power Button (CM) [PWRB] ath_hal: module license 'Proprietary' taints kernel. input: AlpsPS/2 ALPS GlidePoint as /class/input/input6 ath_hal: 0.9.18.0 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) wlan: 0.9.4 ath_pci: 0.9.4 ACPI: PCI Interrupt :04:02.0[A] - GSI 21 (level, low) - IRQ 21 ath_rate_sample: 1.2 (0.9.4) ACPI: EC: non-query interrupt received, switching to interrupt mode ACPI: AC Adapter [ACAD] (on-line) ACPI: Battery Slot [BAT1] (battery present) input: Video Bus as /class/input/input7 ACPI: Video Device [VGA] (multi-head: yes rom: no post: no) wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps wifi0: H/W encryption support: WEP AES AES_CCM TKIP wifi0: mac 7.8 phy 4.5 radio 5.6 wifi0: Use hw queue 1 for WME_AC_BE traffic wifi0: Use hw queue 0 for WME_AC_BK traffic wifi0: Use hw queue 2 for WME_AC_VI traffic wifi0: Use hw queue 3 for WME_AC_VO traffic wifi0: Use hw queue 8 for CAB traffic wifi0: Use hw queue 9 for beacons wifi0: Atheros 5212: mem=0xc020, irq=21 Yenta: CardBus bridge found at :04:04.0 [1179:ff00] Yenta: Using CSCINT to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket :04:04.0, mfunc 0x00111c12, devctl 0x44 Yenta: ISA IRQ mask 0x0ef8, PCI irq 16 Socket status: 3006 Yenta: Raising subordinate bus# of parent bus (#04) from #04 to #08 pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff cs: IO port probe 0xa000-0xafff: clean. pcmcia: parent PCI bridge Memory window: 0xc020 - 0xc02f ACPI: PCI Interrupt :00:14.6[B] - GSI 17 (level, low) - IRQ 17 atiixp-modem: codec reset timeout atiixp-modem: no codec available ACPI: PCI interrupt for device :00:14.6 disabled ACPI: PCI Interrupt :00:14.5[B] - GSI 17 (level, low) - IRQ 17 cs: IO port probe 0x100-0x3af: clean. cs: IO port probe 0x3e0-0x4ff:
Bug#558237: marked as done (linux-source-2.6.32: X with xserver-xorg-video-intel does not work any longer)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-lm...@ries.debian.org and subject line Bug#558237: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #558237, regarding linux-source-2.6.32: X with xserver-xorg-video-intel does not work any longer 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.) -- 558237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558237 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-source-2.6.32 Version: 2.6.32~rc8-1~experimental.1 Severity: important X doesn't work, but doesn't abort; system is unusable. The following message is printed on the console that started X: .../../../libdrm/intel/intel_bufmgr_gem.c:825: Error setting to CPU domain 96: Input/output error .../../../libdrm/intel/intel_bufmgr_gem.c:899: Error setting domain 773: Input/output error -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-rc8-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.32 depends on: ii binutils 2.20-4 The GNU assembler, linker and bina ii bzip2 1.0.5-3high-quality block-sorting file co Versions of packages linux-source-2.6.32 recommends: ii gcc 4:4.3.4-1 The GNU C compiler ii libc6-dev [libc-dev] 2.10.2-2 GNU C Library: Development Librari ii make 3.81-7 An utility for Directing compilati Versions of packages linux-source-2.6.32 suggests: ii kernel-package12.031 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20090803-2 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb
Bug#528834: marked as done (linux-2.6: Mobile IPv6 needs)
Your message dated Mon, 01 Feb 2010 17:56:53 + with message-id e1nc0w5-lg...@ries.debian.org and subject line Bug#528834: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #528834, regarding linux-2.6: Mobile IPv6 needs 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.) -- 528834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.29-4 Severity: wishlist Coin, In order to use, and probably package, Mobile IPv6 tools (mip6d for instance), a few more features should be activated: - CONFIG_XFRM_SUB_POLICY - CONFIG_XFRM_MIGRATE - CONFIG_NET_KEY_MIGRATE Could you please activate them ? Regards. -- Marc Dequènes (Duck) pgpWNqdyawaLD.pgp Description: PGP Digital Signature ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb linux-support-2.6.32-1_2.6.32-6_all.deb to main/l/linux-2.6/linux-support-2.6.32-1_2.6.32-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 528...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 31 Jan 2010 23:09:28 + Source: linux-2.6 Binary: linux-source-2.6.32 linux-doc-2.6.32 linux-manual-2.6.32 linux-patch-debian-2.6.32
Bug#567391: marked as done (Please update aufs2 to new upstream snapshot (aufs2-32 branch))
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-me...@ries.debian.org and subject line Bug#567391: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #567391, regarding Please update aufs2 to new upstream snapshot (aufs2-32 branch) 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.) -- 567391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567391 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-5 Severity: wishlist Hi, please update aufs2 to a newer upstream code. The latest upstream release (i.e. git push) was on Jan 25 and the next one is expected for Feb 2 (next monday). Regards, Julian -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (350, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb linux-support-2.6.32-1_2.6.32-6_all.deb to main/l/linux-2.6/linux-support-2.6.32-1_2.6.32-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 567...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated
Bug#564743: marked as done (3c509 ethernet driver doesn't accept the xcvr parameter)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-m0...@ries.debian.org and subject line Bug#564743: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #564743, regarding 3c509 ethernet driver doesn't accept the xcvr parameter 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.) -- 564743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564743 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image Version: 2,6,30-1-486 I'm trying to make an ethernet connection to an old Linux PC with a 3Com Etherlink III card 3c509B. I want full duplex so per the kernel documentation for 3c509 I must use the 3c509 module and give it the parameter xcvr=12 which forces full duplex. So in /etc/modules I put: 3c059 xcvr=12 But the module doesn't load per lsmod and the syslog shows: Jan 7 15:13:28 davespc kernel: [ 40.355722] 3c509: Unknown parameter `xcvr' I've also tried putting this xcvr option in a file I created in /etc/modprobe.d with the same result. Is this a bug in the software or documentation? David Lawyer ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb linux-support-2.6.32-1_2.6.32-6_all.deb to main/l/linux-2.6/linux-support-2.6.32-1_2.6.32-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 564...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem
Bug#525232: marked as done (Please enable CONFIG_ITCO_VENDOR_SUPPORT)
Your message dated Mon, 01 Feb 2010 17:56:53 + with message-id e1nc0w5-la...@ries.debian.org and subject line Bug#525232: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #525232, regarding Please enable CONFIG_ITCO_VENDOR_SUPPORT 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.) -- 525232: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-15 Severity: wishlist Hi can you please enable CONFIG_ITCO_VENDOR_SUPPORT in kernels? It adds support for some specific hardware which requires extra initialisation to TCO watchdog. -- Michal Čihař | http://cihar.com | http://blog.cihar.com -- Package-specific info: -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-vserver-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.26-2-amd64 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 linux-image-2.6.26-2-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-amd64 suggests: ii grub 0.97-47lenny2 GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 none(no description available) -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-amd64/postinst/bootloader-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/old-dir-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/create-kimage-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/initrd-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-amd64/preinst/abort-install-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/postinst/old-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-initrd-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/bootloader-test-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/overwriting-modules-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/kimage-is-a-directory: linux-image-2.6.26-2-amd64/preinst/failed-to-move-modules-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/prerm/would-invalidate-boot-loader-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/old-system-map-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/abort-overwrite-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/bootloader-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/elilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/prerm/removing-running-kernel-2.6.26-2-amd64: true ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to
Bug#562975: marked as done (linux-2.6: patch for CVE-2009-3939)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-lj...@ries.debian.org and subject line Bug#562975: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #562975, regarding linux-2.6: patch for CVE-2009-3939 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.) -- 562975: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: linux-2.6 version: 2.6.32-3 severity: important tags: patch , security hi, attached is a patch for the megaraid poll_mode_io permissions issue. mike diff -ur a/linux-2.6-2.6.32/drivers/scsi/megaraid/megaraid_sas.c b/linux-2.6-2.6.32/drivers/scsi/megaraid/megaraid_sas.c --- a/linux-2.6-2.6.32/drivers/scsi/megaraid/megaraid_sas.c 2009-12-02 22:51:21.0 -0500 +++ b/linux-2.6-2.6.32/drivers/scsi/megaraid/megaraid_sas.c 2009-12-29 13:02:34.0 -0500 @@ -3451,7 +3451,7 @@ return retval; } -static DRIVER_ATTR(poll_mode_io, S_IRUGO|S_IWUGO, +static DRIVER_ATTR(poll_mode_io, S_IRUGO|S_IWUSR, megasas_sysfs_show_poll_mode_io, megasas_sysfs_set_poll_mode_io); ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb linux-support-2.6.32-1_2.6.32-6_all.deb to main/l/linux-2.6/linux-support-2.6.32-1_2.6.32-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 562...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a
Bug#563847: marked as done (Please enable the f-trace tracers)
Your message dated Mon, 01 Feb 2010 17:56:54 + with message-id e1nc0w6-lx...@ries.debian.org and subject line Bug#563847: fixed in linux-2.6 2.6.32-6 has caused the Debian Bug report #563847, regarding Please enable the f-trace tracers 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.) -- 563847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563847 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: linux-2.6 Version: 2.6.32-3 Severity: wishlist Currently Ftrace is enabled in the kernel, CONFIG_FTRACE=y and CONFIG_DYNAMIC_FTRACE=y. However, some the most useful tracers, such as CONFIG_FUNCTION_TRACER and CONFIG_STACK_TRACER, are disabled. For example: CONFIG_FTRACE=y # CONFIG_FUNCTION_TRACER is not set # CONFIG_IRQSOFF_TRACER is not set # CONFIG_SYSPROF_TRACER is not set # CONFIG_SCHED_TRACER is not set # CONFIG_FTRACE_SYSCALLS is not set ... # CONFIG_POWER_TRACER is not set # CONFIG_STACK_TRACER is not set Since Dynamic Ftrace is already enabled, I can't think of down side to enabling the actual tracers. Please consider this a wishlist request to enabled them. Thanks, Troy signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.32-6 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: firmware-linux-free_2.6.32-6_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb linux-2.6_2.6.32-6.diff.gz to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz linux-2.6_2.6.32-6.dsc to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc linux-doc-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb linux-headers-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb linux-headers-2.6.32-1-all_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb linux-headers-2.6.32-1-common_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-image-2.6.32-1-486_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb linux-libc-dev_2.6.32-6_i386.deb to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb linux-manual-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb linux-patch-debian-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb linux-source-2.6.32_2.6.32-6_all.deb to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb linux-support-2.6.32-1_2.6.32-6_all.deb to main/l/linux-2.6/linux-support-2.6.32-1_2.6.32-6_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 563...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ben Hutchings b...@decadent.org.uk (supplier
Bug#561880: marked as done (inotify: Not assigning sequential ids as expected)
Your message dated Mon, 01 Feb 2010 17:56:54 +
with message-id e1nc0w6-lv...@ries.debian.org
and subject line Bug#561880: fixed in linux-2.6 2.6.32-6
has caused the Debian Bug report #561880,
regarding inotify: Not assigning sequential ids as expected
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.)
--
561880: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6-parisc64
Severity: important
Blocks: 558981
The attatched minimal test case shows these results:
on my i386 machine, it correctly gives two different numbers:
$ gcc test.c; ./a.out
First: 1
Second: 2
however on paer.debian.org (hppa):
$ gcc test.c; ./a.out
First: 1
Second: 1
Based on the manpage of inotify_add_watch, it sounds like the correct
behavior is to have different numbers. It seems that the author of
inotify-tools also interpreted it that way.
This bug is causing my package's tests to fail, which causes it to FTBFS:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558981
Cheers,
Ryan
--
_
Ryan Niebur
ryanrya...@gmail.com
#include sys/inotify.h
#include stdio.h
int main()
{
int fd, wd;
fd = inotify_init ();
wd = inotify_add_watch (fd,
test.c,
IN_OPEN | IN_CLOSE);
printf(First: %d\n, wd);
inotify_rm_watch(fd, wd);
wd = inotify_add_watch (fd,
a.out,
IN_OPEN | IN_CLOSE);
printf(Second: %d\n, wd);
inotify_rm_watch(fd, wd);
}
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.32-6
We believe that the bug you reported is fixed in the latest version of
linux-2.6, which is due to be installed in the Debian FTP archive:
firmware-linux-free_2.6.32-6_all.deb
to main/l/linux-2.6/firmware-linux-free_2.6.32-6_all.deb
linux-2.6_2.6.32-6.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.32-6.diff.gz
linux-2.6_2.6.32-6.dsc
to main/l/linux-2.6/linux-2.6_2.6.32-6.dsc
linux-doc-2.6.32_2.6.32-6_all.deb
to main/l/linux-2.6/linux-doc-2.6.32_2.6.32-6_all.deb
linux-headers-2.6.32-1-486_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-486_2.6.32-6_i386.deb
linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-686-bigmem_2.6.32-6_i386.deb
linux-headers-2.6.32-1-686_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-686_2.6.32-6_i386.deb
linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-all-i386_2.6.32-6_i386.deb
linux-headers-2.6.32-1-all_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-all_2.6.32-6_i386.deb
linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-amd64_2.6.32-6_i386.deb
linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-common-vserver_2.6.32-6_i386.deb
linux-headers-2.6.32-1-common_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-common_2.6.32-6_i386.deb
linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb
to
main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb
linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-headers-2.6.32-1-vserver-686_2.6.32-6_i386.deb
linux-image-2.6.32-1-486_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-image-2.6.32-1-486_2.6.32-6_i386.deb
linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-image-2.6.32-1-686-bigmem_2.6.32-6_i386.deb
linux-image-2.6.32-1-686_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-image-2.6.32-1-686_2.6.32-6_i386.deb
linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-image-2.6.32-1-amd64_2.6.32-6_i386.deb
linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686-bigmem_2.6.32-6_i386.deb
linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-image-2.6.32-1-vserver-686_2.6.32-6_i386.deb
linux-libc-dev_2.6.32-6_i386.deb
to main/l/linux-2.6/linux-libc-dev_2.6.32-6_i386.deb
linux-manual-2.6.32_2.6.32-6_all.deb
to main/l/linux-2.6/linux-manual-2.6.32_2.6.32-6_all.deb
linux-patch-debian-2.6.32_2.6.32-6_all.deb
to main/l/linux-2.6/linux-patch-debian-2.6.32_2.6.32-6_all.deb
linux-source-2.6.32_2.6.32-6_all.deb
to main/l/linux-2.6/linux-source-2.6.32_2.6.32-6_all.deb
linux-support-2.6.32-1_2.6.32-6_all.deb
to
Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda
On Fri, Jan 29, 2010 at 6:46 PM, Paul Wise p...@debian.org wrote: On Fri, 2010-01-29 at 10:54 -0800, Luis R. Rodriguez wrote: Given the OpenSSL stuff in crda 1.1.1, I don't think there are any technical roadblocks before crda/wireless-regdb can be uploaded to Debian (once the packaging implements what I suggested). Debian just needs someone to be the maintainer for it. IIRC Kel doesn't have the time. I don't really want to take on yet more packages, but I could probably offer sponsorship if Kel or others wanted to join pkg-wpa to do the work. Someone on the Debian kernel team might also be willing to do either sponsoring or maintainer-ship on this. Please note that the Debian freeze for the squeeze release is planned for March, so this stuff needs to be done soon. I can help with this only if no one else is up for it. I personally however find building a key on the fly for each build pretty pointless and would like to know if a package would be acceptable upstream on Debian if OpenSSL is used to allow administrators to add their own keys into the /etc/wireless-regdb/pubkeys/ dir for CRDA and from the start only trust John's key. Any idea what proportion of wireless card firmware will respect what Linux and crda tell it? All wireless drivers respect this, regardless of if you have firmware or not. Cool, but I would imagine ultimately it is up to the firmware to decide if it will use its own regulatory data or trust what Linux says? We have no way of overriding what firmware says, but in-kernel drivers do follow cfg80211 regulatory data so if cfg80211 says to disallow channel 13 because a user said so the driver will respect that. The regulatory API provided cfg80211 allows for drivers which have their own regulatory data to inform cfg80211 of this, whether that is that the device was designed for a specific country or it has a custom world regulatory domain. In terms of actual use cases currently all cfg80211 drivers (and therefore all mac80211 drivers) adhere to the regulatory domain that cfg80211 is using. Only a few drivers actually pass along regulatory information to cfg80211 for regulatory purposes. Those drivers are ath5k, ath9k, zd1211rw, ar9170. zd1211rw just passes a country for a few select possible countries it has allowed on the EEPROM. all other Atheros drivers (ath5k, ath9k, ar9170) all share the same EEPROM regulatory information and can either world roam, be part of a country region, or specifically be marked for one country. I have tried documenting this as best as possible here: http://wireless.kernel.org/en/users/Drivers/ath/ In short, most Atheros cards (95%) world roam, as such follow the its own custom world regulatory domain. The different custom world regulatory domains are documented on the wiki. All Intel cards world roam. Actually all wireless drivers do benefit from it. Note that all new wireless drivers upstream are expected to be either cfg80211 based or mac80211 based, that's it. The new regulatory infrastructure is part of cfg80211 and since all mac80211 drivers are cfg80211 drivers that means *every* wireless driver benefits from this and uses it. Excellent. I should note though that some firmware already have their regulatory stuff built-in to the firmware, just as some cards are configured on their EEPROM to use only one country. In those cases the regulatory infrastructure just helps regulatory compliance further, it would never allow more channels, for instance. Hmmm, OK. I guess that makes sense. I imagine it will definitely be the source of some annoyance for users in the future though. Tell me about it, but changing that would mean first getting regulatory agencies to allow regulatory compliance to fall down to the user when they customize a device's regulatory settings. As it stands that is not the case so all we can do upstream for now is allow users to enhance compliance, never allow more. There is also the complexity of calibration involved in allowing new channels but that is a separate topic as well. Luis -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550975: OpenVZ - deb-packages
ma as at this point we won't integrate new features for lenny, It's a pity :( This is very useful functional -- ... 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
Bug#565353: marked as done (linux-2.6: Update bnx2 PCI IDs)
Your message dated Mon, 1 Feb 2010 19:24:50 +0100
with message-id 20100201182450.ga2...@galadriel.inutil.org
and subject line Re: Bug#565353: Info received (Bug#565353: Offer of testing)
has caused the Debian Bug report #565353,
regarding linux-2.6: Update bnx2 PCI IDs
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.)
--
565353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6.26-2-amd64
Severity: important
Tags: patch, lenny
Version: 2.6.26-2
Hi,
The BCM5716 network chipset from Broadcom works perfectly well with the bnx2
driver in 2.6.26 (including the existing firmware), but it has an
unrecognised PCI ID, so the kernel doesn't detect it.
The attached patch adds the relevant PCI ID. We've built patched kernels
locally and verified that it works OK on a Dell PowerEdge R410.
Thanks,
- Matt
diff -urpN linux-source-2.6.26.orig/drivers/net/bnx2.c linux-source-2.6.26/drivers/net/bnx2.c
--- linux-source-2.6.26.orig/drivers/net/bnx2.c 2008-07-13 21:51:29.0 +
+++ linux-source-2.6.26/drivers/net/bnx2.c 2010-01-14 01:54:09.0 +
@@ -56,7 +56,7 @@
#define DRV_MODULE_NAME bnx2
#define PFX DRV_MODULE_NAME :
-#define DRV_MODULE_VERSION 1.7.5
+#define DRV_MODULE_VERSION 1.7.5-1
#define DRV_MODULE_RELDATE April 29, 2008
#define FW_FILE_06 bnx2-06-4.0.5.fw
#define FW_FILE_09 bnx2-09-4.0.5.fw
@@ -87,6 +87,7 @@ typedef enum {
BCM5708S,
BCM5709,
BCM5709S,
+ BCM5716,
} board_t;
/* indexed by board_t, above */
@@ -102,6 +103,7 @@ static struct {
{ Broadcom NetXtreme II BCM5708 1000Base-SX },
{ Broadcom NetXtreme II BCM5709 1000Base-T },
{ Broadcom NetXtreme II BCM5709 1000Base-SX },
+ { Broadcom NetXtreme II BCM5716 1000Base-T },
};
static struct pci_device_id bnx2_pci_tbl[] = {
@@ -123,6 +125,8 @@ static struct pci_device_id bnx2_pci_tbl
PCI_ANY_ID, PCI_ANY_ID, 0, 0, BCM5709 },
{ PCI_VENDOR_ID_BROADCOM, PCI_DEVICE_ID_NX2_5709S,
PCI_ANY_ID, PCI_ANY_ID, 0, 0, BCM5709S },
+ { PCI_VENDOR_ID_BROADCOM, PCI_DEVICE_ID_NX2_5716,
+ PCI_ANY_ID, PCI_ANY_ID, 0, 0, BCM5716 },
{ 0, }
};
diff -urpN linux-source-2.6.26.orig/include/linux/pci_ids.h linux-source-2.6.26/include/linux/pci_ids.h
--- linux-source-2.6.26.orig/include/linux/pci_ids.h 2008-07-13 21:51:29.0 +
+++ linux-source-2.6.26/include/linux/pci_ids.h 2010-01-14 01:55:44.0 +
@@ -1940,6 +1940,7 @@
#define PCI_DEVICE_ID_TIGON3_5752M 0x1601
#define PCI_DEVICE_ID_NX2_5709 0x1639
#define PCI_DEVICE_ID_NX2_5709S 0x163a
+#define PCI_DEVICE_ID_NX2_5716 0x163b
#define PCI_DEVICE_ID_TIGON3_5700 0x1644
#define PCI_DEVICE_ID_TIGON3_5701 0x1645
#define PCI_DEVICE_ID_TIGON3_5702 0x1646
---End Message---
---BeginMessage---
Version: 2.6.32-5
On Mon, Feb 01, 2010 at 03:59:31PM +, Tim Small wrote:
Transferred about a terabyte over NFS over 3 days whilst under
disk/CPU load - with no apparent problems, thanks.
Excellent, closing.
Cheers,
Moritz
---End Message---
Bug#567996: linux-image-amd64: Copying files to USB pendrive is very slow
Package: linux-image-amd64 Version: 2.6.32+23 Severity: normal It seems like this bug: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/197762 The first 250MB get transfered very fast with a 20MB/s rate, I guess because of the cache, then it almost stops and the rate starts decreasing to under 1MB/s. Tested with Nautilus. No error messages, this is the only log: [ 866.565377] usb 1-9: new high speed USB device using ehci_hcd and address 5 [ 866.698759] usb 1-9: New USB device found, idVendor=0951, idProduct=1624 [ 866.698775] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 866.698781] usb 1-9: Product: DataTraveler G2 [ 866.698785] usb 1-9: Manufacturer: Kingston [ 866.698789] usb 1-9: SerialNumber: 0013729945E6F96026270A82 [ 866.699018] usb 1-9: configuration #1 chosen from 1 choice [ 867.019566] Initializing USB Mass Storage driver... [ 867.019794] scsi8 : SCSI emulation for USB Mass Storage devices [ 867.020548] usbcore: registered new interface driver usb-storage [ 867.020555] USB Mass Storage support registered. [ 867.031964] usb-storage: device found at 5 [ 867.031970] usb-storage: waiting for device to settle before scanning [ 872.028897] usb-storage: device scan complete [ 872.030666] scsi 8:0:0:0: Direct-Access Kingston DataTraveler G2 1.00 PQ: 0 ANSI: 2 [ 872.033166] sd 8:0:0:0: Attached scsi generic sg3 type 0 [ 872.036649] sd 8:0:0:0: [sdc] 31309760 512-byte logical blocks: (16.0 GB/14.9 GiB) [ 872.037510] sd 8:0:0:0: [sdc] Write Protect is off [ 872.037514] sd 8:0:0:0: [sdc] Mode Sense: 16 24 09 51 [ 872.037516] sd 8:0:0:0: [sdc] Assuming drive cache: write through [ 872.041576] sd 8:0:0:0: [sdc] Assuming drive cache: write through [ 872.041582] sdc: sdc1 [ 872.044511] sd 8:0:0:0: [sdc] Assuming drive cache: write through [ 872.044516] sd 8:0:0:0: [sdc] Attached SCSI removable disk [ 878.806391] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (10, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/1 CPU core) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-amd64 depends on: ii linux-image-2.6.32-trunk-amd6 2.6.32-5 Linux 2.6.32 for 64-bit PCs linux-image-amd64 recommends no packages. linux-image-amd64 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565353: marked as done (linux-2.6: Update bnx2 PCI IDs)
Sorry, wrong bug number. Of course, this was fixed for unstable much earlier. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568008: linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device
Package: linux-image-2.6.32-trunk-amd64 Version: 2.6.32-5 Every time I boot - and I'm using crypto file systems - I get the series of messages (copied from bootlog): Starting early crypto disks...sda2_crypt (starting)... Unlocking the disk /dev/sda2 (sda2_crypt) Enter passphrase: modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-trunk-amd64/kernel/drivers/crypto/padlock-sha.ko): No such device Key slot 0 unlocked. Any ideas what this FATAL error is about and whether it is a problem? Julian -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568008: linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device
On Mon, 2010-02-01 at 20:23 +, Julian Gilbey wrote: Package: linux-image-2.6.32-trunk-amd64 Version: 2.6.32-5 Every time I boot - and I'm using crypto file systems - I get the series of messages (copied from bootlog): Starting early crypto disks...sda2_crypt (starting)... Unlocking the disk /dev/sda2 (sda2_crypt) Enter passphrase: modprobe: FATAL: Error inserting padlock_sha (/lib/modules/2.6.32-trunk-amd64/kernel/drivers/crypto/padlock-sha.ko): No such device Key slot 0 unlocked. Any ideas what this FATAL error is about and whether it is a problem? This is a known bug (#485070) and doesn't actually cause a problem, though I realise that the error message is alarming and should be fixed. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Processed: reassign 567996 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 567996 linux-2.6 2.6.32-5 Bug #567996 [linux-image-amd64] linux-image-amd64: Copying files to USB pendrive is very slow Bug reassigned from package 'linux-image-amd64' to 'linux-2.6'. Bug No longer marked as found in versions linux-latest-2.6/23. Bug #567996 [linux-2.6] linux-image-amd64: Copying files to USB pendrive is very slow There is no source info for the package 'linux-2.6' at version '2.6.32-5' with architecture '' Unable to make a source version for version '2.6.32-5' Bug Marked as found in versions 2.6.32-5. 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
Processed: reopening 565353, tagging 565353
Processing commands for cont...@bugs.debian.org:
reopen 565353
Bug #565353 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] linux-2.6:
Update bnx2 PCI IDs
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
tags 565353 pending
Bug #565353 [linux-2.6] linux-2.6: Update bnx2 PCI IDs
Added tag(s) pending.
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#567985: [linux-source-2.6.32] kerneloops on boot if LBDAF not used
On Mon, 2010-02-01 at 12:09 -0500, Brent S. Elmer Ph.D. wrote: Package: linux-source-2.6.32 Version: 2.6.32-5 Severity: important --- Please enter the report below this line. --- I get a kerneloops on 2.6.32 kernels unless CONFIG_LBDAF is yes. This is on a Lenovo W500 thinkpad that only has a 150G hard drive so there shouldn't be any need for LBDAF. The kerneloops is very early in the boot process. I always build my own kernels. I copied the 2.6.30 kernel config for my current kernel to the 2.6.32 source directory and did a make oldconfig. The resulting 2.6.32 kernel gave the kerneloops. After a long process of narrowing down what was causing the problem. I found that LBDAF had to be used for the kernel to boot. Please report this upstream at http://bugzilla.kernel.org, including your full config and the oops message. Let us know the bug number so we can track it. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Processed: tagging 567985
Processing commands for cont...@bugs.debian.org: tags 567985 moreinfo Bug #567985 [linux-source-2.6.32] [linux-source-2.6.32] kerneloops on boot if LBDAF not used Added tag(s) moreinfo. 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#565353: Info received (Bug#565353: Offer of testing)
On Mon, 2010-02-01 at 15:59 +, Tim Small wrote: Transferred about a terabyte over NFS over 3 days whilst under disk/CPU load - with no apparent problems, thanks. This will be included in the next stable update, 5.0.5. Unfortunately it missed 5.0.4, but it will be available in stable-proposed-updates soon. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard Brandwein signature.asc Description: This is a digitally signed message part
Processed: reassign 568008 to linux-2.6, forcibly merging 485070 568008
Processing commands for cont...@bugs.debian.org: reassign 568008 linux-2.6 2.6.32-5 Bug #568008 [linux-image-2.6.32-trunk-amd64] linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device Bug reassigned from package 'linux-image-2.6.32-trunk-amd64' to 'linux-2.6'. Bug No longer marked as found in versions linux-2.6/2.6.32-5. Bug #568008 [linux-2.6] linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device There is no source info for the package 'linux-2.6' at version '2.6.32-5' with architecture '' Unable to make a source version for version '2.6.32-5' Bug Marked as found in versions 2.6.32-5. forcemerge 485070 568008 Bug#485070: cryptsetup: strange padlock_aes error during boot Bug#568008: linux-image-2.6.32-trunk-amd64: Error inserting padlock_sha: No such device Bug#509700: kernel: modules:padlock-aes.ko trying exception Bug#540734: padlock: Error inserting padlock_aes (/lib/modules/2.6.26-2-686/kernel/drivers/crypto/padlock-aes.ko) Bug#541289: padlock: Starting MTA [ 35.356507] padlock: VIA PadLock not detected. Bug#566309: linux-image-2.6.30-2-686: aes.ko depends on device specific padlock-aes.ko Forcibly Merged 485070 509700 540734 541289 566309 568008. 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#568025: FTBFS on sparc
Package: linux-2.6 Version: 2.6.32-6 Severity: important Justification: fails to build from source Since we enabled dynamic ftrace, the recordmcount.pl script is used in the build process. This script wrongly detects the target architecture during Debian builds for sparc, and reports it as not supported: https://buildd.debian.org/fetch.cgi?pkg=linux-2.6;ver=2.6.32-6;arch=sparc;stamp=1265049730 Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 568025
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 568025 + pending Bug #568025 [linux-2.6] FTBFS on sparc Added tag(s) 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#568030: FTBFS on armel (and maybe others)
Package: linux-2.6 Version: 2.6.32-6 Severity: important Justification: fails to build from source From https://buildd.debian.org/fetch.cgi?pkg=linux-2.6;ver=2.6.32-6;arch=armel;stamp=1265064985: CC kernel/time/clocksource.o /build/buildd-linux-2.6_2.6.32-6-armel-0P0u54/linux-2.6-2.6.32/debian/build/source_armel_none/kernel/time/clocksource.c: In function 'clocksource_register': /build/buildd-linux-2.6_2.6.32-6-armel-0P0u54/linux-2.6-2.6.32/debian/build/source_armel_none/kernel/time/clocksource.c:556: error: implicit declaration of function 'clocksource_max_deferment' Upstream stable release 2.6.32.7 added this function, conditional on CONFIG_GENERIC_TIME, but added an unconditional use. This has been fixed in mainline in commit a362c638bdf052bf424bce7645d39b101090f6ba (clocksource/events: Fix fallout of generic code changes). Ben. -- System Information: Debian Release: squeeze/sid APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.32-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 568030
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 tags 568030 + pending Bug #568030 [linux-2.6] FTBFS on armel (and maybe others) Added tag(s) 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
Re: Debian 2.6.32 CONFIG_WIRELESS_OLD_REGULATORY, wireless-regdb and crda
On Mon, 2010-02-01 at 09:58 -0800, Luis R. Rodriguez wrote: I can help with this only if no one else is up for it. I personally however find building a key on the fly for each build pretty pointless and would like to know if a package would be acceptable upstream on Debian if OpenSSL is used to allow administrators to add their own keys into the /etc/wireless-regdb/pubkeys/ dir for CRDA and from the start only trust John's key. As part of upstream, you're probably the best person to do the packaging stuff for Debian. The idea was that by default there would be no Debian key installed because the text and binary databases would be unmodified. The build system would detect if Debian had patched the databases and if so generate a new key, sign the binary database with it and install the public key to the /etc/wireless-regdb/pubkeys/ dir. Debian might need to patch the database for the stable release. Thanks for all the information about how wireless card firmware and drivers interact with regulatory information. Hmmm, OK. I guess that makes sense. I imagine it will definitely be the source of some annoyance for users in the future though. Tell me about it, but changing that would mean first getting regulatory agencies to allow regulatory compliance to fall down to the user when they customize a device's regulatory settings. As it stands that is not the case so all we can do upstream for now is allow users to enhance compliance, never allow more. There is also the complexity of calibration involved in allowing new channels but that is a separate topic as well. There is also the opportunity for user-based advocacy for change in the regulations. Whenever someone comes to the kernel wireless folks with a situation where they have been prevented from connecting to a wireless network because of restrictive wireless regulatory data, explain the issue and give them a form letter they can send to their local regulatory agency complaining about the situation and suggesting change. A list of relevant regulatory agency contact details would be useful here too I think. Ideally the manufacturer should be obligated to give users hardware that can be compliant for any level of radio license and defaults to being compliant for the default radio license for the whole population. It would then be up to individual users to comply with the relevant radio license(s). Such a situation would then turn into a much bigger enforcement problem, I guess that is the main reason it doesn't work this way. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: bug 517833 is forwarded to http://bugzilla.kernel.org/show_bug.cgi?id=11655
Processing commands for cont...@bugs.debian.org: forwarded 517833 http://bugzilla.kernel.org/show_bug.cgi?id=11655 Bug #517833 [linux-2.6] better document net.ipv?.conf.all.* interface Set Bug forwarded-to-address to 'http://bugzilla.kernel.org/show_bug.cgi?id=11655'. 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
Processed: tagging as pending bugs that are closed by packages in NEW
Processing commands for cont...@bugs.debian.org:
# Tue Feb 2 07:03:54 UTC 2010
# Tagging as pending bugs that are closed by packages in NEW
# http://ftp-master.debian.org/new.html
#
# Source package in NEW: haskell-qio
tags 567632 + pending
Bug #567632 [wnpp] ITP: haskell-qio -- a language for defining quantum
computations
Added tag(s) pending.
# Source package in NEW: jbig2enc
tags 512518 + pending
Bug #512518 [wnpp] ITP: jbig2enc -- a JBIG2 encoder
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 562975 + pending
Bug #562975 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] linux-2.6:
patch for CVE-2009-3939
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 528834 + pending
Bug #528834 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] linux-2.6:
Mobile IPv6 needs
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 558237 + pending
Bug #558237 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-source-2.6.32: X with xserver-xorg-video-intel does not work any longer
Bug #566376 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-trunk-amd64: X unconditionally hangs up on bootup
Added tag(s) pending.
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 510593 + pending
Bug #510593 {Done: Ben Hutchings b...@decadent.org.uk}
[linux-image-2.6.26-1-amd64] Support more than 8 sound cards
Warning: Unknown package 'linux-image-2.6.26-1-amd64'
Added tag(s) pending.
Warning: Unknown package 'linux-image-2.6.26-1-amd64'
# Source package in NEW: linux-2.6
tags 563161 + pending
Bug #563161 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] Provide
way to distinguish remove and purge in postrm hooks
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 478315 + pending
Bug #478315 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] please
enable CONFIG_PM_TRACE for easier debugging of suspend to ram
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 565494 + pending
Bug #565494 {Done: Ben Hutchings b...@decadent.org.uk}
[linux-image-2.6.26-2-amd64] linux-image-2.6.26-2-amd64: does not include
CONFIG_INFINIBAND_IPOIB_CM infiniband connected mode
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 564807 + pending
Bug #564807 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
xserver-xorg-video-intel: display corruption and white screen with KMS
Bug #564946 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
xserver-xorg-video-intel: screen flickers, tears, turns pink
Added tag(s) pending.
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 561880 + pending
Bug #561880 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] inotify:
Not assigning sequential ids as expected
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 545417 + pending
Bug #545417 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.30-1-amd64: please enable CONFIG_PCIEASPM
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 566547 + pending
Bug #566547 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-trunk-amd64: Segmentation fault during halt
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 567391 + pending
Bug #567391 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] Please
update aufs2 to new upstream snapshot (aufs2-32 branch)
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 563847 + pending
Bug #563847 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux-2.6] Please
enable the f-trace tracers
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 567689 + pending
Bug #567689 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.26-2-amd64: cdc_ether driver fails to communicate with Sphairon
Turbolink 1203 DSL modem
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 564743 + pending
Bug #564743 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] 3c509
ethernet driver doesn't accept the xcvr parameter
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 566213 + pending
Bug #566213 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-trunk-vserver-686-bigmem: vserver_686-bigmem is not bigmem
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 562815 + pending
Bug #562815 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6] Bug in
kernel audit code makes system crash
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 567352 + pending
Bug #567352 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-trunk-686-bigmem: DRM failure during boot
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 525232 + pending
Bug #525232 {Done: Ben Hutchings b...@decadent.org.uk}
[linux-image-2.6.26-2-amd64] Please enable CONFIG_ITCO_VENDOR_SUPPORT
Added tag(s) pending.
# Source package in NEW: linux-2.6
tags 566539 + pending
Bug #566539 {Done:
