Re: Netfilter: kernel panic with REDIRECT target. (2.6.23 and 2.6.23.8)
Sunday 18 November 2007 Tarihinde 21:00:12 yazmıştı: I'm (very) far from being firewall configuration expert, but I'm seeing a consistent kernel panic when the following rule is triggered. iptables -t nat -A PREROUTING -j REDIRECT -i eth2 -p udp --dport 5061 --to-ports 5060 (I'm trying to redirect an alternate port to a SIP server) Am I just being very stupid, or is there something I'm not seeing here? Also post the kernel panic log. -- Faith is believing what you know isn't so -- Mark Twain - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Bluetooth wireless mouse very sluggish when there is moderated network activity
Hi all, I got a Bluetooth wireless mouse identifed as, input: Microsoft Microsoft� Wireless Notebook Presenter Mouse 8000 as /devices/pci:00/:00:1d.1/usb3/3-1/3-1.3/3-1.3:1.0/input/input12 input: USB HID v1.11 Mouse [Microsoft Microsoft� Wireless Notebook Presenter Mouse 8000] on usb-:00:1d.1-1.3 Problem is when there is a moderate traffic on wireless interface (300-400k/s down 50-60k/up on 4Mbit) mouse is really sluggish. This is when I am running ktorrent. If I stop the torrent download/upload its fine again. Any idea how to debug this, or why it might be happening. Btw I confirmed this behaviour on kernel 2.8.18.8, 2.6.22, 2.6.23 and latest GIT tree. P.S: If it matters I am using ipw3945 driver with 2.6.18 kernel and iwl3945 with the newer ones. Regards, ismail -- Faith is believing what you know isn't so -- Mark Twain - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bluetooth wireless mouse very sluggish when there is moderate network activity
s/moderated/moderate of course :-/ Saturday 13 October 2007 Tarihinde 17:13:03 yazmıştınız: Hi all, I got a Bluetooth wireless mouse identifed as, input: Microsoft Microsoft� Wireless Notebook Presenter Mouse 8000 as /devices/pci:00/:00:1d.1/usb3/3-1/3-1.3/3-1.3:1.0/input/input12 input: USB HID v1.11 Mouse [Microsoft Microsoft� Wireless Notebook Presenter Mouse 8000] on usb-:00:1d.1-1.3 Problem is when there is a moderate traffic on wireless interface (300-400k/s down 50-60k/up on 4Mbit) mouse is really sluggish. This is when I am running ktorrent. If I stop the torrent download/upload its fine again. Any idea how to debug this, or why it might be happening. Btw I confirmed this behaviour on kernel 2.8.18.8, 2.6.22, 2.6.23 and latest GIT tree. P.S: If it matters I am using ipw3945 driver with 2.6.18 kernel and iwl3945 with the newer ones. Regards, ismail -- Faith is believing what you know isn't so -- Mark Twain - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Kconfig warnings on latest GIT
Hi, Following Kconfig warnings shows up with latest GIT : drivers/net/Kconfig:2279:warning: 'select' used by config symbol 'UCC_GETH' refers to undefined symbol 'UCC_FAST' drivers/input/keyboard/Kconfig:170:warning: 'select' used by config symbol 'KEYBOARD_ATARI' refers to undefined symbol 'ATARI_KBD_CORE' drivers/input/mouse/Kconfig:161:warning: 'select' used by config symbol 'MOUSE_ATARI' refers to undefined symbol 'ATARI_KBD_CORE' Regards, ismail -- Le mieux est l'ennemi du bien. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
Hi, On Tuesday 24 April 2007 00:23:13 Ismail Dönmez wrote: On Tuesday 24 April 2007 00:17:40 Thomas Graf wrote: * Ismail D?nmez [EMAIL PROTECTED] 2007-04-23 22:09 Yes I know the fix is in but I wondered why its creating such problems with 2.6.18 kernel, guess it depends on some other commits. As long as you apply the complete patch including the additional sanity check for RTN_MAX it should work perfectly fine on 2.6.18. The sanity check part doesn't seem to apply to 2.6.18. I can't think of any connection between the patch and the errors you are seeing. Are you absolutely sure the errors you see are directly connected to applying the patch? Yes actually I am but I'll re-test and see. Thanks. I was able to reproduce the same problem with Linus' GIT tree too. Since I started to see these after I applied the commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e to 2.6.18 tree, there is a big possiblity that the commit is the culprit. I attach the relevant dmesg messages. Problem happened after 12 hours of uptime and and net connection gets stable again after 1-2 minutes. Regards, ismail -- Life is a game, and if you aren't in it to win, what the heck are you still doing here? -- Linus Torvalds (talking about open source development) Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. printk: 1 messages suppressed. Neighbour table overflow. printk: 4 messages suppressed. Neighbour table overflow. printk: 3 messages suppressed. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. printk: 3 messages suppressed. Neighbour table overflow. printk: 15 messages suppressed. Neighbour table overflow. printk: 6 messages suppressed. Neighbour table overflow. printk: 13 messages suppressed. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. Neighbour table overflow. printk: 2 messages suppressed. Neighbour table overflow. printk: 1 messages suppressed. Neighbour table overflow. Neighbour table overflow.
Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
On Wednesday 25 April 2007 11:52:52 Ismail Dönmez wrote: Hi, On Tuesday 24 April 2007 00:23:13 Ismail Dönmez wrote: On Tuesday 24 April 2007 00:17:40 Thomas Graf wrote: * Ismail D?nmez [EMAIL PROTECTED] 2007-04-23 22:09 Yes I know the fix is in but I wondered why its creating such problems with 2.6.18 kernel, guess it depends on some other commits. As long as you apply the complete patch including the additional sanity check for RTN_MAX it should work perfectly fine on 2.6.18. The sanity check part doesn't seem to apply to 2.6.18. I can't think of any connection between the patch and the errors you are seeing. Are you absolutely sure the errors you see are directly connected to applying the patch? Yes actually I am but I'll re-test and see. Thanks. I was able to reproduce the same problem with Linus' GIT tree too. Since I started to see these after I applied the commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e to 2.6.18 tree, there is a big possiblity that the commit is the culprit. I attach the relevant dmesg messages. Problem happened after 12 hours of uptime and and net connection gets stable again after 1-2 minutes. Ignore this my laptop seems to be totally dying now including wireless card too. Sorry for the noise. Regards, ismail -- Life is a game, and if you aren't in it to win, what the heck are you still doing here? -- Linus Torvalds (talking about open source development) signature.asc Description: This is a digitally signed message part.
Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
Hi,
On Monday 23 April 2007 21:51:25 David Miller wrote:
From: Ismail Dönmez [EMAIL PROTECTED]
Date: Mon, 23 Apr 2007 15:06:34 +0300
--- a/net/ipv4/fib_semantics.c
+++ b/net/ipv4/fib_semantics.c
@@ -89,7 +89,7 @@ static const struct
{
int error;
u8 scope;
-} fib_props[RTA_MAX + 1] = {
+} fib_props[RTN_MAX + 1] = {
This fix is already in the net-2.6.22 tree.
Yes I know the fix is in but I wondered why its creating such problems with
2.6.18 kernel, guess it depends on some other commits.
Regards,
ismail
--
Life is a game, and if you aren't in it to win,
what the heck are you still doing here?
-- Linus Torvalds (talking about open source development)
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Problem with commit a0ee18b9b7d3847976c6fb315c06a34fb296de0e
On Tuesday 24 April 2007 00:17:40 Thomas Graf wrote: * Ismail D?nmez [EMAIL PROTECTED] 2007-04-23 22:09 Yes I know the fix is in but I wondered why its creating such problems with 2.6.18 kernel, guess it depends on some other commits. As long as you apply the complete patch including the additional sanity check for RTN_MAX it should work perfectly fine on 2.6.18. The sanity check part doesn't seem to apply to 2.6.18. I can't think of any connection between the patch and the errors you are seeing. Are you absolutely sure the errors you see are directly connected to applying the patch? Yes actually I am but I'll re-test and see. Thanks. Regards, ismail -- Life is a game, and if you aren't in it to win, what the heck are you still doing here? -- Linus Torvalds (talking about open source development) signature.asc Description: This is a digitally signed message part.
Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
On Friday 09 February 2007 23:12:42 James Ketrenos wrote: Please hold all questions until I am done with this email. Thank you. We are pleased to announce the availability of a new driver for the Intel PRO/Wireless 3945ABG Network Connection adapter. This new driver uses the new d80211 subsystem previously only available as part of the wireless-dev tree. You can find the new driver, and additional information about it, here: http://intellinuxwireless.org/iwlwifi. Tried this is on a patched 2.6.20 kernel with ipw3945 device and it always puts the card in 802.11a mode instead of 802.11bg mode. Ideas? Regards, ismail - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG
On Tuesday 13 February 2007 17:10:24 Jeff Chua wrote: On 2/13/07, Ismail Dönmez [EMAIL PROTECTED] wrote: Tried this is on a patched 2.6.20 kernel with ipw3945 device and it always puts the card in 802.11a mode instead of 802.11bg mode. Ideas? Before running iwconfig wlan0 channel 8, the card is set to 802.11a mode. iwconfig shows rate at 54Mb/s. But after setting the channel, it sets to 802.11b mode, and I can't find a way to change from 11Mb/s to 54MB/s. iwlist eth0 rate only show up to 11Mb/s. So, my problem is the card is always in 802.11b mode. So I guess there is a common problem with a/bg modes? Regards, ismail - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 2.6.20-rc2: known unfixed regressions (v2)
31 Ara 2006 Paz 02:47 tarihinde, Adrian Bunk şunları yazmıştı: [...] Subject: ALSA: No sound in KDE with intel hda References : http://lkml.org/lkml/2006/12/30/73 Submitter : Ismail Dönmez [EMAIL PROTECTED] Status : unknown Just tried with 2.6.18.6 and aRts still have no sound, there must be something else broken on my side. Thanks, ismail -- 2 + 2 = 5 for very large values of 2 - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
