Re: mvsata problem

[KIYOHARA Takashi <kiyohara%kk.iij4u.or.jp@localhost>]

Hi! Mark,


From: Mark Davies <mark%ecs.vuw.ac.nz@localhost>
Date: Fri, 15 Oct 2010 15:33:51 +1300

> On Thu, 14 Oct 2010, KIYOHARA Takashi wrote:
> > Can you try rebuilded kernel with MVSATA_DEBUG and ATADEBUG again?
> 
> That produced:
> 
>    [...]
> wd0: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 
> sectors
> mvsata0:3: mvsata_exec_command: drive=0, bcount=512, r_command=0xec, 
> r_head=0x0, r_cyl=0x0, r_sector=0x0, r_count=0x0, r_features=0x0
> mvsata0:3: mvsata_cmd_start: drive=0
> mvsata0:0: mvsata_intr: cause=0x00000800
> mvsata0:3: mvsata_cmd_intr: drive=0
> mvsata0:3: mvsata_cmd_done: drive=0, flags=0x49
> mvsata0:3: mvsata_bio: drive=0, blkno=0, bcount=512
> mvsata0:3: mvsata_bio_start: drive=0
> mvsata0:0: mvsata_intr: cause=0x00000800
> fatal page fault in supervisor mode
>    [...]

hmm...

Do you disable DIAGNOSTIC on your kernel?  Can you try again with
DIAGNOSTIC, if yes?

Please send full backtrace to me, if you look message 'wdcintr: no xfer'
with DIAGNOSTIC.

Thanks,
--
kiyohara