From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, jnelson-kernel-bugzilla@jamponi.net
Subject: Re: [Bugme-new] [Bug 9382] New: etting MTU > 1500 on card "cold" sigsegs the "ip" program and produces an OOPS.
Date: Wed, 14 Nov 2007 19:23:19 -0800 [thread overview]
Message-ID: <20071114192319.e9423144.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-9382-10286@http.bugzilla.kernel.org/>
On Wed, 14 Nov 2007 19:11:38 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9382
>
> Summary: etting MTU > 1500 on card "cold" sigsegs the "ip"
> program and produces an OOPS.
> Product: Drivers
> Version: 2.5
> KernelVersion: VIA Velocity > 1500 MTU cold configure -=> OOPS
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Network
> AssignedTo: jgarzik@pobox.com
> ReportedBy: jnelson-kernel-bugzilla@jamponi.net
>
>
> Most recent kernel where this bug did not occur: Still occurs on latest
> openSUSE 10.3 kernel. A brief scan of the git log for this driver does not
> suggest a fix.
>
> Distribution: openSUSE 10.3
> Hardware Environment: AMD Athlon XP 2200
> Software Environment: kernel 2.6.22.12
> Problem Description: setting MTU > 1500 on card "cold" sigsegs the "ip" program
> and produces an OOPS.
>
> Steps to reproduce:
>
> 1. have a VIA Velocity gig-e NIC, *cold* (unconfigured but module loaded).
> 2. Issue:
>
> ip link set eth0 up 7200 192.168.1.1
>
> This has been an issue since at least 2.6.18 but I wasn't able to reproduce it
> on demand for a whole variety of reasons. Now I am able to reproduce it, 100%
> of the time, on-demand (although this requires a reboot.)
>
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address
> 00000003
> printing eip:
> f96a7772
> *pde = 00000000
> Oops: 0000 [#1]
> SMP
> last sysfs file: /devices/pci0000:00/0000:00:00.0/class
> Modules linked in: xt_tcpudp xt_pkttype ipt_LOG xt_limit drbd snd_pcm_oss
> snd_mixer_oss snd_seq snd_seq_device ipt_REJECT xt_state iptable_mangle
> iptable_nat nf_nat iptable_filter nf_conntrack_ipv4 nf_conntrack nfnetlink
> ip_tables ip6_tables x_tables tcp_bic apparmor dm_crypt loop dm_mirror dm_log
> dm_mod snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm button parport_pc rtc_cmos
> via_velocity sr_mod cdrom snd_timer rtc_core parport snd crc_ccitt rtc_lib
> soundcore snd_page_alloc shpchp sis_agp pci_hotplug agpgart i2c_sis630
> i2c_sis96x i2c_core sg usbhid hid ff_memless ehci_hcd sd_mod ohci_hcd usbcore
> piix sis5513 ide_core edd ext3 mbcache jbd fan pata_sis libata scsi_mod thermal
> processor
> CPU: 0
> EIP: 0060:[<f96a7772>] Tainted: G N VLI
> EFLAGS: 00010046 (2.6.22.12-0.1-default #1)
> EIP is at velocity_rx_refill+0x22/0x1d1 [via_velocity]
> eax: c197a500 ebx: c197a500 ecx: 00000000 edx: df8a9c00
> esi: c197a500 edi: 00000000 ebp: 00000000 esp: f774fe84
> ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068
> Process ip (pid: 4133, ti=f774e000 task=f7a31030 task.ti=f774e000)
> Stack: f774fef0 00000086 3f257025 c170a2a0 00000000 fffffff4 00000200 c197a500
> df8a9e00 fffffff4 f96a798f c01d0360 f96a61a7 c197a500 c197a000 00001c20
> 00000000 f96a8955 00008922 00008922 00000216 c197a000 00000001 00008922
> Call Trace:
> [<f96a798f>] velocity_init_rd_ring+0x6e/0xa0 [via_velocity]
> [<c01d0360>] __delay+0x6/0x7
> [<f96a61a7>] safe_disable_mii_autopoll+0x14/0x26 [via_velocity]
> [<f96a8955>] velocity_change_mtu+0xbc/0x104 [via_velocity]
> [<c026e62a>] dev_set_mtu+0x2d/0x5d
> [<c0270788>] dev_ioctl+0x3b1/0x43e
> [<c012daa8>] ptrace_notify+0x6a/0x94
> [<c026554b>] sock_ioctl+0x19f/0x1be
> [<c02653ac>] sock_ioctl+0x0/0x1be
> [<c017a131>] do_ioctl+0x21/0xa0
> [<c014dcc0>] audit_syscall_entry+0x105/0x13e
> [<c017a3e7>] vfs_ioctl+0x237/0x249
> [<c017a445>] sys_ioctl+0x4c/0x67
> [<c0104ea2>] syscall_call+0x7/0xb
> =======================
> Code: ff 31 c0 5a 5b 5e 5f 5d c3 55 57 56 53 89 c3 83 ec 18 8b a8 f8 00 00 00
> c7 44 24 10 00 00 00 00 89 ef c1 e7 04 03 bb 00 01 00 00 <80> 7f 03 00 0f 88 1d
> 01 00 00 8d 34 ed 00 00 00 00 03 b3 04 01
> EIP: [<f96a7772>] velocity_rx_refill+0x22/0x1d1 [via_velocity] SS:ESP
> 0068:f774fe84
>
next parent reply other threads:[~2007-11-15 3:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-9382-10286@http.bugzilla.kernel.org/>
2007-11-15 3:23 ` Andrew Morton [this message]
2007-11-15 3:38 ` [PATCH] via-velocity: don't oops on MTU change Stephen Hemminger
2007-11-15 3:48 ` David Miller
2007-11-15 8:26 ` Jarek Poplawski
2007-11-15 18:20 ` Stephen Hemminger
2007-11-15 23:10 ` Jarek Poplawski
2007-11-16 2:42 ` Jon Nelson
2007-11-16 4:05 ` Stephen Hemminger
2007-11-16 4:35 ` Stephen Hemminger
2007-11-16 16:21 ` Jon Nelson
2007-11-16 16:47 ` Stephen Hemminger
2007-11-17 0:25 ` David Miller
2007-11-17 0:59 ` Jon Nelson
2007-11-17 15:04 ` Jarek Poplawski
2007-11-28 22:02 ` Jon Nelson
2007-11-28 22:20 ` [PATCH] via-velocity: don't oops on MTU change (resend) Stephen Hemminger
2007-12-01 21:36 ` Jeff Garzik
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=20071114192319.e9423144.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jnelson-kernel-bugzilla@jamponi.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).