From: Dale Ogilvie <k1qeelx02@sneakemail.com>
To: romieu@fr.zoreil.com
Cc: jcliburn@gmail.com, netdev@vger.kernel.org
Subject: Re: Repeatable r8169 kernel oops testcase
Date: Mon, 01 Dec 2008 22:11:07 +1300 [thread overview]
Message-ID: <1228122667.3160.19.camel@localhost.localdomain> (raw)
In-Reply-To: <49336B0A.6000000@sneakemail.com>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
[root@gordon ~]#
cat /sys/devices/system/clocksource/clocksource0/available_clocksource
acpi_pm jiffies tsc
Since I don't have hpet in my available_clocksources I tried notsc and
clocksource=acpi_pm. I also tried the two ethtool commands below.
None of these changes made any difference. Networking is dead until the
r8169 module is unloaded and reloaded. Also, while the network is up but
"dead", mouse input is erratic. Moving the mouse is not smooth at all.
Something is severely wrong while the r8169 module is in this state.
See attached .config.
> Jay Cliburn <jcliburn@gmail.com> :
> [...]
> > Does booting with clocksource=hpet change anything? What about the
> > others in
> > /sys/devices/system/clocksource/clocksource0/available_clocksource
>
> Once this is done, can your send your .config and tell if simply
> issuing an 'ethtool -s eth0 autoneg off' then 'ethtool -s eth0 autoneg on'
> makes a difference ?
>
> --
> Ueimor
>
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 23379 bytes --]
next parent reply other threads:[~2008-12-01 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49336B0A.6000000@sneakemail.com>
2008-12-01 9:11 ` Dale Ogilvie [this message]
2008-12-01 22:43 ` Repeatable r8169 kernel oops testcase Francois Romieu
2008-11-30 10:29 Dale Ogilvie
2008-11-30 12:38 ` Jay Cliburn
2008-11-30 22:45 ` Francois Romieu
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=1228122667.3160.19.camel@localhost.localdomain \
--to=k1qeelx02@sneakemail.com \
--cc=jcliburn@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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