All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "David S. Miller" <davem@davemloft.net>,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	Alan Cox <alan@linux.intel.com>,
	linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-ide: hda: possibly failed opcode: 0x25 on Alpha with 2.6.34-rc3
Date: Tue, 13 Apr 2010 17:34:57 +0200	[thread overview]
Message-ID: <201004131734.57365.bzolnier@gmail.com> (raw)
In-Reply-To: <20100406232659.GA4788@physik.fu-berlin.de>

On Wednesday 07 April 2010 01:26:59 am Adrian Glaubitz wrote:
> Dear IDE maintainers,

I'm flattered but nowadays I'm just a maintainer of a modest
out-of-tree project or two.. ;-)

> I recently installed Debian unstable on an old digital personal
> workstation 433au alpha (Miata) [1] with the default kernel 2.6.32
> from Debian unstable. There were no obvious problems except for the
> tulip network driver which produced a lot of noise [2]. Joe Perches was
> so kind to provide a patch to reduce the noise. I applied the patch
> against 2.6.34-rc3 and rebuilt the kernel with the 2.6.32 Debian
> config using "make oldconfig". The kernel build took around 18 hours ;).
> 
> Anyway, after rebooting the machine into the new kernel (2.6.34-rc3), the
> IDE driver obviously triggered a lot of errors [3] resulting in the kernel
> not being able to mount the root partition.

I think that the highest chance of bringing the right people's
attention to this kernel regression would be achieved by filling
the official bug-report at https://bugzilla.kernel.org/.

Thanks.
--
Bartlomiej Zolnierkiewicz

  reply	other threads:[~2010-04-13 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 23:26 linux-ide: hda: possibly failed opcode: 0x25 on Alpha with 2.6.34-rc3 Adrian Glaubitz
2010-04-13 15:34 ` Bartlomiej Zolnierkiewicz [this message]
2010-04-13 16:46   ` Adrian Glaubitz

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=201004131734.57365.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.