From: Chuck Ebbert <cebbert@redhat.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
linux-kernel@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: possible BUG while using CUPS
Date: Tue, 14 Aug 2007 11:21:21 -0400 [thread overview]
Message-ID: <46C1C871.5020803@redhat.com> (raw)
In-Reply-To: <46C07CEF.1020207@xs4all.nl>
On 08/13/2007 11:46 AM, Udo van den Heuvel wrote:
> Michal Piotrowski wrote:
>> On 11/08/07, Udo van den Heuvel <udovdh@xs4all.nl> wrote:
>>> Using Cups 1.2.12 on Linux 2.6.22.1.
> (...)
>>> I clikc that link and hear the ping-ping of the BUG:
>> This is very interesting. Can you reproduce this bug?
>
> I think so. (at least: I have seen it before: clicking around in Cups
> and this crash/bug/whatever.)
>
>>> This is on a VIA Epia EK8000. ksymoops did not really help me, this is
>>> all output I got.
>>>
>>> Ideas?
>> BTW. Please try 2.6.22.2.
>
> Compiling...
If you can reproduce that, do it after booting with "kstack=2048" and post
that so we can see the whole stack in the oops message.
prev parent reply other threads:[~2007-08-14 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46BD762F.4060801@xs4all.nl>
2007-08-13 15:39 ` possible BUG while using CUPS Michal Piotrowski
2007-08-13 15:46 ` Udo van den Heuvel
2007-08-14 15:21 ` Chuck Ebbert [this message]
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=46C1C871.5020803@redhat.com \
--to=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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;
as well as URLs for NNTP newsgroup(s).