From: Jacek Luczak <difrost@pin.if.uz.zgora.pl>
To: chaosite@gmail.com
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: Something wrong with 2.6.12-rc1-RT-V0.7.43-05
Date: Sat, 02 Apr 2005 22:46:57 +0200 [thread overview]
Message-ID: <424F04C1.7050902@pin.if.uz.zgora.pl> (raw)
In-Reply-To: <424EF485.7050004@pin.if.uz.zgora.pl>
Jacek Luczak napisał(a):
> Matan Peled napisał(a):
>
>> Jacek Luczak wrote:
>>
>>> Hi
>>>
>>> Early morning i made a 2.6.12-rc1 with RT-V0.7.43-05 and this is what I
>>> sow in dmesg after 6 hours of computers work:
>>>
>>> <SNIP!>
>>
>>
>>
>> Hmm... A lot of that seems to involve ndiswrapper. Is there any way
>> you could
>> reproduce this without ndiswrapper loaded?
>
>
> I will try and send it back.
>
It seems that everything is involve by ndiswrapper. Those errors
reappear after module load. Without ndiswrapper kernel works OK.
Jacek
prev parent reply other threads:[~2005-04-02 20:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 19:15 Jacek Luczak
2005-04-02 19:26 ` Matan Peled
[not found] ` <424EF485.7050004@pin.if.uz.zgora.pl>
2005-04-02 20:46 ` Jacek Luczak [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=424F04C1.7050902@pin.if.uz.zgora.pl \
--to=difrost@pin.if.uz.zgora.pl \
--cc=chaosite@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®