Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

[Vcs Ccs]

On Tue, 23 Jul 2019 21:55:16 +0100 Terry Glanfield wrote:
> Thank you for the suggestion.
>
> I've installed 4.19.60 but that gives the same kernel panic.
>
> Where do I start in getting some more information to track what's causing
this?
>
> On Tue, 23 Jul 2019 14:40:59 +0200 Kinky Nekoboi
> wrote:
> > i had and have several problems with 4.19.37-5 ... an selfbuild vanila
> > kernel 4.19.60 with default options fixed most of them for me ...
> >
> > Debian should really push a newer 4.19.y kernel for buster
> >
> > Am 23.07.19 um 14:01 schrieb Terry Glanfield:
> > > This is still failing after an update to 4.19.37-5+deb10u1
> > >
> > > Any clues on where to start tracking this down?
> > >
> >
>
>

Hi Terry!

I had exactly the same problem.

A BIOS upgrade have solved it.

You can download new bios from here:
https://driverscollection.com/_447618233044da0d30a495b6285/Download-HP-Compaq-dc5800-Microtower-BIOS-v.4.02-Re.-A-free

Best regards:

vcs

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

[Harald Dunkel]

FYI:
I had problems with linux-image-4.19.0-5-amd64, too, esp. on writing
large amounts of data to an USB block device (USB-C). "sync" got stuck,
umount didn't work, host became unresponsive, etc. Reset necessary.

linux-image-4.19.0-6-amd64 (in proposed-updates) seems to work better.


Regards
Harri

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

[Terry Glanfield]

Thank you for the suggestion.

I've installed 4.19.60 but that gives the same kernel panic.

Where do I start in getting some more information to track what's causing this?

On Tue, 23 Jul 2019 14:40:59 +0200 Kinky Nekoboi
 wrote:
> i had and have several problems with 4.19.37-5  ... an selfbuild vanila
> kernel 4.19.60 with default options fixed most of them for me ...
>
> Debian should really push a newer 4.19.y kernel for buster
>
> Am 23.07.19 um 14:01 schrieb Terry Glanfield:
> > This is still failing after an update to 4.19.37-5+deb10u1
> >
> > Any clues on where to start tracking this down?
> >
>

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

[Kinky Nekoboi]

i had and have several problems with 4.19.37-5  ... an selfbuild vanila
kernel 4.19.60 with default options fixed most of them for me ...

Debian should really push a newer 4.19.y kernel for buster

Am 23.07.19 um 14:01 schrieb Terry Glanfield:
> This is still failing after an update to 4.19.37-5+deb10u1
>
> Any clues on where to start tracking this down?
>



signature.asc
Description: OpenPGP digital signature

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

[Terry Glanfield]

This is still failing after an update to 4.19.37-5+deb10u1

Any clues on where to start tracking this down?

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

[Ben Hutchings]

On Thu, 2019-07-18 at 21:36 +0100, Terry wrote:
> Package: src:linux
> Version: 4.19.37-5
> Severity: important
> 
> Dear Maintainer,
> 
> I performed an upgrade from stretch to buster today and the kernel
> paniced with a not syncing error.
> 
> I've attempted to switch of acpi but adding the options acpi=off
> pci=noacpi to the boot line but this didn't have any effect.
[...]

Disabling use of ACPI on any PC made in the last 15 years is likely to
make things worse, anyway.

Ben.

-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson




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

Bug#932408: linux-image-4.19.0-5-amd64: kernel panic not syncing

[Terry]

Package: src:linux
Version: 4.19.37-5
Severity: important

Dear Maintainer,

I performed an upgrade from stretch to buster today and the kernel paniced with 
a not syncing error.

I've attempted to switch of acpi but adding the options acpi=off pci=noacpi to 
the boot line but this didn't have any effect.

The details below are from the same machine booted with the 4.9 kernel.

I'll send images of the panic shortly.

Kind regards,
Terry.


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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP Compaq dc5800 Microtower
product_version: 
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: 786F2 v01.04
board_vendor: Hewlett-Packard
board_name: 2820h
board_version: 

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 82Q33 Express DRAM Controller 
[8086:29d0] (rev 02)
Subsystem: Hewlett-Packard Company 82Q33 Express DRAM Controller 
[103c:281e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation 82Q33 Express PCI Express Root 
Port [8086:29d1] (rev 02) (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- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [88] Subsystem: Hewlett-Packard Company 82Q33 Express PCI 
Express Root Port [103c:281e]
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA 
PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee0300c  Data: 41d1
Capabilities: [a0] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- 
TransPend-
LnkCap: Port #2, Speed 2.5GT/s, Width x16, ASPM L0s, Exit 
Latency L0s <1us, L1 <4us
ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ 
DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #1, PowerLimit 75.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Off, PwrInd On, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet+ LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
Capabilities: [100 v1] Virtual Channel
Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
Arb:Fixed- WRR32- WRR64- WRR128-
Ctrl:   ArbSelect=Fixed
Status: InProgress-
VC0:Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb:Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [140 v1] Root Complex Link
Desc:   PortNumber=02 ComponentID=01 EltType=Config
Link0:  Desc:   TargetPort=00 TargetComponent=01 AssocRCRB- 
LinkType=MemMapped LinkValid+
Addr:   fed19000
Kernel driver in use: pcieport
Kernel modules: shpchp

00:03.0 Communication controller [0780]: Intel Corporation 82Q33 Express MEI 
Controller [8086:29d4] (rev 02)
Subsystem: Hewlett-Packard Company 82Q33 Express MEI Controller 
[103c:281e]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr-