Bug 123445
| Summary: | (NET E100) Fedora Core 2 Freeze on Wakeonlan packets hit the network card | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marc Olivier Chouinard <mochouinard> | ||||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 2 | CC: | alan, pfrields | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2005-04-16 05:34:08 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Marc Olivier Chouinard
2004-05-18 16:36:09 UTC
I just tryed again on a Compaq EVO D510 (P4 1.5) and same probleme. I wonder if it might be the traffic on our local network that just make the kernel hang. I'll reboot the machine and let it unplug from the network and see. Wakeonlan make the kernel FREEZE.... NOT GOOD What network chips are these two machines using ? thet both use the e100 driver I tryed it again on my Evo (by tcpdump > to the HD) and once the pc crash, it wont boot again anymore, Bios dont detect the Harddrive. Not good, Going to try another harddrive soon and see if it just HD or machine are is dead Marc HD Dead, Maxtor DiamondMax Plus 8 20gig ATA/133HD. Viva warrenty. This problem really cause alot of bad thing. Hope you can fix it. 12:11:24.262980 10.150.110.203.1469 > 10.150.190.255.32767: udp 102 12:11:24.263003 10.150.110.203.1469 > 10.150.190.255.32767: udp 102 12:11:24.279847 10.150.110.203.1470 > 10.150.190.255.32767: udp 102 12:11:24.279872 10.150.110.203.1470 > 10.150.190.255.32767: udp 102 the WOL request machine send about 4900 of these packets (600 time to 7 different VLAN) After that, the linux is crashed Those are UDP broadcasts not wake on lan packets as far as I can see. As to the disk, Linux has no way of breaking the disk - thats just chance occurence. well those are the packets another linux machine capture from the network card. As for linux breaking the HD.. May be it just bad luck, but it not old machine and on 550 PC, it would be the first that does that over here. I'l attach a dump file that work from the HP machine (up until it crashed) Created attachment 100424 [details]
tcpdump -i eth0 -vv -n > dump.info
From the HP Vectra PC FC2 (Minimal install)
Created attachment 100425 [details]
tcpdump -i eth0 -vv -n > dump2.info (test 2)
From the HP Vectra PC FC2 (Minimal install) (Another test)
I did a manual wake-on-lan on the Linux MAC and it crash. I tryed other MAC and it was fine. Is there any update on this ? I can't put that box live if it vulnerable to DoS attack At the moment I can't duplicate it on any e100 hardware I have nor can find any reference to the same problem anywhere else on the internet. That makes it kind of hard to fix. Ok here my new testing : rmmod e100 after system is booted, and doing wakeonlan again, and system still crash But I just thought to REMOVE ACPI and APM (linux acpi=off apm=off at boot time) and it fine, doesn't crash anymore. Want the wakeonlan program I use, I open source, but I lost the source :( I think this sound a bit like the 129103 bug lots of folks seem to be ancountering on stock core 2 2.6.5-1.358 hangs our ibm e server pentium 4 . No console or login services work from then on but we can ping the box. Fedora Core 2 has now reached end of life, and no further updates will be provided by Red Hat. The Fedora legacy project will be producing further kernel updates for security problems only. If this bug has not been fixed in the latest Fedora Core 2 update kernel, please try to reproduce it under Fedora Core 3, and reopen if necessary, changing the product version accordingly. Thank you. |