Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #52525 > unrolled thread

Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c

Started byCarsten Wolff <carsten@wolffcarsten.de>
First post2016-01-31 18:00 +0100
Last post2016-01-31 23:50 +0100
Articles 9 — 3 participants

Back to article view | Back to linux.debian.kernel

Contents

  Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Carsten Wolff <carsten@wolffcarsten.de> - 2016-01-31 18:00 +0100
    Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Ben Hutchings <ben@decadent.org.uk> - 2016-01-31 23:50 +0100
      Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Carsten Wolff <carsten@wolffcarsten.de> - 2016-02-03 08:40 +0100
        Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Ben Hutchings <ben@decadent.org.uk> - 2016-02-05 02:30 +0100
          Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Carsten Wolff <carsten@wolffcarsten.de> - 2016-02-05 17:10 +0100
            Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Ben Hutchings <ben@decadent.org.uk> - 2016-02-05 18:00 +0100
              Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Carsten Wolff <carsten@wolffcarsten.de> - 2016-03-19 09:10 +0100
                Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c Carsten Wolff <carsten@wolffcarsten.de> - 2016-12-18 19:20 +0100
    Processed: Re: Bug#813327: linux-image-3.16.0-4-amd64: cryptroot  + VIA padlock fails with message from testmgr.c owner@bugs.debian.org (Debian Bug Tracking System) - 2016-01-31 23:50 +0100

#52525 — Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c

FromCarsten Wolff <carsten@wolffcarsten.de>
Date2016-01-31 18:00 +0100
SubjectBug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c
Message-ID<qX3vX-63V-1@gated-at.bofh.it>
Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal

Hi,

I'm not at all sure I'm filing this against the right package. Maybe
cryptsetup, maybe linux, ...

After upgrading this system from wheezy to jessie, unlocking the cryptroot from
initrd with padlock-aes and padlock-sha loaded stopped working. After entering
the passphrase, cryptsetup fails with a message like
"cryptsetup check that kernel supports aes-cbc-essiv:sha265"

In dmesg, there's another message:
[  233.196927] alg: skcipher: Result buffer corruption in chunk test 1 on encryption at page 0 for cbc-aes-padlock: 32 bytes:
[  233.196998] 00000000: 4f 1c 0e cd 0b 96 fd bf 26 50 95 5f 63 a6 7e eb
[  233.197007] 00000010: f2 01 6e 42 a4 8f 6f 86 d3 c6 17 85 4a d4 1d 71
[  233.202194] device-mapper: table: 254:0: crypt: Error allocating crypto tfm
[  233.202259] device-mapper: ioctl: error adding target to table

Things I found out so far:
- booting with latest wheezy kernel (initrd updated by jessie): works, with padlock support.
- from initrd, rmmod padlock-aes and padlock-sha, then modprobe sha256 and cbc,
  then luksOpen: works (slower, of course).
- The code generating the "alg: skcipher:"-message is in crypto/testmgr.c and
  it seems, these lines have only be changed in one commit between 3.2 and
  3.16:
  https://github.com/torvalds/linux/commit/08d6af8c160b6bd9b21a3177e2b1bebc72a21041

Any ideas?

Thanks!

Regards
Carsten

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: VIA Technologies Ltd.
product_name: VX800 
product_version: 1.0
chassis_vendor: VIA Technologies Ltd.
chassis_version: VX800 
bios_vendor: Phoenix Technologies, LTD
bios_version: 6.00 PG
board_vendor: VIA Technologies Ltd.
board_name: VX800 
board_version: 1.0

** PCI devices:
00:00.0 Host bridge [0600]: VIA Technologies, Inc. VX800 Host Bridge [1106:0353] (rev 12)
	Subsystem: VIA Technologies, Inc. VX800 Host Bridge [1106:0353]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 8, Cache Line Size: 64 bytes

00:00.1 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Error Reporting [1106:1353]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes

00:00.2 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Host Bus Control [1106:2353]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes

00:00.3 Host bridge [0600]: VIA Technologies, Inc. VX800 PCI to PCI Bridge [1106:3353]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0

00:00.4 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Power Management Control [1106:4353]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes

00:00.5 PIC [0800]: VIA Technologies, Inc. VX800/VX820 APIC and Central Traffic Control [1106:5353] (prog-if 20 [IO(X)-APIC])
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes

00:00.6 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 Scratch Registers [1106:6353]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes

00:00.7 Host bridge [0600]: VIA Technologies, Inc. VX800/VX820 North-South Module Interface Control [1106:7353]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes

00:01.0 VGA compatible controller [0300]: VIA Technologies, Inc. VX800/VX820 Chrome 9 HC3 Integrated Graphics [1106:1122] (rev 11) (prog-if 00 [VGA controller])
	Subsystem: VIA Technologies, Inc. VX800/VX820 Chrome 9 HC3 Integrated Graphics [1106:1122]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort+ <MAbort+ >SERR- <PERR- INTx-
	Latency: 32
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d8000000 (32-bit, prefetchable) [size=64M]
	Region 1: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
	Region 2: Memory at c0000000 (32-bit, non-prefetchable) [size=256M]
	[virtual] Expansion ROM at 7bf00000 [disabled] [size=64K]
	Capabilities: <access denied>

00:02.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:c353] (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: dfb00000-dfbfffff
	Prefetchable memory behind bridge: 00000000df800000-00000000df8fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:03.0 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:e353] (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: df700000-df7fffff
	Prefetchable memory behind bridge: 00000000dfe00000-00000000dfefffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:03.1 PCI bridge [0604]: VIA Technologies, Inc. VX800/VX820 PCI Express Root Port [1106:f353] (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: dfd00000-dfdfffff
	Prefetchable memory behind bridge: 00000000dfc00000-00000000dfcfffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:0f.0 IDE interface [0101]: VIA Technologies, Inc. VX800 Serial ATA and EIDE Controller [1106:5324] (prog-if 8a [Master SecP PriP])
	Subsystem: VIA Technologies, Inc. VX800 Serial ATA and EIDE Controller [1106:5324]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32
	Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
	Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable)
	Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
	Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable)
	Region 4: I/O ports at fc00 [size=16]
	Capabilities: <access denied>
	Kernel driver in use: pata_via

00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 20
	Region 4: I/O ports at f800 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 22
	Region 4: I/O ports at f400 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:10.2 USB controller [0c03]: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038] (rev a0) (prog-if 00 [UHCI])
	Subsystem: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller [1106:3038]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin C routed to IRQ 21
	Region 4: I/O ports at f000 [size=32]
	Capabilities: <access denied>
	Kernel driver in use: uhci_hcd

00:10.4 USB controller [0c03]: VIA Technologies, Inc. USB 2.0 [1106:3104] (rev 90) (prog-if 20 [EHCI])
	Subsystem: VIA Technologies, Inc. USB 2.0 Controller [1106:3104]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32, Cache Line Size: 64 bytes
	Interrupt: pin D routed to IRQ 23
	Region 0: Memory at dffff000 (32-bit, non-prefetchable) [size=256]
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:11.0 ISA bridge [0601]: VIA Technologies, Inc. VX800/VX820 Bus Control and Power Management [1106:8353]
	Subsystem: VIA Technologies, Inc. VX800/VX820 Bus Control and Power Management [1106:8353]
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Capabilities: <access denied>

00:11.7 Host bridge [0600]: VIA Technologies, Inc. VX8xx South-North Module Interface Control [1106:a353]
	Subsystem: VIA Technologies, Inc. Device [1106:7323]
	Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-

00:13.0 PCI bridge [0604]: VIA Technologies, Inc. VX855/VX875/VX900 PCI to PCI Bridge [1106:b353] (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 0000b000-0000bfff
	Memory behind bridge: dfa00000-dfafffff
	Prefetchable memory behind bridge: 00000000df900000-00000000df9fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:14.0 Audio device [0403]: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller [1106:3288] (rev 20)
	Subsystem: VIA Technologies, Inc. VT8237A/VT8251 HDA Controller [1106:3288]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 307
	Region 0: Memory at dfff8000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 02)
	Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller [10ec:8168]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 306
	Region 0: I/O ports at ec00 [size=256]
	Region 2: Memory at df7ff000 (64-bit, non-prefetchable) [size=4K]
	Region 4: Memory at dfef0000 (64-bit, prefetchable) [size=64K]
	[virtual] Expansion ROM at dfe00000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: r8169

04:04.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet [10ec:8167] (rev 10)
	Subsystem: Jetway Information Co., Ltd. Device [16f3:10ec]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 18
	Region 0: I/O ports at bc00 [size=256]
	Region 1: Memory at dfaff000 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at df900000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: pciback

04:06.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet [10ec:8167] (rev 10)
	Subsystem: Jetway Information Co., Ltd. Device [16f3:10ec]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 19
	Region 0: I/O ports at b800 [size=256]
	Region 1: Memory at dfafe000 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at df920000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: pciback

04:07.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8110SC/8169SC Gigabit Ethernet [10ec:8167] (rev 10)
	Subsystem: Jetway Information Co., Ltd. Device [16f3:10ec]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 32 (8000ns min, 16000ns max), Cache Line Size: 32 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: I/O ports at b400 [size=256]
	Region 1: Memory at dfafd000 (32-bit, non-prefetchable) [size=256]
	Expansion ROM at df940000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: pciback


** USB devices:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard G230
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-3.16.0-4-amd64 depends on:
ii  debconf [debconf-2.0]                   1.5.56
ii  initramfs-tools [linux-initramfs-tool]  0.120
ii  kmod                                    18-3
ii  linux-base                              3.5
ii  module-init-tools                       18-3

Versions of packages linux-image-3.16.0-4-amd64 recommends:
ii  firmware-linux-free  3.3
ii  irqbalance           1.0.6-3

Versions of packages linux-image-3.16.0-4-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 2.02~beta2-22+deb8u1
pn  linux-doc-3.16          <none>

Versions of packages linux-image-3.16.0-4-amd64 is related to:
pn  firmware-atheros                           <none>
pn  firmware-bnx2                              <none>
pn  firmware-bnx2x                             <none>
pn  firmware-brcm80211                         <none>
pn  firmware-intelwimax                        <none>
pn  firmware-ipw2x00                           <none>
pn  firmware-ivtv                              <none>
pn  firmware-iwlwifi                           <none>
pn  firmware-libertas                          <none>
ii  firmware-linux                             0.43
ii  firmware-linux-nonfree                     0.43
pn  firmware-myricom                           <none>
pn  firmware-netxen                            <none>
pn  firmware-qlogic                            <none>
pn  firmware-ralink                            <none>
pn  firmware-realtek                           <none>
ii  xen-hypervisor-4.4-amd64 [xen-hypervisor]  4.4.1-9+deb8u3

-- debconf information:
  linux-image-3.16.0-4-amd64/postinst/mips-initrd-3.16.0-4-amd64:
  linux-image-3.16.0-4-amd64/prerm/removing-running-kernel-3.16.0-4-amd64: true
  linux-image-3.16.0-4-amd64/postinst/depmod-error-initrd-3.16.0-4-amd64: false

[toc] | [next] | [standalone]

#52528

FromBen Hutchings <ben@decadent.org.uk>
Date2016-01-31 23:50 +0100
Message-ID<qX8YG-1Bq-5@gated-at.bofh.it>
In reply to#52525

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo
Control: severity -1 important

On Sun, 2016-01-31 at 16:03 +0100, Carsten Wolff wrote:
> Package: src:linux
> Version: 3.16.7-ckt20-1+deb8u3
> Severity: normal
> 
> Hi,
> 
> I'm not at all sure I'm filing this against the right package. Maybe
> cryptsetup, maybe linux, ...
> 
> After upgrading this system from wheezy to jessie, unlocking the cryptroot from
> initrd with padlock-aes and padlock-sha loaded stopped working. After entering
> the passphrase, cryptsetup fails with a message like
> "cryptsetup check that kernel supports aes-cbc-essiv:sha265"
> 
> In dmesg, there's another message:
> [  233.196927] alg: skcipher: Result buffer corruption in chunk test 1 on encryption at page 0 for cbc-aes-padlock: 32 bytes:
> [  233.196998] 00000000: 4f 1c 0e cd 0b 96 fd bf 26 50 95 5f 63 a6 7e eb
> [  233.197007] 00000010: f2 01 6e 42 a4 8f 6f 86 d3 c6 17 85 4a d4 1d 71
> [  233.202194] device-mapper: table: 254:0: crypt: Error allocating crypto tfm
> [  233.202259] device-mapper: ioctl: error adding target to table
> 
> Things I found out so far:
> - booting with latest wheezy kernel (initrd updated by jessie): works, with padlock support.
> - from initrd, rmmod padlock-aes and padlock-sha, then modprobe sha256 and cbc,
>   then luksOpen: works (slower, of course).
> - The code generating the "alg: skcipher:"-message is in crypto/testmgr.c and
>   it seems, these lines have only be changed in one commit between 3.2 and
>   3.16:
>   https://github.com/torvalds/linux/commit/08d6af8c160b6bd9b21a3177e2b1bebc72a21041
> 
> Any ideas?

That suggests a regression in the padlock-aes driver, although I don't
see any functional changes there.  As a workaround, you can blacklist
it by adding "blacklist=padlock-aes" to the kernel command line.

I wonder whether the compiler version makes a difference.  Does the
3.16 kernel in the wheezy-backports suite behave any differently?

Ben.

-- 
Ben Hutchings
Larkinson's Law: All laws are basically false.

[toc] | [prev] | [next] | [standalone]

#52556

FromCarsten Wolff <carsten@wolffcarsten.de>
Date2016-02-03 08:40 +0100
Message-ID<qY0cF-7kE-1@gated-at.bofh.it>
In reply to#52528

[Multipart message — attachments visible in raw view] — view raw

Hi Ben,

thanks for the quick answer.

On Sunday 31 January 2016 23:37:56 Ben Hutchings wrote:
> That suggests a regression in the padlock-aes driver, although I don't
> see any functional changes there.  As a workaround, you can blacklist
> it by adding "blacklist=padlock-aes" to the kernel command line.

of course, but this machine is mainly serving files and running backups and 
padlock really makes a difference in throughput.

> I wonder whether the compiler version makes a difference.  Does the
> 3.16 kernel in the wheezy-backports suite behave any differently?

Unfortunatly, that wasn't it. The bp.o kernel shows the same symptoms. 
Anything else I can try out or do to provide more info?

Cheers
Carsten

[toc] | [prev] | [next] | [standalone]

#52578

FromBen Hutchings <ben@decadent.org.uk>
Date2016-02-05 02:30 +0100
Message-ID<qYDnI-1Cc-9@gated-at.bofh.it>
In reply to#52556

[Multipart message — attachments visible in raw view] — view raw

On Wed, 2016-02-03 at 08:19 +0100, Carsten Wolff wrote:
> Hi Ben,
> 
> thanks for the quick answer.
> 
> On Sunday 31 January 2016 23:37:56 Ben Hutchings wrote:
> > That suggests a regression in the padlock-aes driver, although I don't
> > see any functional changes there.  As a workaround, you can blacklist
> > it by adding "blacklist=padlock-aes" to the kernel command line.
> 
> of course, but this machine is mainly serving files and running backups and 
> padlock really makes a difference in throughput.
> 
> > I wonder whether the compiler version makes a difference.  Does the
> > 3.16 kernel in the wheezy-backports suite behave any differently?
> 
> Unfortunatly, that wasn't it. The bp.o kernel shows the same symptoms. 
> Anything else I can try out or do to provide more info?

I found what seems to be a bug in the driver, but it was present in
both 3.2 and 3.16.  Please test whether the attached patch fixes this
issue, following the instructions at
<https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>.

Ben.

-- 
Ben Hutchings
It is a miracle that curiosity survives formal education. - Albert Einstein

[toc] | [prev] | [next] | [standalone]

#52587

FromCarsten Wolff <carsten@wolffcarsten.de>
Date2016-02-05 17:10 +0100
Message-ID<qYR7j-2vG-15@gated-at.bofh.it>
In reply to#52578

[Multipart message — attachments visible in raw view] — view raw

On Friday 05 February 2016 01:10:37 Ben Hutchings wrote:
> I found what seems to be a bug in the driver, but it was present in
> both 3.2 and 3.16.  Please test whether the attached patch fixes this
> issue

Hum, the patch only fixes the decision, if and when the key is reset before an 
operation, but not, which cword is used in actual operations, right? So it 
shouldn't change anything in the result? At least, it does not fix the error 
I'm seeing. The message stays the same, including the 32 byte it dumps.

Regards
Carsten

[toc] | [prev] | [next] | [standalone]

#52590

FromBen Hutchings <ben@decadent.org.uk>
Date2016-02-05 18:00 +0100
Message-ID<qYRTI-2MX-9@gated-at.bofh.it>
In reply to#52587

[Multipart message — attachments visible in raw view] — view raw

On Fri, 2016-02-05 at 16:58 +0100, Carsten Wolff wrote:
> On Friday 05 February 2016 01:10:37 Ben Hutchings wrote:
> > I found what seems to be a bug in the driver, but it was present in
> > both 3.2 and 3.16.  Please test whether the attached patch fixes this
> > issue
> 
> Hum, the patch only fixes the decision, if and when the key is reset before an 
> operation, but not, which cword is used in actual operations, right? So it 
> shouldn't change anything in the result?

Apparently if this is not done when switching keys, the Padlock unit
might use stale data derived from the previous key.  However, I don't
think it's a huge risk in practice.

> At least, it does not fix the error 
> I'm seeing. The message stays the same, including the 32 byte it dumps.

Then I'm out of ideas.  I'll pass this to the upstream developers.

Ben.

-- 
Ben Hutchings
It is a miracle that curiosity survives formal education. - Albert Einstein

[toc] | [prev] | [next] | [standalone]

#53243

FromCarsten Wolff <carsten@wolffcarsten.de>
Date2016-03-19 09:10 +0100
Message-ID<rek7n-5yp-1@gated-at.bofh.it>
In reply to#52590

[Multipart message — attachments visible in raw view] — view raw

Hi Ben,

On Friday 05 February 2016 16:54:59 Ben Hutchings wrote:
> On Fri, 2016-02-05 at 16:58 +0100, Carsten Wolff wrote:
> > At least, it does not fix the error 
> > I'm seeing. The message stays the same, including the 32 byte it dumps.
> 
> Then I'm out of ideas.  I'll pass this to the upstream developers.

here's an update on the issue: apparently, the latest wheezy-security kernel 
somehow broke padlock, too. I don't see any of the error messages I get with 
the jessie kernel, but after entering the key at the cryptsetup prompt, it 
responds with "No key available with this passphrase". I now have no kernel 
left to successfully boot with padlock/dm-crypt.

One might think "hardware issue" now, but I can rule this out, it did work 
before and is still working in userspace (patched openssl package, apache/
openvpn using the openssl padlock engine).

Regards
Carsten

[toc] | [prev] | [next] | [standalone]

#56285

FromCarsten Wolff <carsten@wolffcarsten.de>
Date2016-12-18 19:20 +0100
Message-ID<sPOdX-4zd-11@gated-at.bofh.it>
In reply to#53243
Hi,

that Hardware of mine passed away recently, so I won't be able to track this 
issue anymore. I suggest closing the bugreport, unless anybody else speaks up 
about the same problem.

Regards
Carsten

[toc] | [prev] | [next] | [standalone]

#52529 — Processed: Re: Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c

Fromowner@bugs.debian.org (Debian Bug Tracking System)
Date2016-01-31 23:50 +0100
SubjectProcessed: Re: Bug#813327: linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c
Message-ID<qX8YG-1Bq-11@gated-at.bofh.it>
In reply to#52525
Processing control commands:

> tag -1 moreinfo
Bug #813327 [src:linux] linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c
Added tag(s) moreinfo.
> severity -1 important
Bug #813327 [src:linux] linux-image-3.16.0-4-amd64: cryptroot + VIA padlock fails with message from testmgr.c
Severity set to 'important' from 'normal'

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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web