LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 10-24-2005, 12:27 PM   #1
rollo
Member
 
Registered: Apr 2004
Location: France
Distribution: Debian Sid (Kanotix)
Posts: 237

Rep: Reputation: 30
Question Module conflict causing network services to fail


New kernel installed, with few config changes. However, one config change was enabling the following module:

Code:
Bus > PCI > CardBus Bridge support <M>
Now network services fails to start at boot, and I have to go into YaST and initiate the network card manually to get it to work.

Then, on shutdown, I get the following errors just before power-down:

Code:
FATAL: module yenta-socket is in use
FATAL: module pcmcia-core is in use
What could be going on? Is this some kind of module conflict, and is the only solution to recompile the kernel? Extracts from /var/log/boot.log and /var/log/messages follow.

Help appreciated.


Quote:
STARTUP FROM /var/log/boot.log

<notice>start services (network)
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
It's not possible to reject outgoing packets. Expect Timeouts.
Warning: /etc/resolv.conf not found

Warning: No interface active (yet?)ip6tables: No chain/target/match by that name
ip6tables: No chain/target/match by that name
ip6tables: No chain/target/match by that name
done eth-id-00:08:a1:6a:b2:83 No interface found
failedSetting up service network . . . . . . . . . . . . . . . .failed
<notice>exit status of (network) is (7)
Quote:
STARTUP FROM /var/log/messages

Oct 24 17:36:11 linux kernel: Yenta: CardBus bridge found at 0000:00:0c.0 [0e11:b048]
Oct 24 17:36:11 linux kernel: Yenta: Enabling burst memory read transactions
Oct 24 17:36:11 linux kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta: Routing CardBus interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta TI: socket 0000:00:0c.0, mfunc 0x00000000, devctl 0x64
Oct 24 17:36:11 linux kernel: Yenta: ISA IRQ mask 0x06d8, PCI irq 11
Oct 24 17:36:11 linux kernel: Socket status: 30000006
Oct 24 17:36:11 linux kernel: ACPI: PCI Interrupt 0000:00:0c.1[A] -> Link [C187] -> GSI 11 (level, low) -> IRQ 11
Oct 24 17:36:11 linux kernel: Yenta: CardBus bridge found at 0000:00:0c.1 [0e11:b048]
Oct 24 17:36:11 linux kernel: Yenta: Using CSCINT to route CSC interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta: Routing CardBus interrupts to PCI
Oct 24 17:36:11 linux kernel: Yenta TI: socket 0000:00:0c.1, mfunc 0x00000000, devctl 0x64
Oct 24 17:36:11 linux kernel: Yenta: ISA IRQ mask 0x06d8, PCI irq 11
Oct 24 17:36:11 linux kernel: Socket status: 30000020

[...]

Oct 24 17:38:50 linux kernel: 8139too Fast Ethernet driver 0.9.27
Oct 24 17:38:50 linux kernel: PCI: Enabling device 0000:06:00.0 (0000 -> 0003)
Oct 24 17:38:50 linux kernel: ACPI: PCI Interrupt 0000:06:00.0[A] -> Link [C187] -> GSI 11 (level, low) -> IRQ 11
Oct 24 17:38:50 linux kernel: PCI: Setting latency timer of device 0000:06:00.0 to 64
Oct 24 17:38:50 linux kernel: eth0: RealTek RTL8139 at 0xc8bec000, 00:08:a1:6a:b2:83, IRQ 11
Oct 24 17:38:50 linux kernel: eth0: Identified 8139 chip type 'RTL-8139C'
Oct 24 17:38:50 linux kernel: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Oct 24 17:38:51 linux kernel: NET: Registered protocol family 17
Oct 24 17:38:51 linux dhcpcd[13340]: broadcasting DHCP_DISCOVER
Oct 24 17:38:51 linux dhcpcd[13340]: dhcpIPaddrLeaseTime=21600 in DHCP server response.
Oct 24 17:38:51 linux dhcpcd[13340]: dhcpT1value is missing in DHCP server response. Assuming 10800 sec
Oct 24 17:38:51 linux dhcpcd[13340]: dhcpT2value is missing in DHCP server response. Assuming 18900 sec
Oct 24 17:38:51 linux modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file
Oct 24 17:38:53 linux SuSEfirewall2: Another SuSEfirewall2 with PID 13399 found, waiting ...
Oct 24 17:38:54 linux /etc/hotplug/net.agent[13254]: ip6tables: No chain/target/match by that name
Oct 24 17:38:54 linux last message repeated 2 times
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpIPaddrLeaseTime=21594 in DHCP server response.
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT1value is missing in DHCP server response. Assuming 10797 sec
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT2value is missing in DHCP server response. Assuming 18894 sec
Oct 24 17:38:55 linux dhcpcd[13340]: DHCP_OFFER received from (212.198.0.73)
Oct 24 17:38:55 linux dhcpcd[13340]: broadcasting DHCP_REQUEST for 81.67.26.244
Oct 24 17:38:55 linux kernel: SFW2-IN-ILL-TARGET IN=eth0 OUT= MAC=00:08:a1:6a:b2:83:00:30:b8:c2:cd:50:08:00 SRC=81.67.26.1 DST=81.67.26.244 LEN=361 TOS=0x00 PREC=0x00 TTL=255 ID=15994 PROTO=UDP SPT=67 DPT=68 LEN=341
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpIPaddrLeaseTime=21594 in DHCP server response.
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT1value is missing in DHCP server response. Assuming 10797 sec
Oct 24 17:38:55 linux dhcpcd[13340]: dhcpT2value is missing in DHCP server response. Assuming 18894 sec
Oct 24 17:38:55 linux dhcpcd[13340]: DHCP_ACK received from (212.198.0.73)
Oct 24 17:38:55 linux kernel: SFW2-IN-ILL-TARGET IN=eth0 OUT= MAC=00:08:a1:6a:b2:83:00:30:b8:c2:cd:50:08:00 SRC=81.67.26.1 DST=81.67.26.244 LEN=361 TOS=0x00 PREC=0x00 TTL=255 ID=16000 PROTO=UDP SPT=67 DPT=68 LEN=341
Oct 24 17:38:55 linux dhcpcd[13776]: terminating on signal 15
Oct 24 17:38:59 linux SuSEfirewall2: Firewall rules successfully set from /etc/sysconfig/SuSEfirewall2
Oct 24 17:39:00 linux kernel: eth0: no IPv6 routers present


SHUTDOWN FROM /var/log/messages

Oct 23 14:13:53 linux init: Switching to runlevel: 6
Oct 23 14:14:08 linux sshd[4895]: Received signal 15; terminating.
Oct 23 14:14:10 linux kernel: Device 'snd_generic_pm.0' does not have a release() function, it is broken and must be fixed.
Oct 23 14:14:10 linux kernel: Badness in device_release at drivers/base/core.c:83
Oct 23 14:14:10 linux kernel: [kobject_cleanup+105/112] kobject_cleanup+0x69/0x70
Oct 23 14:14:10 linux kernel: [<c020edd9>] kobject_cleanup+0x69/0x70
Oct 23 14:14:10 linux kernel: [kobject_release+0/16] kobject_release+0x0/0x10
Oct 23 14:14:10 linux kernel: [<c020ede0>] kobject_release+0x0/0x10
Oct 23 14:14:10 linux kernel: [kref_put+38/112] kref_put+0x26/0x70
Oct 23 14:14:10 linux kernel: [<c020f5d6>] kref_put+0x26/0x70
Oct 23 14:14:11 linux kernel: [pg0+142017704/1068983296] snd_generic_device_unregister+0x8/0x20 [snd]
Oct 23 14:14:11 linux kernel: [<c8bf84a8>] snd_generic_device_unregister+0x8/0x20 [snd]
Oct 23 14:14:11 linux kernel: [pg0+142015436/1068983296] snd_card_free+0x16c/0x260 [snd]
Oct 23 14:14:11 linux kernel: [<c8bf7bcc>] snd_card_free+0x16c/0x260 [snd]
Oct 23 14:14:11 linux kernel: [complete+34/48] complete+0x22/0x30
Oct 23 14:14:11 linux kernel: [<c0119102>] complete+0x22/0x30
Oct 23 14:14:11 linux kernel: [kobject_cleanup+88/112] kobject_cleanup+0x58/0x70
Oct 23 14:14:11 linux kernel: [<c020edc8>] kobject_cleanup+0x58/0x70
Oct 23 14:14:11 linux kernel: [kobject_release+0/16] kobject_release+0x0/0x10
Oct 23 14:14:11 linux kernel: [<c020ede0>] kobject_release+0x0/0x10
Oct 23 14:14:11 linux kernel: [kobject_release+0/16] kobject_release+0x0/0x10
Oct 23 14:14:11 linux kernel: [<c020ede0>] kobject_release+0x0/0x10
Oct 23 14:14:11 linux kernel: [kref_put+38/112] kref_put+0x26/0x70
Oct 23 14:14:11 linux kernel: [<c020f5d6>] kref_put+0x26/0x70
Oct 23 14:14:11 linux kernel: [pg0+142199309/1068983296] alsa_card_es18xx_exit+0x1d/0x24 [snd_es18xx]
Oct 23 14:14:11 linux kernel: [<c8c24a0d>] alsa_card_es18xx_exit+0x1d/0x24 [snd_es18xx]
Oct 23 14:14:11 linux kernel: [sys_delete_module+340/368] sys_delete_module+0x154/0x170
Oct 23 14:14:11 linux kernel: [<c0130ff4>] sys_delete_module+0x154/0x170
Oct 23 14:14:11 linux kernel: [do_munmap+203/256] do_munmap+0xcb/0x100
Oct 23 14:14:11 linux kernel: [<c014b19b>] do_munmap+0xcb/0x100
Oct 23 14:14:11 linux kernel: [sysenter_past_esp+84/121] sysenter_past_esp+0x54/0x79
Oct 23 14:14:11 linux kernel: [<c0102d4b>] sysenter_past_esp+0x54/0x79
Oct 23 14:14:15 linux SuSEfirewall2: Firewall rules unloaded.
Oct 23 14:14:16 linux kernel: Kernel logging (proc) stopped.
Oct 23 14:14:16 linux kernel: Kernel log daemon terminating.
Oct 23 14:14:17 linux exiting on signal 15
 
Old 10-26-2005, 03:57 AM   #2
AwesomeMachine
Senior Member
 
Registered: Jan 2005
Location: USA and Italy
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 3,262

Rep: Reputation: 582Reputation: 582Reputation: 582Reputation: 582Reputation: 582Reputation: 582
Goto yast and open software installation source.

Disable everything.

Put this in there:

ftp
mirrors.kernel.org
/suse/i386/9.1
finish

Then open install software

Look in package groups

Go all the way to the bottom

open zzz all

goto k and right click on the kernel that is installed.

click update.

do the same thing for modules if there is a separate package for modules in SuSE 9.1. I forgot if there is or not.

Reboot

Do not recompile the kernel in SuSE again.
 
Old 10-26-2005, 01:26 PM   #3
rollo
Member
 
Registered: Apr 2004
Location: France
Distribution: Debian Sid (Kanotix)
Posts: 237

Original Poster
Rep: Reputation: 30
Question

I don't follow the bit about package groups. Are you referring to a package called "zzz"? If so, I don't see it.

There is surely a quicker solution to this than reinstalling or recompiling. It seems to be a simple driver problem of some sort, which has to do with the mysterious error message on shutdown:

Code:
FATAL: module yenta-socket is in use
FATAL: module pcmcia-core is in use
 
Old 11-01-2005, 01:19 PM   #4
rollo
Member
 
Registered: Apr 2004
Location: France
Distribution: Debian Sid (Kanotix)
Posts: 237

Original Poster
Rep: Reputation: 30
More specifically, the scrolling output on shutdown is:

Code:
Shutting down service network
Shutting down PCMCIA cardmgr
FATAL: module yenta-socket is in use
FATAL: module pcmcia-core is in use
Anyone any idea what went wrong?
 
  


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
fail to add speedstep-ich module elvislu Linux - Laptop and Netbook 3 04-03-2005 05:15 AM
Network switch causing problems? marcheikens Linux - Hardware 18 10-27-2004 12:16 AM
Fail shut down console mouse services? SuperCoolAl Fedora 3 03-14-2004 09:26 PM
ATI Driver module build fail Bana Linux - Software 0 02-16-2004 03:54 PM
Network causing unhappiness! Noobee Linux - Networking 4 07-18-2002 03:01 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 01:16 AM.

Main Menu
Advertisement
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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration