Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 15 Jun 2016 21:32:54 +0200
Source: linux
Binary: linux-source-4.6 linux-support-4.6.0-1 linux-doc-4.6 linux-manual-4.6
linux-kbuild-4.6 linux-cpupower libcpupower0 libcpupower-dev linux-perf-4.6
libusbip-dev usbi
On Wednesday 15 June 2016 12:21:56 Ben Hutchings wrote:
> > I have a LUKS rootfs on top of a mdadm managed raid0. Starting from 4.5.5 it
> > doesn't recognize the luks volume at boot. The same happens with 4.6.1
>
> LUKS volumes are recognised and set uo by userland, so are you sure
> this is due
linux_4.6.2-1_multi.changes uploaded successfully to localhost
along with the files:
linux_4.6.2-1.dsc
linux_4.6.2.orig.tar.xz
linux_4.6.2-1.debian.tar.xz
Greetings,
Your Debian queue daemon (running on host franck.debian.org)
Hi Nicholaѕ,
thanks for your mail and sorry for my late answer.
I did some more examination and that fixed the
problem somehow.
On 30/05/16 22:43 -0400, Nicholas D Steeves wrote:
"On 30 May 2016 at 03:32, Rolf Kutz wrote:
Going back to linux-image-4.4.0-0.bpo.1-amd64 on the KVM-Server make
On Wed, 2016-06-15 at 20:39 +0200, TCH wrote:
> Hi!
>
> I have an old G4 MDD, with an X800 card. I've just installed Debian Jessie
> and tried to breathe life into the 2d acceleration, but without success. If
> i install "firmware-linux-nonfree", then it loads the "r420_cp.bin", but
> then i only
Processing control commands:
> tag -1 -moreinfo
Bug #827309 [src:linux] linux-image-3.16.0-4-kirkwood: latest upgrade made WiFi
unstable
Removed tag(s) moreinfo.
--
827309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with prob
Control: tag -1 -moreinfo
On 14-06-16 23:16, Ben Hutchings wrote:
> What was the previous installed version? (/var/log/dpkg.log should
> show this.)
2016-06-05 10:31:50 upgrade linux-image-3.16.0-4-kirkwood:armel
3.16.7-ckt25-1 3.16.7-ckt25-2
Paul
signature.asc
Description: OpenPGP digital
Hi!
I have an old G4 MDD, with an X800 card. I've just installed Debian Jessie
and tried to breathe life into the 2d acceleration, but without success. If
i install "firmware-linux-nonfree", then it loads the "r420_cp.bin", but
then i only got a black screen after boot and the machine freezes
comp
Processing control commands:
> reassign -1 src:linux
Bug #827392 [linux-image-4.6.0.-1-amd64] linux-image-4.6.0.-1-amd64: issues
with intel xorg driver
Warning: Unknown package 'linux-image-4.6.0.-1-amd64'
Bug reassigned from package 'linux-image-4.6.0.-1-amd64' to 'src:linux'.
No longer marked a
control: reassign -1 src:linux
control: found -1 4.6.1-1
[ please leave me out when discussing this bug ]
On Wed, Jun 15, 2016 at 06:54:56PM +0200, Vieno Foo wrote:
> Package: linux-image-4.6.0.-1-amd64
typo in the package name
> Version: linux-image-4.6.0-1-amd64
and this is not a valid versi
Hi
Also there is a third bug in systemd - it does not check if watchdog is alarm
only, like iAMT.
In theory to achieve system reboot on timeout systemd should iterate over all
available watchdogs and select one that is not alarm only.
Thanks
--
Sasha
-Original Message-
From: Sebastia
Hi,
On Wed, Jun 15, 2016 at 01:25:53PM +, Usyskin, Alexander wrote:
> It may be that fdd9b8655933 uncovered the bug in iTCO_wdt because
> it actually removes iAMT watchdog and new implementation does not
> creates one for not provisioned ME.
>
> So before that patch there was two watchdog devi
Your message dated Wed, 15 Jun 2016 17:10:13 +0200
with message-id <20160615151013.GB16860@earth>
and subject line Re: Bug#827323: linux: Regression v4.5 -> v4.6: system freeze
after suspend/resume due to iAMT watchdog
has caused the Debian Bug report #827323,
regarding linux: Regression v4.5 -> v
Hi
It may be that fdd9b8655933 uncovered the bug in iTCO_wdt because it actually
removes iAMT watchdog and new
implementation does not creates one for not provisioned ME.
So before that patch there was two watchdog devices and systemd maybe worked
with iAMT one.
After that patch only one watchdo
Hi,
On Wed, Jun 15, 2016 at 08:00:30AM +, Usyskin, Alexander wrote:
> I assume that "This happened with 4.6, but not with v4.5.", yes?
Yes, sorry.
> Do you have vPro system?
Yes, my CPU is i7-5600U.
> Have you provisioned your ME device?
No, I don't think so.
> If not, the iAMT watchdog
Processing control commands:
> tag -1 moreinfo
Bug #827342 [src:linux] linux-image-4.5.0-2-amd64: luks rootfs not recognized
at boot after upgrade to linux-image 4.5.5
Added tag(s) moreinfo.
--
827342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827342
Debian Bug Tracking System
Contact ow
Control: tag -1 moreinfo
On Wed, 2016-06-15 at 08:56 +0200, Sander van Grieken wrote:
> Package: src:linux
> Version: 4.5.5-1
> Severity: important
>
> Upgrading linux kernel from 4.5.4 to 4.5.5 broke my boot.
>
> I have a LUKS rootfs on top of a mdadm managed raid0. Starting from 4.5.5 it
> doe
Processing commands for cont...@bugs.debian.org:
> tags 827340 + upstream
Bug #827340 [src:linux] linux: CVE-2010-5321 memory leak in videobuf on
multiple calls to mmap()
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
827340: http://bugs.d
Hi
I assume that "This happened with 4.6, but not with v4.5.", yes?
Do you have vPro system? Have you provisioned your ME device?
If not, the iAMT watchdog should not be exposed to user-space and should not
affect systemd.
Do you have /dev/watchdog* with identity "iamt_wdt" at you system?
Thank
Package: src:linux
Version: 4.5.5-1
Severity: important
Upgrading linux kernel from 4.5.4 to 4.5.5 broke my boot.
I have a LUKS rootfs on top of a mdadm managed raid0. Starting from 4.5.5 it
doesn't recognize the luks volume at boot. The same happens with 4.6.1
The raid0 is not explicitly made w
20 matches
Mail list logo
