September 2005 - openSUSE AMD64 - openSUSE Mailing Lists

Suse 9.3 AppleTalk loopback problem patch
by Helmut Tschemernjak 19 Sep '05

19 Sep '05

we found a bug in net/appletalk/ddp.c concerning broadcast packets. In kernel 2.4 it was working and the bug first occured 4 years ago when switching to new SNAP layer handling. This bug can be splitted up into a sending(1) and reception(2) problem: Sending(1) In kernel 2.4 broadcast packets were sent to a matching ethernet device and atalk_rcv() was called to receive it as "loopback" (so loopback packets were shortcutted and handled in DDP layer). When switching to the new SNAP structure, this shortcut was removed and the loopback packet was send to SNAP layer. The author forgot to replace the remote device pointer by the loopback device pointer before sending the packet to SNAP layer (by calling ddp_dl->request() ) therfor the packet was not sent back by underlying layers to ddp's atalk_rcv(). Reception(2) In atalk_rcv() a packet received by this loopback mechanism contains now the (rigth) loopback device pointer (in Kernel 2.4 it was the (wrong) remote ethernet device pointer) and therefor no matching socket will be found to deliver this packet to. Because a broadcast packet should be send to the first matching socket, we removed the network comparison in broadcast case. Below you will find a patch to correct this bug. Its diffed to kernel 2.6.11. Regards, Helmut Tschemernjak HELIOS Software GmbH ---sip--- /usr/src/linux-2.6.11/net/appletalk# diff -u ddp-orig.c ddp.c --- ddp-orig.c 2005-09-19 15:44:10.000000000 +0200 +++ ddp.c 2005-09-19 15:50:54.000000000 +0200 @@ -99,9 +99,11 @@ if (to->sat_port != at->src_port) continue; + /* take first matching socket an send broadcast to it + * don't compare network adress + */ if (to->sat_addr.s_net == ATADDR_ANYNET && - to->sat_addr.s_node == ATADDR_BCAST && - at->src_net == atif->address.s_net) + to->sat_addr.s_node == ATADDR_BCAST) goto found; if (to->sat_addr.s_net == at->src_net && @@ -1444,8 +1446,8 @@ else atif = atalk_find_interface(ddp->deh_dnet, ddp->deh_dnode); - /* Not ours, so we route the packet via the correct AppleTalk iface */ if (!atif) { + /* Not ours, so we route the packet via the correct AppleTalk iface */ atalk_route_packet(skb, dev, ddp, &ddphv, origlen); goto out; } @@ -1593,10 +1595,6 @@ if (usat->sat_addr.s_net || usat->sat_addr.s_node == ATADDR_ANYNODE) { rt = atrtr_find(&usat->sat_addr); - if (!rt) - return -ENETUNREACH; - - dev = rt->dev; } else { struct atalk_addr at_hint; @@ -1604,11 +1602,11 @@ at_hint.s_net = at->src_net; rt = atrtr_find(&at_hint); - if (!rt) - return -ENETUNREACH; - - dev = rt->dev; } + if (!rt) + return -ENETUNREACH; + + dev = rt->dev; SOCK_DEBUG(sk, "SK %p: Size needed %d, device %s\n", sk, size, dev->name); @@ -1678,6 +1676,20 @@ SOCK_DEBUG(sk, "SK %p: Loop back.\n", sk); /* loop back */ skb_orphan(skb); + if (ddp->deh_dnode == ATADDR_BCAST) { + struct atalk_addr at_lo; + + at_lo.s_node = 0; + at_lo.s_net = 0; + + rt = atrtr_find(&at_lo); + if (!rt) { + kfree_skb(skb); + return -ENETUNREACH; + } + dev = rt->dev; + skb->dev = dev; + } ddp_dl->request(ddp_dl, skb, dev->dev_addr); } else { SOCK_DEBUG(sk, "SK %p: send out.\n", sk); ---snip--- --

2 1

SB read failed on non-root fs during boot
by M. Ranjit Mathews 17 Sep '05

17 Sep '05

I'm going to try to fix the problem described below by reinstalling with all 4 drives present; if it's a bug, the bug report goes as follows: I installed SuSE 9.3 on a degraded mirror (SCSI) on a Tyan S2882. Then, I added another identical SCSI drive sdb (so far unused) and 2 SATA drives sdc and sdd. On the SATA drives, I made a mirrored XFS filesystem. During boot, SB read of the XFS filesystem fails. >From the excerpt from the boot log attached below, the bug seems to be that YaST (or whatever other program) has generated a boot sequence whereby the SATA driver isn't loaded till after the SB read is attempted. Once the system has booted, I am able to use the XFS filesystem with the command mdadm -As /dev/md1; mount /dev/md1 /xfs My mdadm.conf file looks like so: # cat /etc/mdadm.conf DEVICE /dev/sdc1 /dev/sdd1 ARRAY /dev/md1 level=raid1 num-devices=2 UUID=4cc9811c:cf7ec5fc:65de479d:972790be devices=/dev/sdc1,/dev/sdd1 <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: considering sda2 ... <6>md: adding sda2 ... <6>md: created md0 <6>md: bind<sda2> <6>md: running: <sda2> <6>raid1: raid set md0 active with 1 out of 2 mirrors <6>md: ... autorun DONE. <5>ReiserFS: md0: found reiserfs format "3.6" with standard journal <5>ReiserFS: md0: using ordered data mode <4>reiserfs: using flush barriers <5>ReiserFS: md0: journal params: device md0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 <5>ReiserFS: md0: checking transaction log (md0) <5>ReiserFS: md0: Using r5 hash to sort names <4>md: raidstart(pid 2095) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 <3>md: could not bd_claim sda2. <4>md: autostart failed! <4>md: raidstart(pid 2095) used deprecated START_ARRAY ioctl. This will not be supported beyond 2.6 <3>md: could not open unknown-block(8,33). <4>md: autostart failed! <6>md: Autodetecting RAID arrays. <6>md: autorun ... <6>md: ... autorun DONE. <6>device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel(a)redhat.com <6>parport0: PC-style at 0x378 [PCSPP] <6>parport0: irq 7 detected <6>lp0: using parport0 (polling). <4>XFS: SB read failed <6>hw_random: AMD768 system management I/O registers at 0x1000. <6>hw_random hardware driver 1.0.0 loaded <6>tg3.c:v3.23 (February 15, 2005) <6>ACPI: PCI interrupt 0000:02:09.0[A] -> GSI 24 (level, low) -> IRQ 169 <6>eth0: Tigon3 [partno(BCM95704A7) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:28:c7:b8 <6>eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] <6>ACPI: PCI interrupt 0000:02:09.1[B] -> GSI 25 (level, low) -> IRQ 177 <6>eth1: Tigon3 [partno(BCM95704A7) rev 2003 PHY(5704)] (PCIX:100MHz:64-bit) 10/100/1000BaseT Ethernet 00:e0:81:28:c7:b9 <6>eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] <6>ACPI: PCI interrupt 0000:03:04.0[A] -> GSI 16 (level, low) -> IRQ 185 <7>libata version 1.10 loaded. <7>sata_sil version 0.9 <6>ACPI: PCI interrupt 0000:03:05.0[A] -> GSI 19 (level, low) -> IRQ 193 <6>ata1: SATA max UDMA/100 cmd 0xFFFFC2000002AC80 ctl 0xFFFFC2000002AC8A bmdma 0xFFFFC2000002AC00 irq 193 <6>ata2: SATA max UDMA/100 cmd 0xFFFFC2000002ACC0 ctl 0xFFFFC2000002ACCA bmdma 0xFFFFC2000002AC08 irq 193 <6>ata3: SATA max UDMA/100 cmd 0xFFFFC2000002AE80 ctl 0xFFFFC2000002AE8A bmdma 0xFFFFC2000002AE00 irq 193 <6>ata4: SATA max UDMA/100 cmd 0xFFFFC2000002AEC0 ctl 0xFFFFC2000002AECA bmdma 0xFFFFC2000002AE08 irq 193 <6>e100: Intel(R) PRO/100 Network Driver, 3.4.1-NAPI <6>e100: Copyright(c) 1999-2005 Intel Corporation

1 0

AMD64 X2 and SMP kernel
by jerry bookter 17 Sep '05

17 Sep '05

Hi folks-- I'm thinking of building a dream machine based on an AMD64 X2 4800+. I looked around on the internet to confirm Linux compatibility and it seems that a lot of people have hit snags getting an SMP kernel onto one. I'm not sure if this is a chipset problem (nforce vs kt800) or something else. It's a good thing I looked before I leaped on this. Has anyone here had any good experiences with an X2 CPU? What motherboard? TIA... :)

4 4

suse 9.3 system reboot on large scp/rsync >3GB
by Ryan Biltz 17 Sep '05

17 Sep '05

Whenever I scp or rsync a large amount of data (>3GB) the system suddenly reboots. The system runs Suse 9.3 (fully updated) . When the system is rebooting from an attempted rsync or scp it displays that dimms 5 and 6 are both bad. I have 12GB total. 5 and 6 are 2 gig dimms from Crucial. I would do a Ctrl+Alt+Del at this point the system comes back normal. I've also reseated the RAM but the results are the same. Has anyone experienced this at all or may know what's going on? TIA. --ryan

2 1

Unable to load shared library (signature?)
by Pierre Patino 16 Sep '05

16 Sep '05

Greetings I've just emerged from a full day of hacking. It all started when I downloaded the latest update for SuSE 9.3. Along with everything else I accepted the kernel update (2.6.11.4-21.9-default) knowing full well I would have to deal with another iteration of the nvidia graphics driver download. After all the updates were properly sucked in and disseminated, I rebooted my computer. All of the boot sequence went well. However, the machine went into an endless login loop: while (1) { show login screen for 800ms clear screen } I was able to CTRL-ALT-BACKSPACE to get to a non-graphics login and then tried to figure out what was happening. startx would exit saying that kdeconfigure or some other binary in /opt/kde3/bin would fail. Upon closer examination, I was able to determine that the kde applications would complain of being "unable to load shared library lxxxxx.so.xxx". I used ldd, export LD_DEBUG=all, strace -f and other utilities to determine that the binary was unable to load the libkxxxx.so.y library. However, I was able to find the library manually at exactly the same location that the binary was complaining about. For example, I would see in strace: ... open("/lib64/libkxxxx.so.4", O_RDONLY) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360\21\0"..., 640) = 640 ... "/lib64/libkxxxx.so.4 not found!" (or something like that) ..... ls -la /lib64/libkxxxx.so.4 had not problems finding the file with wide open permissions. After trying many other fruitless paths, I was able to recover by pointing /opt/kde3 to an older partition. I assume that even though the shared object files were found, they must have lacked some signature Questions: Is there some fine-grained tool that would have told me sooner what was going on? Am I the only one that has gone through this torture? TIA& Cheers P.S. Am I blowing etiquette by posting on two groups?

2 1

Moneyplex with card reader cyberjack
by detlef oertel 16 Sep '05

16 Sep '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I tried to use moneyplex banking software suse-edition on my suse 9.3 x86_64 system in combination with a reinersct cyberjack card reader. But it doesn't worked because moneyplex is a 32 Bit Software and must access the cardreader via a 32-Bit library. This is confirmed by a email from matrica, the producer of the moneyplex software. Working libraries for the cardreader on a x86_64 system are only 64 Bit based. Here are my secifications and experiences: - --------------------------------------------- uname -a: Linux sepia 2.6.11.4-21.8-default #1 Tue Jul 19 12:42:37 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux moneyplex 5.0 suse-edition (Build 11777) lsusb:Bus 003 Device 003: ID 0c4b:0300 Reiner SCT Kartensysteme GmbH cyberJack pinpad(a) I installed the actual driver: ctapi-cyberjack-2.0.9-1_suse920.x86_64.rpm On the commandline I get: cjgeldkarte -l /usr/lib64/readers/libctapi.so Unknown card. (which means: can access cardreader but wrong card inserted, what was correct - it was a HBCI card) Moneyplex tells about /usr/lib64/readers/libctapi.so 'Die von Ihnen ausgewählte Datei ist kein CTAPI-Treiber eines Chipkarten Lesers' (This is not a valid driver for a card reader) Using a 32-Bit driver i get from moneyplex: no contact to the car reader or on the commandline: cjgeldkarte -l /usr/lib/readers/libctapi.so Error loading CT-API library.) - -------------------------------------------- Has anybody a working online bankig software with access to hbci cards on 64-Bit system ? greetings detlef -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDHqZ/iHgljbcBEOYRAtUiAJ0TjS8KsNkCcGQgq7p8JbNhBVp/ngCgt5ca ihlf+edlKUvUElB3l1h4wdg= =NVM8 -----END PGP SIGNATURE-----

4 3

Quick System Clock
by MIGUEL.MARTIN＠telefonica.net 14 Sep '05

14 Sep '05

I have found a solution to the problem with the patch http://bugme.osdl.org/attachment.cgi?id=5755&action=view and the kernel 2.6.13 Trying kernel parameter 'noapic' the system halt at boot time because don't find SATA hard disk. I think that the solution sould be included in the kernel because I have found a lot of people with the same problem or similar, as seen in http://bugme.osdl.org/show_bug.cgi?id=3927 or http://www.ussg.iu.edu/hypermail/linux/kernel/0504.0/0270.html System data are Compaq Presario SR1495ES Model (Desktop) AMD64 3700+ (2.2 GHz) Socket 939 Chipset ATI Radeon XPress 200P 1024 MB RAM (2x512 MB) MSI Motherboard (MS-7093) Video Nvidia Ge Force 6200 Turbocache 256MB (PCI-Express) I attach info from dmesg and /proc/interrupts and lspci I could test new kernels with the solution included Thanks, Miguel Martin. File input Error for file: /internet/programas/tps/webapps/cp/WEB-INF/etc/blank.html

1 0

"top" output
by Marcin Zalewski 14 Sep '05

14 Sep '05

Hello list, I have been trying to figure out what does the cpu usage output from top mean. I get: Cpu(s): 24.8% us, 11.3% sy, 0.0% ni, 55.0% id, 0.0% wa, 0.0% hi, 8.9% si but I cannot figure out what does "wa", "hi", and "si" stand for. Can anybody help? Thanks. -m

1 1

2.6.13.1 kernel doesn't load usb mouse and network modules
by Pierre Patino 14 Sep '05

14 Sep '05

Greetings lixerati I downloaded the latest stable kernel and built it. However, I'm forced to manually load the usb drivers (for the mouse) and the network drivers (sk98lin and other ip-related modules) before the system is at least as usable as with the previous ( 2.6.11.4-21.7-default) kernel. I tried several versions of the 2.6.13.1 kernel based on the config file found in /boot but I'm always forced to load these modules manually. Has anyone beaten this dragon? TIA & cheers

2 1

2.6.13.1 kenel doesn't load usb mouse and network modules
by Pierre Patino 14 Sep '05

14 Sep '05

Greetings lixerati I downloaded the latest stable kernel and built it. However, I'm forced to manually load the usb drivers (for the mouse) and the network drivers (sk98lin and other ip-related modules) before the system is at least as usable as with the previous ( 2.6.11.4-21.7-default) kernel. I tried several versions of the 2.6.13.1 kernel based on the config file found in /boot but I'm always forced to load these modules manually. Has anyone beaten this dragon? TIA & cheers

1 0