From: Jesper Dangaard Brouer <hawk@comx.dk>
To: Maximilian Attems <max@stro.at>
Cc: Michael Prokop <mika@debian.org>, "Marco d'Itri" <md@linux.it>,
Debian kernel team <debian-kernel@lists.debian.org>,
Mike Miller <mike.miller@hp.com>,
Jens Axboe <jaxboe@fusionio.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Kay Sievers <kay.sievers@vrfy.org>,
Martin Pitt <martin.pitt@ubuntu.com>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: HP G6 hardware kernel boot issue > 2.6.37 cciss/hpsa
Date: Tue, 08 Mar 2011 11:29:26 +0100 [thread overview]
Message-ID: <1299580166.11985.11.camel@firesoul.comx.local> (raw)
In-Reply-To: <20110303124705.GA19471@stro.at>
On Thu, 2011-03-03 at 13:47 +0100, Maximilian Attems wrote:
> On Wed, 02 Mar 2011, Jesper Dangaard Brouer wrote:
>
[...]
> please file proper Debian bug report with reportbug.
> we already have scripts dealing with such device changes.
> Had previously thought that the need of them was over after the
> libata change, but obviously you show the contrare.
>
> So fire up reportbug and report against linux-2.6 with severity grave.
I finally succeeded filing a Debian bug-report (as Debians mail system
clamav kept categorizing me as malware... hmm)
Debian bug number: 617256
Link: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617256
Update the case via email: 617256@bugs.debian.org
--
Med venlig hilsen / Best regards
Jesper Brouer
ComX Networks A/S
Linux Network Kernel Developer
Cand. Scient Datalog / MSc.CS
Author of http://adsl-optimizer.dk
LinkedIn: http://www.linkedin.com/in/brouer
[...]
> > Keywords: driver CCISS, HPSA, HP DL G6, uuid, udev, mkinitramfs,
> > initramfs-tools, debian squeeze
More keywords:
HP Smart Array P410i Controller / Smart Array G6 controllers
/dev/cciss/ scsi
next prev parent reply other threads:[~2011-03-08 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:42 Jesper Dangaard Brouer
2011-03-03 12:47 ` Maximilian Attems
2011-03-08 10:29 ` Jesper Dangaard Brouer [this message]
2011-03-08 13:49 ` Ben Hutchings
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=1299580166.11985.11.camel@firesoul.comx.local \
--to=hawk@comx.dk \
--cc=debian-kernel@lists.debian.org \
--cc=eric.dumazet@gmail.com \
--cc=jaxboe@fusionio.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.pitt@ubuntu.com \
--cc=max@stro.at \
--cc=md@linux.it \
--cc=mika@debian.org \
--cc=mike.miller@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®