From: "R. Herbst" <ruediger.herbst@googlemail.com>
To: Matt <jackdachef@gmail.com>
Cc: David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, geert@linux-m68k.org,
benh@kernel.crashing.org
Subject: Re: Sun GEM PPC32 Bug?
Date: Sun, 06 Feb 2011 15:22:25 +0100 [thread overview]
Message-ID: <4D4EAEA1.9030106@googlemail.com> (raw)
In-Reply-To: <AANLkTi=s7Yro4TqtmgW4HPnJx3HiWvX9iJ9NUOYXcR+j@mail.gmail.com>
Am 05.02.2011 21:32, schrieb Matt:
>> Is there a special Kernel parameter (sysctl.conf), that makes it
>> possible to use the Network. So how it is now I canŽt work with it. What
>> can I do at the moment?
>>
>
>> linuxopjemac, thank you for referring to Ben. He replied and might look into it.
>>
>
>> Meanwhile, I put the module reloading and interface restarting into a cron job that executes every hour: sudo crontab -e
>>
> # m h dom mon dow command
> 0 * * * * /usr/sbin/fix-sungem
>
>
>> and the script /usr/sbin/fix-sungem contains
>>
> /sbin/ifdown eth0&& /sbin/rmmod sungem&& /sbin/modprobe sungem&&
> /sbin/ifup eth0
>
> Hope that helps somewhat
>
> Regards
>
> Matt
>
Sorry. No positive effect in my case. Same bad Kernel-Messages for Sun-Gem.
Regards
Rüdi
next prev parent reply other threads:[~2011-02-06 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 16:55 Sun GEM PPC32 Bug? Matt
2011-02-04 20:51 ` Benjamin Herrenschmidt
2011-02-04 22:55 ` David Miller
2011-02-05 18:35 ` R. Herbst
2011-02-05 23:39 ` Benjamin Herrenschmidt
2011-02-05 23:45 ` Benjamin Herrenschmidt
2011-02-06 0:20 ` Matt
2011-02-05 20:32 ` Matt
2011-02-05 23:20 ` Benjamin Herrenschmidt
2011-02-06 14:22 ` R. Herbst [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-02-06 15:01 R. Herbst
2011-02-07 5:34 ` Benjamin Herrenschmidt
2011-02-08 18:28 ` R. Herbst
2011-02-08 19:58 ` Andreas Schwab
2011-02-09 0:18 ` Benjamin Herrenschmidt
2011-02-09 17:37 ` Andreas Schwab
2011-02-03 19:47 R. Herbst
2011-02-04 8:02 ` Geert Uytterhoeven
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=4D4EAEA1.9030106@googlemail.com \
--to=ruediger.herbst@googlemail.com \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=geert@linux-m68k.org \
--cc=jackdachef@gmail.com \
--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