Bug#814855: linux-image-4.4.0-trunk-amd64: Please restore snd-emu10k1 module

[Ben Hutchings]

Control: tag -1 wontfix

On Tue, 2016-02-16 at 01:20 +0100, Kacper Berent wrote:
> Package: src:linux
> Version: 4.4.1-1~exp1
> Severity: normal
> 
> Hello,
> 
> description is simple: I have no sound on my old SoundBlaster because the
> module snd-emu10k1 does not exist in 4.4.1-1~exp1. Please restore it.
> 
> This removal does not seem to be following of upstream:
> http://git.kernel.org/cgit/linux/kernel/git/stable/linux-
> stable.git/tree/sound/pci/emu10k1?h=v4.4.1

It's mentioned in the changelog:

 * [amd64] mm,nvdimm: Disable ZONE_DMA; enable ZONE_DEVICE, NVDIMM_PFN
- This disables drivers for some AC'97 sound cards

Ben.

-- 
Ben Hutchings
Life is what happens to you while you're busy making other plans.
   - John Lennon

signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#814855: linux-image-4.4.0-trunk-amd64: Please restore snd-emu10k1 module

[Debian Bug Tracking System]

Processing control commands:

> tag -1 wontfix
Bug #814855 [src:linux] linux-image-4.4.0-trunk-amd64: Please restore 
snd-emu10k1 module
Added tag(s) wontfix.

-- 
814855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#814855: linux-image-4.4.0-trunk-amd64: Please restore snd-emu10k1 module

[Kacper Berent]

Package: src:linux
Version: 4.4.1-1~exp1
Severity: normal

Hello,

description is simple: I have no sound on my old SoundBlaster because the
module snd-emu10k1 does not exist in 4.4.1-1~exp1. Please restore it.

This removal does not seem to be following of upstream:
http://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/tree/sound/pci/emu10k1?h=v4.4.1

Regards



-- Package-specific info:
** Version:
Linux version 4.4.0-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 
5.3.1 20160205 (Debian 5.3.1-8) ) #1 SMP Debian 4.4.1-1~exp1 (2016-02-10)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.4.0-trunk-amd64 
root=UUID=80358fab-9579-4fd1-b94c-939cdca4a92f ro resume=/dev/sda3 
init=/bin/systemd

** Not tainted

** Kernel log:
[ 3492.108897] traps: nm-applet[1372] general protection ip:7f9a9c3877bd 
sp:7ffe96be7b38 error:0 in libgobject-2.0.so.0.4600.2[7f9a9c353000+51000]
[ 3529.705535] usb 1-7: new high-speed USB device number 7 using ehci-pci
[ 3529.727901] usb 1-7: New USB device found, idVendor=0fce, idProduct=51ba
[ 3529.727913] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3529.727919] usb 1-7: Product: D6633
[ 3529.727925] usb 1-7: Manufacturer: Sony
[ 3529.727930] usb 1-7: SerialNumber: CB5A21V7A5
[ 3536.250239] usb 1-7: USB disconnect, device number 7
[ 3536.587069] usb 1-7: new high-speed USB device number 8 using ehci-pci
[ 3536.609085] usb 1-7: New USB device found, idVendor=0fce, idProduct=81ba
[ 3536.609096] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3536.609103] usb 1-7: Product: D6633
[ 3536.609108] usb 1-7: Manufacturer: Sony
[ 3536.609113] usb 1-7: SerialNumber: CB5A21V7A5
[ 3536.613600] rndis_host 1-7:1.0 usb0: register 'rndis_host' at 
usb-:00:02.1-7, RNDIS device, 02:72:14:02:00:07
[ 3536.644866] rndis_host 1-7:1.0 enx027214020007: renamed from usb0
[ 3536.657970] IPv6: ADDRCONF(NETDEV_UP): enx027214020007: link is not ready
[ 3581.295361] fuse init (API version 7.23)
[13790.916137] usb 1-7: USB disconnect, device number 8
[13790.917529] rndis_host 1-7:1.0 enx027214020007: unregister 'rndis_host' 
usb-:00:02.1-7, RNDIS device
[18978.403793] usb 1-7: new high-speed USB device number 9 using ehci-pci
[18978.425844] usb 1-7: New USB device found, idVendor=0fce, idProduct=51ba
[18978.425856] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[18978.425862] usb 1-7: Product: D6633
[18978.425868] usb 1-7: Manufacturer: Sony
[18978.425873] usb 1-7: SerialNumber: CB5A21V7A5
[18982.318635] usb 1-7: USB disconnect, device number 9
[19030.056247] usb 2-7: new full-speed USB device number 3 using ohci-pci
[19030.108270] usb 2-7: New USB device found, idVendor=0421, idProduct=00aa
[19030.108281] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19030.108288] usb 2-7: Product: Nokia E71
[19030.108294] usb 2-7: Manufacturer: Nokia
[19030.108299] usb 2-7: SerialNumber: 352924029695959
[19030.160026] usb-storage 2-7:1.0: USB Mass Storage device detected
[19030.160122] scsi host6: usb-storage 2-7:1.0
[19030.160242] usbcore: registered new interface driver usb-storage
[19030.161346] usbcore: registered new interface driver uas
[19031.169246] scsi 6:0:0:0: Direct-Access NokiaE71  1.0  
PQ: 0 ANSI: 0
[19031.170394] sd 6:0:0:0: Attached scsi generic sg2 type 0
[19031.193175] sd 6:0:0:0: [sdc] 61495296 512-byte logical blocks: (31.4 
GB/29.3 GiB)
[19031.203222] sd 6:0:0:0: [sdc] Write Protect is off
[19031.203235] sd 6:0:0:0: [sdc] Mode Sense: 03 00 00 00
[19031.210219] sd 6:0:0:0: [sdc] No Caching mode page found
[19031.210232] sd 6:0:0:0: [sdc] Assuming drive cache: write through
[19031.254229]  sdc:
[19031.299216] sd 6:0:0:0: [sdc] Attached SCSI removable disk
[19064.673714] usb 2-7: USB disconnect, device number 3
[19096.863629] usb 2-7: new full-speed USB device number 4 using ohci-pci
[19096.915589] usb 2-7: New USB device found, idVendor=0421, idProduct=00aa
[19096.915601] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[19096.915608] usb 2-7: Product: Nokia E71
[19096.915613] usb 2-7: Manufacturer: Nokia
[19096.915618] usb 2-7: SerialNumber: 352924029695959
[19096.924708] usb-storage 2-7:1.0: USB Mass Storage device detected
[19096.925228] scsi host7: usb-storage 2-7:1.0
[19097.932574] scsi 7:0:0:0: Direct-Access NokiaE71  1.0  
PQ: 0 ANSI: 0
[19097.933776] sd 7:0:0:0: Attached scsi generic sg2 type 0
[19097.956487] sd 7:0:0:0: [sdc] 61495296 512-byte logical blocks: (31.4 
GB/29.3 GiB)
[19097.963577] sd 7:0:0:0: [sdc] Write Protect is off
[19097.963590] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
[19097.970615] sd 7:0:0:0: [sdc] No Caching mode page found
[19097.970631] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[19098.020584]  sdc:
[19098.063551] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[19113.216311] usb 2-7: USB disconnect, device number 4
[19137.084843] usb 2-7: new full-speed USB device number 5 using ohci-pci

Bug#794520: E555: backlight

[Raphaël]

worth mentioning https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450044
which, tragically, was assigned to systemd.

Processed: Re: Bug#812196: linux-image-4.4.0-trunk-amd64: Laptop reboot after suspend system

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #812196 [src:linux] linux-image-4.4.0-trunk-amd64: Laptop reboot after 
suspend system
Ignoring request to alter tags of bug #812196 to the same tags previously set

-- 
812196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#810663: marked as done (Include Device Tree model in reportbug script)

[Debian Bug Tracking System]

Your message dated Mon, 15 Feb 2016 23:37:57 +
with message-id <1455579477.1143.7.ca...@decadent.org.uk>
and subject line Re: Bug#810663: Include Device Tree model in reportbug script
has caused the Debian Bug report #810663,
regarding Include Device Tree model in reportbug script
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.)


-- 
810663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Version: 4.3.3-5
Severity: wishlist
Tags: patch

It would be nice to include the Device Tree model in the reportbug
output.  On DT based platforms, /proc/cpuinfo only includes quite
generic information.

Please note that the strange "echo ... $(cat ..)" construct is
intentional.  'cat /proc/device-tree/model' leads to a strange
character at the end because there's no newline and using echo
gets rid of it.

diff --git a/debian/templates/image.plain.bug/include-model 
b/debian/templates/image.plain.bug/include-model
index 60a7112..9c6aedd 100644
--- a/debian/templates/image.plain.bug/include-model
+++ b/debian/templates/image.plain.bug/include-model
@@ -39,6 +39,11 @@ grep_model() {
 false
 ;;
   esac
+
+  # Device Tree model
+  if [ -r /proc/device-tree/model ]; then
+echo "Device Tree model:" $(cat /proc/device-tree/model)
+  fi
 }
 
 add_model() {

-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Version: 4.3.5-1

You committed this change but forgot to close the bug...

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#812196: linux-image-4.4.0-trunk-amd64: Laptop reboot after suspend system

[Ben Hutchings]

Control: tag -1 moreinfo

On Thu, 2016-01-21 at 13:49 +0100, Alexandre wrote:
> Package: src:linux
> Version: 4.4-1~exp1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> After suspend my laptop (hibernation) i have this message in syslog :
[...]
> Jan 21 12:16:58 debian systemd[1]: Reached target Sleep.
> Jan 21 12:16:58 debian systemd[1]: Starting Suspend...
> Jan 21 12:16:58 debian systemd-sleep[4293]: Suspending system...

That indicates suspend-to-RAM, not hibernation.

> When i try to resume my laptop reboot with this message in syslog :
> 
> Jan 21 13:41:51 debian kernel: [0.657877] PM: Hibernation image not 
> present
> or could not be loaded.

This is unsurprising because it was never hibernated.  But of course it
should have resumed from RAM, not rebooted.

Could you please follow the instructions in
https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt
to find out which step goes wrong?

[...]
> Jan 21 13:41:51 debian kernel: [0.661340] [ cut here
> ]
> Jan 21 13:41:51 debian kernel: [0.661343] WARNING: CPU: 2 PID: 1 at /build
> /linux-tEELBQ/linux-4.4/arch/x86/mm/dump_pagetables.c:225
> note_page+0x5e1/0x790()
> Jan 21 13:41:51 debian kernel: [0.661344] x86/mm: Found insecure W+X
> mapping at address 8805f000/0x8805f000
[...]

This warning is known to appear on amd64 systems booting through UEFI,
and I've found a fix for that which should be included in version
4.4.2-1.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg

signature.asc
Description: This is a digitally signed message part

Processed: Re: Bug#812196: linux-image-4.4.0-trunk-amd64: Laptop reboot after suspend system

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #812196 [src:linux] linux-image-4.4.0-trunk-amd64: Laptop reboot after 
suspend system
Added tag(s) moreinfo.

-- 
812196: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#779628: bcache: task bcache_writebac blocked for more than 240 seconds, system load high when module used

[Tim Small]

On 05/02/16 23:14, Ben Hutchings wrote:

>> https://lkml.org/lkml/2015/12/30/331
>> 
>> It would be good to get this set into Stretch, and possibly a Jessie
>> point release too (IIRC, it will apply cleanly to the Jessie kernel).

> That whole patch series was included in 4.3.3-6, but I have yet to
> apply them and the earlier fixes to the jessie branch.

Great, thanks.  If you do apply those to Jessie and you'd like some
testing carried out, please let me know.

Tim.

Processed: [bts-link] source package src:linux

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package src:linux
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #787348 (http://bugs.debian.org/787348)
> # Bug title: linux-image-3.16.0-4-amd64: Intel NM10/ICH7 it's not detected 
> after 3.13.10-1
> #  * http://bugzilla.kernel.org/show_bug.cgi?id=99221
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> CODE-FIX
> #  * closed upstream
> tags 787348 + fixed-upstream
Bug #787348 [src:linux] linux-image-3.16.0-4-amd64: Intel NM10/ICH7 it's not 
detected after 3.13.10-1
Added tag(s) fixed-upstream.
> usertags 787348 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 787348 + status-RESOLVED resolution-CODE-FIX
There were no usertags set.
Usertags are now: status-RESOLVED resolution-CODE-FIX.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
787348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Uploading linux (4.4.1-1)

[Ben Hutchings]

On Sun, 2016-02-14 at 16:12 +, Ben Hutchings wrote:
> I intend to upload linux version 4.4.1-1 to unstable on Monday or
> Tuesday.

I'd now like to wait for 4.4.2, which should be released late on
Tuesday or on Wednesday.

> * New upstream version, which means an ABI bump.
> 
> * I have combined two armel flavours into one, which requires an
>   update to flash-kernel (already done) and the installer (which
>   I may be able to handle myself).

Martin Michlmayr will handle the installer change.

* I have combined the scsi{,-common,-extra}-modules packages, which
  also requires a change to the build configuration.  I should be
  able to handle that myself.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg


signature.asc
Description: This is a digitally signed message part

Re: Kernel version for stretch

[Ben Hutchings]

On Sun, 2016-02-14 at 15:48 -0500, Martin Michlmayr wrote:
> * Ben Hutchings  [2016-02-14 15:58]:
> > >  * If we stick with 4.4, the Debian Linux maintainers receives
> > >    practically no advantage from Greg's LTS effort.
> > 
> > No, we would benefit from that but this is very early to freeze the
> > kernel and we would need to do a lot of work on backporting hardware
> > support.
> 
> Based on my gut feeling, backporting stuff into 4.4 would be more work
> than doing a long-term stable release based on 4.9.  Based on your
> experience, do you think that's accurate, Ben?

I think they're around the same amount of effort.

> (I think it would be different if we were to use 4.4 when 4.5 was the
> current kernel, but 4.4 to 4.10 is going to be a huge delta.)
> 
> So imho we should get 4.9 into unstable, agree at some point on 4.9 vs
> 4.10 and if we agree on 4.10 then get 4.10-rc releases into unstable,
> and ask people to test daily d-i images based on that.

Yes, that's a good way to reduce the risk of a late switch.

> (Of course I should mention that I'm not part of the kernel team.  But
> speaking as an ARM porter, I think going with 4.4 would be a disaster.
> We're going to see a lot of changes this year, especially on ARM64.)

I know.

> Another option would be to go with 4.4 and make it easy for d-i to
> support kernels from backports (something we should do anyway).  But I
> think releasing with a 1.5 year old kernel is just going to add to the
> "Debian is out of date" view.

There's that too.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow Lindberg

signature.asc
Description: This is a digitally signed message part

Re: Kernel version for stretch

[Mehdi Dogguy]

Hi,

On 2016-02-02 08:34, Niels Thykier wrote:
Based on the current 9 week upstream release cycle, the longterm 
branch
for 2017 will presumably be based on Linux 4.10, released at the end 
of

week 3 (22nd January 2017).  That's well after the planned stretch
freeze date so I don't see how it can be included.



Indeed that is a bit unfortunate.  With the freeze date already
announced, I am very hesitant to move it.



I wouldn't consider it a fail if we decided to shift the freeze date by
two months [1], especially if this move helps project members to 
integrate
better supported versions for their packages. Eventually, it would help 
us

to have a better quality release and enhance its supportability over the
years.

Having that said, it would be nice to hear from Ben if it would be 
doable

to go with 4.9 or with a 4.10rc for some time.

[1] only a few persons seem to have noted those dates anyway (imho).

--
Mehdi