public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ROBERT HANCOCK <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org, christiand59@web.de
Subject: Re: ata2: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl
Date: Sun, 19 Nov 2006 11:18:06 -0500	[thread overview]
Message-ID: <d037c80430c7f.45603d6e@shaw.ca> (raw)
In-Reply-To: <cb8795142da89.455f6345@shaw.ca>

Christian wrote:
> 
> FYI:
> My system config is one 400GB disk at sda, and two 250GB disks on a dmraid 
> nvidia-fakeraid set of sdb and sdc.
> 
> My kernel message buffer gets quickly overrun by a flood of these error 
> messages:
> 
> Nov 17 22:48:12 ubuntu kernel: [  119.566540] attempt to access beyond end of 
> device
> Nov 17 22:48:12 ubuntu kernel: [  119.566602] sdb: rw=0, want=976784000, 
> limit=488397168

This seems like some other issue. For some reason the kernel is trying to access something way out at about 465GB on the /dev/sdb device..

> p.s:
> Why does the kernel report a queue depth of 31/32, but hdparm says its 32? Is 
> this correct?
> 
> ata1.00: ATA-7, max UDMA7, 781422768 sectors: LBA48 NCQ (depth 31/32)

The drive supports 32 but libata reserves one queue entry for its own use, therefore the actual queue depth in use is 31.

  parent reply	other threads:[~2006-11-19 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19  0:47 ata2: EH in ADMA mode, notifier 0x0 notifier_error 0x0 gen_ctl ROBERT HANCOCK
2006-11-19 14:19 ` Christian
2006-11-19 16:18 ` ROBERT HANCOCK [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-18 13:36 Christian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d037c80430c7f.45603d6e@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=christiand59@web.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox