Bug#1035587: linux: broken AHCI controller on MIPS Loongson 3 (regression from 5.10.162-1)
Hi, On Mon, Oct 9, 2023 at 09:08:31 +0100, Jiaxun Yang wrote: > > > 在2023年10月8日十月 上午11:11，Aurelien Jarno写道： > > On 2023-07-19 16:28, Jiaxun Yang wrote: > >> > >> > >> 在 2023/7/8 18:11, Aurelien Jarno 写道: > >> [...] > >> > Any news about that? We need to be able to run the latest stable kernel > >> > on the build daemon. > >> > >> Hi all, > >> > >> After receiving more reports on that patch I think we shoud workaround it > >> in > >> Kernel. > >> > >> I had posted a patch to kernel, kernel bug tracker [1]. > >> > >> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217680 > > > > Any news about that? I haven't spotted any fix for this in Linus' tree > > nor in next. > > Still waiting for a response from PCI folks. > Will resend the patch later. > Any news on this? It's been several months... Thanks, Julien
Bug#1036543: linux: WARNING at drivers/crypto/ccp/sev-dev.c:168 __sev_do_cmd_locked+0x31b/0x350 [ccp]
Source: linux Version: 5.10.179-1 Severity: normal Tags: upstream Control: found -1 5.10.178-3 User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team X-Debbugs-Cc: debian-ad...@lists.debian.org, jcris...@debian.org Hi, We're seeing a new WARNING in kernel logs on several Lenovo servers since the latest bullseye point release, when the ccp module gets loaded: > ccp :44:00.1: no command queues available > ccp :44:00.1: sev enabled > ccp :44:00.1: psp enabled > [ cut here ] > WARNING: CPU: 87 PID: 1534 at drivers/crypto/ccp/sev-dev.c:168 > __sev_do_cmd_locked+0x31b/0x350 [ccp] > Modules linked in: ccp(+) rng_core kvm irqbypass ip6t_REJECT nf_reject_ipv6 > ip6table_filter ip6_tables nfnetlink_log nfnetlink xt_hashlimit ipt_REJECT > nf_reject_ipv4 xt_NFLOG xt_multiport xt_tcpudp xt_state xt_conntrack > nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter loop tun sch_fq > tcp_bbr usbhid uas usb_storage sr_mod cdrom joydev hid_generic hid cdc_ether > usbnet mii drbd drm lru_cache fuse configfs efivarfs ip_tables x_tables > autofs4 ext4 crc16 mbcache jbd2 raid10 raid1 raid0 multipath linear dm_mod > raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor sd_mod > raid6_pq libcrc32c crc32c_generic crc32_pclmul crc32c_intel md_mod ahci > libahci xhci_pci xhci_hcd libata tg3 nvme usbcore nvme_core libphy t10_pi > bnxt_en scsi_mod crc_t10dif crct10dif_generic usb_common i2c_piix4 ptp > crct10dif_pclmul crct10dif_common pps_core > CPU: 87 PID: 1534 Comm: systemd-modules Not tainted 5.10.0-23-amd64 #1 Debian > 5.10.179-1 > Hardware name: Lenovo ThinkSystem SR635 -[7Y99CTO1WW]-/-[7Y99CTO1WW]-, BIOS > CFE126V 06/23/2021 > RIP: 0010:__sev_do_cmd_locked+0x31b/0x350 [ccp] > Code: 31 ed e9 a1 fd ff ff 48 8b 33 44 89 e9 48 c7 c2 f8 fb c4 c0 48 c7 c7 a0 > 2c c5 c0 e8 8f d9 28 de b8 fb ff ff ff e9 3b fe ff ff <0f> 0b b8 ea ff ff ff > e9 34 fe ff ff 44 89 fd e9 f4 fe ff ff b8 f0 > RSP: 0018:b75f82c0fcf8 EFLAGS: 00010246 > RAX: RBX: 90986ef00e98 RCX: > RDX: 0004d908 RSI: 09b2 RDI: b76002c0fd6c > RBP: c0c59000 R08: R09: b75f82c0fc90 > R10: 9098c49bb000 R11: a02153e0 R12: b75f82c0fd6c > R13: 0004 R14: b75f82c0fd68 R15: > FS: 7f3466446900() GS:90f60e5c() knlGS: > CS: 0010 DS: ES: CR0: 80050033 > CR2: 557be22d1c98 CR3: 000131af8000 CR4: 00350ee0 > Call Trace: > ? kobject_uevent_env+0x11f/0x6a0 > ? kfree+0xba/0x490 > ? 0xc0c59000 > sev_get_api_version+0x4a/0xa0 [ccp] > sev_pci_init+0x46/0x300 [ccp] > ? bus_add_driver+0x1a8/0x200 > ? 0xc0c59000 > sp_mod_init+0x18/0x1000 [ccp] > do_one_initcall+0x44/0x1e0 > ? do_init_module+0x23/0x250 > ? kmem_cache_alloc_trace+0xf5/0x200 > do_init_module+0x4c/0x250 > __do_sys_finit_module+0xb1/0x120 > do_syscall_64+0x33/0x80 > entry_SYSCALL_64_after_hwframe+0x61/0xc6 > RIP: 0033:0x7f3466d15f29 > Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 > 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 > 01 c3 48 8b 0d 37 8f 0d 00 f7 d8 64 89 01 48 > RSP: 002b:7ffcbd5be308 EFLAGS: 0246 ORIG_RAX: 0139 > RAX: ffda RBX: 557be22ca9c0 RCX: 7f3466d15f29 > RDX: RSI: 7f3466e09e2d RDI: 0008 > RBP: 0002 R08: R09: 557be22ca9c0 > R10: 0008 R11: 0246 R12: 7f3466e09e2d > R13: R14: 557be22ca970 R15: 557be22ca9c0 > ---[ end trace e089f2660ccf25dd ]--- > ccp :44:00.1: SEV: failed to get status. Error: 0x0 Ben forwarded the report to https://lore.kernel.org/stable/2023051729-jumbo-uncolored-05c1@gregkh/T/#mf89c978a24a0297b279e87de5fa19741f2c63980 after I mentioned it on IRC. Cheers, Julien
Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify
Control: tag -1 upstream fixed-upstream patch On Tue, Apr 4, 2023 at 22:03:28 +0200, Diederik de Haas wrote: > On Tuesday, 4 April 2023 13:11:16 CEST Julien Cristau wrote: > > On Mon, Apr 3, 2023 at 15:16:42 +0200, Diederik de Haas wrote: > > > On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote: > > > > > > On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote: > > > > > Not sure why patchwork still shows v2 of the patch as v4 is available > > > > > here: > > > > > https://lore.kernel.org/all/20230308154244.722337-1-hdego...@redhat.com/ > > > > > > > > I'll give the patch series you linked in the other reply a go now. > > > > > > FTR: 2 out of the 3 patches have landed in 6.1.22 > > > > Thanks for letting me know. I've built 6.1.22 from upstream and it > > doesn't seem to crash. > > That's awesome :-) Let's hope it stays that way now ;-) > > You may have seen it on IRC already, but could you test a > Debian 6.1.20-1 kernel with (only) those patches applied? > These are the URLs: > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y&id=1c5abcb13491da8c049f20462189c12c753ba978 > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.1.y&id=1e8525f37871741a52370627633962f8bdcab15a > > If you need help with that, feel free to ask :-) > > If we know that fixes the issue too, then we have the option of going for > a 6.1.20-2 release with just those 2 patches (and what's already in -2 now). > Testing this now: linux (6.1.20-1a~test) UNRELEASED; urgency=medium * Testing patches ../0001-usb-ucsi-Fix-NULL-pointer-deref-in- ucsi_connector_ch.patch ../0001-usb-ucsi_acpi-Increase-the-command- completion-timeou.patch -- Julien Cristau Wed, 05 Apr 2023 11:09:30 + and it doesn't seem to crash, as far as I can tell. Cheers, Julien
Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify
On Mon, Apr 3, 2023 at 15:16:42 +0200, Diederik de Haas wrote: > On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote: > On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote: > > > Not sure why patchwork still shows v2 of the patch as v4 is available > > > here: > > > https://lore.kernel.org/all/20230308154244.722337-1-hdego...@redhat.com/ > > I'll give the patch series you linked in the other reply a go now. > > FTR: 2 out of the 3 patches have landed in 6.1.22 Thanks for letting me know. I've built 6.1.22 from upstream and it doesn't seem to crash. Cheers, Julien
Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify
On Thu, Mar 16, 2023 at 20:39:51 +0100, Diederik de Haas wrote: > On Thursday, 16 March 2023 18:11:27 CET Julien Cristau wrote: > > > I rebooted on 6.1.15-1 last night and things are still looking good so > > > I'll call this fixed. Thanks. > > > > Spoke too soon: > > > [84564.498495] BUG: kernel NULL pointer dereference, address: > > > 0398 [84564.498502] #PF: supervisor write access in kernel > > > mode > > > [84564.498504] #PF: error_code(0x0002) - not-present page > > > [84564.498506] PGD 4c9444067 P4D 4c9444067 PUD 0 > > > [84564.498510] Oops: 0002 [#1] PREEMPT SMP NOPTI > > > [84564.498512] CPU: 0 PID: 140651 Comm: kworker/0:0 Not tainted > > > 6.1.0-6-amd64 #1 Debian 6.1.15-1 [84564.498516] Hardware name: LENOVO > > > 20XW00ABUS/20XW00ABUS, BIOS N32ET82W (1.58 ) 12/05/2022 [84564.498518] > > > Workqueue: kacpi_notify acpi_os_execute_deferred > > Bummer. > > Since 6.1.8 I found the following 2 commits in drivers/usb/typec/ucsi: > > 3d7f77e55da3455c8844b651e37779c90e201f48 titled > "usb: ucsi: Ensure connector delayed work items are flushed" > > fdd11d7136fd070b3a74d6d8799d9eac28a57fc5 titled > "usb: typec: ucsi: Don't attempt to resume the ports before they exist" > > Especially the first one looks 'promising'. > Can you make a patch which reverts that commit and use 'test-patches' from > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html > to build a kernel and test that? Reverting "usb: ucsi: Ensure connector delayed work items are flushed" doesn't fix the crash, pretty much instant upon unplugging my monitor. I'll give the patch series you linked in the other reply a go now. Cheers, Julien > [ 34.956155] usb 3-6: USB disconnect, device number 4 > [ 34.956164] usb 3-6.1: USB disconnect, device number 6 > [ 34.956167] usb 3-6.1.4: USB disconnect, device number 8 > [ 34.995650] usb 2-3: USB disconnect, device number 2 > [ 34.995654] usb 2-3.1: USB disconnect, device number 3 > [ 34.995655] usb 2-3.1.2: USB disconnect, device number 4 > [ 34.995778] cdc_ncm 2-3.1.2:2.0 enxc84bd6b0b3e0: unregister 'cdc_ncm' > usb-:00:0d.0-3.1.2, CDC NCM (NO ZLP) > [ 35.449317] usb 3-6.5: USB disconnect, device number 7 > [ 35.843033] BUG: kernel NULL pointer dereference, address: 0388 > [ 35.843040] #PF: supervisor write access in kernel mode > [ 35.843041] #PF: error_code(0x0002) - not-present page > [ 35.843043] PGD 0 P4D 0 > [ 35.843046] Oops: 0002 [#1] PREEMPT SMP NOPTI > [ 35.843048] CPU: 0 PID: 2704 Comm: kworker/0:3 Tainted: GE > 6.1.0-7-amd64 #1 Debian 6.1.20-1a~test > [ 35.843051] Hardware name: LENOVO 20XW00ABUS/20XW00ABUS, BIOS N32ET82W > (1.58 ) 12/05/2022 > [ 35.843052] Workqueue: kacpi_notify acpi_os_execute_deferred > [ 35.843058] RIP: 0010:queue_work_on+0x15/0x40 > [ 35.843063] Code: ff ff ff e9 9a fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 > 66 90 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 48 > 0f ba 2a 00 73 15 31 c9 80 e7 02 74 06 fb 0f 1f 44 00 00 89 > [ 35.843065] RSP: 0018:b4a50467be38 EFLAGS: 00010002 > [ 35.843067] RAX: 0202 RBX: 0202 RCX: > > [ 35.843069] RDX: 0388 RSI: 8a0640051000 RDI: > 2000 > [ 35.843070] RBP: 0004 R08: 8a06fa490a38 R09: > 8a06fa490a20 > [ 35.843071] R10: 000f R11: b4a50467bc20 R12: > 8a0d7f639b00 > [ 35.843072] R13: R14: 8a06c642a9c0 R15: > 8a06bc057918 > [ 35.843074] FS: () GS:8a0d7f60() > knlGS: > [ 35.843075] CS: 0010 DS: ES: CR0: 80050033 > [ 35.843076] CR2: 0388 CR3: 00039d410004 CR4: > 00770ef0 > [ 35.843078] PKRU: 5554 > [ 35.843079] Call Trace: > [ 35.843082] > [ 35.843087] ucsi_acpi_notify+0xa8/0xc0 [ucsi_acpi] > [ 35.843092] acpi_ev_notify_dispatch+0x42/0x60 > [ 35.843096] acpi_os_execute_deferred+0x13/0x20 > [ 35.843099] process_one_work+0x1c4/0x380 > [ 35.843102] worker_thread+0x4d/0x380 > [ 35.843105] ? _raw_spin_lock_irqsave+0x23/0x50 > [ 35.843109] ? rescuer_thread+0x3a0/0x3a0 > [ 35.843111] kthread+0xe6/0x110 > [ 35.843114] ? kthread_complete_and_exit+0x20/0x20 > [ 35.843116] ret_from_fork+0x1f/0x30 > [ 35.843121] > [ 35.843122] Modules linked in: xt_conntrack(E) nft_chain_nat(E) > xt_MASQUERADE(E) nf_nat(E) nf_conntrack_netlink(E) nf_conntrack(E) > nf_defrag_ipv6(E) nf_defrag_ipv4(E) xfrm_user(E) xfrm_algo(
Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify
Control: reopen -1 Control: found it 6.1.15-1 On Thu, Mar 16, 2023 at 11:17:19 +0100, Julien Cristau wrote: > Version: 6.1.15-1 > > On Tue, Mar 14, 2023 at 15:29:08 +0100, Diederik de Haas wrote: > > > On Tuesday, 14 March 2023 14:55:04 CET Julien Cristau wrote: > > > Package: src:linux > > > Version: 6.1.12-1 > > > > > > After upgrading to 6.1.12-1 my laptop started hanging regularly (3 times > > > in a few hours). Downgraded to 6.1.8-1 and I've not seen this for a > > > week, so this looks like a recent regression. > > > > Testing now has 6.1.15-1, can you test it with that? > > There's another update in the pipeline (at least to 6.1.19) and when it > > becomes available, it would be useful if you could test that as well. > > I rebooted on 6.1.15-1 last night and things are still looking good so > I'll call this fixed. Thanks. > Spoke too soon: > [84564.498495] BUG: kernel NULL pointer dereference, address: 0398 > [84564.498502] #PF: supervisor write access in kernel mode > [84564.498504] #PF: error_code(0x0002) - not-present page > [84564.498506] PGD 4c9444067 P4D 4c9444067 PUD 0 > [84564.498510] Oops: 0002 [#1] PREEMPT SMP NOPTI > [84564.498512] CPU: 0 PID: 140651 Comm: kworker/0:0 Not tainted 6.1.0-6-amd64 > #1 Debian 6.1.15-1 > [84564.498516] Hardware name: LENOVO 20XW00ABUS/20XW00ABUS, BIOS N32ET82W > (1.58 ) 12/05/2022 > [84564.498518] Workqueue: kacpi_notify acpi_os_execute_deferred > [84564.498525] RIP: 0010:queue_work_on+0x15/0x40 > [84564.498529] Code: ff ff ff e9 9a fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 > 66 90 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 48 > 0f ba 2a 00 73 15 31 c9 80 e7 02 74 06 fb 0f 1f 44 00 00 89 > [84564.498531] RSP: 0018:b15ea96c3e38 EFLAGS: 00010002 > [84564.498533] RAX: 0202 RBX: 0202 RCX: > > [84564.498535] RDX: 0398 RSI: 93ea00051000 RDI: > 2000 > [84564.498536] RBP: 0004 R08: 93ea0383b510 R09: > > [84564.498537] R10: R11: 005f R12: > 93f13f639b00 > [84564.498538] R13: R14: 93ebffadba80 R15: > 93ebdd74a998 > [84564.498539] FS: () GS:93f13f60() > knlGS: > [84564.498540] CS: 0010 DS: ES: CR0: 80050033 > [84564.498541] CR2: 0398 CR3: 000503886004 CR4: > 00770ef0 > [84564.498543] PKRU: 5554 > [84564.498544] Call Trace: > [84564.498546] > [84564.498552] ucsi_acpi_notify+0xa8/0xc0 [ucsi_acpi] > [84564.498557] acpi_ev_notify_dispatch+0x42/0x5a > [84564.498560] acpi_os_execute_deferred+0x13/0x20 > [84564.498563] process_one_work+0x1c4/0x380 > [84564.498565] worker_thread+0x4d/0x380 > [84564.498568] ? _raw_spin_lock_irqsave+0x23/0x50 > [84564.498572] ? rescuer_thread+0x3a0/0x3a0 > [84564.498574] kthread+0xe6/0x110 > [84564.498577] ? kthread_complete_and_exit+0x20/0x20 > [84564.498580] ret_from_fork+0x1f/0x30 > [84564.498584] > [84564.498585] Modules linked in: tun xt_conntrack nft_chain_nat > xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 > nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c > nfnetlink br_netfilter bridge stp llc ctr ccm rfcomm cmac algif_hash > algif_skcipher af_alg snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr > overlay ipmi_devintf bnep ipmi_msghandler binfmt_misc nls_ascii nls_cp437 > vfat fat snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common > snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek > snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl > snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation > soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof > iwlmvm snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core > snd_soc_acpi_intel_match x86_pkg_temp_thermal intel_powerclamp snd_soc_acpi > snd_soc_core coretemp snd_compress mac80211 soundwire_bus btusb mei_hdcp > btrtl kvm_intel btbcm > [84564.498630] btintel intel_rapl_msr snd_hda_intel btmtk pmt_telemetry > pmt_class bluetooth libarc4 snd_intel_dspcfg kvm snd_intel_sdw_acpi iwlwifi > snd_hda_codec irqbypass uvcvideo snd_hda_core videobuf2_vmalloc rapl > processor_thermal_device_pci_legacy videobuf2_memops jitterentropy_rng > snd_hwdep processor_thermal_device intel_cstate cfg80211 videobuf2_v4l2 > snd_pcm processor_thermal_rfim thinkpad_acpi videobuf2_common drbg > processor_thermal_mbox nvram processor_thermal_rapl ansi_cprng videodev > platform_profile snd_timer ecdh_generic iTCO_wdt ledtrig
Bug#1032948: linux-image-6.1.0-5-amd64: oops in ucsi_acpi_notify
Package: src:linux Version: 6.1.12-1 Severity: important X-Debbugs-Cc: jcris...@debian.org Hi, After upgrading to 6.1.12-1 my laptop started hanging regularly (3 times in a few hours). Downgraded to 6.1.8-1 and I've not seen this for a week, so this looks like a recent regression. Not all the hangs left traces in logs, but I got at least one oops: > [ 485.537559] usb 3-6: USB disconnect, device number 4 > [ 485.537569] usb 3-6.1: USB disconnect, device number 6 > [ 485.537574] usb 3-6.1.4: USB disconnect, device number 8 > [ 485.574521] usb 2-3: USB disconnect, device number 2 > [ 485.574529] usb 2-3.1: USB disconnect, device number 3 > [ 485.574531] usb 2-3.1.2: USB disconnect, device number 4 > [ 485.574730] cdc_ncm 2-3.1.2:2.0 enxc84bd6b0b3e0: unregister 'cdc_ncm' > usb-:00:0d.0-3.1.2, CDC NCM (NO ZLP) > [ 486.051935] usb 3-6.5: USB disconnect, device number 7 > [ 486.413430] BUG: kernel NULL pointer dereference, address: 0398 > [ 486.413436] #PF: supervisor write access in kernel mode > [ 486.413438] #PF: error_code(0x0002) - not-present page > [ 486.413440] PGD 0 P4D 0 > [ 486.413442] Oops: 0002 [#1] PREEMPT SMP NOPTI > [ 486.413444] CPU: 0 PID: 129 Comm: kworker/0:2 Not tainted 6.1.0-5-amd64 #1 > Debian 6.1.12-1 > [ 486.413447] Hardware name: LENOVO 20XW00ABUS/20XW00ABUS, BIOS N32ET82W > (1.58 ) 12/05/2022 > [ 486.413448] Workqueue: kacpi_notify acpi_os_execute_deferred > [ 486.413455] RIP: 0010:queue_work_on+0x15/0x40 > [ 486.413460] Code: ff ff ff e9 9a fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 > 66 90 0f 1f 44 00 00 53 9c 58 0f 1f 40 00 48 89 c3 fa 0f 1f 44 00 00 48 > 0f ba 2a 00 73 15 31 c9 80 e7 02 74 06 fb 0f 1f 44 00 00 89 > [ 486.413462] RSP: 0018:af8a80d53e38 EFLAGS: 00010002 > [ 486.413464] RAX: 0202 RBX: 0202 RCX: > > [ 486.413465] RDX: 0398 RSI: 8a2800051000 RDI: > 2000 > [ 486.413466] RBP: 0004 R08: 8a2815581ea0 R09: > > [ 486.413468] R10: R11: 005f R12: > 8a2f3f639b00 > [ 486.413469] R13: R14: 8a28836f3d80 R15: > 8a2860a03798 > [ 486.413470] FS: () GS:8a2f3f60() > knlGS: > [ 486.413471] CS: 0010 DS: ES: CR0: 80050033 > [ 486.413472] CR2: 0398 CR3: 1b010002 CR4: > 00770ef0 > [ 486.413474] PKRU: 5554 > [ 486.413475] Call Trace: > [ 486.413477] > [ 486.413483] ucsi_acpi_notify+0xa8/0xc0 [ucsi_acpi] > [ 486.413488] acpi_ev_notify_dispatch+0x42/0x5a > [ 486.413492] acpi_os_execute_deferred+0x13/0x20 > [ 486.413494] process_one_work+0x1c4/0x380 > [ 486.413497] worker_thread+0x4d/0x380 > [ 486.413500] ? _raw_spin_lock_irqsave+0x23/0x50 > [ 486.413503] ? rescuer_thread+0x3a0/0x3a0 > [ 486.413505] kthread+0xe6/0x110 > [ 486.413508] ? kthread_complete_and_exit+0x20/0x20 > [ 486.413510] ret_from_fork+0x1f/0x30 > [ 486.413515] > [ 486.413515] Modules linked in: xt_conntrack nft_chain_nat xt_MASQUERADE > nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 > xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables libcrc32c nfnetlink > br_netfilter bridge stp llc ctr ccm rfcomm cmac algif_hash algif_skcipher > af_alg snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr overlay > ipmi_devintf bnep ipmi_msghandler binfmt_misc nls_ascii nls_cp437 vfat fat > snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common > snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek > snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl > snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation btusb > soundwire_cadence btrtl snd_sof_intel_hda btbcm snd_sof_pci btintel > snd_sof_xtensa_dsp btmtk snd_sof x86_pkg_temp_thermal intel_powerclamp > snd_sof_utils bluetooth snd_soc_hdac_hda snd_hda_ext_core > snd_soc_acpi_intel_match iwlmvm snd_soc_acpi snd_soc_core coretemp > snd_compress soundwire_bus mac80211 > [ 486.413562] snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi > snd_hda_codec kvm_intel snd_hda_core pmt_telemetry libarc4 mei_hdcp > intel_rapl_msr jitterentropy_rng pmt_class kvm iwlwifi uvcvideo snd_hwdep > irqbypass snd_pcm videobuf2_vmalloc drbg thinkpad_acpi iTCO_wdt > videobuf2_memops videobuf2_v4l2 rapl processor_thermal_device_pci_legacy > nvram ansi_cprng snd_timer intel_pmc_bxt platform_profile videobuf2_common > intel_cstate processor_thermal_device ecdh_generic ledtrig_audio cfg80211 > videodev ucsi_acpi processor_thermal_rfim pcspkr iTCO_vendor_support > processor_thermal_mbox typec_ucsi mei_me processor_thermal_rapl intel_uncore > intel_rapl_common wmi_bmof watchdog roles snd mei mc ecc intel_vsec > intel_soc_dts_iosf typec joydev soundcore ac cdc_mbim rfkill int3403_thermal > cdc_wdm soc_button_array int340x_thermal_zone intel_hid sparse_keymap > int3400_thermal acpi
Bug#975038: linux: please disable legacy DRM options
Source: linux Version: 5.9.6-1 Severity: normal Tags: security X-Debbugs-Cc: Daniel Vetter Says Daniel: 21:55 < danvet> jcristau, maybe disable CONFIG_DRM_LEGACY and CONFIG_NOUVEAU_LEGACY_CTX_SUPPORT while at it 21:55 < danvet> saves you at least one CVE As I understand it, we haven't shipped drivers relying on those options in a few releases. Cheers, Julien
Bug#939873: qla2xxx .. Async-gnlist failed
On Mon, Sep 9, 2019 at 17:51:02 +0100, Ben Hutchings wrote: > On Mon, 9 Sep 2019 16:29:07 + Peter Palfrader > wrote: > > Package: src:linux > > Version: 4.19.67-2 > > Severity: important > > > > The buster kernel, as well as the backports kernel > > (linux-image-5.2.0-0.bpo.2-amd64 5.2.9-2~bpo10+1) fail to boot > > sibelius.debian.org, which has some storage attached to it via, > > presumably, FC. > > > > The kernel keeps printing > > > > | qla2xxx [...]-...: Async-gpdb failed - hdl=.. ... > [...] > > So this controller is: > > 06:01.0 Fibre Channel [0c04]: QLogic Corp. ISP2312-based 2Gb Fibre Channel to > PCI-X HBA [1077:2312] (rev 02) > Subsystem: QLogic Corp. ISP2312-based 2Gb Fibre Channel to PCI-X HBA > [1077:010a] > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr+ > Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- > SERR- Latency: 128 (16000ns min), Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 26 > NUMA node: 0 > Region 0: I/O ports at c800 [size=256] > Region 1: Memory at fe8ff000 (64-bit, non-prefetchable) [size=4K] > Expansion ROM at fe8c [disabled] [size=128K] > Capabilities: > Kernel driver in use: qla2xxx > Kernel modules: qla2xxx > These look similar, though they don't point at a resolution: https://bugzilla.kernel.org/show_bug.cgi?id=199887 https://bugzilla.opensuse.org/show_bug.cgi?id=1121319 Seemingly introduced in 4.11. Cheers, Julien
Bug#929359: linux: instability on arm64 MP30-AR1 servers
Control: found -1 4.19.28-2 On Wed, May 22, 2019 at 11:58:15 +0200, Julien Cristau wrote: > Source: linux > Version: 4.9.168-1 > Severity: important > X-Debbugs-Cc: debian-...@lists.debian.org, debian-ad...@lists.debian.org > User: debian-ad...@lists.debian.org > Usertags: needed-by-DSA-Team > > Hi, > > ever since the 9.9 point release conova-node01.debian.org and > conova-node02.debian.org have been unstable. They run for an hour or > three, and then things go bad. Rebooting back to 4.9.144-3.1 makes them > stable again. > Still happening after upgrading to the stretch-backports kernel: [87461.376828] Bad mode in FIQ handler detected on CPU0, code 0x5600 -- SVC (AArch64) [87461.376834] Internal error: Oops - bad mode: 0 [#1] SMP [87461.389907] Modules linked in: openvswitch nsh nf_nat_ipv6 nf_nat_ipv4 nf_conncount nf_nat binfmt_misc nls_ascii nls_cp437 vfat fat dm_mod ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 nfnetlink_log nfnetlink xt_NFLOG xt_tcpudp xt_hashlimit xt_multiport xt_conntrack efi_pstore nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter ast ttm drm_kms_helper drm xgene_hwmon i2c_algo_bit xgene_edac xgene_dma joydev evdev chaoskey sg xgene_rng mailbox_xgene_slimpro rng_core ipmi_ssif ipmi_devintf ipmi_msghandler efivars tun drbd lru_cache efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx hid_generic usbhid hid xor raid6_pq crc32c_generic libcrc32c raid0 multipath linear raid1 [87461.460161] md_mod sd_mod ahci_xgene libahci_platform libahci xhci_plat_hcd xgene_enet libata xhci_hcd i2c_xgene_slimpro marvell usbcore phy_xgene scsi_mod sdhci_of_arasan mdio_xgene sdhci_pltfm of_mdio cqhci fixed_phy sdhci libphy usb_common gpio_xgene_sb [87461.482839] CPU: 0 PID: 1557 Comm: ovsdb-server Not tainted 4.19.0-0.bpo.4-arm64 #1 Debian 4.19.28-2~bpo9+1 [87461.492528] Hardware name: GIGABYTE R120-P31/MP30-AR1, BIOS D7b 08/26/2016 [87461.499367] pstate: (nzcv daif -PAN -UAO) [87461.504132] pc : 897e2910 [87461.507427] lr : 897e2918 [87461.510722] sp : e32d4440 [87461.514016] x29: e32d4440 x28: 015a [87461.519301] x27: 89928c20 x26: [87461.524586] x25: e32d44f8 x24: e32d4528 [87461.529870] x23: 015a x22: 0090 [87461.535154] x21: d73fd286 x20: 0001 [87461.540439] x19: d743b560 x18: 0024 [87461.545723] x17: 897d7fc0 x16: 899238e0 [87461.551007] x15: 089e8439a422 x14: 0001 [87461.556291] x13: 5ce6a4fa x12: 0018 [87461.561576] x11: 26295eb7 x10: 000155a6 [87461.566860] x9 : d741f300 x8 : [87461.572144] x7 : 0010 x6 : [87461.577429] x5 : e32d42b8 x4 : d73f0410 [87461.582713] x3 : d743b568 x2 : d7403a20 [87461.587997] x1 : 0001 x0 : d743b560 [87461.593283] Process ovsdb-server (pid: 1557, stack limit = 0x03b97138) [87461.600468] ---[ end trace 2ab4838ec3817e8e ]--- [87461.606271] Bad mode in FIQ handler detected on CPU0, code 0x5600 -- SVC (AArch64) [87482.616230] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [87482.622133] rcu: 0-...0: (1 GPs behind) idle=9a6/1/0x4000 softirq=1153372/1153372 fqs=2456 [87482.631564] rcu: (detected by 4, t=5255 jiffies, g=6202645, q=14630) [87482.637973] Task dump for CPU 0: [87482.641182] ovsdb-serverR running task0 1557 1556 0x0002 [87482.648197] Call trace: [87482.650636] __switch_to+0x8c/0xd0 [87482.654018](null) Cheers, Julien
Bug#929431: linux: openvswitch complains of over-mtu packets
Source: linux Version: 4.19.28-2~bpo9+1 Severity: important X-Debbugs-Cc: debian-ad...@lists.debian.org User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team Hi, after upgrading conova-node01.debian.org to the stretch-backports kernel to see if #929359 was reproducible, it started dropping packets. This was not happening prior to the upgrade. Running "ip link set dev eth0 mtu 1504" seems to make things work. May 22 13:32:49 conova-node01/conova-node01 kernel: IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready May 22 13:32:49 conova-node01/conova-node01 kernel: IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready May 22 13:32:49 conova-node01/conova-node01 kernel: openvswitch: Open vSwitch switching datapath May 22 13:32:49 conova-node01/conova-node01 kernel: xgene-enet 1f21.ethernet eth0: Link is Down May 22 13:32:49 conova-node01/conova-node01 kernel: device ovs-system entered promiscuous mode May 22 13:32:49 conova-node01/conova-node01 kernel: netlink: 'ovs-vswitchd': attribute type 5 has an invalid length. May 22 13:32:49 conova-node01/conova-node01 kernel: netlink: 'ovs-vswitchd': attribute type 5 has an invalid length. May 22 13:32:49 conova-node01/conova-node01 kernel: device eth0 entered promiscuous mode May 22 13:32:49 conova-node01/conova-node01 kernel: xgene-enet 1f210030.ethernet eth1: Link is Down May 22 13:32:49 conova-node01/conova-node01 kernel: netlink: 'ovs-vswitchd': attribute type 5 has an invalid length. May 22 13:32:49 conova-node01/conova-node01 kernel: device br-inet entered promiscuous mode May 22 13:32:50 conova-node01/conova-node01 kernel: xgene-enet 1f61.ethernet eth2: Link is Up - 10Gbps May 22 13:32:50 conova-node01/conova-node01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready May 22 13:32:51 conova-node01/conova-node01 kernel: xgene-enet 1f21.ethernet eth0: Link is Up - 1Gbps/Full - flow control off May 22 13:32:52 conova-node01/conova-node01 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready May 22 13:32:52 conova-node01/conova-node01 kernel: xgene-enet 1f210030.ethernet eth1: Link is Up - 1Gbps/Full - flow control off May 22 13:32:59 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:32:59 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:32:59 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:32:59 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:00 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:00 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:00 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:00 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:00 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:00 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:07 conova-node01/conova-node01 kernel: net_ratelimit: 5 callbacks suppressed May 22 13:33:07 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:08 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:15 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:17 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:30 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:34 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:37 conova-node01/conova-node01 kernel: br-inet: dropped over-mtu packet: 1504 > 1500 May 22 13:33:43 conova-node01/conova-node01 kernel: net_ratelimit: 31 callbacks suppressed The network is configured as per bug #929359: /etc/network/interfaces: # The loo
Bug#929366: linux-image-4.19.0-5-octeon: usercopy: Kernel memory overwrite attempt detected (in systemd-timedated)
Source: linux Version: 4.19.37-3 Severity: important X-Debbugs-Cc: debian-ad...@lists.debian.org, debian-m...@lists.debian.org, syst...@packages.debian.org User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team Hi, from mips-sil-01.debian.org's syslog: May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 dbus-daemon[542]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.12565' (uid=115 pid=561 comm="timedatectl show ") May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 systemd[1]: Starting Time & Date Service... May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: usercopy: Kernel memory overwrite attempt detected to SLUB object 'buffer_head' (offset 8, size 88)! May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Kernel bug detected[#1]: May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: CPU: 0 PID: 563 Comm: (imedated) Not tainted 4.19.0-5-octeon #1 Debian 4.19.37-3 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $ 0 : 82a78f48 0064 417135fb8ce5871c May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $ 4 : 417135fb8ce5871c 80002406b678 800024074080 835b May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $ 8 : 0100 80020e9a4018 286f73657420 835b May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $12 : 05f5e100 835b 83590b58 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $16 : c2400038 0058 c2400090 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $20 : 82a2f630 c240 55d29698 c2400038 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $24 : 82dcc9a0 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: $28 : 8001f9094000 8001f9097d30 82b71874 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Hi: 003e7cf8 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Lo: 72b020c49bf017bb May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: epc : 82b71874 usercopy_abort+0x94/0xa0 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: ra: 82b71874 usercopy_abort+0x94/0xa0 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Status: 10109ce3 KX SX UX KERNEL EXL IE May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Cause : 00800024 (ExcCode 09) May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: PrId : 000d9602 (Cavium Octeon III) May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Modules linked in: mmc_block binfmt_misc ip6t_REJECT nf_reject_ipv6 nf_conntrack_ftp xt_CT nfnetlink_log nft_counter xt_hashlimit ipt_REJECT nf_reject_ipv4 xt_NFLOG xt_multiport xt_tcpudp xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c nft_compat nf_tables nfnetlink sg octeon_mmc mmc_core 8250_of leds_gpio i2c_dev octeon_rng rng_core ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb dm_mod ahci_platform libahci_platform libahci ahci_octeon May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Process (imedated) (pid: 563, threadinfo=53386908, task=8966de24, tls=771b84a0) May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: Stack : 0058 006080c0 82b50d60 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 77d57098 82b716c4 8000240bfb00 8001f9097df8 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 0058 0001 800187ea86d0 82f1f7e4 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 832b 800187ea86c0 77d5a7c8 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 77d3 77d57098 May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 7f99ca14 82a30784 0ef08000 417135fb8ce5871c May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 000b55d29698 000b55de72f0 55d29698 417135fb8ce5871c May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 55dea4c0 55de72f0 77d5a7c8 77d5a73c May 22 11:57:53 mips-sil-01/mips-sil-01/:::86.59.118.146 kernel: 77d3 000
Bug#929359: linux: instability on arm64 MP30-AR1 servers
Source: linux Version: 4.9.168-1 Severity: important X-Debbugs-Cc: debian-...@lists.debian.org, debian-ad...@lists.debian.org User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team Hi, ever since the 9.9 point release conova-node01.debian.org and conova-node02.debian.org have been unstable. They run for an hour or three, and then things go bad. Rebooting back to 4.9.144-3.1 makes them stable again. Latest example: May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: PingAck did not arrive in time. May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: peer( Secondary -> Unknown ) conn( Connected -> NetworkFailure ) pdsk( UpToDate -> DUnknown ) May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: new current UUID 3EA2D1FA6B3ACD47:0BEBDA613EA56FD7:D5BF70E0AA6560C5:D5BE70E0AA6560C5 May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: ack_receiver terminated May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: Terminating drbd_a_resource May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: Connection closed May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: conn( NetworkFailure -> Unconnected ) May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: receiver terminated May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: Restarting receiver thread May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: receiver (re)started May 22 04:17:37 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: conn( Unconnected -> WFConnection ) May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: Handshake successful: Agreed network protocol version 101 May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: Feature flags enabled on protocol level: 0x7 TRIM THIN_RESYNC WRITE_SAME. May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: Peer authenticated using 16 bytes HMAC May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: conn( WFConnection -> WFReportParams ) May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: drbd resource3: Starting ack_recv thread (from drbd_r_resource [8449]) May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: drbd_sync_handshake: May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: self 3EA2D1FA6B3ACD47:0BEBDA613EA56FD7:D5BF70E0AA6560C5:D5BE70E0AA6560C5 bits:4 flags:0 May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: peer 0BEBDA613EA56FD6::D5BF70E0AA6560C4:D5BE70E0AA6560C5 bits:0 flags:0 May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: uuid_compare()=1 by rule 70 May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: peer( Unknown -> Secondary ) conn( WFReportParams -> WFBitMapS ) pdsk( DUnknown -> Consistent ) May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: send bitmap stats [Bytes(packets)]: plain 0(0), RLE 28(1), total 28; compression: 100.0% May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: receive bitmap stats [Bytes(packets)]: plain 0(0), RLE 28(1), total 28; compression: 100.0% May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: helper command: /bin/true before-resync-source minor-3 May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: helper command: /bin/true before-resync-source minor-3 exit code 0 (0x0) May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: conn( WFBitMapS -> SyncSource ) pdsk( Consistent -> Inconsistent ) May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: Began resync as SyncSource (will sync 16 KB [4 bits set]). May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: updated sync UUID 3EA2D1FA6B3ACD47:0BECDA613EA56FD7:0BEBDA613EA56FD7:D5BF70E0AA6560C5 May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: Resync done (total 1 sec; paused 0 sec; 16 K/sec) May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: updated UUIDs 3EA2D1FA6B3ACD47::0BECDA613EA56FD7:0BEBDA613EA56FD7 May 22 04:17:38 conova-node01/conova-node01/:::217.196.149.227 kernel: block drbd3: conn( SyncSource -> Connected ) pdsk( Inconsistent -> UpToDate ) May 22 04:17:4
Re: Status and open questions for debian-installer with backports support
On 08/13/2018 01:57 AM, Steve McIntyre wrote: > On Thu, Aug 02, 2018 at 10:56:59AM +0200, Cyril Brulebois wrote: >> => Question: should we restrict architectures we build images for? > > Probably. I'm only thinking x86, arm64 and maybe armhf. Wait for > people to ask for others and add on a case-by-case basis. > I'd even suggest s/x86/amd64/ New 32-bit x86 hardware shouldn't be a huge use case nowadays. Cheers, Julien
Bug#878216: Bug relating linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb and hyper-v gen2 vm
Hi, On Wed, Oct 11, 2017 at 08:45:14 +, Cristiano Casella wrote: > Upgrading our vm with Debian 8 (also just installed) to last version of > linux-image package (linux-image-3.16.0-4-amd64_3.16.48-1_amd64.deb) the > virtual machines can't boot anymore. > > > I attached to this email the two kind of error that we can get in the console. > > > Looking at the changelog > (https://tracker.debian.org/media/packages/l/linux/changelog-3.16.48-1) I > suspect that this changes could be involved in this bug: > > > - [x86] scsi: storvsc: use tagged SRB requests if supported by the device > - [x86] scsi: storvsc: Fix a bug in the handling of SRB status flags > - [x86] scsi: storvsc: properly handle SRB_ERROR when sense message is > present > - [x86] scsi: storvsc: properly set residual data length on errors > > We can provide you all test environments needed or proceede with your support > for a kernel bisect to find the specific error. > If you could bisect between 3.16.43 and 3.16.48, that would be most helpful. Thanks, Julien
Re: Secure boot signing infrastructure - feedback request
On Mon, Oct 9, 2017 at 17:38:56 +0100, Steve McIntyre wrote: > On Mon, Oct 09, 2017 at 02:01:15PM +0100, Ben Hutchings wrote: > >It also makes all these packages unreproducible, which is a policy > >violation. > > Surely *anything* with a signature is going to be unreproducible > directly, by definition. To check for reproducibility, you'll need to > strip the signatures. Or are you claiming something else? > No, the previous scheme allowed reproducibility (in the "dpkg-buildpackage from the source package results in the exact same .deb files" sense), since the signatures were shipped as part of a source package. Attaching fixed signatures to fixed binaries is reproducible. Cheers, Julien
Re: Kernel ABI bump in stretch
On Sun, Sep 3, 2017 at 01:45:48 +0100, Ben Hutchings wrote: > There are several changes in the 4.9-stable branch which I don't think > we can take without changes to the kernel module ABI that will affect > out-of-tree modules. This would mean an ABI bump, changing the names > of all linux-image and linux-headers packages. > > Since we install meta-packages (such as linux-image-amd64) by default, > an 'apt full-upgrade' should result in installing the appropriate new > packages. However, we have been able to avoid such an ABI bump in the > past 3 releases (so far) and this might come as a surprise to users. I > think the point release announcement would need to draw attention to > this. > > If this is totally unacceptable, I can revert the breaking changes, but > some of them fix use-after-free bugs that probably have security > impact. > > Please let us know as soon as possible whether an ABI bump is OK, so > that we can prepare the update in time for the next point release. > This should be fine. We don't ship any pre-built modules in stretch outside the linux source package, so the only other thing we need to do is update d-i at that point release. Cheers, Julien signature.asc Description: PGP signature
Re: Bug#860749: mesa-va-drivers: Critical error in library 'mesa' with i965 video driver
Control: severity -1 important Control: tags -1 - lfs Control: reassign -1 src:linux 4.9.18-1 Control: tags -1 upstream On 05/09/2017 03:27 PM, Andreas Boll wrote: > On Tue, May 09, 2017 at 03:00:34PM +0200, Andreas Boll wrote: >> The following looks like an issue with the kernel graphics driver: > > Looks like a known upstream kernel issue: > https://bugs.freedesktop.org/show_bug.cgi?id=93782 > > Please try the workaround described in comment 40 [1] first, by adding > > video=SVIDEO-1:d > > to the kernel command line. > > Thanks, > Andreas > > [1] https://bugs.freedesktop.org/show_bug.cgi?id=93782#c40 > >> >>> [ 21.472066] [drm:drm_atomic_helper_commit_cleanup_done [drm_kms_helper]] >>> *ERROR* [CRTC:26:pipe A] flip_done timed out >>> [ 21.576017] [ cut here ] >>> [ 21.576062] WARNING: CPU: 0 PID: 100 at >>> /build/linux-9r9Ph5/linux-4.9.18/drivers/gpu/drm/drm_irq.c:1254 >>> drm_wait_one_vblank+0x197/0x1a0 [drm] >>> [ 21.576200] vblank wait timed out on crtc 0 >>> [ 21.576201] Modules linked in: uvcvideo videobuf2_vmalloc arc4 >>> videobuf2_memops iwl3945 videobuf2_v4l2 iwlegacy videobuf2_core >>> snd_hda_codec_si3054 mac80211 videodev media cfg80211 iTCO_wdt >>> iTCO_vendor_support joydev evdev r592 memstick snd_hda_codec_realtek >>> snd_hda_codec_generic rfkill snd_hda_intel pcspkr snd_hda_codec coretemp >>> serio_raw snd_hda_core snd_hwdep lpc_ich mfd_core snd_pcm snd_timer sg i915 >>> shpchp drm_kms_helper ene_ir rc_core drm i2c_algo_bit battery ac snd >>> soundcore video wmi button acpi_cpufreq tpm_tis tpm_tis_core tpm parport_pc >>> ppdev lp parport ip_tables x_tables autofs4 ext4 crc16 jbd2 crc32c_generic >>> fscrypto ecb glue_helper lrw gf128mul ablk_helper cryptd aes_x86_64 mbcache >>> sr_mod cdrom sd_mod ata_generic psmouse i2c_i801 i2c_smbus ata_piix libata >>> scsi_mod tg3 firewire_ohci sdhci_pci >>> [ 21.576257] sdhci mmc_core firewire_core crc_itu_t ptp pps_core libphy >>> ehci_pci uhci_hcd ehci_hcd usbcore usb_common >>> [ 21.576269] CPU: 0 PID: 100 Comm: kworker/u4:3 Not tainted 4.9.0-2-amd64 >>> #1 Debian 4.9.18-1 >>> [ 21.576270] Hardware name: - N/A >>>/IFT01 , BIOS 1.18 06/18/2008 >>> [ 21.576276] Workqueue: events_unbound async_run_entry_fn >>> [ 21.576278] b4928714 a5e440917a60 >>> >>> [ 21.576281] b4676e9e 9898383c a5e440917ab8 >>> >>> [ 21.576283] 0101 98983a6edc08 9898383f8800 >>> b4676f1f >>> [ 21.576286] Call Trace: >>> [ 21.576293] [] ? dump_stack+0x5c/0x78 >>> [ 21.576296] [] ? __warn+0xbe/0xe0 >>> [ 21.576298] [] ? warn_slowpath_fmt+0x5f/0x80 >>> [ 21.576301] [] ? finish_wait+0x3c/0x70 >>> [ 21.576315] [] ? drm_wait_one_vblank+0x197/0x1a0 [drm] >>> [ 21.576317] [] ? prepare_to_wait_event+0xf0/0xf0 >>> [ 21.576389] [] ? >>> intel_get_load_detect_pipe+0x624/0x640 [i915] >>> [ 21.576425] [] ? intel_tv_detect+0x155/0x550 [i915] >>> [ 21.576440] [] ? >>> drm_property_replace_global_blob+0xd8/0x120 [drm] >>> [ 21.576458] [] ? >>> drm_helper_probe_single_connector_modes+0x3f6/0x4e0 [drm_kms_helper] >>> [ 21.576465] [] ? >>> drm_fb_helper_initial_config+0xac/0x440 [drm_kms_helper] >>> [ 21.576500] [] ? intel_fbdev_initial_config+0x14/0x30 >>> [i915] >>> [ 21.576502] [] ? async_run_entry_fn+0x34/0x140 >>> [ 21.576504] [] ? process_one_work+0x184/0x410 >>> [ 21.576506] [] ? worker_thread+0x4d/0x480 >>> [ 21.576508] [] ? process_one_work+0x410/0x410 >>> [ 21.576510] [] ? kthread+0xce/0xf0 >>> [ 21.576512] [] ? __switch_to+0x2c1/0x6c0 >>> [ 21.576514] [] ? kthread_park+0x60/0x60 >>> [ 21.576517] [] ? ret_from_fork+0x25/0x30 >>> [ 21.576519] ---[ end trace 872a41b26fe6df4f ]--- >
Re: Stable update request: kernel changes to fix PIE with large stack
On Sat, Apr 22, 2017 at 21:42:30 +0100, Ben Hutchings wrote: > On Sat, 2017-04-22 at 20:07 +, Niels Thykier wrote: > [...] > > Hi Ben, > > > > Could you please file a pu bug for this? I fear that otherwise, it > > might be overlooked for the next time the SRMs review the outstanding > > stable update requests. > > I already stopped waiting and went ahead and made these changes. Sorry for the lack of reply from SRM here. And thanks for your work. Cheers, Julien
Bug#860424: linux: hp-health fails to start with PAT error
On Sun, Apr 16, 2017 at 18:06:22 +0200, Julien Cristau wrote: > On our HP boxes running stretch or a jessie-backports kernel, the > hp-health monitoring tools no longer want to start. > One suggestion on https://community.hpe.com/t5/Insight-Control-for-Linux/hp-health-hpasmlited-Debian-segfault/td-p/6921253 is to boot with nopat as a workaround. Cheers, Julien
Bug#860424: linux: hp-health fails to start with PAT error
Source: linux Version: 4.9.18-1 Severity: important Tags: upstream X-Debbugs-Cc: debian-ad...@lists.debian.org User: debian-ad...@lists.debian.org Usertag: needed-by-DSA-Team On our HP boxes running stretch or a jessie-backports kernel, the hp-health monitoring tools no longer want to start. daemon.log says: Apr 16 16:01:55 s_local@ubc-enc2bl10 hpasmlited[12054]: StartIpmiRmqThread Apr 16 16:01:55 s_local@ubc-enc2bl10 hpasmlited[12054]: StartIpmiRmqThread: Thread created (TID 759764736) Apr 16 16:01:55 s_local@ubc-enc2bl10 hpasmlited[12054]: IpmiRmqThread: Entry Apr 16 16:01:55 s_local@ubc-enc2bl10 hpasmlited[12054]: (SendRecv_CHIF) CpqCiSend: error=4, "Bad name for the target connection object.". Apr 16 16:01:55 s_local@ubc-enc2bl10 hpasmlited[12054]: (SendRecv_CHIF) CpqCiSend: error=4, "Bad name for the target connection object.". Apr 16 16:01:55 s_local@ubc-enc2bl10 hpasmlited[12054]: ehpsmb_parse_SMBIOS: SMBIOSInitTable was not successful. Apr 16 16:01:55 s_local@ubc-enc2bl10 hpasmlited[12054]: Not able to initialize BIOS interfaces! Apr 16 16:02:00 s_local@ubc-enc2bl10 hpasmlited[12054]: StopIpmiRmqThread Apr 16 16:02:00 s_local@ubc-enc2bl10 hpasmlited[12054]: StopIpmiRmqThread: Thread stopped and dmesg: [ 1000.917235] x86/PAT: hpasmlited:12054 map pfn expected mapping type uncached-minus for [mem 0x788d-0x788d1fff], got write-back It looks like this was reported last month at https://www.spinics.net/lists/kernel/msg2460830.html but I'm not seeing a resolution there. Cheers, Julien
Re: why 4.9.2-2 didn't migrate to testing?
On 01/24/2017 03:20 PM, Roger Shimizu wrote: > Hi there, > > As title, may I know the reason why 4.9.2-2 didn't migrate to testing? > Who says it didn't? 4.9.2-2 *is* in testing. Cheers, Julien
Re: Security improvements for stable kernels
On Sun, Dec 25, 2016 at 11:15:12 +, Ben Hutchings wrote: > I would like to make a couple of improvements to security features in > stable: > > 1. Add the option to disable unprivileged use of perf_event_open(). >This rwequires a small out-of-tree patch that we've carried in >unstable for some time. In unstable this is also enabled by >default, but I don't propose to do that in stable. > > 2. Enable seccomp (system call filtering) for ARM architectures >(armel, armhf, arm64). This is an architecture-dependent feature >that is enabled on all other release architectures. For arm64 this >requires a backport; for the others it's just a config change. >This expands the size of armel images by about 1K. > > Are these suitable for a stable update? > No objection from me. I assume you'll make sure the arm64 seccomp backport is tested early enough (assuming that work hasn't already been done) so we can still disable it if needed for this point release? Cheers, Julien
Bug#839616: linux: add support for chaoskey
Source: linux Version: 3.16.36-1+deb8u1 Severity: important Tags: patch Control: fixed -1 4.1.1-1~exp1 User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team Hi, the attached patch adds the chaoskey driver (http://altusmetrum.org/ChaosKey/). I've smoke tested it in qemu (with usb passthrough). This should include all patches touching drivers/usb/misc/chaoskey.c since its introduction, with the only diff from the upstream patches being context in Kconfig; there's an extra patch to deal with the absence of 0f734e6e768b4b66737b3d3e13f1769a12ecff86 in 3.16. Applies on top of 3.16.36-1+deb8u1, because the tip of the jessie branch doesn't seem to build. Cheers, Julien >From e9060d88141e2978d4acf31716a0502534fdf7b5 Mon Sep 17 00:00:00 2001 From: Julien Cristau Date: Sun, 2 Oct 2016 18:32:04 +0200 Subject: [PATCH] Add chaoskey driver, backported from 4.8. --- debian/changelog | 7 + debian/config/config | 1 + .../chaoskey/USB-chaoskey-read-offset-bug.patch| 31 + .../chaoskey/chaoskey-3.16-no-hwrng-quality.patch | 28 + ...key-Add-support-for-Araneus-Alea-I-USB-RN.patch | 64 +++ ...key-Fix-URB-warning-due-to-timeout-on-Ale.patch | 105 ...river-for-Altus-Metrum-ChaosKey-device-v2.patch | 627 + .../usb-Fix-warnings-in-chaoskey-driver.patch | 57 ++ ...misc-chaoskey-Cleanup-probe-failure-paths.patch | 103 ...aoskey-introduce-an-URB-for-asynchronous-.patch | 187 ++ ...b-misc-fix-chaoskey-build-needs-HW_RANDOM.patch | 33 ++ debian/patches/series | 11 + 12 files changed, 1254 insertions(+) create mode 100644 debian/patches/features/all/chaoskey/USB-chaoskey-read-offset-bug.patch create mode 100644 debian/patches/features/all/chaoskey/chaoskey-3.16-no-hwrng-quality.patch create mode 100644 debian/patches/features/all/chaoskey/hwrng-chaoskey-Add-support-for-Araneus-Alea-I-USB-RN.patch create mode 100644 debian/patches/features/all/chaoskey/hwrng-chaoskey-Fix-URB-warning-due-to-timeout-on-Ale.patch create mode 100644 debian/patches/features/all/chaoskey/usb-Add-driver-for-Altus-Metrum-ChaosKey-device-v2.patch create mode 100644 debian/patches/features/all/chaoskey/usb-Fix-warnings-in-chaoskey-driver.patch create mode 100644 debian/patches/features/all/chaoskey/usb-misc-chaoskey-Cleanup-probe-failure-paths.patch create mode 100644 debian/patches/features/all/chaoskey/usb-misc-chaoskey-introduce-an-URB-for-asynchronous-.patch create mode 100644 debian/patches/features/all/chaoskey/usb-misc-fix-chaoskey-build-needs-HW_RANDOM.patch diff --git a/debian/changelog b/debian/changelog index dcf2adc..5cdf3b2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +linux (3.16.36-2) UNRELEASED; urgency=medium + + [ Julien Cristau ] + * Add chaoskey driver, backported from 4.8. + + -- Aurelien Jarno Tue, 09 Aug 2016 22:05:53 +0200 + linux (3.16.36-1+deb8u1) jessie-security; urgency=high [ Ben Hutchings ] diff --git a/debian/config/config b/debian/config/config index 0b70520..cc363ae 100644 --- a/debian/config/config +++ b/debian/config/config @@ -4107,6 +4107,7 @@ CONFIG_USB_EHSET_TEST_FIXTURE=m CONFIG_USB_ISIGHTFW=m CONFIG_USB_YUREX=m # CONFIG_USB_HSIC_USB3503 is not set +CONFIG_USB_CHAOSKEY=m ## ## file: drivers/usb/misc/sisusbvga/Kconfig diff --git a/debian/patches/features/all/chaoskey/USB-chaoskey-read-offset-bug.patch b/debian/patches/features/all/chaoskey/USB-chaoskey-read-offset-bug.patch new file mode 100644 index 000..9ff8e32 --- /dev/null +++ b/debian/patches/features/all/chaoskey/USB-chaoskey-read-offset-bug.patch @@ -0,0 +1,31 @@ +From 1d5c47f555c5ae050fad22e4a99f88856cae5d05 Mon Sep 17 00:00:00 2001 +From: Alexander Inyukhin +Date: Sat, 26 Sep 2015 15:24:21 +0300 +Subject: [PATCH] USB: chaoskey read offset bug + +Rng reads in chaoskey driver could return the same data under +the certain conditions. + +Signed-off-by: Alexander Inyukhin +Cc: stable +Signed-off-by: Greg Kroah-Hartman +--- + drivers/usb/misc/chaoskey.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/usb/misc/chaoskey.c b/drivers/usb/misc/chaoskey.c +index 3ad5d19..23c7948 100644 +--- a/drivers/usb/misc/chaoskey.c b/drivers/usb/misc/chaoskey.c +@@ -472,7 +472,7 @@ static int chaoskey_rng_read(struct hwrng *rng, void *data, + if (this_time > max) + this_time = max; + +- memcpy(data, dev->buf, this_time); ++ memcpy(data, dev->buf + dev->used, this_time); + + dev->used += this_time; + +-- +2.9.3 + diff --git a/debian/patches/features/all/chaoskey/chaoskey-3.16-no-hwrng-quality.patch b/debian/patches/features/all/chaoskey/chaoskey-3.16-no-hwrng-quality.patch new file mode 100644 index 000..b20fdb0 --- /dev/null +++ b/debian/patches/features/all/chaoskey/chaoskey-3.16-no-hwrng-quality.patch @@ -0,0 +1,28 @@ +From: Julien Cristau +Date: Sun, 02 Oct 2016 17:52
Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid
On Sun, Sep 25, 2016 at 17:06:56 +0200, Michael Biebl wrote: > On Thu, 22 Sep 2016 07:51:36 +0200 Stefan Fritsch wrote: > > Package: src:linux > > Version: 4.7.4-2 > > Severity: grave > > Justification: renders package unusable > > > > When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my > > filesystems fails to mount with: > > > > ext4_iget:4476: inode #8: comm mount: checksum invalid > > > > A fsck does not find any errors, though, and the mount problem persists. > > After rebooting with 4.6, it works. > > > > It seems this is a known problem: > > > > http://www.spinics.net/lists/linux-fsdevel/msg101888.html > > > > > > Not sure about the severity, but I thought I should prevent it from > > migrating to testing until you have looked at it. > > > > > > Does this affect 4.7.2-1 as well, i.e. the current version in testing? The current version in testing is 4.6.4-1. Cheers, Julien
Bug#837978: RM: linux-image-4.6.0-1-versatile-signed -- NBS; no longer built
Package: ftp.debian.org Severity: normal linux-signed no longer builds on armel. Cheers, Julien
Bug#837645: linux-image-3.16.0-4-amd64: iwlwifi module fails to load
On Tue, Sep 13, 2016 at 11:23:55 +0200, Tobias Bengfort wrote: > Package: src:linux > Version: 3.16.36-1+deb8u1 > Severity: important > > Dear Maintainer, > > I am no longer use wifi because the iwlwifi module does not load: > > $ sudo modprobe iwlwifi > modprobe: ERROR: could not insert 'iwlwifi': Unknown symbol in module, or > unknown parameter (see dmesg) > > $ sudo dmesg > ... > [ 888.091279] cfg80211: Unknown symbol wireless_nlevent_flush (err 0) > > This happend after installing version 3.16.36-1+deb8u1 of the kernel > (see https://www.debian.org/security/2016/dsa-3659). > Did you reboot after upgrading your kernel? (You need to do that.) cheers, Julien
Re: Bug#833267: xserver-xorg-input-all: psmouse takes 3min to enable symaptics touchpad
Control: reassign -1 linux On Tue, Aug 2, 2016 at 12:31:35 +0200, Christian Gogolin wrote: > Package: xserver-xorg-input-all > Version: 1:7.7+16 > Severity: important > > Dear Maintainer, > >* What led up to the situation? > > after a recent upgrade including in particular > > [UPGRADE] linux-image-4.6.0-1-amd64:amd64 4.6.3-1 -> 4.6.4-1 > [UPGRADE] xserver-common:amd64 2:1.18.3-1 -> 2:1.18.4-1 > [UPGRADE] xserver-xorg:amd64 1:7.7+15 -> 1:7.7+16 > [UPGRADE] xserver-xorg-core:amd64 2:1.18.3-1 -> 2:1.18.4-1 > [UPGRADE] xserver-xorg-input-all:amd64 1:7.7+15 -> 1:7.7+16 > > the synaptics touchpad takes around 3 minutes to activate itself after > startup, > as can be seen in syslog: > > $ cat /var/log/messages | grep psmouse > Aug 2 12:17:39 x1yoga kernel: [2.374250] psmouse serio1: synaptics: > queried max coordinates: x [..5678], y [..4754] > Aug 2 12:17:39 x1yoga kernel: [2.409507] psmouse serio1: synaptics: > queried min coordinates: x [1262..], y [1098..] > Aug 2 12:17:39 x1yoga kernel: [2.476319] psmouse serio1: synaptics: > Touchpad model: 1, fw: 8.2, id: 0x1e2b1, caps: 0xf002a3/0x940300/0x12e800/0x0, > board id: 3144, fw id: 2059155 > Aug 2 12:17:39 x1yoga kernel: [2.476344] psmouse serio1: synaptics: > serio: > Synaptics pass-through port at isa0060/serio1/input0 > Aug 2 12:17:39 x1yoga kernel: [3.159420] psmouse serio2: trackpoint: IBM > TrackPoint firmware: 0x0e, buttons: 3/3 > Aug 2 12:17:39 x1yoga kernel: [ 20.543125] psmouse serio2: Failed to > deactivate mouse on synaptics-pt/serio0 > Aug 2 12:17:39 x1yoga kernel: [ 21.011213] psmouse serio2: Failed to enable > mouse on synaptics-pt/serio0 > Aug 2 12:20:38 x1yoga kernel: [ 201.277555] psmouse serio2: trackpoint: IBM > TrackPoint firmware: 0x0e, buttons: 3/3 > > The touchpad remains completely unresponsive until the last of the above > messages appears in syslog and then works normally. > > During this time I can still use the xserver normally by tapping on the > touchscreen of my Thinkpad X1 Yoga. > That looks like a kernel issue to me. Cheers, Julien
Bug#833231: initramfs-tools: during initramfs: "/init: line 1: logsave: not found" when e2fsprogs is not installed
On Tue, Aug 2, 2016 at 00:14:14 -0400, Daniel Kahn Gillmor wrote: > Source: initramfs-tools > Version: 0.125 > Severity: normal > Control: affects -1 e2fsprogs > > I have a minimal system with only btrfs filesystems, and e2fsprogs is > not needed on it. It would be nice to be able to uninstall it. > e2fsprogs is Essential: yes. Removing things from Essential is probably nontrivial. I'd say at most this is "wishlist" territory. Cheers, Julien
Bug#829711: X freezes (regression)
On Tue, Jul 5, 2016 at 16:21:44 +0200, Stéphane Glondu wrote: > Package: src:linux > Version: 4.6.2-2 > Severity: important > > Dear Maintainer, > > Starting with linux-image-4.6.0-1-amd64, my system crashes approx. 8 > minutes after boot. The symptoms are: the X server freezes; after a > few seconds, the mouse pointer resumes moving but the rest of the > graphical interface is frozen; then, when I do Ctrl-Alt-F1, the screen > switches to (all) black, then quickly switches to a gray like in the > GDM prompt; then, when I do Ctrl-Alt-Suppr, the screen switches to a > console where I can see the call trace which is at the end of the > attached log. > > This happens reproducibly with linux-image-4.6.0-1-amd64 versions > 4.6.1-1 and 4.6.2-2. It does not happen with linux-image-4.5.0-2-amd64 > 4.5.5-1 (the kernel I'm running right now). > Please forward this upstream, there are some guidelines at https://01.org/linuxgraphics/documentation/how-report-bugs Cheers, Julien
Re: kernel 4.6-1~exp1 built for armel seems failed
On Tue, May 24, 2016 at 19:00:39 +0900, Roger Shimizu wrote: > Dear Ben, > > kernel 4.6-1~exp1 for experimental has been compiling for ARCH=armel > for nearly a week [0]. > Please kindly check what happened and restart the build if necessary. > Thank you! > > [0] https://buildd.debian.org/status/package.php?p=linux&suite=experimental > antheil has a broken fan, buildd is disabled; linux given back. Cheers, Julien
Upcoming stable point release (8.5)
Hi, The next point release for "jessie" (8.5) is scheduled for Saturday, June 4th. Processing of new uploads into jessie-proposed-updates will be frozen during the preceding weekend. Cheers, Julien
Upcoming oldstable point release (7.11)
Hi, The next (and last) point release for "wheezy" (7.11) is scheduled for Saturday, June 4th. Processing of new uploads into wheezy-proposed-updates will be frozen during the preceding weekend. Cheers, Julien
Re: Bug#823355: xserver-xorg-video-intel: Black screen on TTY's ctrl-alt-F* and black screen when going back to X
Control: reassign -1 src:linux 4.5.1-1 On Tue, May 3, 2016 at 23:22:19 +0200, raphael wrote: > Package: xserver-xorg-video-intel > Version: 2:2.99.917+git20160325-1 > Severity: important > > Hi, > > Since last upgrade, I noticed that switching to TTY's with ^-alt-F* gives a > black screen, and trying to go back to the X session gives also a black > screen. > (I have a dual card though no bumblebee installed, only intel driver is used). > Thanks > Submitter confirmed downgrading the kernel to 4.4 fixes it; reassigning. > Raphael > > -- Package-specific info: > X server symlink status: > > lrwxrwxrwx 1 root root 13 Mar 4 2015 /etc/X11/X -> /usr/bin/Xorg > -rwxr-xr-x 1 root root 274 Apr 5 09:05 /usr/bin/Xorg > > VGA-compatible devices on PCI bus: > -- > 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor > Integrated Graphics Controller [8086:0046] (rev 02) > 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT216M [GeForce > GT 330M] [10de:0a2b] (rev a2) > > /etc/X11/xorg.conf does not exist. > > Contents of /etc/X11/xorg.conf.d: > - > total 4 > -rw-r--r-- 1 root root 1247 Apr 30 22:55 10-synaptics.conf > > /etc/modprobe.d contains no KMS configuration files. > > Kernel version (/proc/version): > --- > Linux version 4.5.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version > 5.3.1 20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14) > > Xorg X server log files on system: > -- > -rw-r--r-- 1 root root 29589 May 3 21:35 /var/log/Xorg.0.log > > Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): > - > [ 9.013] > X.Org X Server 1.18.3 > Release Date: 2016-04-04 > [ 9.013] X Protocol Version 11, Revision 0 > [ 9.013] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian > [ 9.013] Current Operating System: Linux palikao 4.5.0-1-amd64 #1 SMP > Debian 4.5.1-1 (2016-04-14) x86_64 > [ 9.013] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.5.0-1-amd64 > root=UUID=33ecf725-aba1-4d6b-922a-bd2e0fdac97d ro quiet splash acpi_osi=Linux > acpi_backlight=vendor init=/lib/sysvinit/init init=/lib/sysvinit/init > init=/sbin/openrc init=/lib/sysvinit/init init=/lib/sysvinit/init > init=/lib/sysvinit/init init=/lib/sysvinit/init init=/lib/sysvinit/init > init=/lib/sysvinit/init init=/lib/sysvinit/init init=/lib/sysvinit/init > init=/lib/sysvinit/init > [ 9.013] Build Date: 05 April 2016 07:00:43AM > [ 9.013] xorg-server 2:1.18.3-1 (http://www.debian.org/support) > [ 9.013] Current version of pixman: 0.33.6 > [ 9.013] Before reporting problems, check http://wiki.x.org > to make sure that you have the latest version. > [ 9.013] Markers: (--) probed, (**) from config file, (==) default > setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > [ 9.013] (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 3 21:35:44 > 2016 > [ 9.038] (==) Using config directory: "/etc/X11/xorg.conf.d" > [ 9.039] (==) Using system config directory "/usr/share/X11/xorg.conf.d" > [ 9.045] (==) No Layout section. Using the first Screen section. > [ 9.045] (==) No screen section available. Using defaults. > [ 9.045] (**) |-->Screen "Default Screen Section" (0) > [ 9.045] (**) | |-->Monitor "" > [ 9.046] (==) No monitor specified for screen "Default Screen Section". > Using a default monitor configuration. > [ 9.046] (==) Automatically adding devices > [ 9.046] (==) Automatically enabling devices > [ 9.046] (==) Automatically adding GPU devices > [ 9.046] (==) Max clients allowed: 256, resource mask: 0x1f > [ 9.060] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not > exist. > [ 9.060] Entry deleted from font path. > [ 9.071] (==) FontPath set to: > /usr/share/fonts/X11/misc, > /usr/share/fonts/X11/100dpi/:unscaled, > /usr/share/fonts/X11/75dpi/:unscaled, > /usr/share/fonts/X11/Type1, > /usr/share/fonts/X11/100dpi, > /usr/share/fonts/X11/75dpi, > built-ins > [ 9.071] (==) ModulePath set to "/usr/lib/xorg/modules" > [ 9.071] (II) The server relies on udev to provide the list of input > devices. > If no devices become available, reconfigure udev or disable > AutoAddDevices. > [ 9.071] (II) Loader magic: 0x5633eacaedc0 > [ 9.071] (II) Module ABI versions: > [ 9.071] X.Org ANSI C Emulation: 0.4 > [ 9.071] X.Org Video Driver: 20.0 > [ 9.071] X.Org XInput driver : 22.1 > [ 9.071] X.Org Server Extension : 9.0 > [ 9.072] (++) using VT number 7 > > [ 9.072] (II) systemd-logind: logind integration requires -keeptty and > -keeptty was not p
Bug#822666: linux-headers-3.16.0-4-amd64: deprecated syntax in linux-headers Makefile
On Sat, Apr 30, 2016 at 22:14:09 +0200, Ben Hutchings wrote: > I request a judgement from the SRM whether this bug is suitable for a > stable update. The change is pretty small: > > --- a/debian/rules.real > +++ b/debian/rules.real > @@ -311,7 +311,9 @@ install-headers_$(ARCH)_$(FEATURESET)_$(FLAVOUR): > $(STAMPS_DIR)/build_$(ARCH)_$( > @echo 'all:' >> $(DIR)/Makefile > @echo ' @$$(MAKE) $$(MAKEARGS) $$(cmd)' >> $(DIR)/Makefile > @echo 'Makefile:;' >> $(DIR)/Makefile > - @echo '$$(cmd) %/: all' >> $(DIR)/Makefile > + @echo '$$(cmd): all' >> $(DIR)/Makefile > + @echo ' @:' >> $(DIR)/Makefile > + @echo '%/: all' >> $(DIR)/Makefile > @echo ' @:' >> $(DIR)/Makefile > > dh_link /usr/lib/$(PACKAGE_NAME_KBUILD)/scripts $(BASE_DIR)/scripts > --- END --- > Feel free to include this change as part of a regular stable kernel update. Cheers, Julien
Re: Bug#822225: xserver-xorg-video-radeon: White glow and flicker on edges of LVDS display on boot
Control: reassign -1 src:linux 4.4.6-1~bpo8+1 On Thu, Apr 28, 2016 at 12:26:04 +0900, Michel Dänzer wrote: > On 22.04.2016 17:17, thomas wrote: > > Package: xserver-xorg-video-radeon > > Version: 1:7.7.0-1 > > Severity: normal > > > > Dear Maintainer, > > > >* What led up to the situation? > >I installed the open radeon driver package instead of the closed one > > > >* What exactly did you do (or not do) that was effective (or > > ineffective)? > >Boot the system > > > >* What was the outcome of this action? > >Increasing white glow on the edges of the built in display, a freeze, > >some flicker and finally the normal boot process continues > > > >* What outcome did you expect instead? > >A normal boot process without the glitches > > > > I am not sure if this is the fault of the display driver, > > Agreed, however... > > > but since it looks like a display (or maybe backlight?) glitch, I > > though it was best to report this under the video driver package. > > ... the display driver is actually the kernel driver with KMS, so this > report should be reassigned to the kernel package. > Reassigning. Cheers, Julien > > > I am worried that it might damage something hardware related, because > > it really doesn't look healthy to me. > > FWIW, IME it's quite unlikely that this kind of issue could result in > hardware damage. > > > -- > Earthling Michel Dänzer | http://www.amd.com > Libre software enthusiast | Mesa and X developer >
Bug#818646: linux-image-4.4.0-1-amd64: CONFIG_ZONE_DMA is not set
On Sat, Mar 19, 2016 at 15:46:46 +1030, Arthur Marsh wrote: > I usually run custom kernels based off the configuration of recent > Debian kernels. > > I notice that as of 4.4.0-1-amd64 (and hence also linux-image-4.5.0-rc7-amd64) > that CONFIG_ZONE_DMA is not set and that disables the EMU10K ALSA sound driver > which is needed for a card that I was considering adding to this machine. > > I do not know if this was an upstream or Debian change, intentional or not, > but it is an unpleasant surprise to discover hardware support removed > especially as at least one ALSA developer runs this hardware himself. > See bugs #814855 and #815787. Cheers, Julien
Re: Reduce required age for src:linux
On Sat, Mar 19, 2016 at 03:19:20 +, Ben Hutchings wrote: > Linux 4.4 has been kept out of testing due to regressions, most notably > in EFI support on amd64. These should all be resolved in the current > unstable version, 4.4.6-1, and I would like to get this into testing as > soon as possible, making way for 4.5 in unstable. > > Please consider reducing the required age to 2 days. > Done. Cheers, Julien
Re: no permission as root?
Ah, right. That is the "protected symlinks" hardening feature. Cheers, Julien On January 19, 2016 9:36:50 PM CET, Die Optimisten wrote: >On 2016-01-19 20:06, Julien Cristau wrote: >> On Tue, Jan 19, 2016 at 19:44:26 +0100, Die Optimisten wrote: >> >>> Hi >>> I#m using/normal Debian, without virtualization, etc/ >>> Why do I have access as user, but not as root >>> >> google for nfs root squash. >> >> Cheers, >> Julien >Hi Julien, >Its local, without NFS! (rootfs ext2, mounted without acl, xattr, etc > ) >Furthermore, if a user created the link, other users can't follow it, >other users can follow only, if created by root. > >test@PcDach:/tmp/BB$ dir RR >lrwxrwxrwx 1 andreas andreas 39 Jan 19 21:25 RR -> /RRR/ >test@PcDach:/tmp/BB$ dir RR/ >ls: cannot access RR/: Permission denied >test@PcDach:/tmp/BB$ >test@PcDach:/tmp/BB$ dir /RRR/# shows all >total 82048 >drwxrwxrwx 3 andreas test 4096 Jan 19 19:04 . >drwxrwxrwx 59 roottest 12288 Jan 15 17:10 .. >... > >Andrew
Re: no permission as root?
On Tue, Jan 19, 2016 at 19:44:26 +0100, Die Optimisten wrote: > > Hi > I#m using normal Debian, without virtualization, etc > Why do I have access as user, but not as root > google for nfs root squash. Cheers, Julien
Re: Bug#793124: regression: vertical pink line on HDMI port with KMS / wrong resolution with linux 4.0.0-2
Control: reassign -1 src:linux 4.0.8-1 On Tue, Jul 21, 2015 at 15:02:48 +0200, Mathieu Roy wrote: > Package: xserver-xorg-video-radeon > Version: 1:7.5.0-1+b1 > Severity: normal > > Hello, > > With ADM Radeon 6870 and an HDMI Samsung screen > > Similarly to https://bugzilla.redhat.com/show_bug.cgi?id=1236337 , after > booting on linux 4.0.0-2 I now get a vertical pink line on the left side and > the screen resolution is set to 1922x1080 instead of the regular 1920x1080 it > was set to until then. > > Booting back on 3.16.0-4-amd64 solves the issue. > Kernel regressions should probably be filed against the kernel... Please bisect and report at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM%2fRadeon Cheers, Julien signature.asc Description: Digital signature
Bug#787004: FTBFS on amd64
On Fri, Jun 5, 2015 at 03:24:39 +0100, Wookey wrote: > Package: linux linux is a source not binary package name. > Version: 4.0.4 That version does not exist. > Followup-For: Bug #787004 > [...] > This does indeed allow the build to complete. Patch attached. > Or you could have noticed that this bug is tagged pending and the fix is already in svn. Cheers, Julien signature.asc Description: Digital signature
Bug#786382: linux-image-4.0.0-1-amd64: Blank screen switching to a VT (Intel Haswell with HD4400)
On Thu, May 21, 2015 at 09:11:04 +0200, Cesare Leonardi wrote: > Package: src:linux > Version: 4.0.2-1 > Severity: normal > > Since kernel version 4.0 (also the previous 4.0.0-trunk from > experimental) if i try to switch to a VT from an X session (also from > the login manager), the screen becomes black and i'm not able to > recover from that situation, neither for the X session. > That's always reproducible and i wasn't able to find a workaround. > > After that you can observe: > - the system is not freezed and you can work blindly. > - the display shows no output but is powered on: the backlight is on and > i can change its brightness. > > After a reboot, looking in the log i always find two message like those: > - > mag 21 07:35:40 etna kernel: [drm:intel_set_cpu_fifo_underrun_reporting > [i915]] *ERROR* uncleared fifo underrun on pipe A > mag 21 07:35:40 etna kernel: [drm:ironlake_irq_handler [i915]] *ERROR* CPU > pipe A FIFO underrun > - > > So it looks like an Intel specific bug. > This is an Asuspro PU301LS notebook, with Haswell i7 4500U and HD4400. > > I had suspected for the "acpi_osi=" kernel parameter that i use to make > the backlight works properly, but i found that removing it makes no > difference. > > Note also that if i don't try to switch to a VT, i'm able to works > apparently without problems, like now while i'm writing this bug. > Please file this upstream at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel See instructions at https://01.org/linuxgraphics/documentation/development/how-report-bugs Thanks, Julien signature.asc Description: Digital signature
Re: linux: give back on ppc64el
On Sat, May 16, 2015 at 19:18:35 +0100, Ben Hutchings wrote: > linux failed to build from source on ppc64el due to a regression in > gcc-4.9 (#785066). This is fixed in gcc-4.9/4.9.2-17. > > Please ensure that buildds are upgraded, then: > > gb linux_4.0.2-1 . ppc64el > jcristau@wuiet:~$ wb gb linux . ppc64el . --extra-depends 'gcc-4.9 (>= 4.9.2-17)' Cheers, Julien signature.asc Description: Digital signature
Re: Bug#774300: base: modprobe radeon crashes latest jessie/testing
Control: severity -1 important Control: reassign -1 src:linux 3.16.7-ckt2-1 On Wed, Dec 31, 2014 at 13:57:38 +0100, Joerg Esser wrote: > Package: base > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > after modprobe readon the whole system crashes. No problems with old wheezy > distro. On Wed, Dec 31, 2014 at 16:56:43 +0100, Jörg Esser wrote: > Ok i found a "solution" I´ve added radeon.dpm=0 to the kernel boot options. > This part from the radeon module has a problem. > I see this is enabled since 3.11 or 3.12. > Should I open a bug report on kernel.org? If this still happens with current kernels, please file a bug at https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM%2fRadeon and let us know the bug number for tracking. Cheers, Julien > Tried different self compiled kernels up to latest stable 3.18.x with radeon > modules. > All have the same problem. System crashes on radeon load. Last syslog > messages are: > > Dec 31 13:40:46 VDR kernel: [ 1568.348752] [drm] Initialized drm 1.1.0 > 20060810 > Dec 31 13:40:46 VDR kernel: [ 1568.470916] [drm] radeon kernel modesetting > enabled. > Dec 31 13:40:46 VDR kernel: [ 1568.471331] [drm] initializing kernel > modesetting (CEDAR 0x1002:0x68F9 0x174B:0xE157). > Dec 31 13:40:46 VDR kernel: [ 1568.471351] [drm] register mmio base: > 0xF7CC > Dec 31 13:40:46 VDR kernel: [ 1568.471353] [drm] register mmio size: 131072 > Dec 31 13:40:46 VDR kernel: [ 1568.471406] ATOM BIOS: CEDAR > Dec 31 13:40:46 VDR kernel: [ 1568.471505] radeon :01:00.0: VRAM: 512M > 0x - 0x1FFF (512M used) > Dec 31 13:40:46 VDR kernel: [ 1568.471508] radeon :01:00.0: GTT: 1024M > 0x2000 - 0x5FFF > Dec 31 13:40:46 VDR kernel: [ 1568.471509] [drm] Detected VRAM RAM=512M, > BAR=256M > Dec 31 13:40:46 VDR kernel: [ 1568.471511] [drm] RAM width 64bits DDR > Dec 31 13:40:46 VDR kernel: [ 1568.471629] [TTM] Zone kernel: Available > graphics memory: 2024374 kiB > Dec 31 13:40:46 VDR kernel: [ 1568.471632] [TTM] Initializing pool allocator > Dec 31 13:40:46 VDR kernel: [ 1568.471646] [TTM] Initializing DMA pool > allocator > Dec 31 13:40:46 VDR kernel: [ 1568.471682] [drm] radeon: 512M of VRAM memory > ready > Dec 31 13:40:46 VDR kernel: [ 1568.471686] [drm] radeon: 1024M of GTT memory > ready. > Dec 31 13:40:46 VDR kernel: [ 1568.471715] [drm] Loading CEDAR Microcode > Dec 31 13:40:46 VDR kernel: [ 1568.487039] radeon :01:00.0: firmware: > direct-loading firmware radeon/CEDAR_pfp.bin > Dec 31 13:40:46 VDR kernel: [ 1568.488583] radeon :01:00.0: firmware: > direct-loading firmware radeon/CEDAR_me.bin > Dec 31 13:40:46 VDR kernel: [ 1568.504933] radeon :01:00.0: firmware: > direct-loading firmware radeon/CEDAR_rlc.bin > Dec 31 13:40:46 VDR kernel: [ 1568.512797] radeon :01:00.0: firmware: > direct-loading firmware radeon/CEDAR_smc.bin > Dec 31 13:40:46 VDR kernel: [ 1568.512804] [drm] Internal thermal controller > with fan control > Dec 31 13:40:46 VDR kernel: [ 1568.533142] [drm] radeon: dpm initialized > Dec 31 13:40:46 VDR kernel: [ 1568.550174] radeon :01:00.0: firmware: > direct-loading firmware radeon/CYPRESS_uvd.bin > Dec 31 13:40:46 VDR kernel: [ 1568.550211] [drm] GART: num cpu pages 262144, > num gpu pages 262144 > Dec 31 13:40:46 VDR kernel: [ 1568.551255] [drm] enabling PCIE gen 2 link > speeds, disable with radeon.pcie_gen2=0 > Dec 31 13:40:46 VDR kernel: [ 1568.564629] [drm] PCIE GART of 1024M enabled > (table at 0x0025D000). > Dec 31 13:40:46 VDR kernel: [ 1568.564754] radeon :01:00.0: WB enabled > Dec 31 13:40:46 VDR kernel: [ 1568.564756] radeon :01:00.0: fence driver > on ring 0 use gpu addr 0x2c00 and cpu addr 0x8800d8b6ec00 > Dec 31 13:40:46 VDR kernel: [ 1568.564758] radeon :01:00.0: fence driver > on ring 3 use gpu addr 0x2c0c and cpu addr 0x8800d8b6ec0c > Dec 31 13:40:46 VDR kernel: [ 1568.570716] radeon :01:00.0: fence driver > on ring 5 use gpu addr 0x0005c418 and cpu addr 0xc90004b9c418 > Dec 31 13:40:46 VDR kernel: [ 1568.570718] [drm] Supports vblank timestamp > caching Rev 2 (21.10.2013). > Dec 31 13:40:46 VDR kernel: [ 1568.570719] [drm] Driver supports precise > vblank timestamp query. > Dec 31 13:40:46 VDR kernel: [ 1568.570734] radeon :01:00.0: irq 49 for > MSI/MSI-X > Dec 31 13:40:46 VDR kernel: [ 1568.570742] radeon :01:00.0: radeon: using > MSI. > Dec 31 13:40:46 VDR kernel: [ 1568.570764] [drm] radeon: irq initialized. > Dec 31 13:40:46 VDR kernel: [ 1568.587411] [drm] ring test on 0 succeeded in > 1 usecs > Dec 31 13:40:46 VDR kernel: [ 1568.587419] [drm] ring test on 3 succeeded in > 3 usecs > Dec 31 13:40:46 VDR kernel: [ 1568.773867] [drm] ring test on 5 succeeded in > 1 usecs > Dec 31 13:40:46 VDR kernel: [ 1568.773873] [drm] UVD initialized successfully. > Dec 31 13:40:46 VDR kernel: [ 1568.774234] [drm] ib tes
Re: Bug#779009: xserver-xorg-video-intel: kernel occasionally spits about intel driver
Control: reassign -1 src:linux 3.16.7-ckt4-3 On Mon, Feb 23, 2015 at 13:08:52 +0530, Ritesh Raj Sarraf wrote: > Package: xserver-xorg-video-intel > Version: 2:2.21.15-2+b2 > Severity: normal > > Hi, > > At times, I have the intel video driver spitting the following: > > > [119838.142088] ---[ end trace 0e1f3f064f2f48a3 ]--- > [119841.961047] [ cut here ] > [119841.961075] WARNING: CPU: 0 PID: 16775 at > /build/linux-y7bjb0/linux-3.16.7-ckt4/drivers/gpu/drm/i915/intel_pm.c:5992 > intel_display_power_put+0x127/0x150 [i915]() > [119841.961076] Modules linked in: snd_usb_audio snd_usbmidi_lib > snd_rawmidi snd_seq_device hid_generic ip6table_filter ip6_tables veth > bnep bluetooth 6lowpan_iphc ctr ccm appletalk ax25 ipx p8023 p8022 psnap > pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc > nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc bridge > stp llc xt_conntrack iptable_filter ipt_MASQUERADE iptable_nat > nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack > xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables > snd_hda_codec_hdmi nls_utf8 nls_cp437 vfat fat uvcvideo > videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev > media hid_multitouch joydev i915 hp_wmi sparse_keymap iTCO_wdt > iTCO_vendor_support x86_pkg_temp_thermal nouveau mxm_wmi > intel_powerclamp intel_rapl kvm_intel > [119841.961099] snd_hda_codec_idt snd_hda_codec_generic snd_hda_intel > arc4 snd_hda_controller kvm rt2800pci snd_hda_codec snd_hwdep rt2800mmio > rt2800lib rt2x00pci rt2x00mmio rt2x00lib eeprom_93cx6 mac80211 cfg80211 > efi_pstore pcspkr psmouse evdev serio_raw efivars rtsx_pci_ms ttm > snd_pcm snd_timer crc_ccitt memstick rfkill snd shpchp soundcore > drm_kms_helper drm i2c_algo_bit video i2c_i801 lpc_ich mei_me i2c_core > mei hp_wireless hp_accel lis3lv02d input_polldev ac processor button > battery intel_smartconnect wmi coretemp fuse parport_pc ppdev lp parport > autofs4 ext4 crc16 mbcache jbd2 btrfs xor raid6_pq algif_skcipher af_alg > usbhid hid dm_crypt dm_mod sg sd_mod crc_t10dif crct10dif_generic > rtsx_pci_sdmmc mmc_core crct10dif_pclmul crct10dif_common crc32_pclmul > crc32c_intel ghash_clmulni_intel ahci libahci > [119841.961128] libata aesni_intel aes_x86_64 lrw gf128mul glue_helper > ablk_helper cryptd scsi_mod ehci_pci ehci_hcd xhci_hcd r8169 rtsx_pci > mii mfd_core usbcore usb_common fan thermal thermal_sys > [119841.961136] CPU: 0 PID: 16775 Comm: kworker/0:2 Tainted: GW > O 3.16.0-4-amd64 #1 Debian 3.16.7-ckt4-3 > [119841.961138] Hardware name: Hewlett-Packard HP ENVY TS 15 Notebook > PC/1963, BIOS F.65 11/20/2014 > [119841.961144] Workqueue: events edp_panel_vdd_work [i915] > [119841.961145] 0009 815096a7 > 810676f7 > [119841.961147] 88024d48002c 880253031d08 88024d48 > 88025f216600 > [119841.961148] 88024d488520 a0a7f187 880036ea2230 > 880253031d08 > [119841.961150] Call Trace: > [119841.961154] [] ? dump_stack+0x41/0x51 > [119841.961157] [] ? warn_slowpath_common+0x77/0x90 > [119841.961162] [] ? > intel_display_power_put+0x127/0x150 [i915] > [119841.961167] [] ? edp_panel_vdd_work+0x2e/0x40 > [i915] > [119841.961169] [] ? process_one_work+0x172/0x420 > [119841.961170] [] ? worker_thread+0x115/0x520 > [119841.961171] [] ? rescuer_thread+0x2d0/0x2d0 > [119841.961173] [] ? kthread+0xbd/0xe0 > [119841.961175] [] ? > kthread_create_on_node+0x180/0x180 > [119841.961176] [] ? ret_from_fork+0x7c/0xb0 > [119841.961178] [] ? > kthread_create_on_node+0x180/0x180 > [119841.961179] ---[ end trace 0e1f3f064f2f48a4 ]--- > signature.asc Description: Digital signature
Re: Bug#774977: upgrade-reports: dist-upgrade (jessi 3.14-2-amd64 -> 3.16.0-4-amd64): xserver unable to identify monitor -> fallback to vesa/not configurable
Control: reassign -1 src:linux 3.16.7-ckt2-1 On Fri, Jan 9, 2015 at 17:14:48 +0100, Thorben Kaufmann wrote: > Gfx: > Asus NVIDIA GeForce GTX750TI > + nouveau driver > Board: > Asus Sabertooth 990FX R2.0 + AMD FX8350 > > Problem: > When dist-upgrading 3.14-2-amd64 to 3.16.0-4-amd64 grafik mode is locked to > either 640x480 or 800x600 on DVI with ugly pixelation. > By trying to configure a higher resolution, only HDMI-Port works with > 1024x768 (also pixelated). Chars are almost unreadable. > One problem seems to be missing ability to read out monitor data. > Reboot with old kernel works around that issue (Resolution 1920x1400). > Please provide kernel and X logs for old and new kernel. Thanks, Julien signature.asc Description: Digital signature
Bug#775297: linux-image-3.16.0-4-amd64: Oops in edac_unregister_sysfs
pped some of the template below. Cheers, Julien -- Package-specific info: ** Version: Linux version 3.16.0-0.bpo.4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Debian 3.16.7-ckt2-1~bpo70+1 (2014-12-08) ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-0.bpo.4-amd64 root=UUID=53a7226c-ad1d-411f-ad14-088ec8889275 ro cgroup_enable=memory console=tty0 console=ttyS1,115200n8 quiet ** Model information sys_vendor:Dell Inc. product_name:PowerEdge 2950 chassis_vendor:Dell Inc. bios_vendor:Dell Inc. bios_version:2.5.0 board_vendor:Dell Inc. board_version:A05 -- Julien Cristau Logilab http://www.logilab.fr/ Informatique scientifique & gestion de connaissances -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150113170652.ga17...@sh76.dev.logilab.fr
Bug#763155: Bug#764528: Cross-referencing i915 kernel bugs on EEEpc
On Sun, Nov 30, 2014 at 17:26:04 +0100, Erich Schubert wrote: > severity 764528 important > tag 764528 +jessie +sid +experimental > tag 771227 +jessie +sid +experimental > block 764528 763155 > block 771227 763155 > merge 764528 771227 > thanks > > All of these are probably the same bug, rendering current kernels > (jessie onward) unusable on EEEpc with older (?) Atom CPUs. > > As far as I can tell, the bug may be in the kernel, not the xorg > driver (xorg shouldn't lock up the kernel; and the kernel itself > reports a BUG after all...) > > > kernel BUG at > > /build/linux-Lep8DD/linux-3.16.3/drivers/gpu/drm/i915/i915_gem_stolen.c:431! > Please report this upstream, following instructions at https://01.org/linuxgraphics/documentation/how-report-bugs, and let us know the bug number for tracking. Cheers, Julien signature.asc Description: Digital signature
Bug#771379: linux-image-3.16-0.bpo.3-amd64: backport kernels not booting when root file system is on an LVM volume
On Sat, Nov 29, 2014 at 22:15:34 +0100, lee wrote: > So installing the backports kernel removes initramfs-tools because it > requires dracut. Shouldn't aptitude pull in the backports version of > initramfs-tools? (I wasn't aware that there is one ) > The backports kernel does very much not require dracut. Cheers, Julien signature.asc Description: Digital signature
Bug#771379: linux-image-3.16-0.bpo.3-amd64: backport kernels not booting when root file system is on an LVM volume
On Fri, Nov 28, 2014 at 23:45:34 +0100, lee wrote: > Package: src:linux > Version: 3.16.5-1~bpo70+1 > Severity: important > > + do an installation that has the root file system on an LVM volume > > + once finished, install the backports kernel > this removes initramfs-tools because the backports kernel uses > dracut > It shouldn't. You need to install initramfs-tools from backports though. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#761182: xserver-xorg-video-nouveau: NV94: screen black after resume from S3
Control: reassign -1 src:linux 3.16.5-1 Control: fixed -1 3.17-1~exp1 Control: tag -1 upstream fixed-upstream Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=83550 On Mon, Nov 10, 2014 at 23:34:56 -0500, Dennis Linnell wrote: > I have been suffering similar symptoms. The problem occurs in all the 3.16 > kernels through 3.16.5-1, but not in any of the 3.14 kernels, most recently > 3.14.15-2. > > As suggested above, I tried the latest kernel, linux-image-3.17-1-686-pae > (3.17-1~exp1) from experimental. That fixed the problem for me. > > This appears to be the relevant upstream bug report: > > https://www.libreoffice.org/bugzilla/show_bug.cgi?id=83550 > > See the patch. It would be nice to see this problem fixed in the jessie 3.16 > kernel. > That's commit 5838ae610ff36777b8fce6f353c2417980c1a1fa upstream. Cheers, Julien signature.asc Description: Digital signature
Re: d-i anna: no packages matching running kernel 3.16-2-amd64 in archive
On Mon, Nov 3, 2014 at 06:12:45 +0100, Geert Stappers wrote: > On Sun, Nov 02, 2014 at 11:12:59PM +0100, Julien Cristau wrote: > > On Sun, Nov 2, 2014 at 22:52:03 +0100, Geert Stappers wrote: > > > > > Hi, > > > > > > background information: > > > * debian-installer from 2014-10-02 > > > > Which image? > > > > It is a netboot. > That image can't work after a kernel ABI change. You should use another image or a daily build. Cheers, Julien signature.asc Description: Digital signature
Re: d-i anna: no packages matching running kernel 3.16-2-amd64 in archive
On Sun, Nov 2, 2014 at 22:52:03 +0100, Geert Stappers wrote: > Hi, > > background information: > * debian-installer from 2014-10-02 Which image? Cheers, Julien signature.asc Description: Digital signature
Bug#766195: [PATCH] ipv6: reuse ip6_frag_id from ip6_ufo_append_data
On Mon, Oct 27, 2014 at 13:40:44 +, Ben Hutchings wrote: > I've now written and tested patches for that remaining regression. > > Source at: > https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.dsc > https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.debian.tar.xz > > Binary at: > https://people.debian.org/~benh/packages/linux-image-3.2.0-4-amd64_3.2.63-2+deb7u1_amd64.deb > > There's a signed .changes file there as well, for verification > (distribution=UNRELEASED in case you are wondering). > > Additional testing would be appreciated. > Installed your package on salieri.debian.org now. Anything we should look out for? Cheers, Julien signature.asc Description: Digital signature
Bug#764718: (no subject)
On Fri, Oct 24, 2014 at 22:04:42 +0200, Pierre Schweitzer wrote: > Dear Rapahel, > Note that you didn't send this to Raphael, unless he was Bcc:ed... Cheers, Julien signature.asc Description: Digital signature
Bug#766195: linux: Network-related panic in Linux 3.2.63
Source: linux
Version: 3.2.63-2
Severity: important
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
X-Debbugs-Cc: debian-ad...@lists.debian.org, m...@debian.org
Hi,
after the latest point release some debian.org hosts became unreliable.
That was tracked down to a panic in the networking code. Ben provided a
test patch:
From: Ben Hutchings
Date: Tue, 21 Oct 2014 00:49:22 +0100
Subject: ipv6: ipv6_select_ident: handle null rt
Forwarded: not-needed
In Linux 3.2, ipv6_select_ident() can apparently still be called with
rt == NULL and must avoid dereferencing it in this case.
We should probably fix the callers, so WARN_ON_ONCE to get a clue
about how this happens.
---
--- a/net/ipv6/ip6_output.c
+++ b/net/ipv6/ip6_output.c
@@ -604,13 +604,18 @@ void ipv6_select_ident(struct frag_hdr *
static bool hashrnd_initialized = false;
u32 hash, id;
+ if (WARN_ON_ONCE(!rt)) {
+ hash = 0;
+ goto reserve;
+ }
+
if (unlikely(!hashrnd_initialized)) {
hashrnd_initialized = true;
get_random_bytes(&ip6_idents_hashrnd,
sizeof(ip6_idents_hashrnd));
}
hash = __ipv6_addr_jhash(&rt->rt6i_dst.addr, ip6_idents_hashrnd);
hash = __ipv6_addr_jhash(&rt->rt6i_src.addr, hash);
-
+reserve:
id = ip_idents_reserve(hash, 1);
fhdr->identification = htonl(id);
}
which resulted in the following trace:
[ 436.375412] [ cut here ]
[ 436.375439] WARNING: at /usr/src/linux-3.2.63/net/ipv6/ip6_output.c:607
ipv6_select_ident+0x28/0x8b()
[ 436.375446] Hardware name: ProLiant DL585 G2
[ 436.375451] Modules linked in: ipmi_devintf ip6t_REJECT ip6t_LOG
nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT ipt_ULOG
xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack ses
xt_hashlimit enclosure xt_multiport iptable_filter ip_tables x_tables crc32c
ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp
libiscsi scsi_transport_iscsi bridge sd_mod dm_round_robin crc_t10dif bonding
xfs ext4 crc16 jbd2 hmac drbd lru_cache 8021q garp stp dm_snapshot loop
dm_multipath scsi_dh vhost_net tun macvtap macvlan kvm_amd kvm radeon ttm
ipmi_si drm_kms_helper ipmi_msghandler k8temp powernow_k8 mperf hpilo drm
power_supply i2c_algo_bit shpchp amd64_edac_mod edac_mce_amd edac_core psmouse
hpwdt i2c_core snd_pcm snd_page_alloc snd_timer snd soundcore processor cdc_acm
pcspkr evdev serio_raw container button thermal_sys ext3 mbcache jbd dm_mod
usbhid hid sg sr_mod cdrom hpsa ata_generic lpfc pata_amd uhci_hcd libata
scsi_transport_fc scsi_tgt ohci_hcd bnx2 ehci_hcd cciss scsi_mod usbcore
usb_common [last unloaded: scsi_wait_scan]
[ 436.375642] Pid: 12085, comm: unbound Not tainted 3.2.0-4-amd64 #1 Debian
3.2.63-2a~test
[ 436.375647] Call Trace:
[ 436.375666] [] ? warn_slowpath_common+0x78/0x8c
[ 436.375676] [] ? ipv6_select_ident+0x28/0x8b
[ 436.375685] [] ? udp6_ufo_fragment+0x124/0x1a2
[ 436.375696] [] ? ipv6_gso_segment+0xb8/0x14e
[ 436.375705] [] ? __wake_up_common+0x40/0x77
[ 436.375715] [] ? skb_gso_segment+0x208/0x28b
[ 436.375725] [] ? __wake_up+0x35/0x46
[ 436.375734] [] ? arch_local_irq_save+0x11/0x17
[ 436.375746] [] ? _raw_spin_lock_irqsave+0x9/0x25
[ 436.375756] [] ? lock_timer_base.isra.29+0x23/0x47
[ 436.375764] [] ? _raw_spin_unlock_irqrestore+0xe/0xf
[ 436.375771] [] ? __mod_timer+0x139/0x14b
[ 436.375781] [] ? _local_bh_enable_ip.isra.11+0x1e/0x88
[ 436.375794] [] ? ip6t_do_table+0x5b2/0x5e4 [ip6_tables]
[ 436.375805] [] ? dev_hard_start_xmit+0x32d/0x518
[ 436.375814] [] ? nf_iterate+0x41/0x77
[ 436.375823] [] ? sch_direct_xmit+0x61/0x135
[ 436.375833] [] ? dev_queue_xmit+0x2c2/0x46b
[ 436.375856] [] ? br_dev_queue_push_xmit+0x9b/0x9f [bridge]
[ 436.375871] [] ? br_dev_xmit+0x12e/0x142 [bridge]
[ 436.375880] [] ? dev_hard_start_xmit+0x3d2/0x518
[ 436.375888] [] ? ip6_fragment+0x801/0x801
[ 436.375897] [] ? dev_queue_xmit+0x3c1/0x46b
[ 436.375906] [] ? ip6_finish_output2+0x216/0x26a
[ 436.375916] [] ? ip6_push_pending_frames+0x307/0x391
[ 436.375925] [] ? udp_v6_push_pending_frames+0x284/0x2fc
[ 436.375934] [] ? udpv6_sendmsg+0x6e0/0x8a0
[ 436.375942] [] ? find_busiest_group+0x1f5/0x805
[ 436.375956] [] ? sock_sendmsg+0xc1/0xde
[ 436.375965] [] ? inet_recvmsg+0x5b/0x6f
[ 436.375974] [] ? sock_recvmsg+0xcd/0xec
[ 436.375982] [] ? sock_kmalloc+0x41/0x63
[ 436.375989] [] ? sock_kmalloc+0x41/0x63
[ 436.375999] [] ? __kmalloc+0x100/0x112
[ 436.376032] [] ? should_resched+0x5/0x23
[ 436.376040] [] ? should_resched+0x5/0x23
[ 436.376048] [] ? _cond_resched+0x7/0x1c
[ 436.376056] [] ? copy_from_user+0x18/0x30
[ 436.376065] [] ? ___sys_sendmsg+0x209/0x2a9
[ 436.376075] [] ? udp_poll+0xf/0x42
[ 436.376082] [] ? should_resched+0x5/0x23
[ 436.376089] [] ? _cond_resched+0x7/0x1c
[ 436.376106] [] ? move_addr_to_user+0x70/0x8a
[ 4
Re: Bug#765590: libdrm-intel1: 3D-graphics freeze using new libdrm-intel1
Control: reassign -1 src:linux 3.16.3-2
On Thu, Oct 16, 2014 at 17:11:47 +0400, Max wrote:
> Package: libdrm-intel1
> Version: 2.4.58-2
> Severity: important
>
> Dear Maintainer,
>
> Today I've upgraded Debian successfully and everything was OK. But when I've
> started my OpenSceneGraph-based application with 3d-graphics, OS stopped
> responding on mouse and keyboard. Htop utility stopped updating. Even
> keyboard stopped responding to Num-lock, Caps-lock etc. I've restarted my PC
> with Reset button, started my 3d-application and got the same situation again.
> I've worked on my OSG-based application for last 3-4 weeks. I did system
> upgrade every day and everything worked without any problems.
>
> Here I can attach some log from my OS. I've got it after freeze happened.
>
Reassigning to the kernel as your log shows crashes there...
Cheers,
Julien
> [ 1611.250190] BUG: unable to handle kernel NULL pointer dereference at
> 0008
> [ 1611.250229] IP: [] interval_tree_iter_next+0x0/0x60
> [ 1611.250258] PGD 81922067 PUD 81ae7067 PMD 0
> [ 1611.250279] Oops: [#1] SMP
> [ 1611.250296] Modules linked in: cfg80211 binfmt_misc nfsd auth_rpcgss
> oid_registry nfs_acl nfs lockd fscache sunrpc x86_pkg_temp_thermal
> intel_powerclamp intel_rapl coretemp kvm crc32_pclmul ghash_clmulni_intel
> aesni_intel aes_x86_64 joydev nouveau lrw gf128mul glue_helper mxm_wmi
> iTCO_wdt ttm psmouse ablk_helper i915 iTCO_vendor_support drm_kms_helper drm
> evdev eeepc_wmi asus_wmi sparse_keymap rfkill snd_hda_codec_realtek
> snd_hda_codec_hdmi snd_hda_codec_generic lpc_ich serio_raw i2c_algo_bit
> i2c_i801 wmi cryptd mfd_core snd_hda_intel pcspkr snd_hda_controller shpchp
> i2c_core snd_hda_codec mei_me snd_hwdep mei snd_pcm snd_timer snd soundcore
> video button battery processor fuse autofs4 ext4 crc16 mbcache jbd2 sg sd_mod
> sr_mod crc_t10dif cdrom crct10dif_generic hid_generic usbhid hid ata_generic
> crct10dif_pclmul crct10dif_common crc32c_intel r8169 mii ata_piix libata
> ehci_pci xhci_hcd ehci_hcd scsi_mod usbcore usb_common fan thermal thermal_sys
> [ 1611.250722] CPU: 2 PID: 1971 Comm: im_kr Not tainted 3.16-2-amd64 #1
> Debian 3.16.3-2
> [ 1611.250750] Hardware name: System manufacturer System Product Name/P8H77-V
> LE, BIOS 1301 08/20/2013
> [ 1611.250782] task: 8800776dd330 ti: 88007755 task.ti:
> 88007755
> [ 1611.250808] RIP: 0010:[] []
> interval_tree_iter_next+0x0/0x60
> [ 1611.250841] RSP: 0018:880077553d30 EFLAGS: 00010246
> [ 1611.250860] RAX: RBX: 880129f178d8 RCX:
>
> [ 1611.250885] RDX: 7fc0800c5fff RSI: 7fc0800c5000 RDI:
>
> [ 1611.250910] RBP: 7fc0800c5000 R08: a03f8650 R09:
>
> [ 1611.250935] R10: R11: 880077553f48 R12:
> 880129f178d8
> [ 1611.250959] R13: R14: R15:
> 7fc0800c5000
> [ 1611.250985] FS: 7fc08f147700() GS:88012fb0()
> knlGS:
> [ 1611.251013] CS: 0010 DS: ES: CR0: 80050033
> [ 1611.251034] CR2: 0008 CR3: 819ec000 CR4:
> 001407e0
> [ 1611.251059] Stack:
> [ 1611.251067] a03f8808 880129f178c0 7fc0800c5fff
>
> [ 1611.251098] 880129f178f0 880129f178d8
> 880036b33400
> [ 1611.251128] 7fc0800c6000 7fc0800c5000
> 7fc0800c5000
> [ 1611.251159] Call Trace:
> [ 1611.251180] [] ?
> i915_gem_userptr_mn_invalidate_range_start+0x1b8/0x230 [i915]
> [ 1611.251216] [] ?
> __mmu_notifier_invalidate_range_start+0x54/0x80
> [ 1611.251244] [] ? change_protection+0x848/0x8b0
> [ 1611.251266] [] ? handle_mm_fault+0xa91/0x11a0
> [ 1611.251289] [] ? mprotect_fixup+0x110/0x270
> [ 1611.251311] [] ? SyS_mprotect+0x15b/0x270
> [ 1611.251333] [] ? system_call_fast_compare_end+0x10/0x15
> [ 1611.251357] Code: 66 66 2e 0f 1f 84 00 00 00 00 00 48 8b 3f 48 85 ff 74 08
> 48 39 77 28 72 02 eb a0 31 c0 c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 <48>
> 8b 4f 08 48 85 c9 74 1b 48 39 71 28 72 15 eb 38 0f 1f 80 00
> [ 1611.251520] RIP [] interval_tree_iter_next+0x0/0x60
> [ 1611.251545] RSP
> [ 1611.251558] CR2: 0008
> [ 1611.260038] ---[ end trace 18d002edd609e2f2 ]---
> [ 1632.257113] INFO: rcu_sched self-detected stall on CPU { 1} (t=5250
> jiffies g=39954 c=39953 q=294)
> [ 1632.257118] sending NMI to all CPUs:
> [ 1632.257121] NMI backtrace for cpu 1
> [ 1632.257123] CPU: 1 PID: 1972 Comm: im_kr Tainted: G D
> 3.16-2-amd64 #1 Debian 3.16.3-2
> [ 1632.257124] Hardware name: System manufacturer System Product Name/P8H77-V
> LE, BIOS 1301 08/20/2013
> [ 1632.257125] task: 88007770f5b0 ti: 8800775f8000 task.ti:
> 8800775f8000
> [ 1632.257126] RIP: 0010:[] []
> find_next_bit+0x4d/0xd0
> [ 1632.257139] RSP: 0018:88012fa83df8 EFLAGS: 0046
> [ 1632.257140] RAX:
Re: Bug#764445: xserver-xorg: screen blanking when rotating with kernel 3.15 or newer with Atom Z36xxx/Z37xxx integrated graphics
Control: reassign -1 src:linux 3.15~rc8-1~exp1 On Wed, Oct 8, 2014 at 09:21:23 +0200, Wolfgang Silbermayr wrote: > Package: xserver-xorg > Version: 1:7.7+7 > Severity: normal > > Dear Maintainers, > > When rotating the screen to the left or right using e.g. "xrandr -o left", it > goes blank. > > I am no longer able to use Ctrl+Alt+F for switching to a console, but the > machine is still reachable over network. It also does not switch back when > calling a shell command like "xrandr -o left; sleep 10; xrandr -o normal". > > I tried the following kernels (partly from snapshots.debian.org and > experimental): > > 3.14-2 => works > 3.15-rc8 => fails > 3.16-2 => fails > 3.17-rc5 => fails > > Please let me know if you need any further information. > On Tue, Oct 14, 2014 at 07:16:39 +0200, Wolfgang Silbermayr wrote: > I reported the bug to upstream: > https://bugs.freedesktop.org/show_bug.cgi?id=84974 > Thanks for doing this. Reassigning to the kernel package. Cheers, Julien signature.asc Description: Digital signature
Bug#764263: linux-image-3.16-2-amd64: WARNING at drivers/base/firmware_class.c:1109 _request_firmware+0x521/0xaf0() [btusb?]
Package: src:linux Version: 3.16.3-2 Severity: normal Hi, I get the following trace in my kernel log, which I don't think I've seen in pre-3.16 versions: Sep 29 19:12:49 betterave kernel: [ 7696.920600] PM: resume of devices complete after 508.149 msecs Sep 29 19:12:49 betterave kernel: [ 7696.921181] [ cut here ] Sep 29 19:12:49 betterave kernel: [ 7696.921188] WARNING: CPU: 2 PID: 3533 at /build/linux-P15SNz/linux-3.16.3/drivers/base/firmware_class.c:1109 _request_firmware+0x521/0xaf0() Sep 29 19:12:49 betterave kernel: [ 7696.921282] Modules linked in: ctr ccm bnep binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd fscache sunrpc nls_utf8 nls_cp437 vfat fat snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic joydev arc4 iwldvm ecb mac80211 x86_pkg_temp_thermal intel_powerclamp intel_rapl btusb coretemp bluetooth kvm_intel kvm 6lowpan_iphc crc32_pclmul ghash_clmulni_intel iTCO_wdt aesni_intel iTCO_vendor_support aes_x86_64 lrw gf128mul glue_helper iwlwifi evdev snd_hda_intel efi_pstore ablk_helper psmouse snd_hda_controller cryptd i915 snd_hda_codec cfg80211 serio_raw snd_hwdep snd_pcm efivars pcspkr thinkpad_acpi snd_timer nvram wmi snd drm_kms_helper ac soundcore i2c_i801 tpm_tis mei_me drm rfkill shpchp i2c_algo_bit lpc_ich tpm battery mei video i2c_core mfd_core button processor loop fuse parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 dm_mod sg sd_mod crc_t10dif crct10dif_generic ahci crct10dif_pclmul crct10dif_common libahci crc32c_intel ehci_pci ehci_hcd xhci_hcd libata sdhci_pci sdhci scsi_mod mmc_core e1000e usbcore usb_common ptp pps_core thermal thermal_sys Sep 29 19:12:49 betterave kernel: [ 7696.921326] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: docking Sep 29 19:12:49 betterave kernel: [ 7696.921327] Sep 29 19:12:49 betterave kernel: [ 7696.921329] PM: Finishing wakeup. Sep 29 19:12:49 betterave kernel: [ 7696.921333] CPU: 2 PID: 3533 Comm: kworker/u17:0 Not tainted 3.16-2-amd64 #1 Debian 3.16.3-2 Sep 29 19:12:49 betterave kernel: [ 7696.921338] Restarting tasks ... Sep 29 19:12:49 betterave kernel: [ 7696.921338] Hardware name: LENOVO 2324CTO/2324CTO, BIOS G2ET92WW (2.52 ) 02/22/2013 Sep 29 19:12:49 betterave kernel: [ 7696.921353] Workqueue: hci0 hci_power_on [bluetooth] Sep 29 19:12:49 betterave kernel: [ 7696.921362] 0009 81506188 81065707 Sep 29 19:12:49 betterave kernel: [ 7696.921365] 880214b3fd48 880201fe6d80 880201c25e80 8800d4797600 Sep 29 19:12:49 betterave kernel: [ 7696.921371] 880214b3fd40 813af2b1 0004ff102100 8800d57bdab8 Sep 29 19:12:49 betterave kernel: [ 7696.921377] Call Trace: Sep 29 19:12:49 betterave kernel: [ 7696.921386] [] ? dump_stack+0x41/0x51 Sep 29 19:12:49 betterave kernel: [ 7696.921394] [] ? warn_slowpath_common+0x77/0x90 Sep 29 19:12:49 betterave kernel: [ 7696.921400] [] ? _request_firmware+0x521/0xaf0 Sep 29 19:12:49 betterave kernel: [ 7696.921405] [] ? request_firmware+0x2c/0x40 Sep 29 19:12:49 betterave kernel: [ 7696.921412] [] ? btusb_setup_bcm_patchram+0x85/0x430 [btusb] Sep 29 19:12:49 betterave kernel: [ 7696.921419] [] ? rpm_check_suspend_allowed+0x6a/0xc0 Sep 29 19:12:49 betterave kernel: [ 7696.921428] [] ? __pm_runtime_idle+0x69/0x80 Sep 29 19:12:49 betterave kernel: [ 7696.921439] [] ? hci_dev_do_open+0x25d/0x920 [bluetooth] Sep 29 19:12:49 betterave kernel: [ 7696.921446] [] ? enqueue_task_fair+0x2cf/0xe20 Sep 29 19:12:49 betterave kernel: [ 7696.921454] [] ? native_sched_clock+0x2d/0x80 Sep 29 19:12:49 betterave kernel: [ 7696.921465] [] ? hci_power_on+0x2c/0x170 [bluetooth] Sep 29 19:12:49 betterave kernel: [ 7696.921473] [] ? ttwu_do_wakeup+0x14/0xd0 Sep 29 19:12:49 betterave kernel: [ 7696.921482] [] ? process_one_work+0x172/0x420 Sep 29 19:12:49 betterave kernel: [ 7696.921488] [] ? worker_thread+0x115/0x520 Sep 29 19:12:49 betterave kernel: [ 7696.921494] [] ? rescuer_thread+0x2d0/0x2d0 Sep 29 19:12:49 betterave kernel: [ 7696.921500] [] ? kthread+0xbd/0xe0 Sep 29 19:12:49 betterave kernel: [ 7696.921507] [] ? kthread_create_on_node+0x180/0x180 Sep 29 19:12:49 betterave kernel: [ 7696.921513] [] ? ret_from_fork+0x7c/0xb0 Sep 29 19:12:49 betterave kernel: [ 7696.921519] [] ? kthread_create_on_node+0x180/0x180 Sep 29 19:12:49 betterave kernel: [ 7696.921522] ---[ end trace 6e5c53426f331854 ]--- Sep 29 19:12:49 betterave kernel: [ 7696.921528] bluetooth hci0: firmware: brcm/BCM20702A0-0a5c-21e6.hcd will not be loaded Sep 29 19:12:49 betterave kernel: [ 7696.921534] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-21e6.hcd not found Sep 29 19:12:49 betterave kernel: [ 7696.928553] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1: Unable to dock! Sep 29 19:12:49 betterave kernel: [ 7696.929287] done. Cheers, Julien -- Package-specific info: ** Version: Linux version 3.16-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.3 (Debian 4.8.3-11) ) #1 SMP
Re: Bug#764073: xserver-xorg-input-synaptics: bcm5974 (Apple unibody trackpad) fails after extended idle
Control: reassign -1 src:linux 3.14.15-2 On Sun, Oct 5, 2014 at 11:24:05 +0200, Riccardo Boninsegna wrote: > Package: xserver-xorg-input-synaptics > Version: 1.8.1-1 > Severity: normal > > Last night, I left my computer by turning down the screen brighness to zero > and the keyboard's to about 20%. > When I increased them again this morning, the mouse cursor wouldn't move. I > immediately tried touching the trackpad with the whole palm (an empirical > "fix" for a problem I experienced while running my computer without battery > where the cursor would stop moving after clicking), which didn't help. > Removing and reloading the module fixed the problem; I'm not aware of this > issue having ever repeated. > > selection of dmesg output follows: > [455030.430023] JBD2: Error -5 detected when updating journal superblock for > sdb1-8. > [491747.172823] bcm5974: bad trackpad package, length: 8 > [491747.180897] bcm5974: bad trackpad package, length: 8 > [491747.187898] bcm5974: bad trackpad package, length: 8 > [491747.196890] bcm5974: bad trackpad package, length: 8 > [...] > [491769.758147] bcm5974: bad trackpad package, length: 8 > [491780.974885] usbcore: deregistering interface driver bcm5974 > [491785.276737] input: bcm5974 as > /devices/pci:00/:00:1a.7/usb3/3-1/3-1.2/3-1.2:1.2/input/input18 > [491785.277028] usbcore: registered new interface driver bcm5974 > Sounds like a kernel issue, reassigning. Cheers, Julien signature.asc Description: Digital signature
Bug#760037: nfs-kernel-server: nfs crashes in set_nfsv4_acl_one
On Sun, Aug 31, 2014 at 12:31:32 -0700, Steve Langasek wrote: > On Sun, Aug 31, 2014 at 09:54:23AM +0200, Frank Denissen wrote: > > > Executing debuild on a self-made package on a nfs4 mounted partition > > (normal pc, i386) provoked the error on the server (sheevaplug - armel > > architecture). The build package contains a large zip file that is unzipped > > during the build phase. > > > I tried to add no_acl to /etc/exports of the nfs4 share but this had no > > effect. > > I exported/imported the partition as nfs. This solved the problem. > > > The log files on the server contained the following information: > > Aug 28 17:00:33 nijlpaard kernel: [ 702.739829] Unable to handle kernel > > NULL pointer dereference at virtual address 0008 > > Aug 28 17:00:33 nijlpaard kernel: [ 702.748064] pgd = c0004000 > > Aug 28 17:00:33 nijlpaard kernel: [ 702.750815] [0008] *pgd= > > Aug 28 17:00:33 nijlpaard kernel: [ 702.754518] Internal error: Oops: 5 > > [#1] > > Aug 28 17:00:33 nijlpaard kernel: [ 702.758453] Modules linked in: autofs4 > > act_police cls_basic cls_flow cls_fw cls_u32 sch_tbf sch_prio sch_htb > > sch_hfsc sch_ingress sch_sfq xt_statistic xt_CT 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 xt_set ip_set 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_udplite 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_defrag_ipv6 ip6_tables nf_tproxy_core 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 > > This points to a kernel bug rather than a bug in the nfs-kernel-server > package. > > > Kernel: Linux 3.2.0-4-kirkwood > > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > Unfortunately, it is probably not useful to reassign this bug to the kernel > package since this is an obsolete and no-longer-supported kernel version. > Well, that's the current stable kernel, so I would hope it's not no-longer-supported. Also this bug looks like a dupe of 754420. Cheers, Julien signature.asc Description: Digital signature
Bug#757805: linux: linux-3.14.13/drivers/gpu/drm/i915/intel_panel.c:696 i9xx_enable_backlight+0xd4/0x100 [i915]()
On Mon, Aug 11, 2014 at 17:46:55 +0300, Martin-Éric Racine wrote: > 2014-08-11 16:56 GMT+03:00 maximilian attems : > > On Mon, Aug 11, 2014 at 04:30:01PM +0300, Martin-Éric Racine wrote: > >> Package: src:linux > >> Version: 3.14.13-2 > >> Severity: normal > >> File: linux > >> > >> While debugging something else, I found the following in syslog: > > > > can you reproduce with latest 3.16 (should be in exp). > > Yes, I can. See attached kernel oops dump. > Please report this upstream following the instructions at https://01.org/linuxgraphics/documentation/how-report-bugs Thanks, Julien signature.asc Description: Digital signature
Re: Bug#755471: ifupdown: fails to bring up network: cannot access '/dev/net/tun': ENOENT
On Mon, Jul 21, 2014 at 16:29:22 +, Thorsten Glaser wrote: > Fun fact: > > $ sudo modprobe tun > $ sudo /etc/init.d/openvpn start > > This seems to work. So I think the module may not be autoloaded > correctly any more. Maybe the kernel? My last boot was on 2nd of > July, therefore almost certainly with linux 3.14.9-1 whereas now > I run: > > Linux tglase.lan.tarent.de 3.14-1-amd64 #1 SMP Debian 3.14.12-1 (2014-07-11) > i686 GNU/Linux > That sounds like #749021 Cheers, Julien signature.asc Description: Digital signature
Re: Bug#741485: xserver-xorg-video-ati: System hang at boot with kernel 3.12+ with ati 4650 and xserver-xorg-video-ati
Control: reassign -1 src:linux 3.14~rc5-1~exp1 Control: severity -1 important On Mon, Mar 17, 2014 at 13:04:34 +0900, Michel Dänzer wrote: > On Fre, 2014-03-14 at 11:50 +0200, Alex wrote: > > > > So i have 2 dmesg one is when i boot normally with 3.14rc5 which i get the > > issueof booting up but black screen a cursor and it constantly tries to fix > > it > > self but comes back to black screen.(dmesg) > > The 2nd dmesg is with radeon.dpm=0 on kernel 3.14rc5 which it successfully > > opens with correct graphics (at least as i see it) but only with kernel > > 3.14rc5 > > and not with kernels 3.13 and 3.12(dmesgnodpm) > > Please file an upstream bug report at > https://bugs.freedesktop.org/enter_bug.cgi?product=DRI , component > DRM/Radeon, and report back the resulting bug number here. > > > P.S. This bug report should be reassigned to the kernel packages. > Doing so now. Cheers, Julien signature.asc Description: Digital signature
Bug#742563: linux: Black screen for internal laptop display on Intel HD Graphics 4400
Control: found -1 3.14~rc7-1~exp1 Control: notfound -1 3.14-rc7 On Mon, Mar 24, 2014 at 21:20:09 -0400, Matthew Horan wrote: > Source: linux > Version: 3.14-rc7 This is not a debian package version. Cheers, Julien signature.asc Description: Digital signature
Bug#740491: nfs-common: fails to upgrade (action "restart" failed)
Package: nfs-common Version: 1:1.2.8-6 Severity: serious On upgrading today, I got: Setting up nfs-common (1:1.2.8-6) ... Installing new version of config file /etc/init.d/nfs-common ... insserv: warning: current start runlevel(s) (2 3 4 5 S) of script `nfs-common' overrides LSB defaults (S). Job for nfs-common.service failed. See 'systemctl status nfs-common.service' and 'journalctl -xn' for details. invoke-rc.d: initscript nfs-common, action "restart" failed. dpkg: error processing package nfs-common (--configure): subprocess installed post-installation script returned error exit status 1 [...] Errors were encountered while processing: nfs-common E: Sub-process /usr/bin/dpkg returned an error code (1) $ sudo systemctl status nfs-common.service nfs-common.service - LSB: NFS support files common to client and server Loaded: loaded (/etc/init.d/nfs-common) Active: failed (Result: exit-code) since Sun 2014-03-02 12:22:37 CET; 5min ago Process: 14279 ExecStop=/etc/init.d/nfs-common stop (code=exited, status=0/SUCCESS) Process: 14288 ExecStart=/etc/init.d/nfs-common start (code=exited, status=1/FAILURE) Mar 02 12:22:37 betterave systemd[1]: Starting LSB: NFS support files common to client and server... Mar 02 12:22:37 betterave rpc.statd[14293]: Version 1.2.8 starting Mar 02 12:22:37 betterave rpc.statd[14293]: Failed to read /var/lib/nfs/state: Success Mar 02 12:22:37 betterave rpc.statd[14293]: Initializing NSM state Mar 02 12:22:37 betterave nfs-common[14288]: Starting NFS common utilities: statd failed! Mar 02 12:22:37 betterave systemd[1]: nfs-common.service: control process exited, code=exited status=1 Mar 02 12:22:37 betterave systemd[1]: Failed to start LSB: NFS support files common to client and server. Mar 02 12:22:37 betterave systemd[1]: Unit nfs-common.service entered failed state. Cheers, Julien -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp111 portmapper 102 tcp111 portmapper 104 udp111 portmapper 103 udp111 portmapper 102 udp111 portmapper 1000241 udp 42073 status 1000241 tcp 42787 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD= NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /run/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (900, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.12-1-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 nfs-common depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-51 ii libc6 2.17-97 ii libcap2 1:2.22-1.2 ii libcomerr2 1.42.9-3 ii libdevmapper1.02.1 2:1.02.83-2 ii libevent-2.0-5 2.0.21-stable-1 ii libgssglue1 0.4-2 ii libk5crypto31.12+dfsg-2 ii libkeyutils11.5.6-1 ii libkrb5-3 1.12+dfsg-2 ii libmount1 2.20.1-5.6 ii libnfsidmap20.25-5 ii libtirpc1 0.2.2-5.1 ii libwrap07.6.q-25 ii lsb-base4.1+Debian12 ii rpcbind 0.2.1-3 ii ucf 3.0027+nmu1 Versions of packages nfs-common recommends: ii python 2.7.5-5 Versions of packages nfs-common suggests: pn open-iscsi pn watchdog -- no debconf information signature.asc Description: Digital signature
Re: Bug#734760: xserver-xorg-input-evdev: ps2 keyboard maniacally retypes keys after one press. sometimes drops keys.
Control: severity -1 important Control: reassign -1 src:linux 3.12.6-1 On Thu, Jan 9, 2014 at 12:11:46 -0500, Mitchell Laks wrote: > Package: xserver-xorg-input-evdev > Version: 1:2.8.2-1 > Severity: grave > Tags: upstream > Justification: renders package unusable > > Dear Maintainer, > > I recently upgraded my motherboard to a ASUS M4a77td motherboard with a 6core > amd processor and > radeon card. > > I use a PS2 m$ft internet keyboard and a usb mouse. > > > > I am having repeated episodes of the various keys, such as the enter key > (and other keys as well) suddenly typing over and over again. I have to hit > 'any' key > to stop it. > Thus it will type keyboarddd etc. > > I replaced the keyboard with another keyboard and it was not a keyboard > hardware problem. > Does not happen when I plug in a usb keyboard. > Doesn't sound like an X issue... Cheers, Julien signature.asc Description: Digital signature
Re: Linux 3.12 transition to testing
On Fri, Jan 3, 2014 at 11:19:42 +0100, Cyril Brulebois wrote: > Ben Hutchings (2014-01-03): > > linux 3.12.6-2 and linux-tools 3.12.6-1 should be ready for transition > > to testing tomorrow, except that they also need to go with linux-latest > > 55 which was uploaded with urgency=low. Please add a hint for > > linux-latest so that this isn't delayed unnecessarily. > > kibi@franck:~$ head -3 hints/kibi > # 2014-01-03 > # RoM: https://lists.debian.org/debian-release/2014/01/msg00022.html > age-days 5 linux-latest/55 > And added a remove hint for nvidia-graphics-modules. Cheers, Julien signature.asc Description: Digital signature
Re: Linux 3.11
On Sun, Nov 17, 2013 at 18:30:15 +, Ben Hutchings wrote: > Linux 3.11 has at last successfully built on all architectures. > > The latest version (3.11.8-1) has only been in unstable for 2 days, but > it has many important fixes and we really should get this into testing > before moving on to Linux 3.12. > > Please force/hint as necessary so that linux, linux-latest and > linux-tools can propagate into testing. > I've removed the nvidia modules, blcr and blktap-dkms were aged, and linux was forced through last night, breaking oss4-dkms on various archs. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#728839: libdrm-nouveau2: Mouse pointer become garbage, then panic in kernel and freeze
Control: reassign -1 linux 3.11.6-2 Moving to the kernel. Still waiting on info about the hardware... Cheers, Julien On Sun, Nov 10, 2013 at 13:03:19 +0400, Vladimir Berezenko wrote: > Some additional panic message: > > Nov 10 12:52:12 QMHomeG5 kernel: [65612.110761] Oops: Kernel access of bad > area, sig: 11 [#1] > Nov 10 12:52:12 QMHomeG5 kernel: [65612.110789] SMP NR_CPUS=32 NUMA PowerMac > Nov 10 12:52:12 QMHomeG5 kernel: [65612.110804] Modules linked in: > rpcsec_gss_krb5 nfsv4 dns_resolver parport_pc lp parport rfcomm bnep > bluetooth > rfkill binfmt_misc nfsd auth_rpcgss oid_registry nfs_acl nfs lockd > fscache sunrpc snd_aoa_fabric_layout snd_aoa_i2sbus snd_aoa_soundbus loop > fuse > snd_usb_audio joydev hid_logitech snd_usbmidi_lib snd_hwdep snd_seq_midi > snd_seq_midi_event ff_memless usbhid hid snd_rawmidi snd_aoa_ > codec_onyx snd_aoa snd_pcm snd_seq snd_seq_device snd_timer sil164 snd evdev > nouveau uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev > soundcore media snd_page_alloc ttm ohci_pci drm_kms_helper o > hci_hcd drm ext4 crc16 mbcache jbd2 windfarm_cpufreq_clamp > windfarm_smu_sensors windfarm_smu_controls windfarm_pm112 > windfarm_lm75_sensor > windfarm_max6690_sensor windfarm_smu_sat windfarm_pid windfarm_core i2c_pow > ermac sd_mod crc_t10dif ata_generic sg firewire_ohci firewire_core ehci_pci > ehci_hcd sr_mod crc_itu_t cdrom sata_svw usbcore tg3 usb_common ptp pps_core > libphy > Nov 10 12:52:12 QMHomeG5 kernel: [65612.27] CPU: 0 PID: 3077 Comm: > klauncher Not tainted 3.11-1-powerpc64 #1 Debian 3.11.6-2 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.41] task: c00175a22040 ti: > c00178928000 task.ti: c00178928000 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.52] NIP: c035471c LR: > c01c1818 CTR: c01c0e20 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.65] REGS: c0017892b5a0 TRAP: > 0300 Not tainted (3.11-1-powerpc64 Debian 3.11.6-2) > Nov 10 12:52:12 QMHomeG5 kernel: [65612.77] MSR: 90009032 > CR: 44028484 XER: > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111214] SOFTE: 1 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111219] DAR: 0075f004fa04, DSISR: > 4000 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR00: c01c1818 > c0017892b820 c0a03318 c00177354800 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR04: c00177142250 > c09a3688 091f6000 c001756efd40 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR08: 0001 > 0075f004fa04 0a445000 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR12: > cfffa000 10132ef8 0004 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR16: 0f6e029c > f7e7c000 10138e18 1011cb80 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR20: 10138d80 > 0001 c0946b05 c001789a4cc0 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR24: 00100100 > 00200200 c001789a4d38 c09a3688 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111227] GPR28: c00177142250 > c00177142220 c001756efd40 c00177354800 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111389] NIP [c035471c] > .__rb_erase_color+0x17c/0x3c0 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111403] LR [c01c1818] > .anon_vma_interval_tree_remove+0x1f8/0x300 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111414] Call Trace: > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111424] [c0017892b820] > [00100100] 0x100100 (unreliable) > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111441] [c0017892b8c0] > [c01c1818] .anon_vma_interval_tree_remove+0x1f8/0x300 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111458] [c0017892b930] > [c01d44e4] .unlink_anon_vmas+0xb4/0x270 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111472] [c0017892ba00] > [c01c41b0] .free_pgtables+0xe0/0x1b0 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111485] [c0017892baa0] > [c01cff50] .exit_mmap+0xf0/0x190 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111500] [c0017892bbc0] > [c009d6bc] .mmput+0x8c/0x180 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111514] [c0017892bc40] > [c00a37c0] .do_exit+0x310/0xb70 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111528] [c0017892bd30] > [c00a40c4] .do_group_exit+0x54/0xf0 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111542] [c0017892bdc0] > [c00a4174] .SyS_exit_group+0x14/0x20 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111558] [c0017892be30] > [c0009edc] syscall_exit+0x0/0xa0 > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111569] Instruction dump: > Nov 10 12:52:12 QMHomeG5 kernel: [65612.111575] e95b 7fc4f378 7fe3fb78 > f8410028 7d3e4b78 7d4903a6 e85b0008 4e800421 > Nov 10 12:52:12 QMHomeG5 kernel: [6
Re: linux-tools and libunwind transition
On Mon, Oct 28, 2013 at 02:08:53 +, Ben Hutchings wrote: > I recently (3.11-1) made linux-tools build-depend on libunwind8-dev, as > the perf tool can optionally make use of this library. I didn't notice > that libunwind was part of a transition or that it is only available on > some architectures. > I'd suggest to switch this to libunwind7-dev if perf can use that, until either gcc itself switches to libunwind8 on ia64, or ia64 is removed. Cheers, Julien signature.asc Description: Digital signature
Bug#719127: Another instance of this crash
Version: 3.10.7-1 On Sun, Aug 18, 2013 at 01:21:02 +0200, Ben Hutchings wrote: > This is from a Lenovo X1 Carbon, and also shows 'Thread overran stack, > or stack corrupted': > > http://richardhartmann.de/img/DSC_0469.JPG > > (small version attached). > Yet another one: http://people.debian.org/~jcristau/panic.jpg Cheers, Julien signature.asc Description: Digital signature
Re: Next (old)stable point releases
On Thu, Sep 5, 2013 at 12:17:54 +0200, Julien Cristau wrote: > On Tue, Sep 3, 2013 at 23:09:44 +0100, Adam D. Barratt wrote: > > > [...] > > > >- Oct 12-13 > > > >- Oct 19-20 > > > > Either of those is fine for me. > > > Alright, let's go for > > Oct 12-13: 7.3 Obviously I meant 7.2... > Oct 19-20: 6.0.8 > > Cheers, > Julien signature.asc Description: Digital signature
Re: Next (old)stable point releases
On Tue, Sep 3, 2013 at 23:09:44 +0100, Adam D. Barratt wrote: > [...] > > >- Oct 12-13 > > >- Oct 19-20 > > Either of those is fine for me. > Alright, let's go for Oct 12-13: 7.3 Oct 19-20: 6.0.8 Cheers, Julien signature.asc Description: Digital signature
Bug#721887: initramfs-tools: breaks system when used with module-init-tools from lenny or older
Control: severity -1 minor On Wed, Sep 4, 2013 at 22:46:53 -0400, Brian Sammon wrote: > Package: initramfs-tools > Version: 0.109.1 > Severity: serious > > *** Please type your report below this line *** > > When I upgrade initramfs-tools to 0.109.1 on my system with > module-init-tools 3.4-1 on it, it overwrites all the initrd.img files in > /boot/ with bad ones, leaving my system unbootable (it brings me to a initrd > command prompt). All the menu items in grub are affected, including the > known-safe fallback boot choices. > > initramfs-tools 0.109.1 with module-init-tools 3.12-2+b1 works. > Skipping stable releases is not supported, meaning mixing packages from Debian version n with packages from Debian version n+2 is not a supported configuration. Cheers, Julien signature.asc Description: Digital signature
Next (old)stable point releases
Hi, we should start thinking about dates for the 7.2 and 6.0.8 point releases. Which week-ends in the coming months would work for ftpmaster, press and cd? (We'd need one date for stable and another later for oldstable.) Anything particular that needs to happen on either the kernel or d-i side? - Sep 7-8 - Sep 14-15 - Sep 21-22 - Sep 28-29 - Oct 5-6 - Oct 12-13 - Oct 19-20 - Oct 26-27 Cheers, Julien signature.asc Description: Digital signature
Re: Uploaded linux (3.10.5-1)
On Sun, Aug 11, 2013 at 11:38:29 +0200, Cyril Brulebois wrote: > kibi@franck:~$ head -2 hints/kibi > # 2013-08-11; RoM: 3.10 in unstable for 4 weeks, biggest regressions fixed, > security fixes shouldn't keep waiting > urgent linux/3.10.5-1 > Added urgent hints for linux-tools and linux-latest. Cheers, Julien signature.asc Description: Digital signature
Bug#705507: nfs-common: rpc.gssd crashes when performing nfs4 mount
On Sun, May 12, 2013 at 19:58:31 +0200, Євгеній Мещеряков wrote: > found 705507 1:1.2.6-3 > thanks > > Ah, original bug report was about this version, sorry for that. This > could be a different bug though. > #707960 probably. Cheers, Julien signature.asc Description: Digital signature
Bug#708037: nfs-utils_1.2.8.orig.tar.bz2 contains object files
Source: nfs-utils Version: 1:1.2.8-1 Severity: important Hi, it looks like the uploaded nfs-utils 1.2.8 tarball contains build artefacts, including lots of object files and various programs. Cheers, Julien signature.asc Description: Digital signature
Bug#707960: rpc.gssd segfaults when mounting a nfsv4 volume
On Sun, May 12, 2013 at 15:38:34 +0200, Luk Claes wrote: > While a segfault is not tolerable you should still not file bugs as > grave that do not break other packages. It's even not serious as the > package is still functional for a lot of people that use it in another > context than you do. > Sounds to me like you're confusing grave and critical. Cheers, Julien signature.asc Description: Digital signature
Re: Bug#707902: xserver-xorg-video-radeon: No 3D acceleration after Wheezy update
Control: reassign -1 src:linux 3.2.41-2 On Sat, May 11, 2013 at 21:07:15 -0400, rich wrote: > Here is modeset=1 information, probe fails in dmesg log. > - > === :~$ dmesg | grep -e drm -e radeon > > [0.00] Kernel command line: > BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-686-pae root=UUID= ro quiet > radeon.modeset=1 > [6.496706] [drm] Initialized drm 1.1.0 20060810 > [6.880970] [drm] radeon kernel modesetting enabled. > [6.881940] [drm] initializing kernel modesetting (RV100 > 0x1002:0x5159 0x1002:0x5159). > [6.881992] [drm] register mmio base: 0xD900 > [6.881995] [drm] register mmio size: 65536 > [6.884707] radeon :01:00.0: putting AGP V2 device into 4x mode > [6.884714] radeon :01:00.0: GTT: 256M 0xC000 - 0xCFFF > [6.884725] radeon :01:00.0: VRAM: 128M 0xD000 - > 0xD7FF (64M used) > [6.884754] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). > [6.884757] [drm] Driver supports precise vblank timestamp query. > [6.884764] radeon :01:00.0: Fatal error during GPU init > [6.884811] [drm] radeon: finishing device. > [6.884858] [drm] radeon: cp finalized > [6.884863] radeon :01:00.0: no bo for sa manager > [6.885536] radeon: probe of :01:00.0 failed with error -22 > Moving to the kernel. Can you try newer kernel versions and see if that makes a difference? Cheers, Julien signature.asc Description: Digital signature
Bug#707144: initramfs-tools: fails to include firmware
[please reply to all, not just to me] On Tue, May 7, 2013 at 22:50:09 +0200, Sebastian Dalfuß wrote: > On Tue, May 07, 2013 at 09:19:12PM +0200, Julien Cristau wrote: > > Why would you need firmware for a wireless driver in initramfs? Root on > > nfs over wifi doesn't sound like a sane thing to do, somehow. > > With the firmware not beeing present during boot, I got a kernel error > message about firmware not beeing found, instead of working wifi. > That's why it seemed that the firmware belongs into initramfs. Putting > the firmware into initramfs solved the problem. > The wireless driver isn't supposed to be in initramfs either... Cheers, Julien signature.asc Description: Digital signature
Bug#707144: initramfs-tools: fails to include firmware
On Tue, May 7, 2013 at 20:38:14 +0200, Sebastian Dalfuß wrote: > Package: initramfs-tools > Version: 0.112 > Severity: normal > > While installing a new kernel or updating initramfs update-initramfs fails to > add necessary firmware to the initramfs. > > Quick'n dirty workaround: > I added > copy_exec "/lib/firmware/iwlwifi-6000g2b-6.ucode" > to the bottom of > manual_add_modules() > in > /usr/share/initramfs-tools/hook-functions > Why would you need firmware for a wireless driver in initramfs? Root on nfs over wifi doesn't sound like a sane thing to do, somehow. Cheers, Julien signature.asc Description: Digital signature
Re: Packaging of Atheros USB wifi card firmware
On Fri, May 3, 2013 at 02:38:04 -0400, Christopher Waid wrote: > There are some issues and/or bugs in the packaging of the firmware for a > few USB atheros chipsets. The firmware-atheros package is in the non-free > repository and while this would be the correct place a few years ago it no > longer is for some atheros firmware. > > The firmware for the Atheros USB chipsets AR9170, AR7010, and AR9271 have > been released under Debian compatible free software licenses. > > The AR9170 firmware included in the firmware-atheros package is also out > of date. The kernel no longer supports the AR9170 firmware. The driver and > firmware which replaced it is Carl9170. This has been true since the 3.0 > kernel. > I can't speak for the other ones, but carl9170 firmware is part of the firmware-linux-free package: http://packages.debian.org/wheezy/firmware-linux-free Cheers, Julien signature.asc Description: Digital signature
Re: Bug#706588: installation-reports: display blackout after rebooting
Control: reassign -1 linux 3.2.41-2 Control: retitle -1 drm/nouveau: black screen on GeForce 8600 GTS [10de:0400] On Thu, May 2, 2013 at 10:38:43 +0900, Takeo Terada wrote: > Installation was normal ended. > But after rebooting, monitor blackouted (When switching flame-buffer mode?). > Error appered in dmesg like below. > [7.664540] [drm] nouveau :01:00.0: DDC responded, but no EDID for > DVI-I-1 > [7.757630] [drm] Cannot find any crtc or sizes - going 1024x768 > [7.759913] [drm] nouveau :01:00.0: allocated 1024x768 fb: 0x32, > bo 880213759000 > Thanks for your report. Booting with the 'nomodeset' kernel parameter should work around this issue temporarily. Can you try installing a newer kernel (e.g. 3.8 from experimental), and see if things work better (without the nomodeset parameter)? Can you describe the graphics setup, in particular what monitors are connected (VGA, DVI, HDMI, ...)? Cheers, Julien > (My hardware) > MotherBoard Intel DP67BGB3 > CPU Intel Corei7 i7-2600 > Graphics card ASUSTeK EN8600GTS SILENT/HTDP/256M (NVIDIA GeForce 8600) > Monitor NANAO S2401W-HBK (1920x1200 bestfit, connect DVI-I) > > -- > > Please make sure that the hardware-summary log file, and any other > installation logs that you think would be useful are attached to this > report. Please compress large files using gzip > > Once you have filled out this report, mail it to sub...@bugs.debian.org. > > == > Installer lsb-release: > == > DISTRIB_ID=Debian > DISTRIB_DESCRIPTION="Debian GNU/Linux installer" > DISTRIB_RELEASE="7.0 (wheezy) - installer build 20130415" > X_INSTALLATION_MEDIUM=cdrom > > == > Installer hardware-summary: > == > uname -a: Linux server02 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux > lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core > Processor Family DRAM Controller [8086:0100] (rev 09) > lspci -knn: Subsystem: Intel Corporation Device [8086:2010] > lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd > Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09) > lspci -knn: Kernel driver in use: pcieport > lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 > Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) > lspci -knn: Subsystem: Intel Corporation Device [8086:4742] > lspci -knn: 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V > Gigabit Network Connection [8086:1503] (rev 05) > lspci -knn: Subsystem: Intel Corporation Device [8086:] > lspci -knn: Kernel driver in use: e1000e > lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 > Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 05) > lspci -knn: Subsystem: Intel Corporation Device [8086:4742] > lspci -knn: Kernel driver in use: ehci_hcd > lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 > Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 05) > lspci -knn: Subsystem: Intel Corporation Device [8086:2007] > lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series > Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b5) > lspci -knn: Kernel driver in use: pcieport > lspci -knn: 00:1c.1 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series > Chipset Family PCI Express Root Port 2 [8086:1c12] (rev b5) > lspci -knn: Kernel driver in use: pcieport > lspci -knn: 00:1c.3 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series > Chipset Family PCI Express Root Port 4 [8086:1c16] (rev b5) > lspci -knn: Kernel driver in use: pcieport > lspci -knn: 00:1c.7 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series > Chipset Family PCI Express Root Port 8 [8086:1c1e] (rev b5) > lspci -knn: Kernel driver in use: pcieport > lspci -knn: 00:1d.0 USB controller [0c03]: Intel Corporation 6 Series/C200 > Series Chipset Family USB Enhanced Host Controller #1 [8086:1c26] (rev 05) > lspci -knn: Subsystem: Intel Corporation Device [8086:4742] > lspci -knn: Kernel driver in use: ehci_hcd > lspci -knn: 00:1f.0 ISA bridge [0601]: Intel Corporation P67 Express Chipset > Family LPC Controller [8086:1c46] (rev 05) > lspci -knn: Subsystem: Intel Corporation Device [8086:4742] > lspci -knn: 00:1f.2 SATA controller [0106]: Intel Corporation 6 Series/C200 > Series Chipset Family SATA AHCI Controller [8086:1c02] (rev 05) > lspci -knn: Subsystem: Intel Corporation Device [8086:4742] > lspci -knn: Kernel driver in use: ahci > lspci -knn: 00:1f.3 SMBus [0c05]: Intel Corporation 6 Series/C200 Series > Chipset Family SMBus Controller [8086:1c22] (rev 05) > lspci -knn: Subsystem: Intel Corporation Device [8086:4742] > lspci -knn: 01:00.0 VGA compatible controller
Bug#706129: reboot will fix this
On Thu, Apr 25, 2013 at 10:40:00 +, Schumacher, Bernd wrote: > The reboot with 3.2.0-4-amd64 did not fix this problem for me. (I have tried > it) Show logs, then, because your initial report was with an out of date kernel image. Cheers, Julien signature.asc Description: Digital signature
Bug#706129: reboot will fix this
On Thu, Apr 25, 2013 at 11:37:25 +0200, Wouter Verhelst wrote: > This occurs because of commit 4189aa4ceebb1cd2b216d88980e35399e299c8c5, > which was recently added to the kernel; it calls kill_bdev, which > previous versions of the nbd driver didn't. This probably means you've > upgraded your kernel package but haven't rebooted yet. If you do, this > issue should go away. > > (Not closing the bug, since this is an ABI change, and presumably that > means the kernel should bump its ABI version -- but I'm leaving that to > kernel maintainers to decide) > The ABI number gets bumped when a newer kernel stops being compatible with old modules, not the other way around. So I think this bug should be closed as invalid. Cheers, Julien signature.asc Description: Digital signature
Bug#706031: linux-image-3.2.0-4-amd64: WARNING at include/net/mac80211.h:3575 rate_control_send_low+0xa3/0x16c [mac80211]
Package: src:linux Version: 3.2.41-2 Severity: important I have several warnings from mac80211 in dmesg. It seems that the machine is sometimes able to recover, sometimes I'm not so sure. Cheers, Julien Apr 22 09:47:39 luzerne kernel: [ 2905.482200] [ cut here ] Apr 22 09:47:39 luzerne kernel: [ 2905.482253] WARNING: at /build/buildd-linux_3.2.41-2-amd64-Wvc92F/linux-3.2.41/include/net/mac80211.h:3575 rate_control_send_low+0xa3/0x16c [mac80211]() Apr 22 09:47:39 luzerne kernel: [ 2905.482262] Hardware name: Latitude E4200 Apr 22 09:47:39 luzerne kernel: [ 2905.482267] Modules linked in: cryptd aes_x86_64 aes_generic parport_pc ppdev lp parport rfcomm bnep cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats binfm t_misc uinput fuse nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext2 loop firewire_sbp2 snd_hda_codec_hdmi snd_hda_codec_idt btusb bluetooth crc16 joydev arc4 uvcvideo videodev v4l2_compat_ioctl32 media dell _wmi sparse_keymap snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq snd_seq_device snd_timer evdev psmouse coretemp dell_laptop dcdbas iwlwifi i915 serio_raw i2c_i801 iTCO_wdt snd iTCO_vendor_ support pcspkr mac80211 cfg80211 drm_kms_helper drm rfkill i2c_algo_bit soundcore i2c_core battery wmi ac video button power_supply acpi_cpufreq mperf processor usbhid hid ext3 mbcache jbd dm_mod sg sd_mod crc_t1 0dif thermal thermal_sys uhci_hcd ahci libahci firewire_ohci sdhci_pci sdhci libata mmc_core firewire_core crc_itu_t ehci_hcd scsi_mod e1000e usbcore usb_common [last unloaded: scs Apr 22 09:47:39 luzerne kernel: i_wait_scan] Apr 22 09:47:39 luzerne kernel: [ 2905.482451] Pid: 2754, comm: NetworkManager Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2 Apr 22 09:47:39 luzerne kernel: [ 2905.482457] Call Trace: Apr 22 09:47:39 luzerne kernel: [ 2905.482462][] ? warn_slowpath_common+0x78/0x8c Apr 22 09:47:39 luzerne kernel: [ 2905.482503] [] ? rate_control_send_low+0xa3/0x16c [mac80211] Apr 22 09:47:39 luzerne kernel: [ 2905.482523] [] ? rs_get_rate+0x51/0x142 [iwlwifi] Apr 22 09:47:39 luzerne kernel: [ 2905.482551] [] ? rate_control_get_rate+0x7c/0x139 [mac80211] Apr 22 09:47:39 luzerne kernel: [ 2905.482580] [] ? invoke_tx_handlers+0x76b/0xded [mac80211] Apr 22 09:47:39 luzerne kernel: [ 2905.482609] [] ? ieee80211_tx+0x5c/0x87 [mac80211] Apr 22 09:47:39 luzerne kernel: [ 2905.482638] [] ? ieee80211_tx_pending+0xd5/0x1a3 [mac80211] Apr 22 09:47:39 luzerne kernel: [ 2905.482650] [] ? add_interrupt_randomness+0x38/0x155 Apr 22 09:47:39 luzerne kernel: [ 2905.482660] [] ? tasklet_action+0x73/0xc2 Apr 22 09:47:39 luzerne kernel: [ 2905.482668] [] ? __do_softirq+0xb9/0x177 Apr 22 09:47:39 luzerne kernel: [ 2905.482678] [] ? call_softirq+0x1c/0x30 Apr 22 09:47:39 luzerne kernel: [ 2905.482689] [] ? do_softirq+0x3c/0x7b Apr 22 09:47:39 luzerne kernel: [ 2905.482697] [] ? irq_exit+0x3c/0x9a Apr 22 09:47:39 luzerne kernel: [ 2905.482705] [] ? do_IRQ+0x82/0x98 Apr 22 09:47:39 luzerne kernel: [ 2905.482715] [] ? common_interrupt+0x6e/0x6e Apr 22 09:47:39 luzerne kernel: [ 2905.482720] Apr 22 09:47:39 luzerne kernel: [ 2905.482726] ---[ end trace fe68ccadcfd21f8c ]--- Apr 23 09:07:25 luzerne kernel: [ 168.088608] [ cut here ] Apr 23 09:07:25 luzerne kernel: [ 168.088634] WARNING: at /build/buildd-linux_3.2.41-2-amd64-Wvc92F/linux-3.2.41/include/net/mac80211.h:3575 rate_control_send_low+0xa3/0x16c [mac80211]() Apr 23 09:07:25 luzerne kernel: [ 168.088638] Hardware name: Latitude E4200 Apr 23 09:07:25 luzerne kernel: [ 168.088641] Modules linked in: cryptd aes_x86_64 aes_generic parport_pc ppdev lp parport bnep rfcomm cpufreq_powersave cpufreq_conservative cpufreq_userspace cpufreq_stats binfmt_misc uinput fuse nfsd nfs nfs_acl auth_rpcgss fscache lockd sunrpc ext2 loop firewire_sbp2 snd_hda_codec_hdmi snd_hda_codec_idt btusb bluetooth crc16 joydev uvcvideo videodev v4l2_compat_ioctl32 media arc4 snd_hda_intel snd_hda_codec dell_wmi sparse_keymap snd_hwdep snd_pcm snd_page_alloc snd_seq iwlwifi snd_seq_device evdev snd_timer psmouse pcspkr serio_raw dell_laptop coretemp dcdbas i915 snd mac80211 iTCO_wdt iTCO_vendor_support i2c_i801 cfg80211 drm_kms_helper rfkill drm i2c_algo_bit wmi i2c_core soundcore video ac button battery acpi_cpufreq mperf power_supply processor usbhid hid ext3 mbcache jbd dm_mod sg sd_mod crc_t10dif firewire_ohci uhci_hcd thermal thermal_sys sdhci_pci sdhci firewire_core crc_itu_t ahci libahci ehci_hcd mmc_core libata scsi_mod usbcore e1000e usb_common [last unloaded: scs Apr 23 09:07:25 luzerne kernel: i_wait_scan] Apr 23 09:07:25 luzerne kernel: [ 168.088734] Pid: 172, comm: kworker/u:4 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2 Apr 23 09:07:25 luzerne kernel: [ 168.088737] Call Trace: Apr 23 09:07:25 luzerne kernel: [ 168.088745] [] ? warn_slowpath_common+0x78/0x8c Apr 23 09:07:25
Re: please advise on kernel upgrade text in release-notes
On Sat, Apr 6, 2013 at 08:19:11 +0200, Paul Gevers wrote: > Hi kernel team, > > Last week I stumbled upon the current text in the release-notes about > kernel/udev upgrade. If we don't update it, it says (among other things) > the text below [1]. I believe this text is obsolete and was ONLY meant > for the lenny to squeeze update. Do you agree that this part should be > removed? Or do you think it should be rewritten (in the latter case, can > you do a proposal)? If some of the current text stays, I say at least > the names wheezy and squeeze are wrong. > The upgrading chapter in the wheezy release notes is not yet written, so yes, much of it is obsolete and will go away. Cheers, Julien signature.asc Description: Digital signature
Bug#704690: linux-image-2.6.32-5-686: xserver-xorg-video-fbdev says (EE)open /dev/fb0: No such file or directory
On Thu, Apr 4, 2013 at 19:33:22 +0100, Philip wrote: > Exactly, that is my point. > > The squeeze-backports kernel WORKS. > The squeeze kernel linux-image-2.6.32-5-686 2.6.32-48squeeze1 DOES NOT WORK. > The kernel works just fine (or at least you haven't described in what way it "does not work"). It just has a different configuration, in particular i915 kms is disabled by default in squeeze, so needs to be explicitly enabled (on the command line or modprobe configuration). xserver-xorg-video-intel deos that, but since you don't have it installed... Closing as not a bug. Cheers, Julien signature.asc Description: Digital signature
Bug#704690: linux-image-2.6.32-5-686: xserver-xorg-video-fbdev says (EE)open /dev/fb0: No such file or directory
On Thu, Apr 4, 2013 at 18:30:08 +0100, Philip wrote: > lsmod, xorg and dmesg logs for SQUEEZE-BACKPORTS kernel (this works) > [...] > (II) FBDEV(0): hardware: inteldrmfb (video memory: 3072kB) That has KMS enabled. Still seems like everything's working as it should, as far as I can tell. Cheers, Julien signature.asc Description: Digital signature
Bug#704690: linux-image-2.6.32-5-686: xserver-xorg-video-fbdev says (EE)open /dev/fb0: No such file or directory
On Thu, Apr 4, 2013 at 17:57:05 +0100, Philip wrote: > Package: linux-2.6 > Version: 2.6.32-48squeeze1 > Severity: normal > > Unable to start Xorg using fbdev driver with this kernel. The Xorg fbdev driver requires a fb driver. If you disable i915 kms, that means enabling vesafb or similar... (IOW I'm not sure what you think the bug is.) Cheers, Julien signature.asc Description: Digital signature
Bug#704166: linux-image-3.2.0-4-amd64: BUG in led_trigger_event
On Thu, Mar 28, 2013 at 20:50:01 +0100, Julien Cristau wrote: > Package: src:linux > Version: 3.2.39-2 > Severity: important > > Hi, > > I got an oops when resuming from suspend. > > Picture from the console at > http://cristau.org/~julien/tmp/bug-led-trigger-event.jpg > basic transcript: BUG: unable to handle kernel paging request at ff4c IP: [] led_trigger_event+0x25/0x62 PGD 1607067 PUD 1608067 PMD 0 Oops: [#1] SMP CPU 0 Modules linked in: [can't be bothered] Pid: 31710, comm: kworker/0:0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.39-2 Dell Inc. Latitude E4200 /0XRV1h RIP: 0010:[] led_trigger_event+0x25/0x62 RSP: 0018:88003704be00 EFLAGS: 00010207 RAX: 0002 RBX: 0020 RCX: RDX: 88003704be38 RSI: RDI: 880074f57658 RBP: 880074f57640 R08: 8800b61908b0 R09: 88008c4f5b58 R10: 4001 R11: 88002da6b6c0 R12: R13: 880074f57660 R14: R15: 8800bce16905 FS: () GS:8800bce0() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: ff4c CR3: 8c63e000 CR4: 000406f0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process: kworker/0:0 (pid: 31710, threadinfo 88003704a000, task 88005b4d23c0) Stack: 88003704be38 8800b6190840 8800b6190840 8800bce16900 a00c6069 a00c6767 0282 8802 8800b61908a8 a00c6093 Call Trace: [] ? power_supply_am_i_supplied+0x18/0x18 [power_supply] [] ? power_supply_update_leds+0xcb/0x11f [power_supply] [] ? power_supply_changed_work+0x2a/0x40 [power_supply] [] ? process_one_work+0x163/0x284 [] ? worker_thread+0xc2/0x145 [] ? manage_workers.isra.25+0x15b/0x15b [] ? kthread+0x76/0x7e [] ? kernel_thread_helper+0x4/0x10 [] ? kthread_worker_fn+0x139/0x139 [] ? gs_change+0x13/0x13 Code: e9 be 23 de ff 90 41 55 48 85 ff 41 54 41 89 f4 55 48 89 fd 53 52 74 48 48 8d 7f 18 4c 8d 6d 20 e8 71 d7 0d 00 48 8b 5d 20 eb 2c <8b> b3 2c ff ff ff 41 39 f4 41 0f 46 f4 f6 83 30 ff ff ff 01 89 RIP [] led_trigger_event+0x25/0x62 RSP CR2: ff4c Cheers, Julien signature.asc Description: Digital signature
Bug#704166: linux-image-3.2.0-4-amd64: BUG in led_trigger_event
Package: src:linux Version: 3.2.39-2 Severity: important Hi, I got an oops when resuming from suspend. Picture from the console at http://cristau.org/~julien/tmp/bug-led-trigger-event.jpg Cheers, Julien -- Package-specific info: ** Version: Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-15) ) #1 SMP Debian 3.2.39-2 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/luzerne-root ro quiet ** Not tainted ** Kernel log: [4.046698] i915 :00:02.0: irq 46 for MSI/MSI-X [4.046706] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [4.046708] [drm] Driver supports precise vblank timestamp query. [4.046760] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [4.101750] iwlwifi :0c:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels [4.110505] input: Dell WMI hotkeys as /devices/virtual/input/input7 [4.118434] Linux media interface: v0.10 [4.122831] Linux video capture interface: v2.00 [4.129799] uvcvideo: Found UVC 1.00 device Integrated_Webcam_2M (0c45:63f3) [4.151142] input: Integrated_Webcam_2M as /devices/pci:00/:00:1a.7/usb1/1-6/1-6:1.0/input/input8 [4.153659] usbcore: registered new interface driver uvcvideo [4.153662] USB Video Class driver (1.1.1) [4.171382] iwlwifi :0c:00.0: firmware: agent loaded iwlwifi-5000-5.ucode into memory [4.171390] iwlwifi :0c:00.0: loaded firmware version 8.83.5.1 build 33692 [4.171681] Registered led device: phy0-led [4.179581] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [4.205186] cfg80211: World regulatory domain updated: [4.205190] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [4.205194] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [4.205198] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [4.205202] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [4.205206] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [4.205210] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [4.601689] fbcon: inteldrmfb (fb0) is primary device [4.653419] ACPI Error: Method parse/execution failed [\SMI_] (Node 8800b9263a10), AE_AML_INFINITE_LOOP (20110623/psparse-536) [4.653432] ACPI Error: Method parse/execution failed [\SMIE] (Node 8800b9275380), AE_AML_INFINITE_LOOP (20110623/psparse-536) [4.653440] ACPI Error: Method parse/execution failed [\NEVT] (Node 8800b9275498), AE_AML_INFINITE_LOOP (20110623/psparse-536) [4.653448] ACPI Error: Method parse/execution failed [\_SB_.PCI0.ISAB.ECDV._Q66] (Node 8800b9277650), AE_AML_INFINITE_LOOP (20110623/psparse-536) [4.693730] usb 2-1.3: new full-speed USB device number 5 using uhci_hcd [4.789089] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input9 [4.805799] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input10 [4.821724] usb 2-1.3: New USB device found, idVendor=413c, idProduct=8160 [4.821732] usb 2-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [4.821738] usb 2-1.3: Product: Dell Wireless 365 Bluetooth Module [4.821743] usb 2-1.3: Manufacturer: Dell Computer Corp [4.874261] Bluetooth: Core ver 2.16 [4.874287] NET: Registered protocol family 31 [4.874290] Bluetooth: HCI device and connection manager initialized [4.874293] Bluetooth: HCI socket layer initialized [4.874295] Bluetooth: L2CAP socket layer initialized [4.874300] Bluetooth: SCO socket layer initialized [4.876118] Bluetooth: Generic Bluetooth USB driver ver 0.6 [4.876513] usbcore: registered new interface driver btusb [5.339342] Console: switching to colour frame buffer device 160x50 [5.350180] fb0: inteldrmfb frame buffer device [5.350185] drm: registered panic notifier [5.383949] acpi device:34: registered as cooling_device2 [5.384754] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input11 [5.384863] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [5.384888] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. [5.384976] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [5.385108] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X [5.385145] snd_hda_intel :00:1b.0: setting latency timer to 64 [5.433208] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input12 [5.450147] HDMI status: Codec=2 Pin=3 Presence_Detect=0 ELD_Valid=0 [5.450480] input: HDA Intel HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input13 [5.450773] input: HDA Intel Mic
Bug#703506: GMA500: higher resolutions than 800x600 don't work
On Thu, Mar 21, 2013 at 12:03:56 -0700, Jonathan Nieder wrote: > I know Alan takes reports through bugzilla.kernel.org Still? I thought that would have kinda stopped after https://plus.google.com/04121194250082892/posts/KW3TdRYwjr9 Cheers, Julien signature.asc Description: Digital signature
Bug#703637: linux-image-3.2.0-4-amd64: Kernel Panic randomly after upgrade to 3.2.39-2
On Fri, Mar 22, 2013 at 01:32:07 +0800, SuperCat wrote: > Package: src:linux > Version: 3.2.39-2 > Severity: important > > Dear Maintainer, > I got kernel panic randomly after I upgrade the kernel from 3.2.35 to > 3.2.39-2. > I have tried to rollback the kernel to 3.2.35, and the kernel works fine > again. > Please provide a log or image of the panic message. > ** Command line: > BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 > root=UUID=713ff01f-7459-40f3-91b0-0192dac30afc ro i915.i915_enable_rc6=1 > i915.i915_enable_fbc=1 i915.lvds_downclock=1 quiet i915.i915_enable_rc6=1 > i915.i915_enable_fbc=1 i915.lvds_downclock=1 > And please remove these i915 options from your kernel command line. There's a reason they're not the default. Cheers, Julien signature.asc Description: Digital signature
Bug#703506: GMA500: higher resolutions than 800x600 don't work
On Wed, Mar 20, 2013 at 22:58:41 -0700, Jonathan Nieder wrote: > Hi again, > > I left out the URL for Intel's bug reporting guidelines: > > Jonathan Nieder wrote: > > Georg Sassen wrote: > > >> While the native resolution (1280x720) worked fine until kernel > >> version 3.2.0.4-686-pae_3.2.35-2, I now only have 800x600 resolution > >> in X11 and the initial framebuffer now on my Nokia Booklet 3G since > >> the update. > > > > Thanks for reporting. Can you reproduce this using > > xserver-xorg-video-modesetting and the 3.8.y kernel from experimental > > as well? > > > > If so, please file a report upstream at bugzilla.kernel.org, product > > Drivers, component Video(DRI - Intel) with the information described > > at [1] and let us know the bug number so we can track it. > > [1] https://01.org/linuxgraphics/documentation/how-report-bugs-0 > That's for i915. psb is not maintained by the same team. So I'm not sure these instructions are appropriate. Cheers, Julien signature.asc Description: Digital signature
Bug#665000: Workaround for this bug
On Wed, Mar 20, 2013 at 22:28:24 +0800, Thomas Goirand wrote: > Hi, > > On one of my server, I had the issue as well. I'm not sure if it's the > exact same one, but at least I fixed it. > > What happened for me was that my KVM over IP was printing "No signal" > just right after the login prompt (eg: the rest of the boot process > seemed to not be bothered). Then I did: > > dpkg-reconfigure grub-pc > > and added: > > radeon.modeset=0 > > to the linux command line. After doing that, then I was able to see my > text mode login prompt (which is the only thing I care for a server, I > will never care about X support...). > > Though, I am wondering if the issue isn't simply that the kernel is > trying to set a mode which is higher than what my KVM over IP can > support. How can I choose such mode (which would be a better fix)? Do > you know Ben, maybe? > KMS drivers should honor modes specified with the video= boot parameter. Optionally on a per-connector basis, e.g. "video=VGA-1:800x600". Cheers, Julien signature.asc Description: Digital signature
Re: Bug#680514: xserver-xorg-video-intel: X locks up with EQ overflow
On Sat, Mar 16, 2013 at 12:39:30 +0200, Modestas Vainius wrote: > Package: xserver-xorg-video-intel > Version: 2:2.19.0-6 > Followup-For: Bug #680514 > > Hello, > > I have started seeing this bug after upgrading kernel to linux 3.2.39-* series > of packages. I have never seen this issue with linux-image-3.2.0-4-amd64 > 3.2.35-2 (which I have downgraded to now) or earlier. > > With 3.2.39-2 X on this Dell Latitude E5420 laptop locks up quite predictably > at least twice a day which makes it basically unusable. Given 3.2.39-2 has > already migrated to wheezy, I see this as pontentially big issue. > This bug (680514) was reported against earlier versions, so there's a good chance yours is different. Please file a separate bug. Also include dmesg from when that happens, and i915_error_state from debugfs (https://01.org/linuxgraphics/documentation/how-get-gpu-error-state). Cheers, Julien signature.asc Description: Digital signature
