Bug#719668: skbuff: skb_over_panic
Package: src:linux Version: 3.10.5-1 Severity: important Dear Maintainer, I am running on a KVM/QEMU VPS. I am experiencing a kernel panic when querying a local bind9 for domains such as ftp.us.debian.org., www.debian.org., and www.ietf.org to name a few. This kernel panic also happens when establishing an ipsec connection with openswan with the VPS setup as responder. Originally, my VPS was configured to use the virtio network card. This caused the VPS to crash when querying the local bind9 for the domains mentioned above, and when attempting to establish the ipsec connection. My VPS provider reconfigured my VPS to use the e1000 network card instead, which now causes a kernel panic as mentioned above. I tried kernels 3.2.0 currently in wheezy, 3.9.0 currently in wheezy-backports, and the kernel I'm reporting this against currently in unstable. The panic is the same under all three kernel versions. This problem originally started being discussed on the debian-user list. The thread can be found at: http://lists.debian.org/debian-user/2013/08/msg00306.html. I also reluctantly decided to file bug reports on the debian bug tracker against openswan http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719459, and against bind9 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719465. I suppose the bugs against openswan and bind9 can be closed, since this seems to be a problem with either how the kernel is interacting with KVM, or with the kernel itself. Here is a stack trace with the VPS in runlevel one, done from the serial console: # dig @localhost www.debian.org. [ 229.466442] skbuff: skb_over_panic: text:a005d0ce len:1660 put:1660 head:880036fab480 data:880036fab4c0 tail:0x6bc end:0x640 dev:eth0 [ 229.472412] [ cut here ] [ 229.474399] kernel BUG at /build/linux-4aFT2B/linux-3.10.5/net/core/skbuff.c:126! [ 229.476345] invalid opcode: [#1] SMP [ 229.476345] Modules linked in: xts gf128mul nf_nat_ftp nf_conntrack_ftp nf_nat nf_conntrack loop dm_crypt snd_pcm snd_page_alloc snd_timer snd soundcore psmouse microcode serio_raw pcspkr evdev virtio_console virtio_balloon ttm drm_kms_helper drm i2c_piix4 i2c_core processor thermal_sys button ext4 crc16 jbd2 mbcache dm_mod sg sr_mod cdrom ata_generic virtio_blk floppy uhci_hcd ehci_hcd ata_piix libata usbcore e1000 virtio_pci virtio_ring virtio usb_common scsi_mod [ 229.476345] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.10-2-amd64 #1 Debian 3.10.5-1 [ 229.476345] Hardware name: , BIOS QEMU 01/01/2007 [ 229.476345] task: 81613400 ti: 8160 task.ti: 8160 [ 229.476345] RIP: 0010:[8138615d] [8138615d] skb_panic+0x5a/0x5c [ 229.476345] RSP: 0018:88003fc03d78 EFLAGS: 00010286 [ 229.476345] RAX: 0089 RBX: 880036c06d40 RCX: 04e004e0 [ 229.476345] RDX: 0b3c RSI: 0046 RDI: 0246 [ 229.476345] RBP: 006e R08: 81693fc0 R09: 814f2cc2 [ 229.476345] R10: R11: R12: 88003b4646d0 [ 229.476345] R13: 880037332800 R14: 88003b776680 R15: 067c [ 229.476345] FS: () GS:88003fc0() knlGS: [ 229.476345] CS: 0010 DS: ES: CR0: 8005003b [ 229.476345] CR2: 7f5e30bce010 CR3: 3c6f9000 CR4: 06f0 [ 229.476345] DR0: DR1: DR2: [ 229.476345] DR3: DR6: 0ff0 DR7: 0400 [ 229.476345] Stack: [ 229.476345] 880036fab4c0 06bc 0640 880037332000 [ 229.476345] 812bb64a a005d0ce c91e2470 00a7 [ 229.476345] 88003b46ca60 880037332000 07000304 067c0001 [ 229.476345] Call Trace: [ 229.476345] IRQ [ 229.476345] [812bb64a] ? skb_put+0x3a/0x3b [ 229.476345] [a005d0ce] ? e1000_clean_rx_irq+0x2c7/0x3cd [e1000] [ 229.476345] [a005c09d] ? e1000_clean+0x5b9/0x725 [e1000] [ 229.476345] [812c35b1] ? __napi_complete+0x1c/0x23 [ 229.476345] [812c6c6c] ? napi_complete+0x29/0x36 [ 229.476345] [a005c1df] ? e1000_clean+0x6fb/0x725 [e1000] [ 229.476345] [812c6d20] ? net_rx_action+0xa7/0x1df [ 229.476345] [810421ba] ? __do_softirq+0xea/0x205 [ 229.476345] [8104239f] ? irq_exit+0x3e/0x81 [ 229.476345] [8100e697] ? do_IRQ+0x80/0x95 [ 229.476345] [813883ed] ? common_interrupt+0x6d/0x6d [ 229.476345] EOI [ 229.476345] [8102e385] ? native_safe_halt+0x2/0x3 [ 229.476345] [810133f6] ? default_idle+0x17/0x3f [ 229.476345] [81072571] ? cpu_startup_entry+0x10d/0x187 [ 229.476345] [816b3d3d] ? start_kernel+0x3e8/0x3f3 [ 229.476345] [816b3777] ? repair_env_string+0x54/0x54 [ 229.476345] [816b3598] ?
Bug#719623: linux-image-3.10-2-amd64: kernel panic on inserting DVB-T stick
I took a quick look at the code and wonder if the problem is caused by an initial zero statistics message? This is all just a wild guess, but if it is correct, then the attached untested patch might fix it... Bjørn From d78a0599d5b5d4da384eae08bf7da316389dfbe5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Bj=C3=B8rn=20Mork?= bj...@mork.no Date: Wed, 14 Aug 2013 10:24:39 +0200 Subject: [PATCH] [media] siano: fix divide error on 0 counters MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ts_packets and ets_packets counters can be 0. Don't fall over if they are. Fixes: [ 846.851711] divide error: [#1] SMP [ 846.851806] Modules linked in: smsdvb dvb_core ir_lirc_codec lirc_dev ir_sanyo_decoder ir_mce_kbd_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder rc_hauppauge smsusb smsmdtv rc_core pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) parport_pc ppdev lp parport cpufreq_userspace cpufreq_powersave cpufreq_stats cpufreq_conservative rfcomm bnep binfmt_misc uinput nfsd auth_rpcgss oid_registry nfs_acl nfs lockd dns_resolver fscache sunrpc ext4 jbd2 fuse tp_smapi(O) thinkpad_ec(O) loop firewire_sbp2 dm_crypt snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm thinkpad_acpi nvram snd_page_alloc hid_generic snd_seq_midi snd_seq_midi_event arc4 usbhid snd_rawmidi uvcvideo hid iwldvm coretemp kvm_intel mac8021 1 cdc_wdm [ 846.853477] cdc_acm snd_seq videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media kvm radeon r852 ttm joydev cdc_ether usbnet pcmcia mii sm_common nand btusb drm_kms_helper tpm_tis acpi_cpufreq bluetooth iwlwifi nand_ecc drm nand_ids i2c_i801 mtd snd_seq_device iTCO_wdt iTCO_vendor_support r592 memstick lpc_ich mperf tpm yenta_socket pcmcia_rsrc pcmcia_core cfg80211 snd_timer snd pcspkr i2c_algo_bit crc16 i2c_core tpm_bios processor mfd_core wmi psmouse mei_me rfkill mei serio_raw soundcore evdev battery button video ac microcode ext3 mbcache jbd md_mod dm_mirror dm_region_hash dm_log dm_mod sg sr_mod sd_mod cdrom crc_t10dif firewire_ohci sdhci_pci sdhci mmc_core firewire_core crc_itu_t thermal thermal_sys ahci libahci ehci_pci uhci_hcd ehci_hcd libata scsi_mod usbcore e1000 e usb_common [ 846.855310] ptp pps_core [ 846.855356] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G O 3.10-2-amd64 #1 Debian 3.10.5-1 [ 846.855490] Hardware name: LENOVO 4061WFA/4061WFA, BIOS 6FET92WW (3.22 ) 12/14/2011 [ 846.855609] task: 81613400 ti: 8160 task.ti: 8160 [ 846.855636] RIP: 0010:[a092be0c] [a092be0c] smsdvb_onresponse+0x264/0xa86 [smsdvb] [ 846.863906] RSP: 0018:88013bc03cf0 EFLAGS: 00010046 [ 846.863906] RAX: RBX: 880133bf6000 RCX: [ 846.863906] RDX: RSI: 88005d3b58c0 RDI: 880133bf6000 [ 846.863906] RBP: 88005d1da000 R08: 0058 R09: 0015 [ 846.863906] R10: 1a0d R11: 021a R12: 88005d3b58c0 [ 846.863906] R13: 88005d1da008 R14: ff8d R15: 880036cf5060 [ 846.863906] FS: () GS:88013bc0() knlGS: [ 846.863906] CS: 0010 DS: ES: CR0: 8005003b [ 846.863906] CR2: 7f3a4b69ae50 CR3: 36dac000 CR4: 000407f0 [ 846.863906] DR0: DR1: DR2: [ 846.863906] DR3: DR6: 0ff0 DR7: 0400 [ 846.863906] Stack: [ 846.863906] 88007a102000 88005d1da000 88005d3b58c0 00085824 [ 846.863906] a08c5aa3 88005d1da000 8800a6907390 8800a69073b0 [ 846.863906] 8800a6907000 a08b642c 021a 8800a69073b0 [ 846.863906] Call Trace: [ 846.863906] IRQ [ 846.863906] [ 846.863906] [a08c5aa3] ? smscore_onresponse+0x1d5/0x353 [smsmdtv] [ 846.863906] [a08b642c] ? smsusb_onresponse+0x146/0x192 [smsusb] [ 846.863906] [a004cb1a] ? usb_hcd_giveback_urb+0x6c/0xac [usbcore] [ 846.863906] [a0217be1] ? ehci_urb_done+0x62/0x72 [ehci_hcd] [ 846.863906] [a0217c82] ? qh_completions+0x91/0x364 [ehci_hcd] [ 846.863906] [a0219bba] ? ehci_work+0x8a/0x68e [ehci_hcd] [ 846.863906] [8107336c] ? timekeeping_get_ns.constprop.10+0xd/0x31 [ 846.863906] [81064d41] ? update_cfs_rq_blocked_load+0xde/0xec [ 846.863906] [81058ec2] ? run_posix_cpu_timers+0x25/0x575 [ 846.863906] [a021aa46] ? ehci_irq+0x211/0x23d [ehci_hcd] [ 846.863906] [a004c0c1] ? usb_hcd_irq+0x31/0x48 [usbcore] [ 846.863906] [810996fd] ? handle_irq_event_percpu+0x49/0x1a4 [ 846.863906] [8109988a] ? handle_irq_event+0x32/0x4b [ 846.863906] [8109bd76] ? handle_fasteoi_irq+0x80/0xb6 [ 846.863906] [8100e93e] ? handle_irq+0x18/0x20 [ 846.863906] [8100e657] ?
Bug#719680: Driver mv643xx_eth_port requests probe deferral
Package: linux Version: 3.10.5-1 Severity: important A Debian on QNAP user reported that Ethernet isn't working with the 3.10.5-1 kernel. Arnaud, do you know if this is a known issue? [6.647426] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4 [6.662138] usbcore: registered new interface driver hub [6.683480] libphy: PHY orion-mdio-mii:00 not found [6.697859] libata version 3.00 loaded. [6.701290] ahci :00:01.0: version 3.0 [6.705406] usbcore: registered new device driver usb [6.716645] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral ... [6.928972] libphy: PHY orion-mdio-mii:00 not found [6.933890] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral ... [7.023110] libphy: PHY orion-mdio-mii:00 not found [7.032389] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral ... [8.209070] libphy: PHY orion-mdio-mii:00 not found [8.213983] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral See http://forum.qnap.com/viewtopic.php?f=147t=78916#p359743 for the complete log. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130814085349.ga9...@jirafa.cyrius.com
Bug#683777: marked as done (linux-image-3.2.0-3-amd64: some multimedia/action keys don't work)
Your message dated Wed, 14 Aug 2013 11:24:52 +0200 with message-id 1376472292.5278.3.camel@rosa and subject line has caused the Debian Bug report #683777, regarding linux-image-3.2.0-3-amd64: some multimedia/action keys don't work to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 683777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src Version: 3.2.21-3 Severity: normal Dear Maintainer, some multimedia/action keys of my notebook don't work. Neither xev nor showkey, evtest or xinput report anything at all when I press (Fn together with) certain keys. Affected are the following combinations: Fn+F2 (display brightness down), Fn+F3 (display brightness up), Fn+F12 (wireless on/off). Other action keys work well out of the box like Fn+F6 (last music title), Fn+F7 (play/pause), Fn+F8 (next music title)… I'm reporting this against linux-image-3.2.0-3-amd64 because I found a similar report against evdev (bug #619466), in Message #10 Cyril Brulebois wrote: Try with evtest $device on a console, if there's nothing coming up, talk to kernel people. Please tell me if you need more information. -- Package-specific info: ** Version: Linux version 3.2.0-3-amd64 (Debian 3.2.21-3) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Thu Jun 28 09:07:26 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-3-amd64 root=/dev/mapper/rosa-root ro quiet pci=noacpi ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [9.856776] rts_pstor: waiting for device to settle before scanning [ 10.188137] ACPI: Battery Slot [BAT1] (battery present) [ 10.195507] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07 [ 10.195753] iTCO_wdt: Found a Cougar Point TCO device (Version=2, TCOBASE=0x0460) [ 10.195971] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) [ 10.200688] Linux video capture interface: v2.00 [ 10.200810] cfg80211: Calling CRDA to update world regulatory domain [ 10.279720] uvcvideo: Found UVC 1.00 device HP TrueVision HD (1bcf:2c07) [ 10.298792] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree: [ 10.298796] Copyright(c) 2003-2011 Intel Corporation [ 10.298943] iwlwifi :02:00.0: PCI-APIC IRQ transform: INT A - IRQ 18 [ 10.298983] iwlwifi :02:00.0: setting latency timer to 64 [ 10.299031] iwlwifi :02:00.0: pci_resource_len = 0x2000 [ 10.299035] iwlwifi :02:00.0: pci_resource_base = c9001109 [ 10.299037] iwlwifi :02:00.0: HW Revision ID = 0x34 [ 10.299217] iwlwifi :02:00.0: irq 49 for MSI/MSI-X [ 10.299311] iwlwifi :02:00.0: Detected Intel(R) Centrino(R) Wireless-N 1030 BGN, REV=0xB0 [ 10.299469] iwlwifi :02:00.0: L1 Enabled; Disabling L0S [ 10.315355] iwlwifi :02:00.0: device EEPROM VER=0x716, CALIB=0x6 [ 10.315359] iwlwifi :02:00.0: Device SKU: 0X150 [ 10.315363] iwlwifi :02:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3 [ 10.315395] iwlwifi :02:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [ 10.332763] iwlwifi :02:00.0: loaded firmware version 18.168.6.1 [ 10.333293] Registered led device: phy0-led [ 10.336932] fbcon: inteldrmfb (fb0) is primary device [ 10.342565] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [ 10.355636] cfg80211: World regulatory domain updated: [ 10.355639] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 10.355643] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.355646] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 10.355649] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 10.355652] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.355654] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 10.361613] input: HP TrueVision HD as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input5 [ 10.361754] usbcore: registered new interface driver uvcvideo [ 10.361756] USB Video Class driver (1.1.1) [ 10.538938] Console: switching to colour frame buffer device 170x48 [ 10.550081] fb0: inteldrmfb frame buffer device [ 10.550087] drm: registered panic notifier [ 10.550347] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 10.550464] i801_smbus :00:1f.3: PCI-APIC IRQ transform: INT C - IRQ 19 [ 10.550486] ACPI: resource :00:1f.3 [io 0x4040-0x405f] conflicts with ACPI region SMBI
Re: Plan of action for Secure Boot support
On Wed, Aug 14, 2013 at 12:30:55AM +0200, Ben Hutchings wrote: Editing of binary packages is icky, so that's not part of the plan. Instead, after dak signs an executable, the package maintainer downloads and copies those into a separate 'source' package, which has a trivial debian/rules. (And of course will generate an appropriate 'Built-Using' header.) This will most likely go via by-hand. So a script on the dak side is needed anyway. Why not do the dummy source package stuff in this script and let dak do all the work semi-automatically? It needs a prepared binary tree in a tar, a list of files to be signed and a DEBIAN dir. Bastian -- Landru! Guide us! -- A Beta 3-oid, The Return of the Archons, stardate 3157.4 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130814094925.ga16...@mail.waldi.eu.org
Bug#691427:
Your E-mail has been picked by the British Telecom Center as a lucky Person of a lump sum of 1,000,000.00. To Claim send info To Email: (btcenter...@outlook.commailto:btcenter...@outlook.com)
Bug#625211: linux-image-2.6.32-5-amd64: Can no longer control backlight
Package: src:linux Version: 3.9.8-1 Followup-For: Bug #625211 No, with the radeon driver it works, sorry for not having checked that. There is already a bug open against fglrx-driver, as brightness is concerned: 719536. The problem remains that one need to specify the kernel attribute in the grub configuration file, it would be nice if that could be handled during installation. Thanks, Carlo. -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-5) ) #1 SMP Debian 3.9.8-1 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.9-1-amd64 root=UUID=221d4a92-44de-42bf-a8c4-1d8844595fbf ro acpi_backlight=vendor acpi_backlight=vendor ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [5.657439] psmouse serio1: elantech: Synaptics capabilities query result 0x08, 0x14, 0x0c. [5.734873] usb 1-1: New USB device found, idVendor=8087, idProduct=0020 [5.734962] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.735378] hub 1-1:1.0: USB hub found [5.735599] hub 1-1:1.0: 6 ports detected [5.775436] lib80211_crypt: registered algorithm 'TKIP' [5.775681] wlan0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 5.100.82.112 [5.787049] input: ETPS/2 Elantech Touchpad as /devices/platform/i8042/serio1/input/input7 [5.846414] usb 2-1: new high-speed USB device number 2 using ehci-pci [5.850581] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X [5.978830] 6[fglrx] Maximum main memory to use for locked dma buffers: 3657 MBytes. [5.978930] usb 2-1: New USB device found, idVendor=8087, idProduct=0020 [5.979001] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.979162] 6[fglrx] vendor: 1002 device: 68e0 count: 1 [5.979547] 6[fglrx] ioport: bar 4, base 0xd000, size: 0x100 [5.979841] 6[fglrx] Kernel PAT support is enabled [5.979934] 6[fglrx] module loaded - fglrx 13.20.4 [Jul 26 2013] with 1 minors [5.980444] hub 2-1:1.0: USB hub found [5.980603] hub 2-1:1.0: 8 ports detected [6.017221] input: HDA Intel MID Mic as /devices/pci:00/:00:1b.0/sound/card0/input8 [6.017393] input: HDA Intel MID Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [6.017808] hda-intel :01:00.1: Handle VGA-switcheroo audio client [6.017924] snd_hda_intel :01:00.1: irq 44 for MSI/MSI-X [6.043568] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci:00/:00:01.0/:01:00.1/sound/card1/input10 [6.050490] usb 1-1.1: new high-speed USB device number 3 using ehci-pci [6.165448] usb 1-1.1: New USB device found, idVendor=1210, idProduct=25f4 [6.165533] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.165618] usb 1-1.1: Product: USB 2.0 PC Camera [6.165688] usb 1-1.1: Manufacturer: Alcor Micro, Corp. [6.250758] usb 2-1.3: new full-speed USB device number 3 using ehci-pci [6.347591] usb 2-1.3: New USB device found, idVendor=0a5c, idProduct=219c [6.347677] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6.347762] usb 2-1.3: Product: Broadcom BCM2070 Bluetooth Device [6.347832] usb 2-1.3: Manufacturer: Broadcom Corp [6.347902] usb 2-1.3: SerialNumber: 001BB1F9E0EB [6.418548] usb 2-1.4: new high-speed USB device number 4 using ehci-pci [6.512591] usb 2-1.4: New USB device found, idVendor=058f, idProduct=6335 [6.512676] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6.512761] usb 2-1.4: Product: Mass Storage Device [6.512824] usb 2-1.4: Manufacturer: Generic [6.512886] usb 2-1.4: SerialNumber: 058F63356336 [6.816996] Bluetooth: Core ver 2.16 [6.817110] NET: Registered protocol family 31 [6.817190] Bluetooth: HCI device and connection manager initialized [6.817278] Bluetooth: HCI socket layer initialized [6.817360] Bluetooth: L2CAP socket layer initialized [6.817435] Bluetooth: SCO socket layer initialized [6.861435] usbcore: registered new interface driver btusb [6.891589] cfg80211: World regulatory domain updated: [6.891653] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [6.891727] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [6.891802] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [6.891889] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [6.891963] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [6.892050] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [7.781854] media: Linux media interface: v0.10 [7.797364] Initializing USB Mass Storage driver... [7.797628] scsi5 : usb-storage 2-1.4:1.0 [7.797845] usbcore: registered new interface driver usb-storage [7.797918] USB Mass Storage
Processed: bug 714974 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=60737
Processing commands for cont...@bugs.debian.org: forwarded 714974 https://bugzilla.kernel.org/show_bug.cgi?id=60737 Bug #714974 [src:linux] nfs-kernel-server: Duplicate cookies reported - jfs partition, with samba Set Bug forwarded-to-address to 'https://bugzilla.kernel.org/show_bug.cgi?id=60737'. thanks Stopping processing here. Please contact me if you need assistance. -- 714974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13764907026505.transcr...@bugs.debian.org
Bug#719717: BUG: soft lockup - CPU#2 stuck for 23s! [kvm:2775] / RIP: 0010:[ffffffffa03f6c95] [ffffffffa03f6c95] kvm_mmu_prepare_zap_page+0x64/0x214 [kvm]
Package: linux-image-amd64 Version: 3.2+46~bpo60+1 Severity: important Hi! I today encountered the following problem when using virsh shutdown guest to shutdown a windows 2003 32bit non r2 guest. (i've migrated this machine from a vmware server 1 vmdk file) Aug 14 16:07:44 k000227a kernel: [4296670.865615] breth0: port 2(vnet0) entering forwarding state Aug 14 16:07:44 k000227a kernel: [4296670.871745] breth0: port 2(vnet0) entering disabled state Aug 14 16:07:44 k000227a kernel: [4296670.872363] device vnet0 left promiscuous mode Aug 14 16:07:44 k000227a kernel: [4296670.872370] breth0: port 2(vnet0) entering disabled state Aug 14 16:08:10 k000227a kernel: [4296696.236047] BUG: soft lockup - CPU#2 stuck for 23s! [kvm:2775] Aug 14 16:08:10 k000227a kernel: [4296696.239639] Modules linked in: 8021q garp tun ip6table_filter ebtable_nat ebtables act_police cls_flow cls_fw cls_u32 sch_htb sch_hfsc sch_ingress sch_sfq xt_time xt_connlimit xt_realm xt_addrtype iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REJECT ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY nf_tproxy_core ip6_tables nf_defrag_ipv6 xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSC P xt_dsc p xt_dccp xt_conntrack xt_connmar Aug 14 16:08:10 k000227a kernel: k xt_CLASSIFY ipt_LOG xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables bridge stp r8169 kvm_amd kvm radeon ttm drm_kms_helper drm snd_pcm snd_timer snd i2c_algo_bit soundcore sr_mod cdrom e100 ohci_hcd snd_page_alloc i2c_piix4 tpm_tis ehci_hcd tg3 tpm powernow_k8 usbcore libphy edac_core tpm_bios processor ata_generic pata_serverworks pcspkr i2c_core mii evdev k8temp sg power_supply usb_common thermal_sys edac_mce_amd sata_svw mperf psmouse serio_raw button dm_mod sata_via sata_sis pata_sis sata_sil sata_nv ext4 jbd2 mbcache crc16 raid1 md_mod ata_piix libata sd_mod crc_t10dif arcmsr scsi_mod shpchp Aug 14 16:08:10 k000227a kernel: [4296696.239888] CPU 2 Aug 14 16:08:10 k000227a kernel: [4296696.239892] Modules linked in: 8021q garp tun ip6table_filter ebtable_nat ebtables act_police cls_flow cls_fw cls_u32 sch_htb sch_hfsc sch_ingress sch_sfq xt_time xt_connlimit xt_realm xt_addrtype iptable_raw xt_comment xt_recent xt_policy ipt_ULOG ipt_REJECT ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY nf_tproxy_core ip6_tables nf_defrag_ipv6 xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSC P xt_dsc p xt_dccp xt_conntrack xt_connmar Aug 14 16:08:10 k000227a kernel: k xt_CLASSIFY ipt_LOG xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables bridge stp r8169 kvm_amd kvm radeon ttm drm_kms_helper drm snd_pcm snd_timer snd i2c_algo_bit soundcore sr_mod cdrom e100 ohci_hcd snd_page_alloc i2c_piix4 tpm_tis ehci_hcd tg3 tpm powernow_k8 usbcore libphy edac_core tpm_bios processor ata_generic pata_serverworks pcspkr i2c_core mii evdev k8temp sg power_supply usb_common thermal_sys edac_mce_amd sata_svw mperf psmouse serio_raw button dm_mod sata_via sata_sis pata_sis sata_sil sata_nv ext4 jbd2 mbcache crc16 raid1 md_mod ata_piix libata sd_mod crc_t10dif arcmsr scsi_mod shpchp Aug 14 16:08:10 k000227a kernel: [4296696.240022] Aug 14 16:08:10 k000227a kernel: [4296696.240022] Pid: 2775, comm: kvm Not tainted 3.2.0-0.bpo.4-amd64 #1 Debian 3.2.46-1~bpo60+1 empty empty/Tyan Transport GT24-B3992 Aug 14 16:08:10 k000227a kernel: [4296696.240022] RIP: 0010:[a03f6c95] [a03f6c95] kvm_mmu_prepare_zap_page+0x64/0x214 [kvm] Aug 14 16:08:10 k000227a kernel: [4296696.240022] RSP: 0018:880142e8fb08 EFLAGS: 0282 Aug 14 16:08:10 k000227a kernel: [4296696.240022] RAX: RBX: 8801010db290 RCX: 8801010db290 Aug 14 16:08:10 k000227a kernel:
Bug#600601: marked as done (Feature request -- USB passthrough for Xen PV)
Your message dated Wed, 14 Aug 2013 16:29:48 +0200 with message-id 20130814142948.GA5017@pisco.westfalen.local and subject line Re: Bug#600601: Feature request -- USB passthrough for Xen PV has caused the Debian Bug report #600601, regarding Feature request -- USB passthrough for Xen PV 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.) -- 600601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-xen-amd64 Version: 2.6.32+28 Severity: wishlist It would be great if the Xennified kernel included the PVUSB code from Xen so that USB devices could be passed through to DomU's. Thanks, Seth Green ---End Message--- ---BeginMessage--- On Tue, Aug 13, 2013 at 08:54:52PM +0100, Ian Campbell wrote: On Tue, 2013-07-09 at 21:48 +0200, Moritz Muehlenhoff wrote: reassign 600601 src:linux thanks On Mon, Oct 18, 2010 at 04:56:05PM +0100, Ian Campbell wrote: tags 600601 +upstream thanks On Mon, 2010-10-18 at 11:13 -0400, Seth Green wrote: Package: linux-image-xen-amd64 Version: 2.6.32+28 Severity: wishlist It would be great if the Xennified kernel included the PVUSB code from Xen so that USB devices could be passed through to DomU's. PVUSB support has not been ported to the PVOPS kernel by Xen upstream, primarily because AFAIK nobody has volunteered to do the required work to forward port the support from the classic Xen kernels. I'm afraid you will need to work with Xen upstream to do so before such feature can be considered for the Debian kernels. This still doesn't seem to be upstream: http://wiki.xen.org/wiki/Xen_USB_Passthrough Correct, seems nobody is interested enough in the feature to do the necessary work. George is tracking it as an item for upstream 4.4 release[0] but AFAIK this doesn't imply that there is anybody working on it. I'm not sure ow worthwhile it is to track this as a Debian bug. Agreed, closing the bug. It doesn't make sense to track generic upstream enhancement bugs as Debian bugs. Cheers, Moritz---End Message---
Bug#561203: marked as done (threads and fork on machine with VIPT-WB cache)
Your message dated Wed, 14 Aug 2013 16:33:06 +0200 with message-id 20130814143305.gb9...@inutil.org and subject line Re: Bug#561203: threads and fork on machine with VIPT-WB cache has caused the Debian Bug report #561203, regarding threads and fork on machine with VIPT-WB cache 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.) -- 561203: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: kde4libs Version: 4:4.3.4-1 Severity: serious User: debian-h...@lists.debian.org Usertags: hppa kde4libs hangs during build on hppa, but the hang location varies. First attempt: [...] [ 48%] Generating org.kde.kded.xml cd kded /usr/bin/qdbuscpp2xml /build/buildd/kde4libs-4.3.4/kded/kdedadaptor.h /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kded/org.kde.kded.xml qdbuscpp2xml: exit code 0 from moc. Aborting QProcess: Destroyed while process is still running. make[3]: *** Deleting file `kded/org.kde.kded.xml' make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. make[2]: *** [kded/CMakeFiles/kdeinit_kded4.dir/all] Error 2 make[1]: *** [all] Terminated make: *** [debian/stamp-makefile-build] Terminated Build killed with signal 15 after 300 minutes of inactivity Second attempt: [...] make[3]: Entering directory `/build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu' cd kio /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kio/kio_automoc.cpp /build/buildd/kde4libs-4.3.4/kio /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kio /usr/bin/moc-qt4 /usr/bin/cmake Generating kdirwatch_p.moc make[3]: *** wait: No child processes. Stop. make[3]: *** Waiting for unfinished jobs make[3]: *** wait: No child processes. Stop. make[2]: *** [kio/CMakeFiles/kio_automoc.dir/all] Error 2 make[1]: *** [all] Terminated make: *** [debian/stamp-makefile-build] Terminated Build killed with signal 15 after 300 minutes of inactivity The third attempt is currently hung at: [...] make[3]: Entering directory `/build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu' cd kdecore /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore/kdecore_automoc.cpp /build/buildd/kde4libs-4.3.4/ kdecore /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore /usr/bin/moc-qt4 /usr/bin/cmake Generating klibrary.moc The build system looks wedged - it isn't consuming any cpu. The build-related processes are: buildd4199 766 0 02:53 ?00:00:00 /usr/bin/make -C obj-hppa-linux-gnu buildd4212 4199 0 02:53 ?00:00:00 /usr/bin/make -f CMakeFiles/Makefile2 all buildd5739 4212 0 02:55 ?00:00:00 /usr/bin/make -f kdecore/CMakeFiles/kdecore_automoc.dir/build.make kdecore/CMakeFiles/kdecore_automoc.dir/build buildd5740 5739 0 02:55 ?00:00:00 /bin/sh -c cd kdecore /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore/kdecore_automoc.cpp /build/buildd/kde4libs-4.3.4/kdecore /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore /usr/bin/moc-qt4 /usr/bin/cmake buildd5741 5740 0 02:55 ?00:00:00 /usr/bin/automoc4 /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore/kdecore_automoc.cpp /build/buildd/kde4libs-4.3.4/kdecore /build/buildd/kde4libs-4.3.4/obj-hppa-linux-gnu/kdecore /usr/bin/moc-qt4 /usr/bin/cmake buildd5755 5741 0 02:56 ?00:00:00 [cmake] defunct strace shows that automoc4 is stuck in a select call: Process 5741 attached - interrupt to quit _newselect(1024, [10], [], NULL, NULL ---End Message--- ---BeginMessage--- On Thu, Jun 10, 2010 at 11:27:16AM -0600, dann frazier wrote: On Thu, Jun 10, 2010 at 07:30:45PM +0300, Modestas Vainius wrote: Hello, On sekmadienis 06 Bir??elis 2010 04:01:23 Modestas Vainius wrote: On penktadienis 04 Bir??elis 2010 08:21:06 dann frazier wrote: My case and my analysis talked about UP kernel, and John David Anglin made a patch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561203#144 After that, the discussion went to SMP cases. It would be better to evaluate the patch again, and make sure it works for UP case and fix failures of buildd, then apply for Linux in Debian (only) for HPPA. I know that the patch is not that ideal because it touches architecture independent part of Linux, but it is worth for Linux in Debian (or Linux for the HPPA machine of buildd, at least). I'm happy to test the patch if necessary
Bug#719725: linux: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Package: linux Severity: whichlist Tags: l10n Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards, -- Fernando Ike http://www.fernandoike.com linux_pt_BR.po.gz Description: application/gzip
Bug#719627: linux-image-3.10-2-amd64: ten minute delay during boot
Hi Ben, On Tue, Aug 13, 2013 at 09:43:14PM +0200, Ben Hutchings wrote: Does this problem go away if you add 'blacklist=tpm_tis' to the kernel command line? Blacklisting tpm_tis makes no difference. The boot process still pauses at exactly the same point. The pause this time was only about five minutes long, but I was booting in single-user mode and had set boot-delay=100 to allow me to inspect the boot messages as they scrolled past, so not everything was identical. Thanks for your help. Matthew -- ** email: m.foul...@blueyonder.co.uk phone: (020) 8286 9910 ** -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130814212047.GA279@tern.local
Bug#625211: linux-image-2.6.32-5-amd64: Can no longer control backlight
Control: tag -1 moreinfo On Wed, 2013-08-14 at 13:15 +0200, Carlo Marchiori wrote: Package: src:linux Version: 3.9.8-1 Followup-For: Bug #625211 No, with the radeon driver it works, sorry for not having checked that. There is already a bug open against fglrx-driver, as brightness is concerned: 719536. So leave this bug alone. The problem remains that one need to specify the kernel attribute in the grub configuration file, it would be nice if that could be handled during installation. Thanks, Carlo. We don't install fglrx by default and therefore the installer doesn't need to work around its bugs. Ben. -- Ben Hutchings Any smoothly functioning technology is indistinguishable from a rigged demo. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#625211: linux-image-2.6.32-5-amd64: Can no longer control backlight
Processing control commands: tag -1 moreinfo Bug #625211 [src:linux] linux-image-2.6.32-5-amd64: Can no longer control backlight Ignoring request to alter tags of bug #625211 to the same tags previously set -- 625211: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625211 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b625211.137651649130785.transcr...@bugs.debian.org
Processed: severity of 719744 is important
Processing commands for cont...@bugs.debian.org: severity 719744 important Bug #719744 [src:linux] linux-image-3.10-2-amd64: fails to boot Severity set to 'important' from 'critical' thanks Stopping processing here. Please contact me if you need assistance. -- 719744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719744 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.137651653731015.transcr...@bugs.debian.org
Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service
On Tue, 2013-08-13 at 19:55 -0400, Alex Vanderpol wrote: I'll send the kernel log, though there's no record of the crash anywhere in the log and I can't really see anything in the log that would be useful... [...] You've sent /var/log/kern.log which I didn't expect would include any useful information. I meant that you should extract the kernel log from the crash dump. Unless you already tried it and this is what you meant when you said 'the dmesg dump is 2.9 GB' (it shouldn't be nearly that large...) Ben. -- Ben Hutchings Man invented language to satisfy his deep need to complain. - Lily Tomlin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1376519103.11676.82.ca...@deadeye.wl.decadent.org.uk
Bug#679978: Thinkpad T430 user, found workaround which works for me
Hello, Linux n00b here. Marcin's post led me to a solution: ...I have found that removing e1000e module before reboot/shutdown solves the problem, so perhaps it is a bug in the kernel... Cheers, Marcin Removing the e1000e module does indeed allow a normal reboot/shutdown. However, running all day without any ethernet module is a ridiculous proposition So, make an addition to a rc script which automatically rmmod's the e1000e module upon shutdown: Edit one of the scripts in /etc/rc0.d or /etc/rc6.d and insert a line which removes the kernel module. From my understanding, rc0.d scripts are responsible for halts/shutdowns, and rc6.d is responsible for reboots. But, these scripts seem to all be symlinked from /etc/init.d, so you could just edit one of the scripts in there instead and it would accomplish the same thing. Since the module we are removing is an ethernet driver, it seems fitting to choose '/etc/rc0.d/K70networking' (aka '/etc/init.d/networking'). And because Debian naturally calls the stop method of this script when shutting down or rebooting, we can simply insert our addition inside the method. Change this: stop) if init_is_upstart; then exit 0 fi check_network_file_systems check_network_swap log_action_begin_msg Deconfiguring network interfaces if ifdown -a --exclude=lo $verbose; then log_action_end_msg $? else log_action_end_msg $? fi ;; So that it reads: stop) if init_is_upstart; then exit 0 fi check_network_file_systems check_network_swap log_action_begin_msg Deconfiguring network interfaces if ifdown -a --exclude=lo $verbose; then log_action_end_msg $? else log_action_end_msg $? fi modprobe -r e1000e ;; Sorry if my terminology is incorrect, or if it's a bad/dangerous idea to edit these scripts. Like I said, I'm really new to Linux; I only learned what a kernel module is a couple days ago, and what an rc script is a few hours ago. So maybe think twice before taking my crap advice and potentially doing something dangerous. Hopefully this is of some help! Kind regards, Edward Peguillan III
Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers
So we had a meeting at DebConf about improving hardware support in stable, and seemed to come to a consensus that compat-drivers (formerly compat-wireless) could be added to stable. See https://lists.debian.org/debian-x/2013/08/msg00119.html. (I forgot about this ITP bug, otherwise I would have cc'd it on that message.) compat-drivers would have to build binary debs for all kernel flavours and udebs for installer images. This can be done with the help of the linux-support-3.2.0-4 and kernel-wedge packages. What is the status of your packaging work? What do you think of this plan, and can I work with you on it? Ben. -- Ben Hutchings Man invented language to satisfy his deep need to complain. - Lily Tomlin signature.asc Description: This is a digitally signed message part
Re: Bug#696038: ITP: compat-wireless-3.5.4 -- backported linux wireless drivers
What I have now is a set of instructions for building packages with modass[1] which I've used for compat-wireless and peak's canbus driver. I would like to (at some point) learn to use dkms, especially if it'll make my job easier. I also welcome someone [a mentor] to work with on this as my packaging skills are pretty hacky. --Jayen [1] I've been meaning to file a bug report to improve the HOWTO.Devel but haven't gotten around to it. On Thu, Aug 15, 2013 at 9:01 AM, Ben Hutchings b...@decadent.org.uk wrote: So we had a meeting at DebConf about improving hardware support in stable, and seemed to come to a consensus that compat-drivers (formerly compat-wireless) could be added to stable. See https://lists.debian.org/debian-x/2013/08/msg00119.html. (I forgot about this ITP bug, otherwise I would have cc'd it on that message.) compat-drivers would have to build binary debs for all kernel flavours and udebs for installer images. This can be done with the help of the linux-support-3.2.0-4 and kernel-wedge packages. What is the status of your packaging work? What do you think of this plan, and can I work with you on it? Ben. -- Ben Hutchings Man invented language to satisfy his deep need to complain. - Lily Tomlin -- Marathon Targets Pty Ltd Marathon, like the run from Marathon to Athens Targets, like the things at which one shoots for practice Sydney, Australia http://www.marathon-targets.com/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cachadqtzun9ltq2y48eysuub+tlhihenrsaehpop-+8exy_...@mail.gmail.com
Bug#719277: linux-image-3.11-rc4-amd64: Kernel crashes when running Folding@Home as a system service
Ah, I didn't know exactly what you meant. Unfortunately I don't know how to extract anything from the dump files I got with kdump-tools. There are two files in the crash dump directory I made and pointed kdump-tools to, dmesg.201308111839 (which is the 2.9 GB file) and dump.201308111839 (the 1.5 GB file). I cannot seem to find anything useful with Google about what to do with these files. I'm pretty sure the Debian-supplied kernel is configured to work with kdump-tools (at least, the default configuration state in the sources was configured correctly for such, and I did get a kernel dump), but I do not have a debug kernel image available, which I'm assuming would probably make this easier. I'm going to look into trying to set things up better so I can hopefully get a crash dump I can actually do something with, I found a site that has some useful information and maybe I can get something that's actually useful, though if you know how to work with those files I mentioned above, I'll gladly take that information as well. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/520c4205.1040...@gmail.com
Bug#714974: [PATCH] jfs: avoid misuse of cookie value of 2
On Wed, 14 Aug 2013 at 22:54, Dave Kleikamp wrote: It looks like the problem is that jfs was using a cookie value of 2 for a real directory entry, where NFSv4 expect 2 to represent ... This patch has so far only been lightly tested. Hm, a first compile of 3.11-rc5 errors out with: CC [M] fs/jfs/jfs_dtree.o /usr/local/src/linux-git/fs/jfs/jfs_dtree.c: In function ‘add_index’: /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:13: error: invalid storage class for function ‘free_index’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:493:1: warning: ISO C90 forbids mixed declarations and code [-Wdeclaration-after-statement] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:521:13: error: invalid storage class for function ‘modify_index’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:546:12: error: invalid storage class for function ‘read_index’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:927:12: error: invalid storage class for function ‘dtSplitUp’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:1327:12: error: invalid storage class for function ‘dtSplitPage’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:1639:12: error: invalid storage class for function ‘dtExtendPage’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:1872:12: error: invalid storage class for function ‘dtSplitRoot’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2234:12: error: invalid storage class for function ‘dtDeleteUp’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2744:12: error: invalid storage class for function ‘dtRelink’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2915:13: error: invalid storage class for function ‘add_missing_indices’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:2982:34: error: invalid storage class for function ‘next_jfs_dirent’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c::12: error: invalid storage class for function ‘dtReadFirst’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3405:12: error: invalid storage class for function ‘dtReadNext’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3581:12: error: invalid storage class for function ‘dtCompare’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3657:12: error: invalid storage class for function ‘ciCompare’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3765:12: error: invalid storage class for function ‘ciGetLeafPrefixKey’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3832:13: error: invalid storage class for function ‘dtGetKey’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:3896:13: error: invalid storage class for function ‘dtInsertEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4054:13: error: invalid storage class for function ‘dtMoveEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4255:13: error: invalid storage class for function ‘dtDeleteEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4350:13: error: invalid storage class for function ‘dtTruncateEntry’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4430:13: error: invalid storage class for function ‘dtLinelockFreelist’ /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:4565:1: error: expected declaration or statement at end of input /usr/local/src/linux-git/fs/jfs/jfs_dtree.c: At top level: /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:152:12: warning: ‘dtSplitUp’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:155:12: warning: ‘dtSplitPage’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:158:12: warning: ‘dtExtendPage’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:161:12: warning: ‘dtSplitRoot’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:164:12: warning: ‘dtDeleteUp’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:167:12: warning: ‘dtRelink’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:169:12: warning: ‘dtReadFirst’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:171:12: warning: ‘dtReadNext’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:174:12: warning: ‘dtCompare’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:176:12: warning: ‘ciCompare’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:179:13: warning: ‘dtGetKey’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:182:12: warning: ‘ciGetLeafPrefixKey’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:185:13: warning: ‘dtInsertEntry’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:188:13: warning: ‘dtMoveEntry’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:192:13: warning: ‘dtDeleteEntry’ used but never defined [enabled by default] /usr/local/src/linux-git/fs/jfs/jfs_dtree.c:194:13: warning:
