Bug#820156: parse_numeric function cannot handle composite device numbers of more than 8 hex digits

2016-04-07 Thread Stephen Powell
On Tue, Apr 5, 2016, at 20:37, Ben Hutchings wrote: > > I'm not applying this until the kernel actually supports device numbers > that large.  Currently it defines (in include/linux/kdev_t.h): > > static inline u32 new_encode_dev(dev_t dev) { ... } > static inline dev_t new_decode_dev(u32 dev) {

Bug#820403: jessie-pu: package linux/3.16.7-ckt25-2

2016-04-07 Thread Ben Hutchings
Package: release.debian.org Severity: normal Tags: jessie User: release.debian@packages.debian.org Usertags: pu The recent point release (8.4) introduced several regressions in src:linux. In particular bug #819881 (radeon crasher) is affecting a fair number of users. Bug #820176 (usb

Bug#820182: linux-image-3.16.0-4-amd64: freezes on scrolling in iceweasel

2016-04-07 Thread Björn Siebke
Package: src:linux Version: 3.16.7-ckt25-1 Followup-For: Bug #820182 Hey there, just had the same problem on scrolling through a LibreOffice Writer docuement containing graphics (GDI MetaFile). It does not occur if I change the cursor's position, but only when scrolling with the mouse reel or by

Bug#820306: [Fwd: Re: Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected]

2016-04-07 Thread Ben Hutchings
Forwarded Message From: Vince Barwinski To: Ben Hutchings Subject: Re: Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected Date: Thu, 7 Apr 2016 20:54:14 +1000

Processed: Re: Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #820306 [src:linux] general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected Ignoring request to alter tags of bug #820306 to the same tags previously set -- 820306:

Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Ben Hutchings
Control: tag -1 moreinfo On Thu, 2016-04-07 at 20:54 +1000, Vince Barwinski wrote: > My /var/log/messages only had messages for today. Then /var/log/messages.1 etc. will have the older messages. > So I rebooted into my new > kernel 4.4.0-1-amd64 with the bug and recreated the bug. My output

Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Zlatan Todoric
The bug was also reported from Sparky Linux and not Debian. Cheers, Zlatan On April 7, 2016 11:57:28 AM GMT+02:00, gregor herrmann wrote: >control: reassign -1 linux-image-4.4.0-1-amd64 > >On Thu, 07 Apr 2016 19:46:04 +1000, Vince Barwinski wrote: > >> Just another thing. I

Processed: Re: Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #820306 [src:linux] general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected Added tag(s) moreinfo. -- 820306: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820306 Debian Bug Tracking System

Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Ben Hutchings
Control: tag -1 moreinfo On Thu, 2016-04-07 at 19:32 +1000, Vince wrote: > Package: general > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > >    * What led up to the situation? USB mass storage device was > accidentally disconnected causing immediate system

Processed: Re: Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:linux 4.4.6-1 Bug #820306 [linux-image-4.4.0-1-amd64] general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected Bug reassigned from package 'linux-image-4.4.0-1-amd64' to 'src:linux'. Ignoring request

Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Ben Hutchings
Control: reassign -1 src:linux 4.4.6-1 Control: severity -1 important On Thu, 2016-04-07 at 11:57 +0200, gregor herrmann wrote: > control: reassign -1 linux-image-4.4.0-1-amd64 > > On Thu, 07 Apr 2016 19:46:04 +1000, Vince Barwinski wrote: > > > > > Just another thing. I must emphasize that

Processed: Re: Bug#820306: general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected

2016-04-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 linux-image-4.4.0-1-amd64 Bug #820306 [general] general: Kernel 4.4.0-1-amd64 causes system crash when USB mass storage device accidentally disconnected Bug reassigned from package 'general' to 'linux-image-4.4.0-1-amd64'. Ignoring request to alter

Processed: Re: [Bug 94757] powerpc64 & 64Kb kernel pagesize not working with nouveau

2016-04-07 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:xserver-xorg-video-nouveau 1:1.0.12-1 Bug #790690 [src:linux] linux-image-3.16.0-4-powerpc64: powerpc64 & 64Kb kernel pagesize not working with nouveau Bug reassigned from package 'src:linux' to 'src:xserver-xorg-video-nouveau'. No longer marked as

Bug#790690: [Bug 94757] powerpc64 & 64Kb kernel pagesize not working with nouveau

2016-04-07 Thread Mathieu Malaterre
Control: reassign -1 src:xserver-xorg-video-nouveau 1:1.0.12-1 Since nouveau people are currently considering that not supporting 64K page is a bug. It is time to re-affect the bug to nouveau instead of src:linux.

Re: Fixing a regression in linux in 8.4

2016-04-07 Thread Adam D. Barratt
On Thu, 2016-04-07 at 02:04 +0100, Ben Hutchings wrote: > Bug #819881 is affecting a fair number of users and I'm wondering how > best to get the fix deployed. I can upload to jessie-pu any time but > most users won't get it that way, and the next point release is just > too far away. I can also