Re: 2.6.25-rc2 + smartd = hang
> [EMAIL PROTECTED] said: > > Could you try bisecting it down to the guilty commit using git-bisect? > > [ the "old" stuff got few hundred commits in 2.6.25 ] > > Thanks, Bart Ok, I got this: 852738f39258deafb3d89c187cb1a4050820d555 is first bad commit commit 852738f39258deafb3d89c187cb1a4050820d555 Author: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> Date: Sat Jan 26 20:13:12 2008 +0100 ide: convert "empty" REQ_TYPE_ATA_CMD requests to use REQ_TYPE_ATA_TASKFILE Based on the previous work by Tejun Heo. There should be no functionality changes caused by this patch. Cc: Tejun Heo <[EMAIL PROTECTED]> Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> :04 04 e65605824ccc1c8bda2ab6f917b5457d36c5537e 5fb514a261b13494c5e9c035f9e7598276ce8839 M drivers I'll run with the last known good version for a while,so if there's any more testing needed let me know. /A -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: Could you try bisecting it down to the guilty commit using git-bisect? [ the old stuff got few hundred commits in 2.6.25 ] Thanks, Bart Ok, I got this: 852738f39258deafb3d89c187cb1a4050820d555 is first bad commit commit 852738f39258deafb3d89c187cb1a4050820d555 Author: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] Date: Sat Jan 26 20:13:12 2008 +0100 ide: convert empty REQ_TYPE_ATA_CMD requests to use REQ_TYPE_ATA_TASKFILE Based on the previous work by Tejun Heo. There should be no functionality changes caused by this patch. Cc: Tejun Heo [EMAIL PROTECTED] Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] :04 04 e65605824ccc1c8bda2ab6f917b5457d36c5537e 5fb514a261b13494c5e9c035f9e7598276ce8839 M drivers I'll run with the last known good version for a while,so if there's any more testing needed let me know. /A -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: > Could you try bisecting it down to the guilty commit using git-bisect? > [ the "old" stuff got few hundred commits in 2.6.25 ] > Thanks, Bart Will do. It'll take a while though. Not a fast machine and used by the household... /A -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: Could you try bisecting it down to the guilty commit using git-bisect? [ the old stuff got few hundred commits in 2.6.25 ] Thanks, Bart Will do. It'll take a while though. Not a fast machine and used by the household... /A -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: >> But at this point libata is working much better than the old IDE stuff, and >> it really is worth moving things over if you can. > > Ok, I'll take a stab at that tomorrow. Two things... Having switched to ata_piix i can confirm that smartd doesn't hand the system anymore. Still.. There seem to be a bug vs. the old drivers somewhere. Will that be addressed, or should there be a big warning for the old stuff (DEPRECATED?) /A -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: > the comment on the very top of drivers/ata says: > tristate "Serial ATA (prod) and Parallel ATA (experimental) drivers" That's the one I was referring to. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: But at this point libata is working much better than the old IDE stuff, and it really is worth moving things over if you can. Ok, I'll take a stab at that tomorrow. Two things... Having switched to ata_piix i can confirm that smartd doesn't hand the system anymore. Still.. There seem to be a bug vs. the old drivers somewhere. Will that be addressed, or should there be a big warning for the old stuff (DEPRECATED?) /A -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: the comment on the very top of drivers/ata says: tristate Serial ATA (prod) and Parallel ATA (experimental) drivers That's the one I was referring to. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: > So that's using the old IDE drivers. And the network and USB are sharing > IRQ#11 with each other. > If you are going to be using newer kernels like this (2.6.23+), then you > might consider shifting those drives over to libata drivers. > This involves a little bit of work -- building a kernel with libata and > "ata_piix" built-in instead of the old IDE drivers, and then rearranging /etc/ > fstab to match the new device names (eg. /dev/sda instead of /dev/hda). > But at this point libata is working much better than the old IDE stuff, and > it really is worth moving things over if you can. Ok, I'll take a stab at that tomorrow. Two things... Is smartd prepared to handle /dev/sdX style devices? If this is the prefered driver these days, maybe it shouldn't be marked experimental in the menu anymore? /A -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: > The sysrq-e output is probably just standard ext3 journalling unrelated to > the problem... what does dmesg say? lspci? What's your hardware setup? dmesg ; smartd ; dmesg yields no new entries in dmesg. It seems on disk accesses are dead. it still routes packets fine. This is an old PII-300 with 2 IDS disks and a DVD R/W. tippex ~ # lspci -vv 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 02) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: agpgart-intel Kernel modules: intel-agp 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- 2.6.24.2 dmesg: Feb 22 00:09:18 tippex Linux version 2.6.24.2 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2)) #9 PREEMPT Thu Feb 21 16:08:47 CET 2008 Feb 22 00:09:18 tippex BIOS-provided physical RAM map: Feb 22 00:09:18 tippex BIOS-e820: - 0009f800 (usable) Feb 22 00:09:18 tippex BIOS-e820: 0009f800 - 000a (reserved) Feb 22 00:09:18 tippex BIOS-e820: 000f - 0010 (reserved) Feb 22 00:09:18 tippex BIOS-e820: 0010 - 1400 (usable) Feb 22 00:09:18 tippex BIOS-e820: - 0001 (reserved) Feb 22 00:09:18 tippex 320MB LOWMEM available. Feb 22 00:09:18 tippex Entering add_active_range(0, 0, 81920) 0 entries of 256 used Feb 22 00:09:18 tippex Zone PFN ranges: Feb 22 00:09:18 tippex DMA 0 -> 4096 Feb 22 00:09:18 tippex Normal 4096 ->81920 Feb 22 00:09:18 tippex Movable zone start PFN for each node Feb 22 00:09:18 tippex early_node_map[1] active PFN ranges Feb 22 00:09:18 tippex 0:0 ->81920 Feb 22 00:09:18 tippex On node 0 totalpages: 81920 Feb 22 00:09:18 tippex DMA zone: 32 pages used for memmap Feb 22 00:09:18 tippex DMA zone: 0 pages reserved Feb 22 00:09:18 tippex DMA zone: 4064 pages, LIFO batch:0 Feb 22 00:09:18 tippex Normal zone: 608 pages used for memmap Feb 22 00:09:18 tippex Normal zone: 77216 pages, LIFO batch:15 Feb 22 00:09:18 tippex Movable zone: 0 pages used for memmap Feb 22 00:09:18 tippex DMI 2.1 present. Feb 22 00:09:18 tippex Allocating PCI resources starting at 2000 (gap: 1400:ebff) Feb 22 00:09:18 tippex Built 1 zonelists in Zone order, mobility grouping on. Total pages: 81280 Feb 22 00:09:18 tippex Kernel command line: ro pci=usepirqmask root=/dev/hdb1 Feb 22 00:09:18 tippex Local APIC disabled by BIOS -- you can enable it with "lapic" Feb 22 00:09:18 tippex mapped APIC to b000 (01286000) Feb 22 00:09:18 tippex Initializing CPU#0 Feb 22 00:09:18 tippex PID hash table entries: 2048 (order: 11, 8192 bytes) Feb 22 00:09:18 tippex Detected 300.694 MHz processor. Feb 22 00:09:18 tippex Console: colour VGA+ 80x25 Feb 22 00:09:18 tippex console [tty0] enabled Feb 22 00:09:18 tippex Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar Feb 22 00:09:18 tippex ... MAX_LOCKDEP_SUBCLASSES:8 Feb 22 00:09:18 tippex ... MAX_LOCK_DEPTH: 30 Feb 22 00:09:18 tippex ... MAX_LOCKDEP_KEYS:2048 Feb 22 00:09:18 tippex ... CLASSHASH_SIZE: 1024 Feb 22 00:09:18 tippex ... MAX_LOCKDEP_ENTRIES: 8192 Feb 22 00:09:18 tippex ... MAX_LOCKDEP_CHAINS: 16384 Feb 22 00:09:18 tippex ... CHAINHASH_SIZE: 8192 Feb 22 00:09:18 tippex memory used by lock dependency info: 1024 kB Feb 22 00:09:18 tippex per task-struct memory footprint: 1680 bytes Feb 22 00:09:18 tippex Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Feb 22 00:09:18 tippex Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Feb 22 00:09:18 tippex Memory: 317364k/327680k available (3055k kernel code, 9844k reserved, 1265k data, 188k init, 0k highmem) Feb 22 00:09:18 tippex virtual kernel memory layout: Feb 22 00:09:18 tippex fixmap : 0xfffba000 - 0xf000 ( 276 kB) Feb 22 00:09:18 tippex vmalloc : 0xd480 - 0xfffb8000 ( 695 MB) Feb 22 00:09:18 tippex lowmem : 0xc000 - 0xd400 ( 320 MB) Feb 22 00:09:18 tippex .init : 0xc053c000 - 0xc056b000 ( 188 kB) Feb 22 00:09:18 tippex .data : 0xc03fbccc
2.6.25-rc2 + smartd = hang
Hi, Trying out 2.6.25-rc2 smartd always causes my box to hang. I can switch vt:s and the keyboard seems to work. Using sysrq-e I noticed a callpath open -> ext3 -> journals -> sync_buffer -> io_scheduel -> generic_unplig_device. I'd guess the open stems from smartd. Removing smartd from the startup, I'm now using rc2 fine... I got a nice jpg showing it as well. Known issue? /A -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: lockdep warning
[EMAIL PROTECTED] said: > > Any chance that > > git revert 69cc64d8d92 > > makes this report go away? I've tested the patch and I no longer get that lock thing in my syslog. /A -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: lockdep warning
[EMAIL PROTECTED] said: > This needs to be CCed to netdev. > Any chance that > git revert 69cc64d8d92 > makes this report go away? I'll have to install a git repo to check, or maybe you can send me the diff to reverse vs. 2.6.25-rc2? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
lockdep warning
I found this is a newly booted 2.6.25-rc2's syslog. Feb 21 20:46:33 tippex BUG: rwlock wrong owner on CPU#0, runscript.sh/2633, d2c04084 Feb 21 20:46:33 tippex Pid: 2633, comm: runscript.sh Not tainted 2.6.25-rc2 #3 Feb 21 20:46:33 tippex [] rwlock_bug+0x50/0x60 Feb 21 20:46:33 tippex [] _raw_write_unlock+0x56/0x60 Feb 21 20:46:33 tippex [] _write_unlock+0x1d/0x50 Feb 21 20:46:33 tippex [] neigh_timer_handler+0x18e/0x2d0 Feb 21 20:46:33 tippex [] run_timer_softirq+0x119/0x180 Feb 21 20:46:33 tippex [] ? lock_release_holdtime+0x5d/0x80 Feb 21 20:46:33 tippex [] ? neigh_timer_handler+0x0/0x2d0 Feb 21 20:46:33 tippex [] __do_softirq+0x54/0xb0 Feb 21 20:46:33 tippex [] do_softirq+0x35/0x40 Feb 21 20:46:33 tippex [] irq_exit+0x44/0x50 Feb 21 20:46:33 tippex [] do_IRQ+0x47/0x80 Feb 21 20:46:33 tippex [] common_interrupt+0x23/0x28 Feb 21 20:46:33 tippex === It doesn't make any sens to me but I guess it does to others. The other bad thing is that the machine hangs shortly after boot bitching about 'hdb: lost interrupt' on the console. Kown problem? /A -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
lockdep warning
I found this is a newly booted 2.6.25-rc2's syslog. Feb 21 20:46:33 tippex BUG: rwlock wrong owner on CPU#0, runscript.sh/2633, d2c04084 Feb 21 20:46:33 tippex Pid: 2633, comm: runscript.sh Not tainted 2.6.25-rc2 #3 Feb 21 20:46:33 tippex [c02342d0] rwlock_bug+0x50/0x60 Feb 21 20:46:33 tippex [c0234356] _raw_write_unlock+0x56/0x60 Feb 21 20:46:33 tippex [c040365d] _write_unlock+0x1d/0x50 Feb 21 20:46:33 tippex [c03289be] neigh_timer_handler+0x18e/0x2d0 Feb 21 20:46:33 tippex [c0125449] run_timer_softirq+0x119/0x180 Feb 21 20:46:33 tippex [c013856d] ? lock_release_holdtime+0x5d/0x80 Feb 21 20:46:33 tippex [c0328830] ? neigh_timer_handler+0x0/0x2d0 Feb 21 20:46:33 tippex [c0121a64] __do_softirq+0x54/0xb0 Feb 21 20:46:33 tippex [c0121af5] do_softirq+0x35/0x40 Feb 21 20:46:33 tippex [c0121cb4] irq_exit+0x44/0x50 Feb 21 20:46:33 tippex [c0105757] do_IRQ+0x47/0x80 Feb 21 20:46:33 tippex [c01039c3] common_interrupt+0x23/0x28 Feb 21 20:46:33 tippex === It doesn't make any sens to me but I guess it does to others. The other bad thing is that the machine hangs shortly after boot bitching about 'hdb: lost interrupt' on the console. Kown problem? /A -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: lockdep warning
[EMAIL PROTECTED] said: This needs to be CCed to netdev. Any chance that git revert 69cc64d8d92 makes this report go away? I'll have to install a git repo to check, or maybe you can send me the diff to reverse vs. 2.6.25-rc2? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: lockdep warning
[EMAIL PROTECTED] said: Any chance that git revert 69cc64d8d92 makes this report go away? I've tested the patch and I no longer get that lock thing in my syslog. /A -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
2.6.25-rc2 + smartd = hang
Hi, Trying out 2.6.25-rc2 smartd always causes my box to hang. I can switch vt:s and the keyboard seems to work. Using sysrq-e I noticed a callpath open - ext3 - journals - sync_buffer - io_scheduel - generic_unplig_device. I'd guess the open stems from smartd. Removing smartd from the startup, I'm now using rc2 fine... I got a nice jpg showing it as well. Known issue? /A -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: The sysrq-e output is probably just standard ext3 journalling unrelated to the problem... what does dmesg say? lspci? What's your hardware setup? dmesg ; smartd ; dmesg yields no new entries in dmesg. It seems on disk accesses are dead. it still routes packets fine. This is an old PII-300 with 2 IDS disks and a DVD R/W. tippex ~ # lspci -vv 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 02) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 64 Region 0: Memory at e800 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 1.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none Kernel driver in use: agpgart-intel Kernel modules: intel-agp 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64 I/O behind bridge: c000-cfff Memory behind bridge: eda0-efaf Prefetchable memory behind bridge: e180-e58f Secondary status: 66MHz+ FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B+ PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- 00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) (prog-if 80 [Master]) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 Region 0: [virtual] Memory at 01f0 (32-bit, non-prefetchable) [disabled] [size=8] Region 1: [virtual] Memory at 03f0 (type 3, non-prefetchable) [disabled] [size=1] Region 2: [virtual] Memory at 0170 (32-bit, non-prefetchable) [disabled] [size=8] Region 3: [virtual] Memory at 0370 (type 3, non-prefetchable) [disabled] [size=1] Region 4: I/O ports at ffa0 [size=16] Kernel driver in use: PIIX_IDE 00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01) (prog-if 00 [UHCI]) Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64 Interrupt: pin D routed to IRQ 11 Region 4: I/O ports at 6000 [size=32] Kernel driver in use: uhci_hcd Kernel modules: uhci-hcd 00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin ? routed to IRQ 9 Kernel driver in use: piix4_smbus Kernel modules: i2c-piix4 00:0a.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) Subsystem: RaLink Unknown device 2560 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 64, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 10 Region 0: Memory at efffe000 (32-bit, non-prefetchable) [size=8K] Capabilities: [40] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: rt2500pci Kernel modules: rt2500pci 00:0b.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100] (rev 05) Subsystem: Intel Corporation 82558B PRO/100+ PCI (TP) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF-
Re: 2.6.25-rc2 + smartd = hang
[EMAIL PROTECTED] said: So that's using the old IDE drivers. And the network and USB are sharing IRQ#11 with each other. If you are going to be using newer kernels like this (2.6.23+), then you might consider shifting those drives over to libata drivers. This involves a little bit of work -- building a kernel with libata and ata_piix built-in instead of the old IDE drivers, and then rearranging /etc/ fstab to match the new device names (eg. /dev/sda instead of /dev/hda). But at this point libata is working much better than the old IDE stuff, and it really is worth moving things over if you can. Ok, I'll take a stab at that tomorrow. Two things... Is smartd prepared to handle /dev/sdX style devices? If this is the prefered driver these days, maybe it shouldn't be marked experimental in the menu anymore? /A -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
sync & asyck i/o
According to the man page for fsync it copies in-core data to disk prior to its return. Does that take async i/o to the media in account? I.e. does it wait for completion of the async i/o to the disk? /Anders PGP signature
sync asyck i/o
According to the man page for fsync it copies in-core data to disk prior to its return. Does that take async i/o to the media in account? I.e. does it wait for completion of the async i/o to the disk? /Anders PGP signature
romfs as initrd
Running 2.4.0-test10 I try to get an romfs image to work as an initrd
image. It does work when mount `normally` using `mount -o loop`.
However, when used as initrd image it fails. Here's the relevant part
of dmesg:
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: enabling 64 loop devices
RAMDISK: romfs filesystem found at block 0
RAMDISK: Loading 3183 blocks [1 disk]
into ram disk... done.Freeing initrd
memory: 3184k freed
...
devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x0
Trying fs: ext2
Trying fs: cramfs
wrong magic
Trying fs: romfs
ROMFS DEBUG: rsb_word0 0 rsb_word1 0 sz 0
Kernel panic: VFS: Unable to mount root fs on 01:00
Where the ROMFS DEBUG message comes for this section of romfs/inode.c:
if (rsb->word0 != ROMSB_WORD0 || rsb->word1 != ROMSB_WORD1
|| sz < ROMFH_SIZE) {
if (!silent)
printk ("VFS: Can't find a romfs filesystem on
dev "
"%s.\n", kdevname(dev));
printk ("ROMFS DEBUG: rsb_word0 %i rsb_word1 %i sz
%i\n",rsb->word0,rsb->word1,sz);
goto out;
Not knowing that much about fs (and VFS) internals it seems that the
image is identified by the initrd code, but currupted/misplaced so it
cannot be used by the VFS when trying to mount it. I have no ideas what
steps are supposed to happen in between these two.
Help and insights appreciated.
/Anders
PGP signature
romfs as initrd
Running 2.4.0-test10 I try to get an romfs image to work as an initrd
image. It does work when mount `normally` using `mount -o loop`.
However, when used as initrd image it fails. Here's the relevant part
of dmesg:
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: enabling 64 loop devices
RAMDISK: romfs filesystem found at block 0
RAMDISK: Loading 3183 blocks [1 disk]
into ram disk... done.Freeing initrd
memory: 3184k freed
...
devfs: v0.102 (2622) Richard Gooch ([EMAIL PROTECTED])
devfs: boot_options: 0x0
Trying fs: ext2
Trying fs: cramfs
wrong magic
Trying fs: romfs
ROMFS DEBUG: rsb_word0 0 rsb_word1 0 sz 0
Kernel panic: VFS: Unable to mount root fs on 01:00
Where the ROMFS DEBUG message comes for this section of romfs/inode.c:
if (rsb-word0 != ROMSB_WORD0 || rsb-word1 != ROMSB_WORD1
|| sz ROMFH_SIZE) {
if (!silent)
printk ("VFS: Can't find a romfs filesystem on
dev "
"%s.\n", kdevname(dev));
printk ("ROMFS DEBUG: rsb_word0 %i rsb_word1 %i sz
%i\n",rsb-word0,rsb-word1,sz);
goto out;
Not knowing that much about fs (and VFS) internals it seems that the
image is identified by the initrd code, but currupted/misplaced so it
cannot be used by the VFS when trying to mount it. I have no ideas what
steps are supposed to happen in between these two.
Help and insights appreciated.
/Anders
PGP signature
RE: [PATCH] swap= kernel commandline
>= Original Message From [EMAIL PROTECTED] (Eric W. Biederman) = >Werner Almesberger <[EMAIL PROTECTED]> writes: > >> Eric W. Biederman wrote: >> > I have one that loads a second kernel over the network using dhcp >> > to configure it's interface and tftp to fetch the image and boots >> > that is only 20kb uncompressed >> >> Neat ;-) My goal is actually not only size, but also to have a relatively >> normal build environment, e.g. my example is with shared newlib, regular >> ash, and - unfortunately rather wasteful - glibc's ld.so. >> >> But a tftp loader in 20kB is rather good. Now the next challenge is the >> same thing with NFS. Then we can finally kill nfsroot ;-) > >Hmm. What does it take to mount an NFS partition? > >Anyway. All I did was wrote a tiny libc that is just a bunch of >wrappers for syscalls, and some string functions. Then I just wrote >a straight forward C program to do the job. Except for my added >kexec call I can compile with glibc :) > >Now if glibc wouldn't link in 200k of unused crap when you make a >trivial static binary I'd much prefer to use it... > >Though I wish it was possible to have a ramfs preloader instead of >initrd. An initramfs would allow me to not even compile in the block >device driver layer, and be more efficient. > A discussion on l-k two months ago revealed that someone actually had made a patch that took a tarball (masquaraded as an initrd image) and unpacked it into a ramfs. I've got the mail samewhere if you want it. /Anders - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
RE: [PATCH] swap=device kernel commandline
= Original Message From [EMAIL PROTECTED] (Eric W. Biederman) = Werner Almesberger [EMAIL PROTECTED] writes: Eric W. Biederman wrote: I have one that loads a second kernel over the network using dhcp to configure it's interface and tftp to fetch the image and boots that is only 20kb uncompressed Neat ;-) My goal is actually not only size, but also to have a relatively normal build environment, e.g. my example is with shared newlib, regular ash, and - unfortunately rather wasteful - glibc's ld.so. But a tftp loader in 20kB is rather good. Now the next challenge is the same thing with NFS. Then we can finally kill nfsroot ;-) Hmm. What does it take to mount an NFS partition? Anyway. All I did was wrote a tiny libc that is just a bunch of wrappers for syscalls, and some string functions. Then I just wrote a straight forward C program to do the job. Except for my added kexec call I can compile with glibc :) Now if glibc wouldn't link in 200k of unused crap when you make a trivial static binary I'd much prefer to use it... Though I wish it was possible to have a ramfs preloader instead of initrd. An initramfs would allow me to not even compile in the block device driver layer, and be more efficient. A discussion on l-k two months ago revealed that someone actually had made a patch that took a tarball (masquaraded as an initrd image) and unpacked it into a ramfs. I've got the mail samewhere if you want it. /Anders - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
/ on ramfs, possible?
I want my / to be a ramfs filesystem. I intend to populate it from an initrd image, and then remount / as the ramfs filesystem. Is that at all possible? The way I see it the kernel requires / on a device (major,minor) or nfs. Am I out of luck using ramfs as /? If it's easy to fix, how do I fix it? /Anders PGP signature
/ on ramfs, possible?
I want my / to be a ramfs filesystem. I intend to populate it from an initrd image, and then remount / as the ramfs filesystem. Is that at all possible? The way I see it the kernel requires / on a device (major,minor) or nfs. Am I out of luck using ramfs as /? If it's easy to fix, how do I fix it? /Anders PGP signature
Re: BUG: Kernel freezes after load
I tested this with no improvement. I really hopes this one gets solved before the release of 240. /Anders [EMAIL PROTECTED] said: > Can you grab and try the latest test patch, test9-pre7, from ftp:// > ftp.us.kernel.org/pub/linux/kernel/testing/ [EMAIL PROTECTED] said: > On two systems (Laptop and Pentium 60) I've Installed RedHat 6.2 > Compiled 2.4.0-test8 (make menuconfig _no changes_) installed (lilo) > On the P60 it freezes with after the message > "Uncompressing Linux Ok, booting the kernel" > The P60 is eisa based and dates back from 1993. I can send more info > on the machine tonight if needed. > /Anders PGP signature
BUG: Kernel freezes after load
On two systems (Laptop and Pentium 60) I've Installed RedHat 6.2 Compiled 2.4.0-test8 (make menuconfig _no changes_) installed (lilo) On the P60 it freezes with after the message "Uncompressing Linux Ok, booting the kernel" The P60 is eisa based and dates back from 1993. I can send more info on the machine tonight if needed. /Anders - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
BUG: Kernel freezes after load
On two systems (Laptop and Pentium 60) I've Installed RedHat 6.2 Compiled 2.4.0-test8 (make menuconfig _no changes_) installed (lilo) On the P60 it freezes with after the message "Uncompressing Linux Ok, booting the kernel" The P60 is eisa based and dates back from 1993. I can send more info on the machine tonight if needed. /Anders - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: BUG: Kernel freezes after load
I tested this with no improvement. I really hopes this one gets solved before the release of 240. /Anders [EMAIL PROTECTED] said: Can you grab and try the latest test patch, test9-pre7, from ftp:// ftp.us.kernel.org/pub/linux/kernel/testing/ [EMAIL PROTECTED] said: On two systems (Laptop and Pentium 60) I've Installed RedHat 6.2 Compiled 2.4.0-test8 (make menuconfig _no changes_) installed (lilo) On the P60 it freezes with after the message "Uncompressing Linux Ok, booting the kernel" The P60 is eisa based and dates back from 1993. I can send more info on the machine tonight if needed. /Anders PGP signature
