Bug 131298

Summary: LSB should require RPM
Product: [openSUSE] SUSE Linux 10.1 Reporter: Peter Bowen <pzb>
Component: BasesystemAssignee: Thorsten Kukuk <kukuk>
Status: RESOLVED INVALID QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: unspecified   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Peter Bowen 2005-10-28 15:19:43 UTC
The LSB calls for applications to be in RPM format (LSB 3.0 section 22).  However our lsb package does not require rpm.  Maybe it should?  Or is the fact that the LSB does not require a tool to be able to install RPMs a reason not to require rpm?
Comment 1 Thorsten Kukuk 2005-10-28 15:46:08 UTC
It is a very bad idea to create such circulare dependencies to core packages. rpm is a core package, without RPM you cannot install the lsb rpm.
And LSB does not require in anyway rpm itself. You can also use cpio to install such packages (which is stupid to do, but valid).
Comment 2 LTC BugProxy 2005-11-14 09:14:11 UTC
---- Additional Comments From sychung@tw.ibm.com  2005-11-14 04:04 EDT -------
After reviewing net/core/link_watch.c and net/sched/sch_generic.c, SLES9 SP3 
RC1 (kernel 2.6.5-7.236) already fixed this bug.

I will test the kernel 2.6.5-7.236 to verify this bug is fixed. 
Comment 3 LTC BugProxy 2005-11-15 06:54:01 UTC
---- Additional Comments From sychung@tw.ibm.com  2005-11-15 01:50 EDT -------
SLES9-SP3-RC1 (kernel 2.6.5-7.236) already tested.

The resoult:

Source Box:
==============================================================================
[root@xlinuxt01 root]# uname -a
Linux xlinuxt01 2.6.5-7.236-i686 #1 Tue Nov 15 14:33:34 CST 2005 i686 i686 
i386 GNU/Linux

[root@xlinuxt01 root]# ethtool -i eth2
driver: tg3
version: 3.37
firmware-version:
bus-info: 0000:02:05.0

[root@xlinuxt01 root]# rmmod tg3;modprobe tg3
[root@xlinuxt01 root]#
[root@xlinuxt01 root]# ifdown eth2
    eth2      device: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet 
(rev 02)
    eth2      configuration: eth-id-00:0d:60:0f:e4:73
[root@xlinuxt01 root]# ifup eth2;tcpdump -i eth2 -n
    eth2      device: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet 
(rev 02)
    eth2      configuration: eth-id-00:0d:60:0f:e4:73
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes
14:55:39.817395 fe80::20d:60ff:fe0f:e473 > ff02::2: icmp6: router solicitation
14:55:43.816769 fe80::20d:60ff:fe0f:e473 > ff02::2: icmp6: router solicitation

2 packets captured
2 packets received by filter
0 packets dropped by kernel

[root@xlinuxt01 root]# ethtool -S eth2 | grep ring_set_send_prod_index
     ring_set_send_prod_index: 2

Tcpdump Box:
==============================================================================
[root@plinuxt02 ~]# ethtool -i eth3
driver: e1000
version: 6.0.54-k2-NAPI
firmware-version: N/A
bus-info: 0000:61:01.1

[root@plinuxt02 ~]# rmmod e1000
[root@plinuxt02 ~]# modprobe e1000
[root@plinuxt02 ~]# tcpdump -i eth3 -n
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth3, link-type EN10MB (Ethernet), capture size 96 bytes
06:50:01.483619 fe80::20d:60ff:fe0f:e473 > ff02::2: icmp6: router solicitation
06:50:05.482645 fe80::20d:60ff:fe0f:e473 > ff02::2: icmp6: router solicitation

2 packets captured
2 packets received by filter
0 packets dropped by kernel

[root@plinuxt02 ~]# ethtool -S eth3 | grep rx_packets
     rx_packets: 2


From the message above, the BCM5703C of \"Source Box\" shows it sent 2 packets 
(ring_set_send_prod_index) and \"Tcpdump Box\" also reveived 2 packets 
(rx_packets). In other words, there are no any lost packets. 
Comment 4 LTC BugProxy 2005-11-15 06:59:02 UTC
changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ACCEPTED                    |CLOSED




------- Additional Comments From sychung@tw.ibm.com  2005-11-15 01:53 EDT -------
SLES9-SP3-RC1 (kernel 2.6.5-7.236) already fixed this bug.

Change the Status of this bug to CLOSED.