lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 20 May 2010 16:21:50 +0800 From: steven <mqyoung@...il.com> To: netdev@...r.kernel.org Cc: romieu@...zoreil.com Subject: Issue on RTL8169scd(l), can not transmit packet Dear All, I am porting openPOWERLINK to Loongson/MIPS platform, so I have to write a driver for RTL8169scl(RTL8169scd in kernel) firstly. Now, my driver could receive packet(confirmed by printing the content of packets and comparing them with the data wireshark captured). But RTL8169 didn't send any packet(I use wireshark to capture the packet). And I found some bits in Tx Desc(Transmit Descriptor) has been modified, such as OWN, that's to say RTL8169 could read/write the transmit descriptor buffer. Things seems OK, but I can not capture any packet.() I use pci_alloc_consistent to allocate the memory for TxDesc/RxDesc Tx buffer/Rx buffer. The first field of my TxDesc is 0xb000003c. The environment: Target<===> HUB <===>PC_with_wireshark The LED(whose port connects to the target) on HUB doesn't flash when the target keeps sending packet or it receives packets. I print the content of all the registers of RTL8169 in Linux kernel, I found the configuration in kernel and in my driver are the same except PHY Access, but the config of all the PHY regs are the same with kernel's. There is no "system error interrupt" occurs, but I am not sure whether it will screw up. [14403.742503] 0x10---------0x9EAD4000 [14403.742991] 0x14---------0x00000000 [14403.743478] 0x18---------0x00000000 [14403.744799] 0x1C---------0x00000000 [14403.745309] 0x20---------0x9EB18000 [14403.745801] 0x24---------0x00000000 [14403.746289] 0x28---------0x05744700 [14403.746778] 0x2C---------0xB61C07FB [14403.747265] 0x37---------0x0C [14403.747702] 0x38---------0x00 [14403.749221] 0x3C---------0xC1FF [14403.749692] 0x3E---------0x0000 [14403.750146] 0x40---------0x1B000600 [14403.750636] 0x44---------0x00000000 [14403.751123] 0x48---------0x09AF2BDA [14403.751612] 0x50---------0x00 [14403.752973] 0x51---------0x05 [14403.753423] 0x52---------0xCD [14403.753860] 0x53---------0x00 [14403.754295] 0x54---------0xA1 [14403.754731] 0x55---------0x00 [14403.755164] 0x56---------0x01 [14403.755600] 0x58---------0x00000000 [14403.757212] 0x60---------0x00000000 [14403.757722] 0x6c---------0x06 [14403.758160] 0xC4---------0x8EAD [14403.758771] 0xC6---------0x7962 [14403.759230] 0xC8---------0x1020 [14403.759682] 0xCA---------0x45D6 [14403.761115] 0xCC---------0x6353 [14403.761589] 0xDA---------0x4000 [14403.762047] 0xE0---------0x0028 [14403.762500] 0xE4---------0x9E76C000 [14403.762987] 0xE8---------0x00000000 [14403.763475] 0xEC---------0x0000003F Does anyone have some idea? Thank you very very much. Steven -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists