From: Chris Rankin <rankincj@yahoo.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [BUG] Linux 2.6.20.1 - unable to handle kernel paging request - accessing freed memory?
Date: Thu, 1 Mar 2007 13:27:49 +0000 (GMT) [thread overview]
Message-ID: <700199.70204.qm@web52902.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0703011330330.29829@sbz-30.cs.Helsinki.FI>
Oh yes - I'd better mention what my Ethernet devices are:
$ cat /proc/net/dev
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo
colls carrier compressed
lo: 820705 15570 0 0 0 0 0 0 820705 15570 0 0 0
0 0 0
eth0: 3289077 14258 0 0 0 0 0 639 1379700 14175 0 0 0
0 0 0
eth1: 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0
eth2: 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0
$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:0D:56:0D:E7:3F
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:56ff:fe0d:e73f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14262 errors:0 dropped:0 overruns:0 frame:0
TX packets:14175 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3289533 (3.1 MiB) TX bytes:1379700 (1.3 MiB)
Base address:0xdcc0 Memory:ff6e0000-ff700000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:15570 errors:0 dropped:0 overruns:0 frame:0
TX packets:15570 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:820705 (801.4 KiB) TX bytes:820705 (801.4 KiB)
# /sbin/ifconfig eth1
eth1 Link encap:UNSPEC HWaddr 87-FF-FF-FF-FF-FF-FF-00-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
# /sbin/ifconfig eth2
eth2 Link encap:UNSPEC HWaddr 00-02-3C-00-A1-03-71-11-00-00-00-00-00-00-00-00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
I think that eth1 and eth2 are both "eth1394" devices, automatically loaded on the two Firewire
"hubs"(?) in this machine?
Cheers,
Chris
___________________________________________________________
All New Yahoo! Mail – Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html
next prev parent reply other threads:[~2007-03-01 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-26 1:26 [BUG] Linux 2.6.20.1 - unable to handle kernel paging request - accessing freed memory? Chris Rankin
2007-02-26 18:42 ` Randy Dunlap
2007-02-26 19:57 ` [Alsa-devel] " Takashi Iwai
2007-02-27 13:25 ` Chris Rankin
2007-02-27 14:48 ` Pekka Enberg
2007-03-01 11:28 ` Chris Rankin
2007-03-01 11:32 ` Pekka J Enberg
2007-03-01 13:22 ` Chris Rankin
2007-03-01 13:27 ` Chris Rankin [this message]
2007-03-07 23:29 ` Chris Rankin
2007-03-08 1:26 ` Chris Rankin
2007-02-26 20:08 ` Chris Rankin
2007-02-27 14:42 ` Pekka Enberg
2007-02-27 17:04 ` Chris Rankin
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=700199.70204.qm@web52902.mail.yahoo.com \
--to=rankincj@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=randy.dunlap@oracle.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