On Mon, 2015-12-21 at 12:56 +1030, Arthur Marsh wrote:
> > This is no way an acceptable patch. The driver needs to be converted
> > properly to the Linux 2.6+ device model, instead of adding further
> > kluges to it.
> >
> > Ben.
> >
>
> Thanks, that patch wasn't provided by me. The old driver
This is no way an acceptable patch. The driver needs to be converted
properly to the Linux 2.6+ device model, instead of adding further
kluges to it.
Ben.
Thanks, that patch wasn't provided by me. The old driver just broke
during other updates and that patch was provided as a workaround to
Control: tag -1 - patch
On Mon, 2015-12-21 at 12:17 +1030, Arthur Marsh wrote:
> Package: src:linux
> Version: 4.3.3-2
> Severity: normal
> Tags: upstream patch
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
> * What led up to the si
Processing control commands:
> tag -1 - patch
Bug #808567 [src:linux] linux-image-4.3.0-1-686-pae: eata module required for
DPT SCSI adapter fails, lack of response upstream
Removed tag(s) patch.
--
808567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808567
Debian Bug Tracking System
Conta
Processing control commands:
> severity -1 important
Bug #808563 [src:linux] Boot with 4.3: SATA errors. Returning to 4.2: no errors
Severity set to 'important' from 'grave'
> tag -1 moreinfo
Bug #808563 [src:linux] Boot with 4.3: SATA errors. Returning to 4.2: no errors
Added tag(s) moreinfo.
--
Control: severity -1 important
Control: tag -1 moreinfo
On Mon, 2015-12-21 at 09:18 +0800, 積丹尼 Dan Jacobson wrote:
> The first time it happened I couldn't boot again without a fsck.ext4 via
> a rescue CD!
I'm so tired of this routine.
Ben.
--
Ben Hutchings
One of the nice things about standard
Package: src:linux
Version: 4.3.3-2
Severity: normal
Tags: upstream patch
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Attempting to load a kernel later than 4.2.0.
* What exactly did you do (or not do) th
Processing commands for cont...@bugs.debian.org:
> severity 808563 grave
Bug #808563 [src:linux] Boot with 4.3: SATA errors. Returning to 4.2: no errors
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
808563: http://bugs.de
The first time it happened I couldn't boot again without a fsck.ext4 via
a rescue CD!
When converting and splitting the kernel svn repository to git, I left
the 'people' directory alone. Now I would like to move those files
that are still used to a git repository or repositories.
The following subdirectories exist:
* benh/
- last commit: 2015
- contains: miscellaneous scripts
Package: src:linux
Version: 4.3.3-2
Severity: important
I am getting these errors (sort -u'd here) with linux-image-4.3.0-1-686-pae
res 40/00:20:00:48:11/00:00:26:00:00/40 Emask 0x60 (host bus error)
ata1.00: cmd 61/d0:d8:80:9e:10/05:00:26:00:00/40 tag 27 ncq 761856 out
ata1.00: configur
Debian kernel packages for powerpc and ppc64el are broken following
some recent toolchain upgrades:
https://bugs.debian.org/808043
https://bugs.debian.org/808246
Please can you investigate this as a matter of urgency.
Ben.
--
Ben Hutchings
Always try to do things in chronological order;
it's l
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 14 Dec 2015 21:10:28 +
Source: linux
Binary: linux-source-3.16 linux-doc-3.16 linux-manual-3.16
linux-support-3.16.0-4 linux-libc-dev linux-headers-3.16.0-4-all
linux-headers-3.16.0-4-all-alpha kernel-image-3
Your message dated Sun, 20 Dec 2015 18:02:40 +
with message-id
and subject line Bug#785189: fixed in linux 3.16.7-ckt20-1+deb8u1
has caused the Debian Bug report #785189,
regarding sendfile to AF_ALG socket loses data
to be marked as done.
This means that you claim that the problem has been d
Package: src:linux
Version: 4.3.3-2
Severity: normal
Dear Maintainer,
* What led up to the situation?
Since the upgrade to kernel 4.3, the machine becomes unresponsive after
a few hours (keyborad frozen, blank screen) necessitating a hard reboot.
* What exactly did you do (or not do) that
15 matches
Mail list logo
