I've gotten a couple of Jan 22 10:23:05 barley kernel: eth0: Something Wicked happened! 000b. from my firewall machine the last few days. Always on the internal interface. Kernel is 2.2.16. Somebody want to remind me what is wicked? Thanks Nick
According to Bill S. By the pricking of my thumbs, something wicked this way comes. According to find /usr/src/linux -follow -type f | xargs grep wicked /usr/src/linux/drivers/net/fc/iph5526.c: /* We care about the SCSI writes only. Those are the wicked ones Note that this is a comment, not a message. Is this the SuSE 7.0 2.2.16 kernel? Jeff Quoting Nick Zentena <zentena@hophead.dyndns.org>:
I've gotten a couple of
Jan 22 10:23:05 barley kernel: eth0: Something Wicked happened! 000b.
from my firewall machine the last few days. Always on the internal interface. Kernel is 2.2.16. Somebody want to remind me what is wicked?
Thanks Nick
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck
On January 22, 2001 11:08 am, Jeffrey Taylor wrote:
According to Bill S. By the pricking of my thumbs, something wicked this way comes.
According to find /usr/src/linux -follow -type f | xargs grep wicked
/usr/src/linux/drivers/net/fc/iph5526.c: /* We care about the SCSI writes only. Those are the wicked ones
Note that this is a comment, not a message. Is this the SuSE 7.0 2.2.16 kernel?
It's a SuSE kernel but I don't remember if it's stock or not. I followed your lead and looked for more examples of Something wicked. Looks like it's every where in the source. I guess the part that makes the most sense is the one in my network card driver. /* Recovery for other fault sources not known. */ Thats the comment after the print statement. So I get the feeling it basically means an unknown error happened. Thanks Nick
Jeffrey Taylor wrote:
Quoting Nick Zentena <zentena@hophead.dyndns.org>:
I've gotten a couple of
Jan 22 10:23:05 barley kernel: eth0: Something Wicked happened! 000b.
from my firewall machine the last few days. Always on the internal interface. Kernel is 2.2.16. Somebody want to remind me what is wicked?
According to find /usr/src/linux -follow -type f | xargs grep wicked
/usr/src/linux/drivers/net/fc/iph5526.c: /* We care about the SCSI writes only. Those are the wicked ones
Note that this is a comment, not a message. Is this the SuSE 7.0 2.2.16 kernel?
This is what I get by giving 'wicked' a capital letter ;-) chris@galaxy:~/skydive > find /usr/src/linux -follow -type f | xargs grep Wicked /usr/src/linux/drivers/net/starfire.c: printk(KERN_ERR "%s: Something Wicked happened! %4.4x.\n", /usr/src/linux/drivers/net/via-rhine.c: printk(KERN_ERR "%s: Something Wicked happened! %4.4x.\n", /usr/src/linux/drivers/net/yellowfin.c: printk(KERN_ERR "%s: Something Wicked happened! %4.4x.\n", /usr/src/linux/drivers/net/hamachi.c: printk(KERN_ERR "%s: Something Wicked happened! %4.4x.\n", /usr/src/linux/drivers/net/natsemi.c: printk(KERN_ERR "%s: Something Wicked happened! %4.4x.\n", /usr/src/linux/drivers/net/sundance.c: printk(KERN_ERR "%s: Something Wicked happened! %4.4x.\n", chris@galaxy:~/skydive > I'm guessing, Nick, that you're using the via-rhine driver for your network card, in which case, this is the appropriate bit of code: if ((intr_status & ~( IntrLinkChange | IntrStatsMax | IntrTxAbort | IntrTxAborted)) && debug > 1) { printk(KERN_ERR "%s: Something Wicked happened! %4.4x.\n", dev->name, intr_status); /* Recovery for other fault sources not known. */ writew(CmdTxDemand | np->chip_cmd, dev->base_addr + ChipCmd); } Now, I'm no C coder, so I can't help you (looks to me like a catch-all 'something went wrong' message though), but this may help you, Jeffrey, or someone else figure this out... It may be easier to see if there are any other error messages nearby in /var/log/messages. Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
participants (3)
-
Chris Reeves -
Jeffrey Taylor -
Nick Zentena