redhat-list Digest, Vol 9, Issue 28
Aimin Yan
aiminy at iastate.edu
Sat Nov 27 17:17:24 UTC 2004
I run lspci
I get the following:
then how to do next?
Aimin
00:00.0 Host bridge: Intel Corp. 82852/855GM Host Bridge (rev 02)
00:00.1 System peripheral: Intel Corp. 855GM/GME GMCH Memory I/O Control
Registers (rev 02)
00:00.3 System peripheral: Intel Corp. 855GM/GME GMCH Configuration Process
Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corp. 82852/855GM Integrated
Graphics Device (rev 02)
00:02.1 Display controller: Intel Corp. 82852/855GM Integrated Graphics
Device (rev 02)
00:1d.0 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corp. 82801DB (ICH4) USB UHCI #3 (rev 03)
00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
(rev 03)
00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI Bridge (rev 83)
00:1f.0 ISA bridge: Intel Corp. 82801DBM LPC Interface Controller (rev 03)
00:1f.1 IDE interface: Intel Corp. 82801DBM (ICH4) Ultra ATA Storage
Controller (rev 03)
00:1f.3 SMBus: Intel Corp. 82801DB/DBM (ICH4) SMBus Controller (rev 03)
00:1f.5 Multimedia audio controller: Intel Corp. 82801DB (ICH4) AC'97 Audio
Controller (rev 03)
00:1f.6 Modem: Intel Corp. 82801DB (ICH4) AC'97 Modem Controller (rev 03)
02:01.0 Network controller: Intel Corp. PRO/Wireless LAN 2100 3B Mini PCI
Adapter (rev 04)
02:04.0 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
02:04.1 CardBus bridge: Texas Instruments PCI7420 CardBus Controller
02:04.2 FireWire (IEEE 1394): Texas Instruments: Unknown device 802e
02:04.3 Unknown mass storage controller: Texas Instruments PCI7420 Flash
Media Controller
02:05.0 Ethernet controller: Broadcom Corporation BCM5705M 10/100/1000Base
T (rev 02)
At 11:00 2004-11-26, you wrote:
>Send redhat-list mailing list submissions to
> redhat-list at redhat.com
>
>To subscribe or unsubscribe via the World Wide Web, visit
> https://www.redhat.com/mailman/listinfo/redhat-list
>or, via email, send a message with subject or body 'help' to
> redhat-list-request at redhat.com
>
>You can reach the person managing the list at
> redhat-list-owner at redhat.com
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of redhat-list digest..."
>
>
>Today's Topics:
>
> 1. Checkpoint Firewall-1 NG FP2 (Brian McGrew)
> 2. firewall survey (Dana Holland)
> 3. how to set up wireless network connection in Fedro 2 (Aimin Yan)
> 4. Re: how to set up wireless network connection in Fedro 2 (Edward)
> 5. Re: how to set up wireless network connection in Fedro 2
> (C. Linus Hicks)
> 6. Re: firewall survey (Pete Nesbitt)
> 7. RE: Perl script Problem with Linux (Padiyath Sreekumaran)
> 8. Re: Perl script Problem with Linux (Jason Dixon)
> 9. Power down of SMP servers (McDougall, Marshall (FSH))
> 10. kernel panic HP DL 380 G3 (Amanda Galligan)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Thu, 25 Nov 2004 10:14:00 -0800
>From: "Brian McGrew" <Brian at doubledimension.com>
>Subject: Checkpoint Firewall-1 NG FP2
>To: "General Red Hat Linux discussion list" <redhat-list at redhat.com>
>Message-ID:
>
><E936DB2FBF741340845C3DFCFAD364254758 at constellation.doubledimension.com>
>
>Content-Type: text/plain; charset="us-ascii"
>
>Good day all,
>
>I'm wondering if anyone has any experience running Checkpoint Firewall-1
>NG Feature Pack 2 under RedHat 7.3 or 9.0? If so, what hardware is good
>and how well does it run?
>
>Thanks,
>
>-brian
>
>Brian D. McGrew {brian at doubledimension.com || pacemakertaker at rock.com }
>---
> > Failure is not an option; it is included with every Microsoft product.
>
>
>
>------------------------------
>
>Message: 2
>Date: Thu, 25 Nov 2004 15:00:45 -0600
>From: Dana Holland <dana.work at navarrocollege.edu>
>Subject: firewall survey
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <41A647FD.3070409 at navarrocollege.edu>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>
>Although this isn't entirely on topic for this list, I thought this
>would be an excellent group to ask...
>
>As our college prepares for reaccreditation, we're starting to evaluate
>some of our internal processes. I'm trying to compare what we do with
>others when it comes to technology, so I've designed a little survey
>dedicated to just one decision-making process you might have to go
>through. If you have time to answer these questions, it would be very
>much appreciated.
>
>1. Does your institution/organization use a firewall at the enterprise
>level (institution-wide)?
>
>2. Do you use a commercial product or a self-built product?
>
>3. Is your firewall considered to be a hardware appliance or a software
>solution?
>
>4. Related to question 3, do you feel that one is better than the
>other? Why or why not?
>
>5. What factors are involved in your decision to choose a firewall?
>
>6. Do you have a formal management process for evaluating a firewall?
>If so, would you be willing to share it?
>
>7. Obviously, cost and personnel experience are major factors when
>choosing a firewall? Are there other factors that are just as important?
>
>Thanks in advance for your help.
>--
>************************************************************
>Dana Holland dana.holland at navarrocollege.edu 903-875-7355
>Navarro College Corsicana, TX
>http://www.navarrocollege.edu/staff_pages/dana/dana.html
>************************************************************
>All opinions stated are my own, and probably don't even
>vaguely resemble those of Navarro College. :)
>
>
>
>
>------------------------------
>
>Message: 3
>Date: Thu, 25 Nov 2004 16:09:21 -0600
>From: Aimin Yan <aiminy at iastate.edu>
>Subject: how to set up wireless network connection in Fedro 2
>To: redhat-list at redhat.com
>Message-ID:
> <6.0.1.1.2.20041125160751.0417d220 at aiminy.mail.iastate.edu>
>Content-Type: text/plain; charset="us-ascii"; format=flowed
>
>hello,
>does anyone know how to set up wireless network connection in Fedro 2?
>
>thanks,
>
>Aimin Yan
>
>
>
>
>------------------------------
>
>Message: 4
>Date: Fri, 26 Nov 2004 09:15:24 +0800
>From: Edward <edward at tripled.iinet.net.au>
>Subject: Re: how to set up wireless network connection in Fedro 2
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <41A683AC.3070807 at tripled.iinet.net.au>
>Content-Type: text/plain; charset=us-ascii; format=flowed
>
>
>
>Aimin Yan wrote:
>
> > hello,
> > does anyone know how to set up wireless network connection in Fedro 2?
> >
> > thanks,
> >
> > Aimin Yan
>
>run lspci to find out what chipset is on your wireless card first - let
>us know, and we'll go from there.
>
>Regards,
>Ed.
>
>
>
>------------------------------
>
>Message: 5
>Date: Thu, 25 Nov 2004 17:20:34 -0500
>From: "C. Linus Hicks" <lhicks at nc.rr.com>
>Subject: Re: how to set up wireless network connection in Fedro 2
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <1101421234.14749.26.camel at lh4.linush.net>
>Content-Type: text/plain
>
>On Thu, 2004-11-25 at 16:09 -0600, Aimin Yan wrote:
> > hello,
> > does anyone know how to set up wireless network connection in Fedro 2?
>
>What is "Fedro 2"? If you mean Fedora Core 2, you might have better luck
>with your question on fedora-list:
>
>http://www.redhat.com/mailman/listinfo/fedora-list
>
>--
>C. Linus Hicks <lhicks at nc.rr.com>
>
>
>
>------------------------------
>
>Message: 6
>Date: Thu, 25 Nov 2004 19:20:09 -0800
>From: Pete Nesbitt <pete at linux1.ca>
>Subject: Re: firewall survey
>To: dana.holland at navarrocollege.edu, General Red Hat Linux discussion
> list <redhat-list at redhat.com>
>Message-ID: <200411251920.09137.pete at linux1.ca>
>Content-Type: text/plain; charset="iso-8859-1"
>
>Hi,
>see inserted replies....
>
>On November 25, 2004 01:00 pm, Dana Holland wrote:
> > Although this isn't entirely on topic for this list, I thought this
> > would be an excellent group to ask...
> >
> > As our college prepares for reaccreditation, we're starting to evaluate
> > some of our internal processes. I'm trying to compare what we do with
> > others when it comes to technology, so I've designed a little survey
> > dedicated to just one decision-making process you might have to go
> > through. If you have time to answer these questions, it would be very
> > much appreciated.
> >
> > 1. Does your institution/organization use a firewall at the enterprise
> > level (institution-wide)?
>
>a) at work we use an ACL on a cisco router with firewalls on local servers
>b) at home (just as serious/important) I use a dedicated linux box for a fw.
>
> >
> > 2. Do you use a commercial product or a self-built product?
>
>The fw's used on servers at work are all IPtables (more correctly NetFilter &
>IPtables) for Linux, and for Solaris we use ...can't remember the name but it
>is similar OSS (non-commecial). I use home grown scripts to manage iptables.
>
>Same for home (but pure linux:-)
>
> >
> > 3. Is your firewall considered to be a hardware appliance or a software
> > solution?
>
>a) at work, of course the cisco routers are hardware (running software:)
> -the IPtables on a server (or workstation) is a software solution.
>
>b) my home firewall is a software solution (IPtables on Linux). Although, as
>it is a dedicated headless box with little other functionality, it could be
>considered an appliance.
>
> >
> > 4. Related to question 3, do you feel that one is better than the
> > other? Why or why not?
>
>There may be speed advantages to hardware solutions that are based on a ASIC
>(application specific integrated circuit) as they have little overhead.
>However, using a barebones linux box you can get very good performance and
>any loss is easily offset in the granularity and flexability of a software
>solution. Also, from a security aspect, sometimes vendors of proprietary
>solutions are not as forth coming as they could be when it comes to reporting
>vulnerabilities.
>
> >
> > 5. What factors are involved in your decision to choose a firewall?
>
>Most important is reliability and ability to maintain it. Not necessarily
>ease
>of maintenance but understanding the underlying process so you can
>troubleshoot and react to (planned or imposed) changes.
>
> >
> > 6. Do you have a formal management process for evaluating a firewall?
> > If so, would you be willing to share it?
>
>We don't have a formal process.
>
>Typically, it is the configuration that you are concerned with (plus stable &
>fast), so any scans or penetration testing would really be checking the rules
>(not the FW persay) unless there is a unpatched vulnerability in the fw.
>
> >
> > 7. Obviously, cost and personnel experience are major factors when
> > choosing a firewall? Are there other factors that are just as important?
>
>Experience and solid understanding of the how to write, maintain and review
>firewall rules is extremely important. You must be able to say for sure if
>the fw is blocking a broken service as that is the usual first suspect. You
>need to know with certainty because you can't be stopping the firewall just
>to prove it isn't the problem. (fyi, i find tcpwrappers is often overlooked
>when sorting out connectivity of a new service).
>
>I think cost should be a consideration in respect to the ability to buy a
>firewall (or train/outsource), however, remember what your looking for,
>protection not savings! I preffer IPtables, despite the free price tag,
>simply because it is simple to add/remove/alter rules as needed, is well
>maintained, and has plenty of community support. I do not encourage the use
>of the front-ends that restrict the granularity or creation of custom rules,
>hinder a learning of the process of IPtables for new users, or that create
>there own non-standard config files. If a front-end exists that simply
>creates/inserts an iptables command line entry, that would be a good tool.
>One of the best things about IPtables is you can create and run your own
>script with lots of comments and custom rules, include keywords for grepping
>log entries, and react to emergencies very quickly.
>
>Given that the cost is ok and that you have ample experience on staff, then
>the single most important aspect would probably be flexability. Meaning the
>ability to create custom rules in very little time, with minimal impact on
>the network. Actually although that is a single factor, it is determined by
>both the firewall and the admins experience.
>
>I worked one place and they had to reboot the firewall box in order to
>impliment new rules. That may have been either the fw, the os or the admin
>that caused this requirement, but I think either way it was unaceptable.
>
>You may also be looking for more than a fw, and may be concerned with
>email/spam filtering, vpn connections, etc.
>
> >
> > Thanks in advance for your help.
> > --
> > ************************************************************
> > Dana Holland dana.holland at navarrocollege.edu 903-875-7355
> > Navarro College Corsicana, TX
> > http://www.navarrocollege.edu/staff_pages/dana/dana.html
> > ************************************************************
> > All opinions stated are my own, and probably don't even
> > vaguely resemble those of Navarro College. :)
>
>
>Hope that helps.
>--
>Pete Nesbitt, rhce
>
>
>
>------------------------------
>
>Message: 7
>Date: Fri, 26 Nov 2004 08:16:55 +0100
>From: Padiyath Sreekumaran <Kumar.Padiyath at psi.ch>
>Subject: RE: Perl script Problem with Linux
>To: "'golharam at umdnj.edu'" <golharam at umdnj.edu>, "'General Red Hat
> Linux discussion list'" <redhat-list at redhat.com>
>Message-ID: <ABC4EFAF3217D311A39200508B08F7FC04A95067 at psi17.psi.ch>
>Content-Type: text/plain
>
>
> Hello,
> Iam not an expert in Perl programming. Iam wondering why
> Iam getting syntax error only with Linux OS. On SUN and Tru64
> it works without any changes. Is it NOT possible that this error
> comes from Perl setup or missing Perl routines on Linux? I made
> a debug of the Perl script and found that the program dies in a
> Perl script subroutine. But I donot know why.Any help is appreciated.
>
> Thanks in advance.
> Regards,
> Kumar
>
>-----Original Message-----
>From: Ryan Golhar [mailto:golharam at umdnj.edu]
>Sent: Donnerstag, 25. November 2004 16:50
>To: 'General Red Hat Linux discussion list'
>Subject: RE: Perl script Problem with Linux
>
> > Error in ./dnewsreport.103.conf line 9: must be 'section' instead of
> > '#'
>
>It looks like the perl script is dying with an error in the
>configuration file. Double-check the configuration file to make sure its
>format is correct...
>
>Ryan
>
>-----Original Message-----
>From: redhat-list-bounces at redhat.com
>[mailto:redhat-list-bounces at redhat.com] On Behalf Of Ed Greshko
>Sent: Thursday, November 25, 2004 1:59 AM
>To: General Red Hat Linux discussion list
>Subject: Re: Perl script Problem with Linux
>
>
>Padiyath Sreekumaran wrote:
>
> > I have a perl script which reads a configuration file. This
> > Script works on SUN as well as Tru64 to certain extend. Since I
>donot
> > have all the input files on SUN and Tru64 the script stops. The
> > Problem on Linux is that it dies immediately in line 9 of the
> > Configuration file. Iam using Perl version 5.8 and Redhat 9.0. The
> > problem is in the routine read_conf of the perl script. Iam not an
> > expert on Perl. Can any one help me? Am I missing any Perl modules
> > on
> >
> > Linux? Thanks for your help.
> >
> >
> >
> > Iam enclosing both files: script and config file
>
>Seems as if the listserver strips out attachments.... Which is not a
>bad thing, IMHO.
>
> > # perl -v
> > This is perl, v5.8.0 built for i386-linux-thread-multi
> >
> > (with 1 registered patch, see perl -V for more detail)
> >
> > # uname -a
> >
> > Linux pc4289 2.4.20-28.9 #1 Thu Dec 18 13:45:22 EST 2003 i686 i686
> > i386 GNU/Linux
> >
> > I know that I should have send this problem to Perl FAQ. Since I
>get
> > error with Linux I thought that I shall ask here. Sorry for that.
> >
> > Error I get on Linux:
> >
> > # ./dnewsreport103.pl -f ./dnewsreport.103.conf
> >
> > Error in ./dnewsreport.103.conf line 9: must be 'section' instead of
> > '#'
>
>One common problem that presents itself in many ways is the setting of
>the LANG environment variable. In later versions of RH it often
>defaults to:
>
>LANG=en_US.UTF-8
>
>try changing that to
>
>LANG=en_US
>
>or whatever you are using minus the .UTF-8
>
>This is just a stab in the dark. YMMV.
>
>Ed
>
>
>
>--
>"I think the problem, to be quite honest with you, is that you've never
>actually known what the question is."
>
>--The computer "Deep Thought" in "Hitchhiker's Guide to The Galaxy"
>
>--
>redhat-list mailing list
>unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/redhat-list
>
>
>
>
>------------------------------
>
>Message: 8
>Date: Fri, 26 Nov 2004 07:14:30 -0500
>From: Jason Dixon <jason at dixongroup.net>
>Subject: Re: Perl script Problem with Linux
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID: <B98A6894-3FA4-11D9-A204-000D93C63BA8 at dixongroup.net>
>Content-Type: text/plain; charset=US-ASCII; format=flowed
>
>On Nov 26, 2004, at 2:16 AM, Padiyath Sreekumaran wrote:
>
> > Hello,
> > Iam not an expert in Perl programming. Iam wondering why
> > Iam getting syntax error only with Linux OS. On SUN and Tru64
> > it works without any changes. Is it NOT possible that this error
> > comes from Perl setup or missing Perl routines on Linux? I made
> > a debug of the Perl script and found that the program dies in a
> > Perl script subroutine. But I donot know why.Any help is
> > appreciated.
>
>I *am* an expert in Perl programming, but that won't help you any
>without my ability to actually review the code you're referring to.
>Mailing lists like this one filter out attachments, so you'll need to
>provide a link to the code in question. Without that, you're spinning
>your wheels and wasting our time.
>
>--
>Jason Dixon
>DixonGroup Consulting
>http://www.dixongroup.net
>
>
>
>
>------------------------------
>
>Message: 9
>Date: Fri, 26 Nov 2004 08:18:55 -0600
>From: "McDougall, Marshall (FSH)" <MarMcDouga at gov.mb.ca>
>Subject: Power down of SMP servers
>To: General Red Hat Linux discussion list <redhat-list at redhat.com>
>Message-ID:
> <EFCBF8B206ABD211AC3D00A0C9DEBF7E02C40202 at wpg1166ex1.gov.mb.ca>
>Content-Type: text/plain
>
>I have several Intel SMP servers that I can't get to power off
>automatically. I have googled high and low to find a process where I can
>have them power off when I issue power_off or shutdown -h or any one of the
>other available commands to make them do that. Any single CPU machines I
>have do it without question or any special configuration.
>
>These server are running RH 7.2, ES2.1 and ES3 with the various current
>kernels. Does anybody have an SMP server running Linux that will power down
>when you tell it to? If so, how did you accomplish that task. All replies
>appreciated.
>
>Regards, Marshall
>
>
>
>------------------------------
>
>Message: 10
>Date: Fri, 26 Nov 2004 15:02:30 -0000
>From: Amanda Galligan <Amanda.Galligan at esat.com>
>Subject: kernel panic HP DL 380 G3
>To: "'redhat-list at redhat.com'" <redhat-list at redhat.com>
>Message-ID:
> <6FD0C1A3379D2047B391E218D0AD9B611726C1 at exchange1.dublin.esat.ie>
>Content-Type: text/plain; charset="iso-8859-1"
>
>We've received this error on HP DL 380 running Redhat 2.1 AS with kernel
>2.4.9-e.38smp
>
>this error has already occured on another HP identical hardware and OS
>config. Is there issues with HP and this version of Kernel ?
>
>Nov 26 13:49:14 DHB0125A-IEDRL kernel: ------------[ cut here ]------------
>Nov 26 13:49:15 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-109
>Nov 26 13:49:15 DHB0125A-IEDRL eac: Warning: loading
>/lib/modules/2.4.9-e.38smp/kernel/drivers/net/eac/iprpf.o will taint the
>kernel: non-GPL license - Commercial, see LICENSE file for details
>Nov 26 13:49:15 DHB0125A-IEDRL kernel: kernel BUG at slab.c:1155!
>Nov 26 13:49:15 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-110
>Nov 26 13:49:15 DHB0125A-IEDRL kernel: invalid operand: 0000
>Nov 26 13:49:15 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-111
>Nov 26 13:49:15 DHB0125A-IEDRL kernel: Kernel 2.4.9-e.38smp
>Nov 26 13:49:15 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-72
>Nov 26 13:49:15 DHB0125A-IEDRL kernel: CPU: 0
>Nov 26 13:49:15 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-73
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: EIP: 0010:[kmem_cache_grow+38/640]
>Tainted: P
>Nov 26 13:49:16 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-74
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: EIP: 0010:[<c0137d36>] Tainted:
>P
>Nov 26 13:49:16 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-75
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: EFLAGS: 00010282
>Nov 26 13:49:16 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-76
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: EIP is at kmem_cache_grow [kernel]
>0x26
>Nov 26 13:49:16 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-77
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: eax: 0000001e ebx: f7fc9080 ecx:
>c02f6e84 edx: 00004dec
>Nov 26 13:49:16 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-78
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: esi: f7fc9080 edi: 000001f0 ebp:
>dd170000 esp: dd171e98
>Nov 26 13:49:16 DHB0125A-IEDRL modprobe: modprobe: Can't locate module
>block-major-79
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: ds: 0018 es: 0018 ss: 0018
>Nov 26 13:49:16 DHB0125A-IEDRL kernel: Process modprobe (pid: 2144,
>stackpage=dd171000)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: Stack: c0266c2b 00000483 c012d690
>ddaeff20 dd8082e0 401a2000 dd171ec0 dd551400
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: 00104025 c030a848 f7fc9080
>f7fc9080 00000246 dd170000 c01383e8 f7fc9080
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: 000001f0 f8aca05d f8aeca60
>c02f94c0 00000000 00000000 00000100 ddacb000
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: Call Trace:
>[call_spurious_interrupt+132298/157983] .rodata.str1.1 [kernel] 0x2ba6 (0xd
>d171e98)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: Call Trace: [<c0266c2b>]
>.rodata.str1.1 [kernel] 0x2ba6 (0xdd171e98)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [handle_mm_fault+240/336]
>handle_mm_fault [kernel] 0xf0 (0xdd171ea0)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<c012d690>] handle_mm_fault [kernel]
>0xf0 (0xdd171ea0)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [kmalloc+312/352] kmalloc [kernel]
>0x138 (0xdd171ed0)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<c01383e8>] kmalloc [kernel] 0x138
>(0xdd171ed0)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<f8aca05d>] routem_init [iprpf] 0xbd
>(0xdd171edc)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<f8aeca60>] routem_sockopt [iprpf]
>0x0 (0xdd171ee0)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<f8ac8f41>] ecpf_init [iprpf] 0xa5
>(0xdd171efc)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<f8ac8ec5>] ecpf_init [iprpf] 0x29
>(0xdd171f0c)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [__free_pages+27/32] __free_pages
>[kernel] 0x1b (0xdd171f28)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<c013de6b>] __free_pages [kernel]
>0x1b (0xdd171f28)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [sys_init_module+1365/1616]
>sys_init_module [kernel] 0x555 (0xdd171f2c)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<c011d995>] sys_init_module [kernel]
>0x555 (0xdd171f2c)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<f8ac8060>] ecpf_dev_get_by_name
>[iprpf] 0x0 (0xdd171f58)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [system_call+51/56] system_call
>[kernel] 0x33 (0xdd171fc0)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: [<c01073e3>] system_call [kernel]
>0x33 (0xdd171fc0)
>Nov 26 13:49:17 DHB0125A-IEDRL kernel:
>Nov 26 13:49:17 DHB0125A-IEDRL kernel:
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: Code: 0f 0b 58 5a f7 c7 00 10 00 00
>0f 85 3e 02 00 00 b8 00 e0 ff
>Nov 26 13:49:17 DHB0125A-IEDRL kernel: <0>Kernel panic: not continuing
>
>
>
>
>
>
>
>Esat Telecommunications Limited
>is a wholly owned subsidiary of BT Group plc
>Registered in Ireland, Registration No. 141524
>Grand Canal Plaza, Upper Grand Canal Street, Dublin, Ireland
>
>This electronic message contains information (and may contain files) from
>Esat Telecommunications Limited which may be privileged or confidential. The
>information is intended to be for the sole use of the individual(s) or
>entity named above. If you are not the intended recipient be aware that any
>disclosure, copying, distribution or use of the contents of this information
>and or files is prohibited. If you have received this electronic message in
>error, please notify us by telephone or email (to the numbers or address
>above) immediately. http://www.esatbt.com
>
>
>------------------------------
>
>__
>redhat-list mailing list
>Unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/redhat-list
>
>End of redhat-list Digest, Vol 9, Issue 28
>******************************************
More information about the redhat-list
mailing list