Hi there.
For a long time now I have had some issues with USB 2.0 enabled on one of my machines, but *only* in Linux. In Windows everything works fine, which makes me think that there's simply something that is not implemented/wrongly detected in Linux.
I get a bunch of these when the ehci-hcd module is loaded:
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
hub 5-3:1.0: Cannot enable port 2. Maybe the USB cable is bad?
At least 100 and they continue to show up until I unload the ehci-hcd module.
My load with ehci-hcd loaded is very high. Typically about 2-3 whereas it would be around 0.5 otherwise.
At one point I replied to a bug with a similar problem on the vanilla kernel and got a patch that could block a USB hub, which took care of the load issue, but would also result in my wireless rt2570 disappearing. It was loaded like this:
#!/bin/sh
modprobe ehci-hcd
sleep 1s
echo 2 > /sys/class/usb_hub/usbhub5.2/ignore
date > /tmp/fix-usb.log 2&>1
I have (hopefully) attached the patch to this message.
Is there any way that we can get closer to what the real problem is here? Even if it means installing some debug software in Windows and running a battery of tests, I would just really like to have working USB 2.0 again...
I also wonder why the patch never made it to the kernel. It was scheduled for inclusion at one point. Maybe it has issues?
For the record: This happens with almost all 2.6 kernels I have tried, SUSE or otherwise. I think I didn't see it around 2.6.5, but I'm not quite sure. 2.4.x kernels do not have the problem as far as I can tell, but then USB 2.0 is a 2.6 feature, right?
If I do not load the ehci-hcd module I *can* actually see and use my wireless adapter, but naturally it maxes out at 12 Mbit/s...
The machine is pretty responsive even with the high load, but is does not seem right that is should behave this way.
Hello,
I've run into a very weird problem here. I'm using an external USB
harddisk and when I plug it, it's correctly detected:
usb 4-1: new high speed USB device using ehci_hcd and address 2
usb 4-1: new device found, idVendor=059b, idProduct=007e
usb 4-1: new device strings: Mfr=56, Product=63, SerialNumber=88
usb 4-1: Product: Iomega HDD USB 2.0 Drive
usb 4-1: Manufacturer: Iomega
usb 4-1: SerialNumber: 03000B5AE5F4
usb 4-1: configuration #1 chosen from 1 choice
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 0:0:0:0: Direct-Access ST325082 3A PQ: 0 ANSI: 0
usb-storage: device scan complete
sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 33 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 33 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: Attached scsi generic sg0 type 0
If I try to mount /dev/sda1, I got the following error:
# mount /dev/sda1 /mnt
mount: /dev/sda1 already mounted or /mnt busy
And it is really not mounted:
# grep sda /proc/mounts
#
Looking at /proc/partitions I identified that /dev/sda1 is "the same" as
/dev/dm-6:
8 0 244198584 sda
8 1 244196001 sda1
253 5 244198584 dm-5
253 6 244196001 dm-6
If I try to mount /dev/dm-6, it works:
# mount /dev/dm-6 /mnt
# cat /proc/mounts | grep mnt
/dev/dm-6 /mnt ext3 rw,data=ordered 0 0
#
If I unplug the disk and plug it again, it will be detected as /dev/sdb:
usb 4-1: USB disconnect, address 2
usb 4-1: new high speed USB device using ehci_hcd and address 3
usb 4-1: new device found, idVendor=059b, idProduct=007e
usb 4-1: new device strings: Mfr=56, Product=63, SerialNumber=88
usb 4-1: Product: Iomega HDD USB 2.0 Drive
usb 4-1: Manufacturer: Iomega
usb 4-1: SerialNumber: 03000B5AE5F4
usb 4-1: configuration #1 chosen from 1 choice
scsi1 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usb 4-1: reset high speed USB device using ehci_hcd and address 3
scsi 1:0:0:0: Direct-Access ST325082 3A PQ: 0 ANSI: 0
sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 33 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 33 00 00 00
sd 1:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 1:0:0:0: [sdb] Attached SCSI disk
sd 1:0:0:0: Attached scsi generic sg0 type 0
usb-storage: device scan complete
Mounting /dev/sdb1 works as expected:
# mount /dev/sdb1 /mnt
# cat /proc/mounts | grep mnt
/dev/sdb1 /mnt ext3 rw,data=ordered 0 0
But, if I try to mount /dev/dm-6 now, it doesn't work:
# mount /dev/dm-6 /mnt
mount: you must specify the filesystem type
And I get a lot of error messages on dmesg:
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device dm-6, logical block 244195904
Buffer I/O error on device dm-6, logical block 244195905
Buffer I/O error on device dm-6, logical block 244195906
Buffer I/O error on device dm-6, logical block 244195907
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device dm-6, logical block 244195904
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device dm-6, logical block 244195905
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device dm-6, logical block 244195906
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device dm-6, logical block 244195907
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device dm-6, logical block 244195904
scsi 0:0:0:0: rejecting I/O to dead device
Buffer I/O error on device dm-6, logical block 244195905
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
scsi 0:0:0:0: rejecting I/O to dead device
I'm following Factory (Beta-3 on PPC: 2.6.22.5-4-default #1 2007/08/27
09:51:45 UTC ppc ppc ppc GNU/Linux), and I don't remember seeing this problem,
let's say, 20 days ago. I'd appreciate any help to debug this, I'll start
by trying with older kernels.
Below, the full dmesg for reference.
Thanks!
Leonardo
Using PowerMac machine description
Total memory = 1024MB; using 2048kB for hash table (at cfe00000)
Linux version 2.6.22.5-4-default (geeko@buildhost) (gcc version 4.2.1
(SUSE Linux)) #1 2007/08/27 09:51:45 UTC
Found initrd at 0xc4100000:0xc4390c00
Found UniNorth memory controller & host bridge @ 0xf8000000 revision: 0xd2
Mapped at 0xfdfc0000
Found a Intrepid mac-io controller, rev: 0, mapped at 0xfdf40000
Processor NAP mode on idle enabled.
PowerMac motherboard: Mac mini
Entering add_active_range(0, 0, 262144) 0 entries of 256 used
Found UniNorth PCI host bridge at 0x00000000f0000000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0x00000000f2000000. Firmware bus number: 0->0
Found UniNorth PCI host bridge at 0x00000000f4000000. Firmware bus number: 0->0
via-pmu: Server Mode is disabled
PMU driver v2 initialized for Core99, firmware: 55
nvram: Checking bank 0...
nvram: gen0=228, gen1=229
nvram: Active bank is: 1
nvram: OF partition at 0x410
nvram: XP partition at 0x1020
nvram: NR partition at 0x1120
Top of RAM: 0x40000000, Total RAM: 0x40000000
Memory hole size: 0MB
Zone PFN ranges:
DMA 0 -> 196608
Normal 196608 -> 196608
HighMem 196608 -> 262144
early_node_map[1] active PFN ranges
0: 0 -> 262144
On node 0 totalpages: 262144
DMA zone: 1536 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 195072 pages, LIFO batch:31
Normal zone: 0 pages used for memmap
HighMem zone: 512 pages used for memmap
HighMem zone: 65024 pages, LIFO batch:15
Built 1 zonelists. Total pages: 260096
Kernel command line: root=/dev/vg/root quiet sysrq=1
mpic: Setting up MPIC " MPIC 1 " version 1.2 at 80040000, max 4 CPUs
mpic: ISU size: 64, shift: 6, mask: 3f
mpic: Initializing for 64 sources
PID hash table entries: 4096 (order: 12, 16384 bytes)
GMT Delta read from XPRAM: 0 minutes, DST: off
time_init: decrementer frequency = 41.620997 MHz
time_init: processor frequency = 1416.666661 MHz
Console: colour dummy device 80x25
console handover: boot [udbg0] -> real [tty0]
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
High memory: 262144k
Memory: 1028688k/1048576k available (4392k kernel code, 281256k
reserved, 164k data, 467k bss, 208k init)
Calibrating delay loop... 83.20 BogoMIPS (lpj=166400)
Security Framework v1.0.0 initialized
Mount-cache hash table entries: 512
device-tree: Duplicate name in /cpus/PowerPC,G4@0, renamed to "l2-cache#1"
NET: Registered protocol family 16
KeyWest i2c @0xf8001003 irq 42 /uni-n@f8000000/i2c@f8001000
channel 0 bus <multibus>
channel 1 bus <multibus>
KeyWest i2c @0x80018000 irq 26 /pci@f2000000/mac-io@17/i2c@18000
channel 0 bus <multibus>
PMU i2c /pci@f2000000/mac-io@17/via-pmu@16000/pmu-i2c
channel 1 bus <multibus>
channel 2 bus <multibus>
PCI: Probing PCI hardware
PCI: Cannot allocate resource region 0 of device 0001:10:18.0
PCI: Cannot allocate resource region 0 of device 0001:10:19.0
Apple USB OHCI 0001:10:18.0 disabled by firmware
Apple USB OHCI 0001:10:19.0 disabled by firmware
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Unpacking initramfs... done
Freeing initrd memory: 2627k freed
Thermal assist unit not available
audit: initializing netlink socket (disabled)
audit(1188436210.328:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
PCI: Enabling device 0000:00:10.0 (0006 -> 0007)
radeonfb (0000:00:10.0): Invalid ROM signature 0 should be 0xaa55
radeonfb: Retrieved PLL infos from Open Firmware
radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=190.00 Mhz, System=250.00 MHz
radeonfb: PLL min 12000 max 35000
i2c-adapter i2c-2: unable to read EDID block.
i2c-adapter i2c-2: unable to read EDID block.
i2c-adapter i2c-2: unable to read EDID block.
radeonfb: Monitor 1 type CRT found
radeonfb: EDID probed
radeonfb: Monitor 2 type CRT found
radeonfb: EDID probed
Console: switching to colour frame buffer device 160x64
radeonfb (0000:00:10.0): ATI Radeon Yb
Generic RTC Driver v1.07
Macintosh non-volatile memory driver v1.1
pmac_zilog: 0.6 (Benjamin Herrenschmidt <benh(a)kernel.crashing.org>)
ttyS0 at MMIO 0x80013020 (irq = 22) is a Z85c30 ESCC - Serial port
ttyS1 at MMIO 0x80013000 (irq = 23) is a Z85c30 ESCC - Serial port
Serial: MPC52xx PSC UART driver
MacIO PCI driver attached to Intrepid chipset
input: Macintosh mouse button emulation as /class/input/input0
apm_emu: PMU APM Emulation initialized.
adb: starting probe task...
adb: finished probe task...
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PCI: Enabling device 0002:20:0d.0 (0000 -> 0002)
ide0: Found Apple UniNorth ATA-6 controller, bus ID 3, irq 39
Probing IDE interface ide0...
hda: ST9808210A, ATA DISK drive
hdb: MATSHITACD-RW CW-8124, ATAPI CD/DVD-ROM drive
hda: Enabling Ultra DMA 5
hdb: Enabling Ultra DMA 2
ide0 at 0xf1022000-0xf1022007,0xf1022160 on irq 39
ide1: Found Apple KeyLargo ATA-3 controller, bus ID 0, irq 24
Probing IDE interface ide1...
Probing IDE interface ide1...
hda: max request size: 512KiB
hda: 156301488 sectors (80026 MB) w/8192KiB Cache, CHS=16383/255/63, UDMA(100)
hda: cache flushes supported
hda: [mac] hda1 hda2 hda3 hda4 hda5
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
Apple USB OHCI 0001:10:18.0 disabled by firmware
Apple USB OHCI 0001:10:19.0 disabled by firmware
PCI: Enabling device 0001:10:1a.0 (0000 -> 0002)
ohci_hcd 0001:10:1a.0: OHCI Host Controller
ohci_hcd 0001:10:1a.0: new USB bus registered, assigned bus number 1
ohci_hcd 0001:10:1a.0: irq 29, io mem 0x80083000
usb usb1: new device found, idVendor=0000, idProduct=0000
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.22.5-4-default ohci_hcd
usb usb1: SerialNumber: 0001:10:1a.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Enabling device 0001:10:1b.0 (0000 -> 0002)
ohci_hcd 0001:10:1b.0: OHCI Host Controller
ohci_hcd 0001:10:1b.0: new USB bus registered, assigned bus number 2
ohci_hcd 0001:10:1b.0: irq 63, io mem 0x80082000
usb usb2: new device found, idVendor=0000, idProduct=0000
usb usb2: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.22.5-4-default ohci_hcd
usb usb2: SerialNumber: 0001:10:1b.0
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
PCI: Enabling device 0001:10:1b.1 (0000 -> 0002)
ohci_hcd 0001:10:1b.1: OHCI Host Controller
ohci_hcd 0001:10:1b.1: new USB bus registered, assigned bus number 3
ohci_hcd 0001:10:1b.1: irq 63, io mem 0x80081000
usb usb3: new device found, idVendor=0000, idProduct=0000
usb usb3: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb3: Product: OHCI Host Controller
usb usb3: Manufacturer: Linux 2.6.22.5-4-default ohci_hcd
usb usb3: SerialNumber: 0001:10:1b.1
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
usb 1-1: new full speed USB device using ohci_hcd and address 2
mice: PS/2 mouse device common for all mice
PowerMac i2c bus pmu 2 registered
PowerMac i2c bus pmu 1 registered
PowerMac i2c bus mac-io 0 registered
PowerMac i2c bus uni-n 1 registered
PowerMac i2c bus uni-n 0 registered
usb 1-1: new device found, idVendor=05ac, idProduct=1000
usb 1-1: new device strings: Mfr=0, Product=0, SerialNumber=0
usb 1-1: configuration #1 chosen from 1 choice
usbcore: registered new interface driver hiddev
input: HID 05ac:1000 as /class/input/input1
input: USB HID v1.11 Keyboard [HID 05ac:1000] on usb-0001:10:1a.0-1
input: HID 05ac:1000 as /class/input/input2
input: USB HID v1.11 Mouse [HID 05ac:1000] on usb-0001:10:1a.0-1
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
NET: Registered protocol family 1
NET: Registered protocol family 17
input: PMU as /class/input/input3
Freeing unused kernel memory: 208k init
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel(a)redhat.com
PCI: Enabling device 0001:10:1b.2 (0004 -> 0006)
ehci_hcd 0001:10:1b.2: EHCI Host Controller
ehci_hcd 0001:10:1b.2: new USB bus registered, assigned bus number 4
ehci_hcd 0001:10:1b.2: irq 63, io mem 0x80080000
ehci_hcd 0001:10:1b.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb4: new device found, idVendor=0000, idProduct=0000
usb usb4: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb4: Product: EHCI Host Controller
usb usb4: Manufacturer: Linux 2.6.22.5-4-default ehci_hcd
usb usb4: SerialNumber: 0001:10:1b.2
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 5 ports detected
md: linear personality registered for level -1
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
JBD: barrier-based sync failed on dm-2 - disabling barriers
ieee80211_crypt: registered algorithm 'NULL'
sungem.c:v0.98 8/24/03 David S. Miller (davem(a)redhat.com)
hdb: ATAPI 24X DVD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
PHY ID: 4061e4, addr: 0
eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:14:51:00:d8:38
eth0: Found BCM5221 PHY
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno(a)linux.intel.com>
Linux agpgart interface v0.102 (c) Dave Jones
agpgart: Detected Apple UniNorth 2 chipset
agpgart: configuring for size idx: 8
agpgart: AGP aperture is 32M @ 0x0
PCI: Enabling device 0002:20:0e.0 (0000 -> 0002)
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[40]
MMIO=[f5000000-f50007ff] Max Packet=[2048] IR/IT contexts=[8/8]
bcm43xx driver
PCI: Enabling device 0001:10:12.0 (0004 -> 0006)
bcm43xx: Chip ID 0x4306, rev 0x3
bcm43xx: Number of cores: 5
bcm43xx: Core 0: ID 0x800, rev 0x4, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0x5, vendor 0x4243
bcm43xx: Core 2: ID 0x80d, rev 0x2, vendor 0x4243
bcm43xx: Core 3: ID 0x807, rev 0x2, vendor 0x4243
bcm43xx: Core 4: ID 0x804, rev 0x9, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Analog: 2, Type 2, Revision 2
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
eth0 renamed to eth0_rename
eth1 renamed to eth0
udev: renamed network interface eth1 to eth0
eth0_rename renamed to eth1
udev: renamed network interface eth0_rename to eth1
snd-aoa-fabric-layout: found bus with layout 58
snd-aoa-fabric-layout: Using direct GPIOs
snd-aoa-fabric-layout: can use this codec
Adding 2104504k swap on /dev/hda4. Priority:-1 extents:1 across:2104504k
JBD: barrier-based sync failed on dm-2 - disabling barriers
ieee1394: Host added: ID:BUS[0-00:1023] GUID[001451fffe00d838]
JBD: barrier-based sync failed on dm-2 - disabling barriers
eth1: Link is up at 100 Mbps, full-duplex.
loop: module loaded
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-0, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
fuse init (API version 7.8)
AppArmor: AppArmor initialized
audit(1188436228.874:2): info="AppArmor initialized" pid=1602
JBD: barrier-based sync failed on dm-4 - disabling barriers
JBD: barrier-based sync failed on dm-3 - disabling barriers
eth1: Link is up at 100 Mbps, full-duplex.
eth1: Pause is disabled
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
Mobile IPv6
ip6_tables: (C) 2000-2006 Netfilter Core Team
ip_tables: (C) 2000-2006 Netfilter Core Team
audit(1188436241.978:3): audit_pid=2536 old=0 by auid=4294967295
eth1: no IPv6 routers present
JBD: barrier-based sync failed on dm-0 - disabling barriers
JBD: barrier-based sync failed on dm-1 - disabling barriers
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
Hello!
Recently I was made aware of the fact that Ingo Molnar released a patch
which brings CFS to earlier kernel versions including 2.6.22. Since
anecdotal evidence strongly suggests that the new scheduler performs
better for various desktop related workloads I would like to ask if it
is still possible to merge this patch with the current 10.3 kernel.
Since stability is probably a concern of the kernel release team I'd
like to mention that I've read reports that no severe issues have arisen
with CFS for several months now.
Link to patches:
http://people.redhat.com/mingo/cfs-scheduler/
With best regards,
Erunno
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
I have been encountering some intermittent lockups while running recent
2.6.22.3-*-default kernels on a HP dv6400 laptop (Turion64 X2 TL-56
processor) These kernels where sync'd out on factory some time after Friday
(17 Aug) (I recall a 2.6.22.3-2 and currently the kernel-default-2.6.22.3-5)
I did not have this problem with the previous -default kernels from Factory.
I am now running a kernel-vanilla-2.6.22.3-20070818105014
(from /pub/projects/kotd/HEAD) without encountering any lockups.
# rpm -q kernel-vanilla --changelog | head -3
* Sat Aug 18 2007 - trenn(a)suse.de
- patches.arch/acpi_autoloading_ia64_hp_fix.patch: Use
acpi_device_id for IA64 HP driver, otherwise those fail to boot.
I have tried "nmi_watchdog=2 crashkernel=..." to try get a dump that will shed
some light on the issue but no luck. I have noticed some boot issues
stemming from boot.clock so added a file /etc/modprobe.d/rtc which contains:
blacklist rtc_cmos
blacklist rtc_core
blacklist rtc_lib
Even with the above blacklisted, the system still has intermittent lockups
with the -default kernel, some times shortly after I get logged in. Other
times it will take over an hour before a lockup occurs.
Any tips or suggestions?
# rpm -q kernel-default-2.6.22.3-5 --changelog | head -3
* Fri Aug 17 2007 - teheo(a)suse.de
- patches.drivers/scsi-throttle-SG_DXFER_TO_FROM_DEV-warning-better:
SCSI: throttle SG_DXFER_TO_FROM_DEV warning message better
# rpm -q kernel-vanilla-2.6.22.3-20070818105014 --changelog | head -7
* Sat Aug 18 2007 - trenn(a)suse.de
- patches.arch/acpi_autoloading_ia64_hp_fix.patch: Use
acpi_device_id for IA64 HP driver, otherwise those fail to boot.
* Fri Aug 17 2007 - teheo(a)suse.de
- patches.drivers/scsi-throttle-SG_DXFER_TO_FROM_DEV-warning-better:
SCSI: throttle SG_DXFER_TO_FROM_DEV warning message better
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
Hi,
I am currently running 2.6.22.3-ccj53-rt@i586 (bs's 2.6.22.3-16.1 plus
my patches), and I must say, that runs great. The last rt I tried
(2.6.12,13? no idea..) gave me traces all over, but this one is good.
NO_HZ and HZ=1000 at the same time. About 133 pmtmr interrupts when
idle, about 200 when playing audio, and up to 1200 (yes, it is actually
more than 1000) when something is burning cycles.
Now there are some minor issues. First is that kernel-source is of
course against the regular patch series, not rt; as a result,
kernel-syms does not include rt configs either; overall I would not know
how to build KMPs for the rt flavor right now. If you have some ideas,
let me know. If it is not possible, that's ok, but hardly useful for the
end-user when he's stuck without X :p
Another hard problem I see if that XFS does not support the usrquota
option under rt ("unknown mount option"). What gives?
thanks,
Jan
--
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
On Sat, 2007-08-18 at 22:17 +0200, Bernhard Walle wrote:
> * Suresh Jayaraman <sjayaraman(a)novell.com> [2007-08-10 12:11]:
> > i386 machine, I am getting the following error:
> >
> > "arch/i386/kernel/entry.S:598: Error: CFI instruction used without
> > previous .cfi_startproc"
> >
> > Binutils version - 2.17.50.0.5
>
> Try following patch:
>
The patch fixed the compilation error. Thanks!
--
Suresh Jayaraman
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
When kdb support is enabled in openSUSE 10.2 kernel (2.6.18.2-34) on a
i386 machine, I am getting the following error:
"arch/i386/kernel/entry.S:598: Error: CFI instruction used without
previous .cfi_startproc"
Binutils version - 2.17.50.0.5
Guess it's a known issue but couldn't find any relevent bugs/patches in
openSUSE bugzilla. Is it a know issue? Where can I find the fix?
Thanks,
--
Suresh Jayaraman
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
I tried running the openSUSE 10.3b1 installer (using the GNOME x86
CD), and ran across a problem with detected disk geometry on a
Thinkpad T41p, with no other OS installed.
I have had problems in the past with openSUSE 10.2: fdisk detects a
C/H/S geometry of 9729/255/63, while the kernel itself would detect a
much higher C value, with H=16. On my first install things worked fine
for a while, until the system locked up during use a few days
afterwards (running the latest kernel), which is probably due to the
kernel accessing the disk (and writing to it) using the wrong
geometry.
On 10.2 I can just pass 'hda=9729,255,63' to force the kernel to use
the same geometry used to partition the disk.
On 10.3, I tried passing 'sda=9729,255,63' but to no avail; YaST would
warn that parted could not access the disk and thus I could not touch
the partition table, and dropping to a console and checking with fdisk
shows that only 9300-something cylinders are detected.
Has something changed in the kernel between 2.6.18 and 2.6.22 that
causes even fdisk/parted to see a different geometry? How can I
override this at boot time?
Out of curiosity, I've seen claims that keeping a Windows partition on
disk would force parted etc. to use the disk geometry that Windows
sees, so a consistent geometry is always used. Any truth to that?
Many thanks,
--
Michel
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org
Playing with powertop, I got the following suggestion:
Suggestion: Enable the CONFIG_USB_SUSPEND kernel configuration option.
This option will automatically disable UHCI USB when not in use, and may
save approximately 1 Watt of power.
Is this something we should do in our kernel? Or what is the risk for
this? Will it break automatic access to hot-pluggable devices?
Andreas
--
Andreas Jaeger, Director Platform/openSUSE, aj(a)suse.de
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Hallo,
Should we add the dwarf2 unwinder or not for 10.3?
Kernel oopses use approximate backtracing and also
report old left over garbage on the stack. In some
cases this can make oopses very hard to read.
Jan Beulich ported the NLKD dwarf2 unwinder to the kernel
to solve this problem.
It was merged to mainline, but due to some early teething
problems Linus drew it out. In the end it was relatively
stable though.
I'm wondering if we should add it to the opensuse 10.3
kernel anyways.
Advantages
- Better backtraces for kernel oopses. Saves developer
time which is very valuable.
- Would help testing it further
Disadvantages:
- Might still have bugs
(but in this case we fall back and should not lose any information)
- Increases kernel binary size in memory by ~10% for the unwind
information.
Opinions?
-Andi
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kernel+help(a)opensuse.org