LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-21-2005, 07:06 AM   #1
Charred
Member
 
Registered: Mar 2005
Location: Utah, USA
Distribution: Slackware 11
Posts: 816
Blog Entries: 2

Rep: Reputation: 30
Kernel OOPS morphs into BUG?


I have finally gotten around to configuring the NIC card in my desktop, and am attempting to network my desktop with my notebook such that the notebook can access the internet via my desktop (ip forwarding).
My lspci:
Code:
00:10.0 Ethernet controller: Atheros Communications, Inc. AR5212 802.11abg NIC (rev 01)
00:11.0 Ethernet controller: Macronix, Inc. [MXIC] MX98713 (rev 11)
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP 1X/2X (rev 5c)
After ensuring my kernel (A semi-custom 2.6.10) was configured to allow Masquerading, and blindly obeying a HOWTO I can't find at the moment, I first set up rc.firewall thus:
Code:
insmod ip_tables
insmod ip_conntrack
insmod ip_conntrack_ftp
insmod ipt_state
insmod iptable_nat
insmod ipt_MASQUERADE



echo 1 > /proc/sys/net/ipv4/ip_forward



iptables --flush


iptables --table nat --flush
iptables --delete-chain


iptables --table nat --delete-chain


iptables --table nat --append POSTROUTING --out-interface ath0 -j 
MASQUERADE
iptables --append FORWARD --in-interface eth0 -j ACCEPT
and my rc.inet1.conf:
Code:
# Config information for eth0:
#IPADDR[0]="192.168.1.254"  #This,
#NETMASK[0]="255.255.255.0"  #this,
#USE_DHCP[0]=""  #and this as advised by the HOWTO.
IPADDR[0]=""  #This,
NETMASK[0]=""  #this,
USE_DHCP[0]="yes"  #and this were altered secondary to the OOPS.
DHCP_HOSTNAME[0]=""
My rc.local looks like this:
Code:
ifconfig ath0 up
iwconfig ath0 essid "BlahBlah" #I'm surrounded by wireless networks, this ensures I use mine.
dhcpcd ath0
dhcpcd eth0  #This is new.
Upon reboot, I was greeted with the following message:
Code:
Aug 21 01:33:13 Taltos kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000028
Aug 21 01:33:13 Taltos kernel:  printing eip:
Aug 21 01:33:13 Taltos kernel: e9130bdf
Aug 21 01:33:13 Taltos kernel: *pde = 00000000
Aug 21 01:33:13 Taltos kernel: Oops: 0002 [#1]
Aug 21 01:33:13 Taltos kernel: PREEMPT 
Aug 21 01:33:13 Taltos kernel: Modules linked in: snd_pcm_oss snd_mixer_oss ipv6 iptable_nat ip_conntrack iptable_filter pcspkr intel_agp ath_pci ath_rate_onoe wlan ath_hal tulip nls_utf8 agpgart evdev psmouse
Aug 21 01:33:13 Taltos kernel: CPU:    0
Aug 21 01:33:13 Taltos kernel: EIP:    0060:[<e9130bdf>]    Tainted: P      VLI
Aug 21 01:33:13 Taltos kernel: EFLAGS: 00010256   (2.6.10) 
Aug 21 01:33:13 Taltos kernel: EIP is at ieee80211_add_ssid+0x1f/0x50 [wlan]
Aug 21 01:33:13 Taltos kernel: eax: 00000000   ebx: 00000028   ecx: 00000000   edx: 00000000
Aug 21 01:33:13 Taltos kernel: esi: e7174b7c   edi: e71743f4   ebp: e71743f4   esp: e7b0bd5c
Aug 21 01:33:13 Taltos kernel: ds: 007b   es: 007b   ss: 0068
Aug 21 01:33:13 Taltos kernel: Process ifconfig (pid: 2720, threadinfo=e7b0a000 task=e72b8140)
Aug 21 01:33:13 Taltos kernel: Stack: 00000000 00000000 e71743f4 e9131a08 00000028 e7174b7c 00000000 e90ef581 
Aug 21 01:33:13 Taltos kernel:        e7060000 e7174000 e1e9fec0 00000028 00000000 00000001 e71743f4 00000000 
Aug 21 01:33:13 Taltos kernel:        e9132cc3 e71743f4 e744de00 00000040 00000000 e744de00 e7060000 e7174000 
Aug 21 01:33:13 Taltos kernel: Call Trace:
Aug 21 01:33:13 Taltos kernel:  [<e9131a08>] ieee80211_send_mgmt+0x9a8/0x9f0 [wlan]
Aug 21 01:33:13 Taltos kernel:  [<e90ef581>] ath_chan_change+0x21/0x50 [ath_pci]
Aug 21 01:33:13 Taltos kernel:  [<e9132cc3>] ieee80211_newstate+0x2f3/0x6b0 [wlan]
Aug 21 01:33:13 Taltos kernel:  [<e90efa6d>] ath_newstate+0x1ad/0x3b0 [ath_pci]
Aug 21 01:33:13 Taltos kernel:  [<e912e3b4>] ieee80211_next_scan+0x124/0x180 [wlan]
Aug 21 01:33:13 Taltos kernel:  [<e912e27e>] ieee80211_begin_scan+0x7e/0x90 [wlan]
Aug 21 01:33:13 Taltos kernel:  [<e9132c63>] ieee80211_newstate+0x293/0x6b0 [wlan]
Aug 21 01:33:13 Taltos kernel:  [<e90efa6d>] ath_newstate+0x1ad/0x3b0 [ath_pci]
Aug 21 01:33:13 Taltos kernel:  [<e90eb215>] ath_init+0x195/0x2d0 [ath_pci]
Aug 21 01:33:13 Taltos kernel:  [<c02eaff5>] dev_open+0x85/0xa0
Aug 21 01:33:13 Taltos kernel:  [<c02eefb4>] dev_mc_upload+0x24/0x50
Aug 21 01:33:13 Taltos kernel:  [<c02ec613>] dev_change_flags+0x53/0x130
Aug 21 01:33:13 Taltos kernel:  [<c02eaec5>] dev_load+0x25/0x70
Aug 21 01:33:13 Taltos kernel:  [<c0328747>] devinet_ioctl+0x257/0x5d0
Aug 21 01:33:13 Taltos kernel:  [<c032aca6>] inet_ioctl+0x66/0xb0
Aug 21 01:33:13 Taltos kernel:  [<c02e1fd9>] sock_ioctl+0xd9/0x260
Aug 21 01:33:13 Taltos kernel:  [<c0160e6a>] sys_ioctl+0xca/0x230
Aug 21 01:33:13 Taltos kernel:  [<c01026bf>] syscall_call+0x7/0xb
Aug 21 01:33:13 Taltos kernel: Code: 8b 7c 24 04 83 c4 08 c3 8d 74 26 00 83 ec 0c 8b 44 24 18 89 1c 24 8b 5c 24 10 89 c1 89 74 24 04 c1 e9 02 8b 74 24 14 89 7c 24 08 <c6> 03 00 43 88 03 43 89 df f3 a5 a8 02 74 02 66 a5 a8 01 74 01
After rebooting via CD1, I discovered /etc/rc.d/rc.ip_forwarding, so I ran

# chmod -x /etc/rc.d/rc.firewall (I feel safe doing this because I'm already behind a firewall),

then I ran

# chmod 755 /etc/rc.d/rc.ip_forward

rebooted, and was killed by the same OOPS, so after consulting man pages, and much thought, I realized that I had gotten nowhere, so I made the changes to rc.inet1.conf noted in blue, rebooted again, and got:
Code:
Aug 21 02:45:13 Taltos dhcpcd[1372]: recvfrom: Network is down 
Aug 21 02:45:23 Taltos kernel: kernel BUG at net/core/skbuff.c:91!
Aug 21 02:45:23 Taltos kernel: invalid operand: 0000 [#1]
Aug 21 02:45:23 Taltos kernel: PREEMPT 
Aug 21 02:45:23 Taltos kernel: Modules linked in: snd_pcm_oss snd_mixer_oss pcspkr intel_agp ath_pci ath_rate_onoe wlan ath_hal tulip nls_utf8 evdev agpgart psmouse
Aug 21 02:45:23 Taltos kernel: CPU:    0
Aug 21 02:45:23 Taltos kernel: EIP:    0060:[<c02ec5cb>]    Tainted: P      VLI
Aug 21 02:45:23 Taltos kernel: EFLAGS: 00010296   (2.6.10) 
Aug 21 02:45:23 Taltos kernel: EIP is at skb_over_panic+0x3b/0x50
Aug 21 02:45:23 Taltos kernel: eax: 0000002c   ebx: e703d5e0   ecx: 00000000   edx: 00000000
Aug 21 02:45:23 Taltos kernel: esi: 00000130   edi: 00000015   ebp: e788e3f4   esp: e1e73d18
Aug 21 02:45:23 Taltos kernel: ds: 007b   es: 007b   ss: 0068
Aug 21 02:45:23 Taltos kernel: Process dhcpcd (pid: 2593, threadinfo=e1e72000 task=e7f9e540)
Aug 21 02:45:23 Taltos kernel: Stack: c03a00a0 e91396ca 00000015 00000015 c037ff3c e91396d6 e703d5e0 00000015 
Aug 21 02:45:23 Taltos kernel:        e91396ca 00000000 00000000 e788e3f4 e91349dc e1e73d68 00000015 e788e000 
Aug 21 02:45:23 Taltos kernel:        e90f9581 e716c000 e788e000 e788e3f4 e90f9695 00000000 00000001 e788e3f4 
Aug 21 02:45:23 Taltos kernel: Call Trace:
Aug 21 02:45:23 Taltos kernel:  [<e91396ca>] ieee80211_getmgtframe+0xba/0xe0 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e91396d6>] ieee80211_getmgtframe+0xc6/0xe0 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e91396ca>] ieee80211_getmgtframe+0xba/0xe0 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e91349dc>] ieee80211_send_mgmt+0x97c/0x9f0 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e90f9581>] ath_chan_change+0x21/0x50 [ath_pci]
Aug 21 02:45:23 Taltos kernel:  [<e90f9695>] ath_chan_set+0xe5/0x1f0 [ath_pci]
Aug 21 02:45:23 Taltos kernel:  [<e9135cc3>] ieee80211_newstate+0x2f3/0x6b0 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e90f9a6d>] ath_newstate+0x1ad/0x3b0 [ath_pci]
Aug 21 02:45:23 Taltos kernel:  [<e91313b4>] ieee80211_next_scan+0x124/0x180 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e913127e>] ieee80211_begin_scan+0x7e/0x90 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e9135c63>] ieee80211_newstate+0x293/0x6b0 [wlan]
Aug 21 02:45:23 Taltos kernel:  [<e90f9a6d>] ath_newstate+0x1ad/0x3b0 [ath_pci]
Aug 21 02:45:23 Taltos kernel:  [<e90f5215>] ath_init+0x195/0x2d0 [ath_pci]
Aug 21 02:45:23 Taltos kernel:  [<c02f1f15>] dev_open+0x85/0xa0
Aug 21 02:45:23 Taltos kernel:  [<c02f5e54>] dev_mc_upload+0x24/0x50
Aug 21 02:45:23 Taltos kernel:  [<c02f34b3>] dev_change_flags+0x53/0x130
Aug 21 02:45:23 Taltos kernel:  [<c02f1de5>] dev_load+0x25/0x70
Aug 21 02:45:23 Taltos kernel:  [<c032f437>] devinet_ioctl+0x257/0x5d0
Aug 21 02:45:23 Taltos kernel:  [<c0331996>] inet_ioctl+0x66/0xb0
Aug 21 02:45:23 Taltos kernel:  [<c0352101>] packet_ioctl+0x151/0x180
Aug 21 02:45:23 Taltos kernel:  [<c02e8f49>] sock_ioctl+0xd9/0x260
Aug 21 02:45:23 Taltos kernel:  [<c0160e6a>] sys_ioctl+0xca/0x230
Aug 21 02:45:23 Taltos kernel:  [<c01026bf>] syscall_call+0x7/0xb
Aug 21 02:45:23 Taltos kernel: Code: c0 0f 44 c2 89 44 24 10 8b 44 24 1c 89 44 24 0c 8b 41 60 c7 04 24 a0 00 3a c0 89 44 24 08 8b 44 24 20 89 44 24 04 e8 d5 7e e2 ff <0f> 0b 5b 00 09 e1 39 c0 83 c4 14 c3 89 f6 8d bc 27 00 00 00 00
I seriously doubt that I've been able to uncover an actual bug in the kernel after only 4-5 months of Linux usage (although I do have a great talent for breaking things), and I think the problem's got something to do with my wifi card, as I get a segmentation fault when I try to bring it up manually. I'm using Slax to connect to the internet at the moment, so I know the wifi card still works, but the only thing I'm sure about here is that I'm swimming in the deep end of the pool without the benefit of lessons.
The questions are:
  • Is this really a bug?
  • What obvious things have I missed in configuring my network?
 
Old 08-28-2005, 03:21 AM   #2
Charred
Member
 
Registered: Mar 2005
Location: Utah, USA
Distribution: Slackware 11
Posts: 816
Blog Entries: 2

Original Poster
Rep: Reputation: 30
I upgraded to the 2.6.12.5 kernel, and now I no longer get a segmentation fault when booting up. While following a much better HOWTO on tldp.org, I suddenly realized that I couldn't ping my loopback device with eth0.

Long story short, the problem was the half-arsed way macronix cloned the tulip chipset for their mx98713 NIC. It will not play with the tulip driver, and given its age and easy replacability, I'm gonna yank it in favor of something I know will work.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel Oops 2.6.11 --What does it mean??? ynakacs Linux - General 4 08-06-2005 04:38 AM
trying tp install slack10.1 gives kernel oops timsoft Slackware 2 04-03-2005 04:15 PM
Kernel 2.6.8-> Oops on NFS EyesOnly Linux - Software 2 08-15-2004 05:35 AM
Horrible Kernel Oops Thetargos Linux - General 2 08-13-2003 12:47 AM
Kernel oops on boot imbert Linux - Software 1 03-10-2003 01:16 PM


All times are GMT -5. The time now is 11:07 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration