Re: New panic in wdc_ata_bio_intr

2017-10-17 Thread Jaromír Doleček
Not at the moment - on the end, I committed the version with flag. Thanks for report and testing! Jaromir 2017-10-16 21:12 GMT+02:00 Chavdar Ivanov : > Well, that was a good one. Running just fine now: > > ~ uname -a > NetBSD nt61p.lorien.lan 8.99.4 NetBSD 8.99.4 (GENERIC)

Re: New panic in wdc_ata_bio_intr

2017-10-17 Thread Chavdar Ivanov
Well, that was a good one. Running just fine now: ~ uname -a NetBSD nt61p.lorien.lan 8.99.4 NetBSD 8.99.4 (GENERIC) #1: Mon Oct 16 20:01:05 BST 2017 sysbu...@nt61p.lorien.lan:/home/sysbuild/src/sys/arch/amd64/compile/GENERIC amd64 ~ dmesg | grep wd0 wd0 at atabus0 drive 0 wd0: wd0: drive

Re: New panic in wdc_ata_bio_intr

2017-10-17 Thread Jaromír Doleček
Okay, can you try following patch? It puts puts back a flag for IRQ handling. If it works, I might have an idea what's happening. I think there is some rogue interrupt disturbing the state. If it doesn't work, can you please try to compile kernel with ATADEBUG, and set atadebug_mask (possibly via

Re: New panic in wdc_ata_bio_intr

2017-10-16 Thread Chavdar Ivanov
Sorry, it still crashes the same way. I made sure all was updated before trying, I do have ident /netbsd | grep wdc $NetBSD: atapi_wdc.c,v 1.128 2017/10/10 21:37:49 jdolecek Exp $ $NetBSD: ata_wdc.c,v 1.108 2017/10/15 11:27:14 jdolecek Exp $ $NetBSD: wdc_isa.c,v 1.60 2017/10/07

Re: New panic in wdc_ata_bio_intr

2017-10-16 Thread Jaromír Doleček
Hi, should be fixed in rev. 1.285 of dev/ic/wdc.c, can you please check? Jaromir 2017-10-14 17:48 GMT+02:00 Chavdar Ivanov : > It still panics the same way, no difference. > > On my other laptop, an HP EliteBook, I haven't the problem at all, only on > the two T61p's (one of

Re: New panic in wdc_ata_bio_intr

2017-10-16 Thread Chavdar Ivanov
It still panics the same way, no difference. On my other laptop, an HP EliteBook, I haven't the problem at all, only on the two T61p's (one of them stopped working a week ago, though). Chavdar Ivanov On Sat, 14 Oct 2017 at 15:45 Jaromír Doleček wrote: > Sorry, this

Re: New panic in wdc_ata_bio_intr

2017-10-16 Thread Jaromír Doleček
Sorry, this fixed patch 2017-10-14 16:23 GMT+02:00 Jaromír Doleček : > Can you try attached patch? > > Jaromir > > 2017-10-11 1:04 GMT+02:00 Chavdar Ivanov : > >> The timeouts when running under VirtualBox disappeared, but of course the >> panic on my

Re: New panic in wdc_ata_bio_intr

2017-10-16 Thread Jaromír Doleček
Can you try attached patch? Jaromir 2017-10-11 1:04 GMT+02:00 Chavdar Ivanov : > The timeouts when running under VirtualBox disappeared, but of course the > panic on my T61p remains. > > Chavdar Ivanov > > On Tue, 10 Oct 2017 at 22:40 Jaromír Doleček

Re: New panic in wdc_ata_bio_intr

2017-10-11 Thread Michael van Elst
jaromir.dole...@gmail.com (=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=) writes: >can you try with dev/scsipi/atapi_wdc.c 1.128? That should resolve the >timeouts for atapi, at least it did for me. For testing I did disable ahci mode, and promptly got timeouts ("interrupt lost") from pciide when

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
The timeouts when running under VirtualBox disappeared, but of course the panic on my T61p remains. Chavdar Ivanov On Tue, 10 Oct 2017 at 22:40 Jaromír Doleček wrote: > Hey, > > can you try with dev/scsipi/atapi_wdc.c 1.128? That should resolve the > timeouts for

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Jaromír Doleček
Hey, can you try with dev/scsipi/atapi_wdc.c 1.128? That should resolve the timeouts for atapi, at least it did for me. Jaromir 2017-10-10 8:08 GMT+02:00 Rares Aioanei : > I get that also on VBox, except it doesn't try to add cd0a as a swap > device, nor does it show an

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Rares Aioanei
I get that also on VBox, except it doesn't try to add cd0a as a swap device, nor does it show an endless stream of "lost interrupt" messages; eventually I get a login prompt. This is with yesterday's latest -CURRENT. On Sun, Oct 8, 2017 at 5:17 PM, Chavdar Ivanov wrote: > I

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
Examining the relevant commit in this period, it is only the NCQ update which has anything to doç ... Merge support for SATA NCQ (Native Command Queueing) from jdolecek-ncq branch ... It is way too complicated for me to try to back it out piecemeal to find something. But as far as I understand it

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
A bit sad responding to myself... Anyway, https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201710060130Z/amd64/binary/kernel/netbsd-GENERIC.gz works fine. https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201710071630Z/amd64/binary/kernel/netbsd-GENERIC.gz crashes, in case someone else is hit by

Re: New panic in wdc_ata_bio_intr

2017-10-10 Thread Chavdar Ivanov
The same happens with the kernel built some hour ago. The last kernel I am running on the T61p is from 05/10/2017. I just tested https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201710081900Z/amd64/binary/kernel/netbsd-GENERIC.gz with exactly the same result. There have been quite a few recent

New panic in wdc_ata_bio_intr

2017-10-09 Thread Chavdar Ivanov
System updated about two hours ago. I am getting: wd0 at atabus0 drive 0 wd0: wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 298 GB, 620181 cyl, 16 head, 63 sec, 512 bytes/sect x 625142448 sectors piixide0:0:0: bad state 0 in wdc_ata_bio_intr panic: wdc_ata_bio_intr: bad

Re: New panic in wdc_ata_bio_intr

2017-10-09 Thread Chavdar Ivanov
I tried the same kernel on a VirtualBox guest - it doesn't crash, but one gets endless piixide0:1:0: lost interrupt type: atapi tc_bcount: 0 tc_skip: 0 stream of messages. Also /etc/rc.d/swap2 start hangs while trying to add /dev/cd0a as a dump device... as shown by ktruss. Weird.