[WBEL-users] PCRE-Error: Compiling php- 4.3.8
wb@whx.de
wb@whx.de
Mon, 6 Sep 2004 18:29:06 +0200
hi,
/root/php-4.3.8/ext/pcre/php_pcre.c: In function `php_pcre_match':
/root/php-4.3.8/ext/pcre/php_pcre.c:413: `PCRE_INFO_NAMECOUNT' undeclared (first use in this function)
/root/php-4.3.8/ext/pcre/php_pcre.c:413: (Each undeclared identifier is reported only once
/root/php-4.3.8/ext/pcre/php_pcre.c:413: for each function it appears in.)
/root/php-4.3.8/ext/pcre/php_pcre.c:415: `PCRE_INFO_NAMETABLE' undeclared (first use in this function)
/root/php-4.3.8/ext/pcre/php_pcre.c:416: `PCRE_INFO_NAMEENTRYSIZE' undeclared (first use in this function)
make: *** [ext/pcre/php_pcre.lo] Fehler 1
I think the problem is because of old PCRE-Packages (3.9).
Is there an actual RPM of PCRE 4.5 ?
Greets
Wilhelm
Am Sonntag, 5. September 2004, 17:55, schrieb whitebox-users-request@beau.org:
> Send Whitebox-users mailing list submissions to
> whitebox-users@beau.org
> To subscribe or unsubscribe via the World Wide Web, visit
> http://beau.org/mailman/listinfo/whitebox-users
> or, via email, send a message with subject or body 'help' to
> whitebox-users-request@beau.org
> You can reach the person managing the list at
> whitebox-users-admin@beau.org
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Whitebox-users digest..."
> Today's Topics:
> 1. network shuts down just because (Daniel Bahena)
> 2. Determining the Cause of a Kernel Panic (Daniel J. Summers)
> 3. Re: Sendmail SPF SRS Question (Pete Stevens)
> 4. Re: apt-get repository? (Andy)
> 5. Determining the Cause of a Kernel Panic (Daniel J. Summers)
> 6. Re: Determining the Cause of a Kernel Panic (Greg Knaddison)
> 7. Re: Determining the Cause of a Kernel Panic (Randy Kelsoe)
> 8. Re: Determining the Cause of a Kernel Panic (Daniel J. Summers)
> 9. Re: Determining the Cause of a Kernel Panic (Daniel J. Summers)
> 10.
> =?iso-8859-1?Q?Re:_Re:_[WBEL-users]_Determining_the_Cause_of_a_Kernel_Panic?=
> (timspam@meanor.net)
> --__--__--
> Message: 1
> From: Daniel Bahena <daniel@informatux.dyndns.org>
> To: whitebox-users@beau.org
> Organization: Informatux.net
> Date: Sat, 04 Sep 2004 12:07:36 -0500
> Subject: [WBEL-users] network shuts down just because
> Hi
> I just installed a WBEL on a Pentium 3 @ 1.2 gigs and 128 ram (i'm
> waiting for the 512 ram module).
> It has 2 network adapters, 1 is a SIS 900 and the other is a Realtek
> 8139C
> 40 gig hard drive
> and a adsl connection @ 1mb
> It has been running for 4 days, and 2 times it has happened that the
> network just stops. I have this from last night in /var/log/messages
> Sep 4 05:17:25 secundaria named[889]: shutting down: flushing changes
> Sep 4 05:17:25 secundaria named[889]: stopping command channel on
> 127.0.0.1#953
> Sep 4 05:17:26 secundaria named: succeeded
> Sep 4 05:17:26 secundaria named[889]: no longer listening on
> 127.0.0.1#53
> Sep 4 05:17:26 secundaria named[889]: no longer listening on
> 192.168.0.254#53
> Sep 4 05:17:26 secundaria named[889]: no longer listening on
> 201.135.209.74#53
> Sep 4 05:17:26 secundaria named[889]: exiting
> Sep 4 05:17:27 secundaria adsl-stop: Killing pppd
> Sep 4 05:17:27 secundaria adsl-stop: Killing adsl-connect
> Sep 4 05:17:27 secundaria network: Interrupción de la interfaz ppp0:
> succeeded
> Sep 4 05:17:27 secundaria pppd[1346]: Terminating on signal 15.
> Sep 4 05:17:27 secundaria pppd[1346]: Connection terminated.
> Sep 4 05:17:27 secundaria pppd[1346]: Connect time 867.1 minutes.
> Sep 4 05:17:27 secundaria pppd[1346]: Sent 1947022 bytes, received
> 6318347 bytes.
> Sep 4 05:17:27 secundaria pppoe[1347]: read (asyncReadFromPPP): Session
> 18441: Input/output error
> Sep 4 05:17:27 secundaria pppoe[1347]: Sent PADT
> Sep 4 05:17:27 secundaria /etc/hotplug/net.agent: NET unregister event
> not supported
> Sep 4 05:17:27 secundaria pppd[1346]: Exit.
> Sep 4 05:17:27 secundaria network: Interrupción de la interfaz eth0:
> succeeded
> Sep 4 05:17:28 secundaria network: Interrupción de la interfaz eth1:
> succeeded
> Sep 4 05:17:28 secundaria network: Interrupción de la interfaz de
> loopback: succeeded
> Sep 4 05:17:28 secundaria sysctl: net.ipv4.ip_forward = 0
> Sep 4 05:17:28 secundaria network: Deshabilitando el reenvio de
> paquetes IPv4: succeeded
> Sep 4 05:17:29 secundaria apmd[798]: System Standby
> Other thing is that I see a lot of this messages also in
> /var/log/messages:
> Sep 3 13:45:02 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 216.73.87.11#53
> Sep 3 13:45:04 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.11#53
> Sep 3 13:45:05 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 206.65.183.13#53
> Sep 3 13:45:07 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.12#53
> Sep 3 13:45:27 secundaria named[889]: lame server resolving
> 'm3.3md.doubleclick.net' (in '3md.doubleclick.NET'?): 216.73.87.11#53
> Sep 3 14:10:17 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.12#53
> Sep 3 14:10:17 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 65.205.8.11#53
> Sep 3 14:10:17 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 206.65.183.13#53
> Sep 3 14:10:18 secundaria named[889]: lame server resolving
> 'ad.3ad.doubleclick.net' (in '3ad.doubleclick.NET'?): 216.73.87.11#53
> Sep 3 14:10:27 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.163#53
> Sep 3 14:10:27 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.240.41#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.164#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.240.41#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.164#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.163#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.240.41#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.163#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.164#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.240.41#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.163#53
> Sep 3 14:10:28 secundaria named[889]: lame server resolving
> '85.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.164#53
> Sep 3 14:10:29 secundaria named[889]: lame server resolving
> '55.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.240.41#53
> Sep 3 14:10:29 secundaria named[889]: lame server resolving
> '55.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.163#53
> Sep 3 14:10:29 secundaria named[889]: lame server resolving
> '55.128.94.200.in-addr.arpa' (in '128.94.200.in-addr.arpa'?):
> 207.248.224.164#53
> Is that good or bad? If it is bad, how can I avoid that?
> And to finish, what mirror for WBEL updates supports rsync? I'm from
> Cuernavaca, Morelos and here we have a LUG and already have a mirror for
> FC1 & FC2 base system and updates, besides dag, freshrpms, newrpms and a
> extra directory. We want to set up a mirror for WBEL, any server adress
> that might be useful? Our url is http://softwarelibremorelos.gob.mx
> Thanks for all your time and help
> Best wishes
> --
> Daniel Bahena <daniel@informatux.dyndns.org>
> Informatux.net
> --__--__--
> Message: 2
> Date: Sat, 04 Sep 2004 13:34:57 -0500
> From: "Daniel J. Summers" <danieljs@knology.net>
> To: whitebox-users@beau.org
> Subject: [WBEL-users] Determining the Cause of a Kernel Panic
> How does one determine the cause of a kernel panic (when the computer
> freezes, and the caps/num/scroll lock lights blink)? I've had a couple
> this morning, and they seem to go away with a reboot (although I did get
> one during a boot). I'm suspicious of my network setup, but without
> knowing how to find a log or dump or something like that, I don't know
> what's causing it. Thanks...
> --
> *Daniel J. Summers*
> E-mail - danieljs@knology.net <mailto:danieljs@knology.net>
> *Web Sites:*
> Personal - http://www.knology.net/~mopsmom/daniel
> <http://www.knology.net/%7Emopsmom/daniel/index.html>
> Sunday School - http://www.knology.net/~mopsmom/sundayschool
> <http://www.knology.net/%7Emopsmom/daniel/sundayschool/index.xml>
> My Linux Adventure -
> http://www.knology.net/~mopsmom/daniel/linux.html
> <http://www.knology.net/%7Emopsmom/daniel/linux.html>
> GEEKCODE 3.12 GCS/IT d s-:+ a C++ L++ E--- W++ N++ o? K- w !O M--
> V PS+ PE++ Y? !PGP t+ 5? X+ R* tv b+ DI++ D+ G- e h---- r+++ y++++
> --__--__--
> Message: 3
> Date: Sat, 4 Sep 2004 19:52:21 +0100 (BST)
> From: Pete Stevens <pete@ex-parrot.com>
> To: John Hinton <webmaster@ew3d.com>
> cc: Whitebox Users <whitebox-users@beau.org>
> Subject: Re: [WBEL-users] Sendmail SPF SRS Question
> On Fri, 3 Sep 2004, John Hinton wrote:
>> So, has anybody started installing the hacks that are out there? Anybody
>> have any good 'howto' pages? Suggestions for the best path to take?
>> Milters perhaps?
> You might have to publish SPF records & force authenticated SMTP on your users
> through your own mail server but I wouldn't worry about filtering incoming
> mail that isn't SPF valid.
> http://www.ciphertrust.com/spf_stats
> 31 of the F1000 companies have adopted SPF, 34% more spam passes SPF checks
> than legitimate mail.
> Yours,
> Pete stevens
> --
> Pete Stevens
> pete@ex-parrot.com
> Virtual WBEL servers http://www.mythic-beasts.com/vds.html
> A fanatic is one who can't change his mind and won't change the subject.
> -- Winston Churchill
> --__--__--
> Message: 4
> Date: Sat, 04 Sep 2004 19:37:13 -0400
> From: Andy <industrial_soup@dynacomp.net>
> To: Mark Quitoriano <markquitoriano@gmail.com>, whitebox-users@beau.org
> CC: ekg@tricity.wsu.edu
> Subject: Re: [WBEL-users] apt-get repository?
> I use this really cool script called repo-janitor
> http://imsb.au.dk/~mok/repo-janitor.php
> It automaticaly mirrors the official yum repository, and then "aptizes" it.
> Among other things it generates html pages and then allows you to access
> the repository using apt or yum.
> Highly recommend it!
> Andy
> Mark Quitoriano wrote:
>>please post it and help me create another repository i want apt-get to
>>be full bloom for whitebox.
>>
>>
>>>
>>>On Tue, 31 Aug 2004 14:06:58 -0700, Ed <ekg@tricity.wsu.edu> wrote:
>>>
>>>
>>>>We have an apt-rpn repository here, which I use to keep all of our white
>>>>box systems up to date. I am using the scripts from freshrpms, modified
>>>>to use whitebox instead of red hat, and to incorporate extra rpm's
>>>>easily. If any are interested I can post the scripts and directory
>>>>structure.
>>>>
>>>>
>>_______________________________________________
>>Whitebox-users mailing list
>>Whitebox-users@beau.org
>>http://beau.org/mailman/listinfo/whitebox-users
>>
>>
>>
>>
>>
> --__--__--
> Message: 5
> Date: Sat, 04 Sep 2004 21:49:17 -0500
> From: "Daniel J. Summers" <danieljs@knology.net>
> To: whitebox-users@beau.org
> Subject: [WBEL-users] Determining the Cause of a Kernel Panic
> (My apologies if this is a dupe for anyone - I sent this about 10 hours
> ago, and it still hasn't shown up in my list (or in the online archive),
> although other messages have.)
> How does one determine the cause of a kernel panic (when the computer
> freezes, and the caps/num/scroll lock lights blink)? I've had a couple
> this morning, and they seem to go away with a reboot (although I did get
> one during a boot). I'm suspicious of my network setup, but without
> knowing how to find a log or dump or something like that, I don't know
> what's causing it. Thanks...
> (As a follow-up - I was using ndiswrapper 0.8, and I found that version
> 0.10 was available. I downloaded it, compiled it, reset everything up,
> and so far, no panics. I'd still like to know if there's a log
> somewhere though... :> )
> --
> *Daniel J. Summers*
> E-mail - danieljs@knology.net <mailto:danieljs@knology.net>
> *Web Sites:*
> Personal - http://www.knology.net/~mopsmom/daniel
> <http://www.knology.net/%7Emopsmom/daniel/index.html>
> Sunday School - http://www.knology.net/~mopsmom/sundayschool
> <http://www.knology.net/%7Emopsmom/daniel/sundayschool/index.xml>
> My Linux Adventure -
> http://www.knology.net/~mopsmom/daniel/linux.html
> <http://www.knology.net/%7Emopsmom/daniel/linux.html>
> GEEKCODE 3.12 GCS/IT d s-:+ a C++ L++ E--- W++ N++ o? K- w !O M--
> V PS+ PE++ Y? !PGP t+ 5? X+ R* tv b+ DI++ D+ G- e h---- r+++ y++++
> --__--__--
> Message: 6
> Date: Sat, 4 Sep 2004 21:37:41 -0600
> From: Greg Knaddison <greg.knaddison@gmail.com>
> Reply-To: Greg Knaddison <greg.knaddison@gmail.com>
> To: Whitebox-users@beau.org
> Subject: Re: [WBEL-users] Determining the Cause of a Kernel Panic
> Hi,
> How confident are you that it's a software issue and not a hardware
> issue? Or are you open to all ideas and just looking for more clues
> to the cause?
> I had a machine that would die randomly and it really frustrated me
> until I pinned it down to times when the processor was being used
> intensively....and then to the fact that there was a piddly small fan
> on the processor.
> Greg
> On Sat, 04 Sep 2004 21:49:17 -0500, Daniel J. Summers
> <danieljs@knology.net> wrote:
>> (My apologies if this is a dupe for anyone - I sent this about 10 hours
>> ago, and it still hasn't shown up in my list (or in the online archive),
>> although other messages have.)
>>
>> How does one determine the cause of a kernel panic (when the computer
>> freezes, and the caps/num/scroll lock lights blink)? I've had a couple
>> this morning, and they seem to go away with a reboot (although I did get
>> one during a boot). I'm suspicious of my network setup, but without
>> knowing how to find a log or dump or something like that, I don't know
>> what's causing it. Thanks...
>>
>> (As a follow-up - I was using ndiswrapper 0.8, and I found that version
>> 0.10 was available. I downloaded it, compiled it, reset everything up,
>> and so far, no panics. I'd still like to know if there's a log
>> somewhere though... :> )
>>
>> --
>> *Daniel J. Summers*
>> E-mail - danieljs@knology.net <mailto:danieljs@knology.net>
>> *Web Sites:*
>> Personal - http://www.knology.net/~mopsmom/daniel
>> <http://www.knology.net/%7Emopsmom/daniel/index.html>
>> Sunday School -
>> http://www.knology.net/~mopsmom/sundayschool
>> <http://www.knology.net/%7Emopsmom/daniel/sundayschool/index.xml>
>> My Linux Adventure -
>> http://www.knology.net/~mopsmom/daniel/linux.html
>> <http://www.knology.net/%7Emopsmom/daniel/linux.html>
>>
>> GEEKCODE 3.12 GCS/IT d s-:+ a C++ L++ E--- W++ N++ o? K- w !O M--
>> V PS+ PE++ Y? !PGP t+ 5? X+ R* tv b+ DI++ D+ G- e h---- r+++ y++++
>> _______________________________________________
>> Whitebox-users mailing list
>> Whitebox-users@beau.org
>> http://beau.org/mailman/listinfo/whitebox-users
>>
> --__--__--
> Message: 7
> Date: Sat, 04 Sep 2004 22:51:57 -0500
> From: Randy Kelsoe <randykel@swbell.net>
> To: whitebox-users@beau.org
> Subject: Re: [WBEL-users] Determining the Cause of a Kernel Panic
> Daniel J. Summers wrote:
>> How does one determine the cause of a kernel panic (when the computer
>> freezes, and the caps/num/scroll lock lights blink)? I've had a
>> couple this morning, and they seem to go away with a reboot (although
>> I did get one during a boot). I'm suspicious of my network setup, but
>> without knowing how to find a log or dump or something like that, I
>> don't know what's causing it. Thanks...
> General system logs are in /var/log/ and you should start with 'messages'.
> A freeze is not a panic. A lot of times with a freeze, you will not see
> anything in the logs. There are also different kinds of freezes, or lock
> ups. If you have another machine on the network, you can try to ping or
> ssh into the box when it appears locked up. You can also try a
> 'Ctrl-Alt-Backspace' to restart X.
> Which mobo are you using? Have you updated your BIOS to the latest
> version? What other hardware are you using? Are you using a stock WBEL
> kernel, or have you compiled your own?
> Have you tried running memtest86 on the machine? If not, you can get the
> Ultimate Boot CD at:
> http://www.ultimatebootcd.com/
> boot from it and run memtest86 overnight if possible. If you have a
> flaky memory dimm, it will probably find it. If you get no errors with
> memtest, you might also run the disk diags for your hard drive and see
> if that finds anything. If you sill don't see any errors, reboot, and
> try the dmesg command. See if you can find anything unusual there.
>>
>> (As a follow-up - I was using ndiswrapper 0.8, and I found that
>> version 0.10 was available. I downloaded it, compiled it, reset
>> everything up, and so far, no panics. I'd still like to know if
>> there's a log somewhere though... :> )
>>
> --__--__--
> Message: 8
> Date: Sun, 05 Sep 2004 08:18:58 -0500
> From: "Daniel J. Summers" <danieljs@knology.net>
> To: Whitebox Enterprise Linux Users List <whitebox-users@beau.org>
> Subject: Re: [WBEL-users] Determining the Cause of a Kernel Panic
> Greg Knaddison wrote:
>>Hi,
>>
>>How confident are you that it's a software issue and not a hardware
>>issue? Or are you open to all ideas and just looking for more clues
>>to the cause?
>>
>>
> Of course. :) The ndiswrapper was just a guess, because on the one
> panic I got while I was booting, that's where it was (brining up
> wlan0). When I was running FC2 on this box, it would simply freeze - no
> mouse, no caps lock key response, nothing. Now that I've got WBEL back
> on it, at least it's maintaining enough control that the kernel is
> blinking the lights instead of it just being hard locked. I hope I'm
> that much closer to figuring out what's going on.
>>I had a machine that would die randomly and it really frustrated me
>>until I pinned it down to times when the processor was being used
>>intensively....and then to the fact that there was a piddly small fan
>>on the processor.
>>
>>
> Hmm... Well, this machine has never been able to run folding@home - it
> locks the machine up after about 10 minutes under Linux, and about an
> hour under Windows. (Not quite sure what the time difference means...)
> So yes, I'm certainly open to the fact that I may have hardware issues
> (other than running an non-HCL wireless LAN card).
> --
> *Daniel J. Summers*
> E-mail - danieljs@knology.net <mailto:danieljs@knology.net>
> *Web Sites:*
> Personal - http://www.knology.net/~mopsmom/daniel
> <http://www.knology.net/%7Emopsmom/daniel/index.html>
> Sunday School - http://www.knology.net/~mopsmom/sundayschool
> <http://www.knology.net/%7Emopsmom/daniel/sundayschool/index.xml>
> My Linux Adventure -
> http://www.knology.net/~mopsmom/daniel/linux.html
> <http://www.knology.net/%7Emopsmom/daniel/linux.html>
> GEEKCODE 3.12 GCS/IT d s-:+ a C++ L++ E--- W++ N++ o? K- w !O M--
> V PS+ PE++ Y? !PGP t+ 5? X+ R* tv b+ DI++ D+ G- e h---- r+++ y++++
> --__--__--
> Message: 9
> Date: Sun, 05 Sep 2004 08:26:52 -0500
> From: "Daniel J. Summers" <danieljs@knology.net>
> To: Whitebox Enterprise Linux Users List <whitebox-users@beau.org>
> Subject: Re: [WBEL-users] Determining the Cause of a Kernel Panic
> Randy Kelsoe wrote:
>> Daniel J. Summers wrote:
>>
>>> How does one determine the cause of a kernel panic (when the computer
>>> freezes, and the caps/num/scroll lock lights blink)? I've had a
>>> couple this morning, and they seem to go away with a reboot (although
>>> I did get one during a boot). I'm suspicious of my network setup,
>>> but without knowing how to find a log or dump or something like that,
>>> I don't know what's causing it. Thanks...
>>
>>
>> General system logs are in /var/log/ and you should start with
>> 'messages'.
>> A freeze is not a panic. A lot of times with a freeze, you will not
>> see anything in the logs. There are also different kinds of freezes,
>> or lock ups. If you have another machine on the network, you can try
>> to ping or ssh into the box when it appears locked up. You can also
>> try a 'Ctrl-Alt-Backspace' to restart X.
>> Which mobo are you using? Have you updated your BIOS to the latest
>> version? What other hardware are you using? Are you using a stock WBEL
>> kernel, or have you compiled your own?
> Yes - I would get freezes with FC2, but never saw the lights blinking.
> I'll keep that Ctrl-Alt-Backspace sequence in mind. As best as I can
> tell, I've got the latest BIOS. I'm not running anything outlandish -
> PS/2 keyboard and mouse, Via integrated sound card, Riva TNT AGP video
> card, IDE CD-ROM, DVD/CD-RW, 20GB and 2GB hard drives, and an iBlitzz
> wireless LAN card (not on the HCL, which is why I'm using ndiswrapper).
> I'm using the stock WBEL kernel, and the only module I've compiled for
> it is ndiswrapper.
>> Have you tried running memtest86 on the machine? If not, you can get
>> the Ultimate Boot CD at:
>>
>> http://www.ultimatebootcd.com/
>>
>> boot from it and run memtest86 overnight if possible. If you have a
>> flaky memory dimm, it will probably find it. If you get no errors with
>> memtest, you might also run the disk diags for your hard drive and see
>> if that finds anything. If you sill don't see any errors, reboot, and
>> try the dmesg command. See if you can find anything unusual there.
> Thanks for the tips - I'll give that a shot this afternoon. :) As you
> probably saw in the previous message, this machine has had, shall we
> say, stability issues. I was just so happy to finally have a lock-up
> where I might actually have a log!