rawhide report: 20061012 changes
by Build System
Updated Packages:
anaconda-11.1.1.1-1
-------------------
* Wed Oct 11 2006 Chris Lumens <clumens(a)redhat.com> - 11.1.1.1-1
- Ignore basepath in getHeader to fix CD installs (pnasrat).
- Fix package installation.
booty-0.80-1
------------
* Wed Oct 11 2006 Peter Jones <pjones(a)redhat.com> - 0.80-1
- Copy "nodmraid" and "nompath" args from the kernel command line (#209377)
dmraid-1.0.0.rc13-1.fc6
-----------------------
* Wed Oct 11 2006 Heinz Mauelshagen <heinzm(a)redhat.com> - 1.0.0.rc13-1
- metadata.c: fixed bug returning wrang unified RAID type (bz#210085)
- pdc.c: fixed magic number check
initscripts-8.45.3-1
--------------------
* Wed Oct 11 2006 Bill Nottingham <notting(a)redhat.com> 8.45.2-1
- Handle "nodmraid" and "nompath" command line options (#209377, <pjones(a)redhat.com>)
- translation updates: da, fi, zh_CN, ja
kernel-2.6.18-1.2768.fc6
------------------------
* Wed Oct 11 2006 Dave Jones <davej(a)redhat.com>
- Silence some useless messages that still get printed with 'quiet'
- 2.6.18.1rc1
- utrace: fix signal deliver on ptrace_detach()
* Wed Oct 11 2006 Jon Masters <jcm(a)redhat.com>
- kABI dep fixes.
- Change find-provides to use symvers instead and take a directory.
* Wed Oct 11 2006 Dave Jones <davej(a)redhat.com>
- Tux lockdep fixes.
libiec61883-1.0.0-11.fc6
------------------------
* Wed Oct 11 2006 Jarod Wilson <jwilson(a)redhat.com> - 1.0.0-11
- Use .fc6 tag
python-pyblock-0.24-2
---------------------
* Wed Oct 11 2006 Peter Jones <pjones(a)redhat.com> - 0.24-2
- Rebuild for new dmraid
Broken deps for s390
----------------------------------------------------------
systemtap - 0.5.9-1.fc6.s390 requires kernel >= 0:2.6.9-11
17 years, 7 months
ip6tables -m state (match state) not working...
by Michael H. Warfield
Hey all,
I've found that the IPv6 state matching is non-functional in FC6. I
first tried it in Test3 and have just reinstalled the entire system from
scratch from rawhide and verified it from the latest rawhide.
As installed, ip6tables has included the following default rules in the
rule sets (for this particular install):
:
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 445 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A RH-Firewall-1-INPUT -j DROP
With those rule sets, I was unable to establish any IPv6 connections to
or from the box.
Specifically, attempting to connect to the box with ssh (22/tcp)
resulted in a timeout (DROP). While timing out, a check on the server
indicated no socket indicating a connection attempt. The client system
(other system) has a socket in SYN SENT. It appears, in this case, that
the "-m state --state NEW" for port 22 was not triggered and we fell
through to the "-j DROP" rule at the end.
In the outbound case, the connection also times out but, this time, the
while the client system (this system) is in SYN SENT, the other system
is on SYN RECV. That indicates that the SYN packet was sent out
successfully and the other system did respond but the response was not
allowed back. In this case, it's the "-m state --state
ESTABLISHED,RELATED" rule failed to trigger and the packet is, again,
dropped.
If I add a rule "-m tcp -p tcp --dport 22 -j ACCEPT" with no state
matching, then inbound ssh connections succeed and function. Outbound
connections still fail though, because the ESTABLISHED state match still
isn't firing and now it a source port 22 on the incoming packets. So, I
can add a second rule "-m tcp -p tcp --sport 22 -j ACCEPT" to solve that
one.
Basically, the only way to work around it is to put in stateless
filtering (which is working). So the stateful filtering is broken for
IPv6. Worth noting that stateful filtering didn't even exist in FC5 and
earlier (I think it was introduced in kernel 2.6.16 or somewhere
thereabouts) so it's pretty new anyways. But it does mean that, if you
enabled the firewall, IPv6 becomes pretty much non-functional because
the firewall is failing and dropping everything coming in.
Filed in bugzilla: 209945
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209945
Regards,
Mike
--
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw(a)WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
17 years, 7 months
Calling yum from within a kickstart file in fc6pre
by Mogens Kjaer
For FC <= 5, I could call yum during the
kickstart installation from the %post section.
When I do this in FC6-pre, I get the following error:
/usr/bin/yum -y install nautilus-open-terminal
Traceback (most recent call last):
File "/usr/bin/yum", line 29, in ?
yummain.main(sys.argv[1:])
File "/usr/share/yum-cli/yummain.py", line 85, in main
base.getOptionsConfig(args)
File "/usr/share/yum-cli/cli.py", line 192, in getOptionsConfig
errorlevel=opts.errorlevel)
File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 123, in
doConfigSetup
self.doLoggingSetup(startupconf.debuglevel, startupconf.errorlevel)
File "/usr/lib/python2.4/site-packages/yum/__init__.py", line 147, in
doLoggingSetup
logginglevels.doLoggingSetup(debuglevel, errorlevel)
File "/usr/lib/python2.4/site-packages/yum/logginglevels.py", line
116, in doLoggingSetup
syslog = logging.handlers.SysLogHandler(log_dev)
File "/usr/lib/python2.4/logging/handlers.py", line 601, in __init__
self._connect_unixsocket(address)
File "/usr/lib/python2.4/logging/handlers.py", line 617, in
_connect_unixsocket
self.socket.connect(address)
File "<string>", line 1, in connect
socket.error: (111, 'Connection refused')
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/lib/python2.4/logging/__init__.py", line 1333, in shutdown
h.close()
File "/usr/lib/python2.4/logging/handlers.py", line 642, in close
if self.unixsocket:
AttributeError: SysLogHandler instance has no attribute 'unixsocket'
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib/python2.4/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/usr/lib/python2.4/logging/__init__.py", line 1333, in shutdown
h.close()
File "/usr/lib/python2.4/logging/handlers.py", line 642, in close
if self.unixsocket:
AttributeError: SysLogHandler instance has no attribute 'unixsocket'
I've repeated it several times, always the same error.
It works fine after installation, no "connection refused".
- or is there a smarter way of doing this?
Mogens
--
Mogens Kjaer, Carlsberg A/S, Computer Department
Gamle Carlsberg Vej 10, DK-2500 Valby, Denmark
Phone: +45 33 27 53 25, Fax: +45 33 27 47 08
Email: mk(a)crc.dk Homepage: http://www.crc.dk
17 years, 7 months
2.6.18-1.2189.fc5: Decreased data throughput?
by Mostafa Afgani
Hi,
In order to use the JMicron controller on my Asus P5B, I decided to
try out 2.6.18-1.2189.fc5 kernel from updates-testing. Prior to this I
was stuck running the 2.6.15-1.2054_FC5 kernel due to stability
issues.
For the HDD, I am using the ICH8 sata ports running in AHCI mode. To
test throughput, I ran the following command:
$ dd if=/dev/zero of=/tmp/dummy bs=100k count=10
With the 2054 kernel, I see a throughput of around 500 MB/s. With the
2189, that value is almost half at around 230 MB/s.
I've checked the output of dmesg for both kernels, and apart from the
ahci version and the failure to probe the JMicron controller on 2054,
they are nearly identical:
demsg-2054:
------------------
ahci 0000:00:1f.2: version 1.2
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports ? Gbps 0x33 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ilck stag led pmp pio
ata1: SATA max UDMA/133 cmd 0xFFFFC2000000C900 ctl 0x0 bmdma 0x0 irq 17
ata2: SATA max UDMA/133 cmd 0xFFFFC2000000C980 ctl 0x0 bmdma 0x0 irq 17
ata3: SATA max UDMA/133 cmd 0xFFFFC2000000CA00 ctl 0x0 bmdma 0x0 irq 17
ata4: SATA max UDMA/133 cmd 0xFFFFC2000000CA80 ctl 0x0 bmdma 0x0 irq 17
ata1: SATA link up 3.0 Gbps (SStatus 123)
ata1: dev 0 cfg 49:2f00 82:746b 83:7f01 84:4023 85:7469 86:3c01 87:4023 88:407f
ata1: dev 0 ATA-7, max UDMA/133, 488397168 sectors: LBA48
ata1: dev 0 configured for UDMA/133
scsi0 : ahci
ata2: SATA link down (SStatus 0)
scsi1 : ahci
ata3: SATA link down (SStatus 0)
scsi2 : ahci
ata4: SATA link down (SStatus 0)
scsi3 : ahci
Vendor: ATA Model: WDC WD2500KS-00M Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part
ata5: SATA max UDMA/133 cmd 0xFFFFC20000028100 ctl 0x0 bmdma 0x0 irq 16
ata6: SATA max UDMA/133 cmd 0xFFFFC20000028180 ctl 0x0 bmdma 0x0 irq 16
ata5: SATA link down (SStatus 0)
scsi4 : ahci
ata6: SATA link down (SStatus 0)
scsi5 : ahci
GSI 18 sharing vector 0xB9 and IRQ 18
ACPI: PCI Interrupt 0000:02:00.1[B] -> GSI 17 (level, low) -> IRQ 18
ahci: probe of 0000:02:00.1 failed with error -12
dmesg-2189:
------------------
ahci 0000:00:1f.2: version 2.0
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 177
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports ? Gbps 0x33 impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ilck stag led pmp pio
ata1: SATA max UDMA/133 cmd 0xFFFFC20000026900 ctl 0x0 bmdma 0x0 irq 233
ata2: SATA max UDMA/133 cmd 0xFFFFC20000026980 ctl 0x0 bmdma 0x0 irq 233
ata3: SATA max UDMA/133 cmd 0xFFFFC20000026A00 ctl 0x0 bmdma 0x0 irq 233
ata4: SATA max UDMA/133 cmd 0xFFFFC20000026A80 ctl 0x0 bmdma 0x0 irq 233
scsi0 : ahci
PM: Adding info for No Bus:host0
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-7, max UDMA/133, 488397168 sectors: LBA48
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : ahci
PM: Adding info for No Bus:host1
ata2: SATA link down (SStatus 0 SControl 300)
scsi2 : ahci
PM: Adding info for No Bus:host2
ata3: SATA link down (SStatus 0 SControl 0)
scsi3 : ahci
PM: Adding info for No Bus:host3
ata4: SATA link down (SStatus 0 SControl 0)
PM: Adding info for No Bus:target0:0:0
Vendor: ATA Model: WDC WD2500KS-00M Rev: 02.0
Type: Direct-Access ANSI SCSI revision: 05
PM: Adding info for scsi:0:0:0:0
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2
sd 0:0:0:0: Attached scsi disk sda
ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 169
PCI: Setting latency timer of device 0000:02:00.0 to 64
ahci 0000:02:00.0: AHCI 0001.0000 32 slots 2 ports 3 Gbps 0x3 impl SATA mode
ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part
ata5: SATA max UDMA/133 cmd 0xFFFFC20000028100 ctl 0x0 bmdma 0x0 irq 169
ata6: SATA max UDMA/133 cmd 0xFFFFC20000028180 ctl 0x0 bmdma 0x0 irq 169
scsi4 : ahci
PM: Adding info for No Bus:host4
ata5: SATA link down (SStatus 0 SControl 300)
scsi5 : ahci
PM: Adding info for No Bus:host5
ata6: SATA link down (SStatus 0 SControl 300)
Regards,
Mostafa
17 years, 7 months
repos down?
by cornel panceac
fc6pre: are the repos down? i can't connect to devel nor extras-devel ...
"
Error: Cannot find a valid baseurl for repo: extras-development
"
or it's my network's proxy server?
17 years, 7 months
re: re: dvd drive appears confused (ireason = 0x01),
by Gianluca Cecchi
On Wed, 11 Oct 2006 16:26:55 -0400 Alan Cox wrote:
> This usually occurs when there are IRQ routing problems in the BIOS tables
Thanks Alan,
any hints on how to verify and eventually correct?
I saw some references about irqpoll kernel parameter but with
performance issues drawbacks...
Another important thing to say furthermore, is that the same drive
connected to a dual athlon xp machine with standard ide channels
worked tipically at 5x-8x during dvd isos burning activities with
centos 4.4 os. And analogous results on the same machine with fc5.
First tests on this fc6 machine show a speed that is not faster than 2.60X ;-(
burning sw is k3b in all the cases.
Is there any driver optimization parameters here? are others using
JMB363 experimenting same performance issues?
17 years, 7 months
linux/config.h header file missing?
by Garrett Mitchener
I've tried building several kernel-related programs on FC6 test3, like
an older version of the mptscsi driver and the ATI proprietary driver
for FireGL graphics cards and such. I keep running into this error
that they want to #include <linux/config.h> and there is no such file
in any of the kernel versions. Is this a packaging mistake where this
file has somehow been left out of an RPM? Or has something happened
recently in kernel development such that the kernel no longer comes
with this file?
I've been able to get many of these things to compile by creating an
empty file, as in,
touch /usr/src/kernels/2.6.18-1.2747.fc6-x86_64/include/linux/config.h
but I'm a little uneasy about this hack.
-- Garrett Mitchener
17 years, 7 months
dvd drive appears confused (ireason = 0x01)
by Gianluca Cecchi
Hello all,
I have fc6 dev updated at yesterday and I'm having these kind of messages
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying to recov
er by ending request.
They appear tipically when there is no disc in drive.
For two times, after running commands involving the network (yum
update for downloading many packages but not extensive tests to
confirm this is the reason) I got continuously these messages and no
way then to control the pc, but powering off it.
MB is asus p5b-vm with ICH8/G965 chipsets and the unique ide channel
for the cd drive is controlled externally form the chipsets by the
JMicron jmb363.
I don't either understand why the cd is seen as hde and not hda ......
Some outputs:
[gcecchi@tekka ~]$ cat /proc/ide/drivers
ide-disk version 1.18
ide-floppy version 0.99.newide
ide-cdrom version 4.61
[gcecchi@tekka ~]$ ls -l /proc/ide/
total 0
-r--r--r-- 1 root root 0 Oct 11 21:35 drivers
lrwxrwxrwx 1 root root 8 Oct 11 21:35 hde -> ide2/hde
dr-xr-xr-x 3 root root 0 Oct 11 21:35 ide2
[gcecchi@tekka ~]$ cat /proc/ide/ide2/hde/model
ATAPI DVD DUAL 8X4X12
[root@tekka gcecchi]# cat /proc/ide/ide2/hde/settings
name value min max mode
---- ----- --- --- ----
current_speed 0 0 70 rw
dsc_overlap 0 0 1 rw
init_speed 0 0 70 rw
io_32bit 0 0 3 rw
keepsettings 0 0 1 rw
nice1 1 0 1 rw
number 0 0 3 rw
pio_mode write-only 0 255 w
unmaskirq 0 0 1 rw
using_dma 1 0 1 rw
>From dmesg I get:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
JMB363: IDE controller at PCI slot 0000:03:00.1
ACPI: PCI Interrupt 0000:03:00.1[B] -> GSI 17 (level, low) -> IRQ 177
JMB363: chipset revision 2
JMB363: 100% native mode on irq 177
ide2: BM-DMA at 0xb400-0xb407, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0xb408-0xb40f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: ATAPI DVD DUAL 8X4X12, ATAPI CD/DVD-ROM drive
ide2 at 0xbc00-0xbc07,0xb882 on irq 177
Probing IDE interface ide3...
Probing IDE interface ide0...
Probing IDE interface ide1...
Probing IDE interface ide3...
ide-floppy driver 0.99.newide
The cable connected to the dvd-rw is a 80 pin one. I don't know if it
can influence...
Any help from those using similar MBs in hw is appreciated.
Thanks in advance
Gianluca
17 years, 7 months
Metacity group-switching bug
by Michel Salim
Hi,
Group-switching between windows belonging to the same application
landed in GNOME 2.16.0, and generally works fine in most cases
(Macheads such as me should be happy!).
An exception, though, is gnome-terminal: the Window List panel applet
groups terminal windows properly, but for some reason, Metacity does
not.
Also, to change the shortcut for group-switching one still has to use
gconf-editor, it's not in System->Preferences->Keyboard Shortcuts yet.
The former is presumably a Metacity bug. Where should I file the
second bug? control-center?
Thanks,
--
Michel Salim
http://www.cs.indiana.edu/~msalim
http://the-dubois-papers.blogspot.com/
17 years, 7 months
FC6 Pre first attempt failed
by Guy Fraser
I thought I would give it a go, so I got the DVD using the torrent.
1) The Media test failed, but the sha1sum was correct.
2) The install would not progress past the X cursor.
The system I tested it on is a tricky beast. It has SATA,
SATA RAID and PATA drives, as well as a dual head nVidia
AGP 8X video card. During start up both SATA chip sets were
found, and apparently the standard nVidia driver works.
>From what I could tell, there was no disk activity once the
X cursor was displayed. I flipped through the pseudo terminals
and did not notice any errors.
When I get another chance to test, I will try a text install
then I will disconnect the SATA drives like I had to do to get
FC5 to install, and see how far I get then.
Question: Does the installer scan all drives for previous installs?
If it does, then that might explain the apparent inactivity.
I use the machine as a video archive server, and have over a
terrabyte of storage. I am not certain if reading from all
drives are indicated on the HD LED so it may not appear to be
doing anything.
17 years, 7 months
