Bug#826614: CONFIG_MAC_SCSI and CONFIG_MAC8390 are set to 'y'
I checked the kernel builds in snapshot.debian.org, and all of the Linux builds that were archived since this bug report was opened 8 months ago still exhibit the same problem. If the BTS is the wrong way to have this issue addressed, would someone please refer me to some instructions for bringing this sort of issue to the attention of the appropriate developers, i.e. someone willing to consider both the problem and the solution and then respond? Thanks in advance.
Bug#854066: Severitiy set to non-rc
On Sun, 2017-02-05 at 19:07 +0100, Patrick Matthäi wrote: > Hi Ben, > > first thanks for your good work for Debian especially for the Linux kernel! > > But with #854066 I have to disagree / argue with you. You lowered the > severity to a non rc bug, but it is in my eyes. You claimed this was RC due to "data loss", but that depends on having a reasonable expectation that the data was persistent. As you only described a crash/hang, and not corruption of persistent storage, you did not justify the RC status. > At the moment we have got a project: Linux instead of Windows on Desktops > for Developers. > > So we switched many of our employe to Debian stretch (jessie would be > too old) and I have got an eye on the daily updates. With 4.9.x one > desktop (individual) does not boot at all, have to acc. it again. All > other desktopts do not wake up anymore (kernel panic?) if they fall in > sleep. > > This is rc for me, if you think not, why? Many different hardware types > are affected You said "All PCs do have got the same GPU", so it sounds like this does not affect a very large range of systems. But if this is a very common GPU then this could be RC. Ben. -- Ben Hutchings A free society is one where it is safe to be unpopular. - Adlai Stevenson signature.asc Description: This is a digitally signed message part
Bug#854066: linux-image-4.9.0-1-amd64: Several HP desktops do not wake up anymore since 4.9
Hi Patrick On Fri, Feb 03, 2017 at 04:46:40PM +0100, Patrick Matthäi wrote: > Justification: causes non-serious data loss > Severity: grave Please show how it produces data loss. Output of fsck will help. > ** Tainted: OE (12288) > * Out-of-tree module has been loaded. > ** Loaded modules: > vboxpci(OE) > vboxnetadp(OE) > vboxnetflt(OE) > vboxdrv(OE) Please remove this out-of-tree modules. This modules are of questionable quality. We can't and won't support them. Regards, Bastian -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0
Bug#854066: Severitiy set to non-rc
Hi Ben, first thanks for your good work for Debian especially for the Linux kernel! But with #854066 I have to disagree / argue with you. You lowered the severity to a non rc bug, but it is in my eyes. At the moment we have got a project: Linux instead of Windows on Desktops for Developers. So we switched many of our employe to Debian stretch (jessie would be too old) and I have got an eye on the daily updates. With 4.9.x one desktop (individual) does not boot at all, have to acc. it again. All other desktopts do not wake up anymore (kernel panic?) if they fall in sleep. This is rc for me, if you think not, why? Many different hardware types are affected ||
Bug#854281: Crash because of NULL pointer dereference in `pick_next_task_fair`
Package: linux-image-3.16.0-4-amd64 Version: 3.16.39-1 Severity: important Dear Debian folks, Linux 3.16.39 and earlier crash almost daily with the trace below. ``` Feb 04 10:05:58 fujitsu01 kernel: BUG: unable to handle kernel NULL pointer dereference at 0078 Feb 04 10:05:58 fujitsu01 kernel: IP: [] pick_next_task_fair+0x6b8/0x820 Feb 04 10:05:58 fujitsu01 kernel: PGD d700be067 PUD c681b8067 PMD 0 Feb 04 10:05:58 fujitsu01 kernel: Oops: [#1] SMP Feb 04 10:05:58 fujitsu01 kernel: Modules linked in: ipt_REJECT binfmt_misc veth xt_nat xt_tcpudp ipt_MASQUERADE xfrm_user xfrm_algo iptab le_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack bridge stp llc xt_multiport iptable_filter ip_tables x_tables x86_pkg_temp_thermal coretemp evdev ppdev kvm_intel kvm crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk _helper cryptd pcspkr serio_raw shpchp tpm_tis tpm wmi parport_pc parport fujitsu_laptop video acpi_cpufreq acpi_pad processor button autofs 4 btrfs xor raid6_pq crct10dif_pclmul crct10dif_common crc32c_intel ahci libahci e1000e psmouse xhci_hcd ptp libata pps_core nvme usbcore sc si_mod usb_common thermal fan thermal_sys i2c_hid hid i2c_core Feb 04 10:05:58 fujitsu01 kernel: CPU: 4 PID: 28 Comm: ksoftirqd/4 Not tainted 3.16.0-4-amd64 #1 Debian 3.16.39-1 Feb 04 10:05:58 fujitsu01 kernel: Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0 for D3417-B1x02/09/ 2016 Feb 04 10:05:58 fujitsu01 kernel: task: 880fde868c20 ti: 880fde87 task.ti: 880fde87 Feb 04 10:05:58 fujitsu01 kernel: RIP: 0010:[] [] pick_next_task_fair+0x6b8/0x820 Feb 04 10:05:58 fujitsu01 kernel: RSP: 0018:880fde873de0 EFLAGS: 00010046 Feb 04 10:05:58 fujitsu01 kernel: RAX: 00012279 RBX: 880fdaafd1c0 RCX: Feb 04 10:05:58 fujitsu01 kernel: RDX: 0001 RSI: 880fdb0d3f28 RDI: 880f23500c98 Feb 04 10:05:58 fujitsu01 kernel: RBP: 880fdb0d3f00 R08: R09: b80a Feb 04 10:05:58 fujitsu01 kernel: R10: 021f R11: 0008 R12: Feb 04 10:05:58 fujitsu01 kernel: R13: R14: R15: 88102e512f40 Feb 04 10:05:58 fujitsu01 kernel: FS: () GS:88102e50() knlGS: Feb 04 10:05:58 fujitsu01 kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 04 10:05:58 fujitsu01 kernel: CR2: 0078 CR3: 000c209f9000 CR4: 003407e0 Feb 04 10:05:58 fujitsu01 kernel: DR0: DR1: DR2: Feb 04 10:05:58 fujitsu01 kernel: DR3: DR6: fffe0ff0 DR7: 0400 Feb 04 10:05:58 fujitsu01 kernel: Stack: Feb 04 10:05:58 fujitsu01 kernel: 880f23500c20 0001810a0964 880fde868c20 00012f40 Feb 04 10:05:58 fujitsu01 kernel: 88102e512fb8 8101ca75 880fde869078 880fde868c20 Feb 04 10:05:58 fujitsu01 kernel: 88102e512f40 0004 Feb 04 10:05:58 fujitsu01 kernel: Call Trace: Feb 04 10:05:58 fujitsu01 kernel: [] ? sched_clock+0x5/0x10 Feb 04 10:05:58 fujitsu01 kernel: [] ? __schedule+0x106/0x6f0 Feb 04 10:05:58 fujitsu01 kernel: [] ? smpboot_thread_fn+0xc6/0x190 Feb 04 10:05:58 fujitsu01 kernel: [] ? SyS_setgroups+0x170/0x170 Feb 04 10:05:58 fujitsu01 kernel: [] ? kthread+0xbd/0xe0 Feb 04 10:05:58 fujitsu01 kernel: [] ? kthread_create_on_node+0x180/0x180 Feb 04 10:05:58 fujitsu01 kernel: [] ? ret_from_fork+0x58/0x90 Feb 04 10:05:58 fujitsu01 kernel: [] ? kthread_create_on_node+0x180/0x180 Feb 04 10:05:58 fujitsu01 kernel: Code: 49 8b 7c 24 78 48 39 fd 74 2f 44 8b 73 68 45 8b 6c 24 68 45 39 ee 0f 8e c7 00 00 00 48 89 ef 48 89 de e8 ac 91 ff ff 48 8b 5b 70 <49> 8b 7c 24 78 48 8b 6b 78 48 39 fd 75 d1 48 85 ed 74 cc 4c 89 Feb 04 10:05:58 fujitsu01 kernel: RIP [] pick_next_task_fair+0x6b8/0x820 ``` Please find all Linux kernel messages attached. There is a similar report on the Linux kernel mailing list (LKML) [1] for Linux 3.10.0. Please tell me, if you need more information, or how I can help to get a fix submitted. Thanks, Paul [1] https://lkml.org/lkml/2016/5/31/990Feb 03 09:57:13 barberini01 kernel: Initializing cgroup subsys cpuset Feb 03 09:57:13 barberini01 kernel: Initializing cgroup subsys cpu Feb 03 09:57:13 barberini01 kernel: Initializing cgroup subsys cpuacct Feb 03 09:57:13 barberini01 kernel: Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.39-1 (2016-12-30) Feb 03 09:57:13 barberini01 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 root=UUID=37c4a852-27a8-40da-bfc5-03a047fd8faa ro quiet noisapnp cgroup_enable=memory swapaccount=1 Feb 03 09:57:13 barberini01 kernel: e820: BIOS-provided physical RAM map: Feb 03 09:57:13 barberini01 kernel: B
Processed: Re: btrfs-tools: btrfs device stats show error (no such device) for newly added disk until FS remount
Processing commands for cont...@bugs.debian.org:
> reassign 724951 linux
Bug #724951 {Done: Hideki Yamane } [linux] btrfs-tools:
btrfs device stats show error (no such device) for newly added disk until FS
remount
Ignoring request to reassign bug #724951 to the same package
> fixed 724951 3.13~rc6-1~exp1
Bug #724951 {Done: Hideki Yamane } [linux] btrfs-tools:
btrfs device stats show error (no such device) for newly added disk until FS
remount
There is no source info for the package 'linux' at version '3.13~rc6-1~exp1'
with architecture ''
Unable to make a source version for version '3.13~rc6-1~exp1'
Ignoring request to alter fixed versions of bug #724951 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
724951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: RE: btrfs-progs: btrfs filesystem defrag order of arguments different results
Processing commands for cont...@bugs.debian.org: > reassign 724951 linux Bug #724951 [btrfs-tools] btrfs-tools: btrfs device stats show error (no such device) for newly added disk until FS remount Bug reassigned from package 'btrfs-tools' to 'linux'. No longer marked as found in versions btrfs-tools/0.19+20130705-2. Ignoring request to alter fixed versions of bug #724951 to the same values previously set > fixed 724951 3.13~rc6-1~exp1 Bug #724951 [linux] btrfs-tools: btrfs device stats show error (no such device) for newly added disk until FS remount There is no source info for the package 'linux' at version '3.13~rc6-1~exp1' with architecture '' Unable to make a source version for version '3.13~rc6-1~exp1' Marked as fixed in versions 3.13~rc6-1~exp1. > thanks Stopping processing here. Please contact me if you need assistance. -- 724951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#724951: marked as done (btrfs-tools: btrfs device stats show error (no such device) for newly added disk until FS remount)
Your message dated Mon, 06 Feb 2017 01:21:32 +0900 with message-id <1486311692.11965.4.ca...@gmail.com> and subject line RE: btrfs-progs: btrfs filesystem defrag order of arguments different results has caused the Debian Bug report #724951, regarding btrfs-tools: btrfs device stats show error (no such device) for newly added disk until FS remount to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 724951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: btrfs-tools Version: 0.19+20130705-2 Severity: normal When new disk added to btrfs volume, right after adding 'btrfs device stats' failing: ERROR: ioctl(BTRFS_IOC_GET_DEV_STATS) on /dev/sdg1 failed: No such device home:/home/amarao# btrfs device remove /dev/sdg1 /media/JBOD/ If filesystem after device adding is unmounted and mounted back everything is ok. Log to reproduce: # btrfs device add /dev/sdg1 /media/JBOD/ # btrfs device stats /media/JBOD/ [/dev/sdb1].write_io_errs 0 [/dev/sdb1].read_io_errs0 [/dev/sdb1].flush_io_errs 0 [/dev/sdb1].corruption_errs 0 [/dev/sdb1].generation_errs 0 [/dev/sdc1].write_io_errs 0 [/dev/sdc1].read_io_errs0 [/dev/sdc1].flush_io_errs 0 [/dev/sdc1].corruption_errs 0 [/dev/sdc1].generation_errs 0 [/dev/sdd1].write_io_errs 0 [/dev/sdd1].read_io_errs0 [/dev/sdd1].flush_io_errs 0 [/dev/sdd1].corruption_errs 0 [/dev/sdd1].generation_errs 0 [/dev/sde1].write_io_errs 0 [/dev/sde1].read_io_errs0 [/dev/sde1].flush_io_errs 0 [/dev/sde1].corruption_errs 0 [/dev/sde1].generation_errs 0 [/dev/sdf1].write_io_errs 0 [/dev/sdf1].read_io_errs0 [/dev/sdf1].flush_io_errs 0 [/dev/sdf1].corruption_errs 0 [/dev/sdf1].generation_errs 0 ERROR: ioctl(BTRFS_IOC_GET_DEV_STATS) on /dev/sdg1 failed: No such device # btrfs device delete /dev/sdg1 /media/JBOD/ # btrfs device add /dev/sdg1 /media/JBOD/ # umount /media/JBOD/ # mount /dev/sdb1 /media/JBOD/ # btrfs device stats /media/JBOD/ [/dev/sdb1].write_io_errs 0 [/dev/sdb1].read_io_errs0 [/dev/sdb1].flush_io_errs 0 [/dev/sdb1].corruption_errs 0 [/dev/sdb1].generation_errs 0 [/dev/sdc1].write_io_errs 0 [/dev/sdc1].read_io_errs0 [/dev/sdc1].flush_io_errs 0 [/dev/sdc1].corruption_errs 0 [/dev/sdc1].generation_errs 0 [/dev/sdd1].write_io_errs 0 [/dev/sdd1].read_io_errs0 [/dev/sdd1].flush_io_errs 0 [/dev/sdd1].corruption_errs 0 [/dev/sdd1].generation_errs 0 [/dev/sde1].write_io_errs 0 [/dev/sde1].read_io_errs0 [/dev/sde1].flush_io_errs 0 [/dev/sde1].corruption_errs 0 [/dev/sde1].generation_errs 0 [/dev/sdf1].write_io_errs 0 [/dev/sdf1].read_io_errs0 [/dev/sdf1].flush_io_errs 0 [/dev/sdf1].corruption_errs 0 [/dev/sdf1].generation_errs 0 [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 0 [/dev/sdg1].generation_errs 0 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages btrfs-tools depends on: ii e2fslibs1.42.8-1 ii libblkid1 2.20.1-5.5 ii libc6 2.17-93 ii libcomerr2 1.42.8-1 ii liblzo2-2 2.06-1.2 ii libuuid12.20.1-5.5 ii zlib1g 1:1.2.8.dfsg-1 btrfs-tools recommends no packages. btrfs-tools suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- reassign 724951 linux fixed 724951 3.13~rc6-1~exp1 thanks It's not btrfs-progs bug but linux. I've confirmed this with 3.11.10-1 and 3.12.9-1, and not in 3.13~rc6-1~exp1.--- End Message ---
Bug#854231: Add Information
Rest of Message: -- Package-specific info: ** Version: Linux version 4.9.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.9.2-2~bpo8+1 (2017-01-26) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.1-amd64 root=UUID=808992a4-a439-4c52-8f40-154f1d7fd66e ro iommu=noagp security=apparmor quiet ** Tainted: PWOE (12801) * Proprietary module has been loaded. * Taint on warning. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [ 13.735576] CPU: 1 PID: 525 Comm: setserial Tainted: P OE 4.9.0-0.bpo.1-amd64 #1 Debian 4.9.2-2~bpo8+1 [ 13.735578] Hardware name: MSI MS-7369/MS-7369, BIOS V2.9 03/17/2009 [ 13.735582] 9ff2a1f5 a31c01103ad8 [ 13.735589] 9fc77884 a0b47e98 a31c01103b30 a0b47e98 [ 13.735595] 9142269f0bf4 914226884c00 9fc778ff [ 13.735600] Call Trace: [ 13.735611] [] ? dump_stack+0x5c/0x77 [ 13.735619] [] ? __warn+0xc4/0xe0 [ 13.735624] [] ? warn_slowpath_fmt+0x5f/0x80 [ 13.735629] [] ? __list_add+0xab/0xb0 [ 13.735636] [] ? univ8250_setup_irq+0x149/0x250 [ 13.735641] [] ? serial8250_do_startup+0x188/0x6d0 [ 13.735645] [] ? uart_startup.part.18+0x5f/0x140 [ 13.735651] [] ? tty_port_open+0x86/0xd0 [ 13.735655] [] ? uart_open+0x37/0x50 [ 13.735659] [] ? tty_open+0xeb/0x670 [ 13.735665] [] ? chrdev_open+0xbe/0x190 [ 13.735668] [] ? cdev_put+0x20/0x20 [ 13.735673] [] ? do_dentry_open+0x1d3/0x2e0 [ 13.735680] [] ? path_openat+0x2e9/0x14e0 [ 13.735686] [] ? page_add_file_rmap+0x11/0x120 [ 13.735690] [] ? do_filp_open+0x91/0x100 [ 13.735694] [] ? handle_mm_fault+0xdd0/0x1650 [ 13.735698] [] ? __check_object_size+0x10b/0x1dc [ 13.735703] [] ? do_sys_open+0x127/0x210 [ 13.735710] [] ? system_call_fast_compare_end+0xc/0x9b [ 13.735714] ---[ end trace bf866f96a65b60aa ]--- [ 13.740470] [ cut here ] [ 13.740487] WARNING: CPU: 1 PID: 527 at /home/zumbi/linux-4.9.2/lib/list_debug.c:36 __list_add+0xab/0xb0 [ 13.740490] list_add double add: new=a0b480b0, prev=a0b480b0, next=a0b480b0. [ 13.740491] Modules linked in: joydev snd_hda_codec_realtek(+) snd_hda_codec_generic powernow_k8 edac_mce_amd edac_core kvm_amd evdev pcspkr serio_raw kvm irqbypass snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm_oss snd_mixer_oss k8temp parport_serial snd_pcm button snd_timer snd soundcore shpchp i2c_nforce2 acpi_cpufreq tpm_tis tpm_tis_core tpm nvidia(POE) drm w83627ehf hwmon_vid fuse parport_pc ppdev lp parport autofs4 ext4 crc16 jbd2 fscrypto mbcache dm_mirror dm_region_hash dm_log dm_mod uas usb_storage hid_logitech_hidpp hid_logitech_dj usbhid hid sg sd_mod sr_mod cdrom psmouse r8169 mii ohci_pci ahci libahci libata fjes ohci_hcd scsi_mod ehci_pci ehci_hcd usbcore usb_common [ 13.740586] CPU: 1 PID: 527 Comm: setserial Tainted: PW OE 4.9.0-0.bpo.1-amd64 #1 Debian 4.9.2-2~bpo8+1 [ 13.740588] Hardware name: MSI MS-7369/MS-7369, BIOS V2.9 03/17/2009 [ 13.740592] 9ff2a1f5 a31c01103ad8 [ 13.740598] 9fc77884 a0b480b0 a31c01103b30 a0b480b0 [ 13.740603] 9142290ec334 91422689b000 9fc778ff [ 13.740608] Call Trace: [ 13.740620] [] ? dump_stack+0x5c/0x77 [ 13.740628] [] ? __warn+0xc4/0xe0 [ 13.740633] [] ? warn_slowpath_fmt+0x5f/0x80 [ 13.740638] [] ? __list_add+0xab/0xb0 [ 13.740645] [] ? univ8250_setup_irq+0x149/0x250 [ 13.740650] [] ? serial8250_do_startup+0x188/0x6d0 [ 13.740654] [] ? uart_startup.part.18+0x5f/0x140 [ 13.740660] [] ? tty_port_open+0x86/0xd0 [ 13.740664] [] ? uart_open+0x37/0x50 [ 13.740668] [] ? tty_open+0xeb/0x670 [ 13.740673] [] ? chrdev_open+0xbe/0x190 [ 13.740677] [] ? cdev_put+0x20/0x20 [ 13.740681] [] ? do_dentry_open+0x1d3/0x2e0 [ 13.740688] [] ? path_openat+0x2e9/0x14e0 [ 13.740695] [] ? page_add_file_rmap+0x11/0x120 [ 13.740699] [] ? do_filp_open+0x91/0x100 [ 13.740703] [] ? handle_mm_fault+0xdd0/0x1650 [ 13.740707] [] ? __check_object_size+0x10b/0x1dc [ 13.740712] [] ? do_sys_open+0x127/0x210 [ 13.740719] [] ? system_call_fast_compare_end+0xc/0x9b [ 13.740722] ---[ end trace bf866f96a65b60ab ]--- [ 13.853856] input: HDA Digital PCBeep as /devices/pci:00/:00:07.0/sound/card0/input8 [ 13.854783] input: HDA NVidia Front Mic as /devices/pci:00/:00:07.0/sound/card0/input9 [ 13.854959] input: HDA NVidia Rear Mic as /devices/pci:00/:00:07.0/sound/card0/input10 [ 13.855137] input: HDA NVidia Line as /devices/pci:00/:00:07.0/sound/card0/input11 [ 13.855305] input: HDA NVidia Line Out Front as /devices/pci:00/:00:07.0/sound/card0/input12 [ 13.855477] input: HDA NVidia Line Out Surround as /devices/pci:00/:00:07.0/soun
Bug#854231: linux-image-4.9.0-0.bpo.1-amd64: setserial traces while booting with 4.9.0, bpo kernel
Package: src:linux Version: 4.9.2-2~bpo8+1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrading from linux-image-4.8.15 to Linux-image-4.9.2 * What exactly did you do (or not do) that was effective (or ineffective)? Nothing but booting Got in contact with greg KH, to much differences in source for inspection. Weitergeleitete Nachricht Betreff:Message with no Package: tag cannot be processed! (linux-image-4.9.0-0.bpo.1-amd64: setserial traces while booting with 4.9.0, bpo kernel) Datum: Sat, 04 Feb 2017 12:54:01 + Von:Debian Bug Tracking System An: Wolfgang Schnitker Your message didn't have a Package: line at the very first line of the mail body (part of the pseudo-header), or didn't have a Package: line at all. Unfortunatly, this means that your message has been ignored completely. Without this information we are unable to categorise or otherwise deal with your problem report. Please _resubmit_ your report to sub...@bugs.debian.org and tell us which package the report is for. For help, check out http://www.debian.org/Bugs/Reporting. Your message was dated Sat, 4 Feb 2017 13:52:19 +0100 and had message-id and subject linux-image-4.9.0-0.bpo.1-amd64: setserial traces while booting with 4.9.0, bpo kernel. The complete text of it is attached to this message. If you need any assistance or explanation please contact ow...@bugs.debian.org and include the the attached message. If you didn't send the attached message (spam was sent forging your from address), we apologize; please disregard this message. -- -1: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=-1 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Wolfgang Schnitker To: Debian Bug Tracking System Subject: linux-image-4.9.0-0.bpo.1-amd64: setserial traces while booting with 4.9.0 bpo kernel Message-ID: <20170204124554.7321.53791.reportbug@rocket2> X-Mailer: reportbug 6.6.3 Date: Sat, 04 Feb 2017 13:45:54 +0100 Package: src:linux Version: 4.9.2-2~bpo8+1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- Package-specific info: ** Version: Linux version 4.9.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.9.2-2~bpo8+1 (2017-01-26) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.1-amd64 root=UUID=808992a4-a439-4c52-8f40-154f1d7fd66e ro iommu=noagp security=apparmor quiet ** Tainted: PWOE (12801) * Proprietary module has been loaded. * Taint on warning. * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: [ 13.735576] CPU: 1 PID: 525 Comm: setserial Tainted: P OE 4.9.0-0.bpo.1-amd64 #1 Debian 4.9.2-2~bpo8+1 [ 13.735578] Hardware name: MSI MS-7369/MS-7369, BIOS V2.9 03/17/2009 [ 13.735582] 9ff2a1f5 a31c01103ad8 [ 13.735589] 9fc77884 a0b47e98 a31c01103b30 a0b47e98 [ 13.735595] 9142269f0bf4 914226884c00 9fc778ff [ 13.735600] Call Trace: [ 13.735611] [] ? dump_stack+0x5c/0x77 [ 13.735619] [] ? __warn+0xc4/0xe0 [ 13.735624] [] ? warn_slowpath_fmt+0x5f/0x80 [ 13.735629] [] ? __list_add+0xab/0xb0 [ 13.735636] [] ? univ8250_setup_irq+0x149/0x250 [ 13.735641] [] ? serial8250_do_startup+0x188/0x6d0 [ 13.735645] [] ? uart_startup.part.18+0x5f/0x140 [ 13.735651] [] ? tty_port_open+0x86/0xd0 [ 13.735655] [] ? uart_open+0x37/0x50 [ 13.735659] [] ? tty_open+0xeb/0x670 [ 13.735665] [] ? chrdev_open+0xbe/0x190 [ 13.735668] [] ? cdev_put+0x20/0x20 [ 13.735673] [] ? do_dentry_open+0x1d3/0x2e0 [ 13.735680] [] ? path_openat+0x2e9/0x14e0 [ 13.735686] [] ? page_add_file_rmap+0x11/0x120 [ 13.735690] [] ? do_filp_open+0x91/0x100 [ 13.735694] [] ? handle_mm_fault+0xdd0/0x1650 [ 13.735698] [] ? __check_object_size+0x10b/0x1dc [ 13.735703] [] ? do_sys_open+0x127/0x210 [ 13.735710] [] ? system_call_fast_compare_end+0xc/0x9b [ 13.735714] ---[ end trace bf866f96a65b60aa ]--- [ 13.740470] [ cut here ] [ 13.740487] WARNING: CPU: 1 PID: 527 at /home/zumbi/linux-4.9.2/lib/list_debug.c:36 __list_add+0xab/0xb0 [ 13.740490] list_add double add: new=a0b480b0, prev=a0b480b0, next=a0b480b0. [ 13.740491] Modules linked in: joydev snd_hda_codec_realtek(+) snd_hda_codec_generic powernow_k8 edac_mce_amd edac_c
