Re: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
* David Brownell [EMAIL PROTECTED] [080808 02:51]: On Thursday 07 August 2008, Tony Lindgren wrote: Two problems on the OSK5912: - cpufreq oopses on boot - continuous i2c overflow errors ISTR both of these bugs are in mainline too. I'd say the I2C regression is higher priority. Hmm, I wonder what has broken I2C? Seems fixed now; goof in earlier error handling patch. Anyways, let's fix these regressions before tagging. I've not yet looked at the cpufreq thing, but after applying the patch from Chandra Shekhar the I2C problem went away. OK However that still doesn't make OSK happy. It wedges sometime after freeing init memory ... timer interrupts are no longer happening, the LED stops flashing. The userspace has sometimes started the watchdog daemon, in which case a watchdog timeout fires and it reboots. Hmm could it be the dmtimer posted mode patch applied earlier? FWIW mainline fails *really* early, before showing any kernel messages at all. Bummer, too bad my osk is also connected to my non-responding remote power switch :( I'll tag v2.6.26-omap1 despite these issues, we can branch and do -omap2 when we have sorted these remaining issues out. Tony -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
* David Brownell [EMAIL PROTECTED] [080807 02:30]: On Tuesday 05 August 2008, Tony Lindgren wrote: Also please check that things work for your board, let's try to tag v2.6.26-omap1 within next few days so we can move on again. Two problems on the OSK5912: - cpufreq oopses on boot - continuous i2c overflow errors ISTR both of these bugs are in mainline too. I'd say the I2C regression is higher priority. Hmm, I wonder what has broken I2C? Anyways, let's fix these regressions before tagging. Tony - Dave CPUFREQ oopsing 5Linux version 2.6.26-omap1 ([EMAIL PROTECTED]) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-53)) #186 PREEMPT Wed Aug 6 16:12:29 PDT 2008 CPU: ARM926EJ-S [41069263] revision 3 (ARMv5TEJ), cr=00053177 Machine: TI-OSK Memory policy: ECC disabled, Data cache writeback 7On node 0 totalpages: 8192 7 DMA zone: 64 pages used for memmap 7 DMA zone: 0 pages reserved 7 DMA zone: 8128 pages, LIFO batch:0 7 Normal zone: 0 pages used for memmap 7 Movable zone: 0 pages used for memmap OMAP1611b revision 2 handled as 16xx id: 26058c80eb051c15 6SRAM: Mapped pa 0x2000 to va 0xd700 size: 0x10 CPU0: D VIVT write-back cache CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128 5Kernel command line: console=ttyS0,115200 mem=32M ip=dhcp root=/dev/nfs i2c_omap.clock=400 3Unknown boot option `i2c_omap.clock=400': ignoring Clocks: ARM_SYSST: 0x1000 DPLL_CTL: 0x2833 ARM_CKCTL: 0x2000 6Clocking rate (xtal/DPLL1/MPU): 12.0/192.0/192.0 MHz Total of 128 interrupts in 4 interrupt banks 6OMAP GPIO hardware version 1.0 4MUX: initialized M7_1610_GPIO62 PID hash table entries: 128 (order: 7, 512 bytes) Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES:8 ... MAX_LOCK_DEPTH: 48 ... MAX_LOCKDEP_KEYS:2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 16384 ... CHAINHASH_SIZE: 8192 memory used by lock dependency info: 992 kB per task-struct memory footprint: 1920 bytes 6Dentry cache hash table entries: 4096 (order: 2, 16384 bytes) 6Inode-cache hash table entries: 2048 (order: 1, 8192 bytes) 6Memory: 32MB = 32MB total 5Memory: 26936KB available (2476K code, 2919K data, 104K init) 6SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 7Calibrating delay loop... 94.82 BogoMIPS (lpj=474112) Mount-cache hash table entries: 512 6CPU: Testing write buffer coherency: ok 6net_namespace: 256 bytes 6NET: Registered protocol family 16 4MUX: initialized M19_1610_CAM_RSTZ 4MUX: initialized Y15_1610_CAM_OUTCLK 4MUX: initialized H19_1610_CAM_EXCLK 4MUX: initialized W13_1610_CCP_CLKM 4MUX: initialized Y12_1610_CCP_CLKP 4MUX: initialized W14_1610_CCP_DATAP 4MUX: initialized N20_1610_GPIO11 4MUX: initialized P20_1610_GPIO4 4MUX: initialized PWL 6OMAP DMA hardware version 1 6DMA capabilities: 000c::01ff:003f:007f 6omap_dsp_init() done 1Unable to handle kernel NULL pointer dereference at virtual address 1pgd = c0004000 1[] *pgd= Internal error: Oops: 5 [#1] PREEMPT Modules linked in: CPU: 0Not tainted (2.6.26-omap1 #186) PC is at wq_per_cpu+0xc/0x14 LR is at queue_delayed_work_on+0x90/0x124 pc : [c005068c]lr : [c00510f0]psr: 6013 sp : c1c21dbc ip : c1c21dcc fp : c1c21dc8 r10: 0292 r9 : 0001 r8 : r7 : r6 : c0561c20 r5 : r4 : c0561c04 r3 : 0001 r2 : r1 : r0 : Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel Control: 0005317f Table: 10004000 DAC: 0017 Process swapper (pid: 1, stack limit = 0xc1c20260) Stack: (0xc1c21dbc to 0xc1c22000) 1da0:c1c21df0 1dc0: c1c21dcc c00510f0 c0050690 c0561be0 0292 c02aa654 c0561be0 c1c38840 1de0: c1c21e1c c1c21df4 c0175358 c0051070 c1c38840 1e00: 0001 c001c818 c1c21e38 c1c21e20 c0172e00 c017514c 1e20: c1c21e5c c1c38840 c1c21e58 c1c21e3c c0173454 c0172d30 c02980f0 1e40: c1c38840 c0561ad0 c1c21f28 c1c21e5c c0174428 c0173348 0001 1e60: 0002ee00 5dc0 00989680 0002ee00 0002ee00 1e80: 0002ee00 c02aa654 c1c38874 c1c38874 c0173dd4 c0561bb0 1ea0: c02704f9 5dc0 0002ee00 1ec0: 1ee0: 0001 dead4ead c02d1f40 c02592d4 c1c388e0 1f00: c1c388e0 c02aa3d0 c02a7680 c02af8c0 c02af8c8 c1c21f54 1f20: c1c21f2c c0137920 c0174204 c1c04098 c02af8c0
Re: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
On Thursday 07 August 2008, Tony Lindgren wrote: Two problems on the OSK5912: - cpufreq oopses on boot - continuous i2c overflow errors ISTR both of these bugs are in mainline too. I'd say the I2C regression is higher priority. Hmm, I wonder what has broken I2C? Seems fixed now; goof in earlier error handling patch. Anyways, let's fix these regressions before tagging. I've not yet looked at the cpufreq thing, but after applying the patch from Chandra Shekhar the I2C problem went away. However that still doesn't make OSK happy. It wedges sometime after freeing init memory ... timer interrupts are no longer happening, the LED stops flashing. The userspace has sometimes started the watchdog daemon, in which case a watchdog timeout fires and it reboots. FWIW mainline fails *really* early, before showing any kernel messages at all. - Dave -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
On Tue, Aug 5, 2008 at 11:41 PM, Dirk Behme [EMAIL PROTECTED] wrote: Gadiyar, Anand wrote: Hi all, I've pushed all the patches I have in my omap inbox, except for the omap serial driver that I want to look more. I've tried to comment on the ones that did not get pushed, then erased everything from my omap inbox. Some drivers should get integrated via other mailing lists, and some debug patches can probably stay as debug patches, and some patches I probably have accidentally deleted :) And the PM patches I lost track of, so those should be reposted. So please check your patches, and repost your patches if something is left out. Also please check that things work for your board, let's try to tag v2.6.26-omap1 within next few days so we can move on again. Cheers, Tony Boot tested on 3430SDP with the defconfig. Things work okay so far. Same with BeagleBoard. Dirk -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Hi all, Boot tested on omap2evm with defconfig. The printks from omapfb(irq errors) is stalling the console sometimes, otherwise everything seems to be fine. Regards, Arun C -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
On an omap3evm with the defconfig, the kernel is failing to identify a jffs2 filesystem. It's booting from NFS just fine. I had built the latest code checked into linux-omap last week - file system booting had been working, IIRC. Loading TI reference 2.6.22 kernel finds the file system just fine as well. I'll begin looking into this next week if someone else doesn't beat me to it. Texas Instruments X-Loader 1.41 Detected Samsung MuxOneNAND1G Flash Starting OS Bootloader... U-Boot 1.1.4 (Jun 6 2008 - 18:25:31) OMAP3-GP rev 2, CPU-OPP2 L3-165MHz OMAP3EVM 1.0 Version + mPOP (Boot ONND) DRAM: 128 MB OneNAND Manufacturer: Samsung (0xec) Muxed OneNAND 128MB 1.8V 16-bit (0x30) OneNAND version = 0x0221 Scanning device for bad blocks num of blocks = 2048 In:serial Out: serial Err: serial Reseting CHIP... Done LAN9x18 (0x01150002) detected. Setting mac address: 00:50:c2:7e:86:9f start Auto negotiation... (take ~2sec) Auto negotiation complete, 100BaseTX, full duplex Hit any key to stop autoboot: 0 OMAP3EVM # run boot_fs Done ## Booting image at 8000 ... Image Name: Linux-2.6.26-omap1-04784-g040378 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:1515692 Bytes = 1.4 MB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK OK Starting kernel ... Uncompressing Linux. . done, booting the kernel. 5Linux version 2.6.26-omap1-04784-g040378c-dirty ([EMAIL PROTECTED]) (gcc v ersion 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #3 Tue Aug 5 14:45:54 E DT 2008 CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=00c5387f Machine: OMAP3 EVM Memory policy: ECC disabled, Data cache writeback 7On node 0 totalpages: 32768 7 DMA zone: 256 pages used for memmap 7 DMA zone: 0 pages reserved 7 DMA zone: 32512 pages, LIFO batch:7 7 Normal zone: 0 pages used for memmap 7 Movable zone: 0 pages used for memmap 6OMAP3430 ES2.2 6SRAM: Mapped pa 0x4020 to va 0xd700 size: 0x10 CPU0: D VIPT write-through cache CPU0: cache: 768 bytes, associativity 1, 8 byte lines, 64 sets Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 5Kernel command line: mem=128M console=ttyS0,115200n8 noinitrd root=/dev/mtdbl ock4 rw rootfstype=jffs2 ip=10.51.0.10:10.51.0.30:10.2.8.1:255.255.252.0:omap-ev m0:eth0:on 6Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz 6GPMC revision 5.0 6IRQ: Found an INTC at 0xd820 (revision 4.0) with 96 interrupts 6Total of 96 interrupts on 1 active controller 6OMAP34xx GPIO hardware version 2.5 PID hash table entries: 512 (order: 9, 2048 bytes) Console: colour dummy device 80x30 6Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) 6Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) 6Memory: 128MB = 128MB total 5Memory: 126720KB available (2776K code, 230K data, 116K init) 7Calibrating delay loop... 498.87 BogoMIPS (lpj=1945600) Mount-cache hash table entries: 512 6CPU: Testing write buffer coherency: ok 6net_namespace: 192 bytes 6NET: Registered protocol family 16 4Warning: L2 cache not enabled. Check your bootloader. L2 off results in perfo rmance loss 6OMAP DMA hardware revision 4.0 3USB: No board-specific platform config found 6i2c_omap i2c_omap.1: bus 1 rev3.12 at 2600 kHz 6i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz 6i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz 6TWL4030: TRY attach Slave TWL4030-ID0 on Adapter OMAP I2C adapter [1] 6TWL4030: TRY attach Slave TWL4030-ID1 on Adapter OMAP I2C adapter [1] 6TWL4030: TRY attach Slave TWL4030-ID2 on Adapter OMAP I2C adapter [1] 6TWL4030: TRY attach Slave TWL4030-ID3 on Adapter OMAP I2C adapter [1] 6Initialized TWL4030 USB module 5SCSI subsystem initialized 6NET: Registered protocol family 2 7Switched to high resolution mode on CPU 0 6IP route cache hash table entries: 1024 (order: 0, 4096 bytes) 6TCP established hash table entries: 4096 (order: 3, 32768 bytes) 6TCP bind hash table entries: 4096 (order: 2, 16384 bytes) 6TCP: Hash tables configured (established 4096 bind 4096) 6TCP reno registered 6NET: Registered protocol family 1 4NetWinder Floating Point Emulator V0.97 (double precision) 5VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) 6JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc. 6msgmni has been set to 247 6io scheduler noop registered 6io scheduler anticipatory registered (default) 6io scheduler deadline registered 6io scheduler cfq registered 6omapfb: configured for panel omap3evm 6omapfb: DISPC version 3.0 initialized 6omapfb: Framebuffer initialized. Total vram 614400 planes 1 6omapfb: Pixclock 24000 kHz hfreq 45.2 kHz vfreq 70.3 Hz 6Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled 6serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a
RE: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
Hi all, I've pushed all the patches I have in my omap inbox, except for the omap serial driver that I want to look more. I've tried to comment on the ones that did not get pushed, then erased everything from my omap inbox. Some drivers should get integrated via other mailing lists, and some debug patches can probably stay as debug patches, and some patches I probably have accidentally deleted :) And the PM patches I lost track of, so those should be reposted. So please check your patches, and repost your patches if something is left out. Also please check that things work for your board, let's try to tag v2.6.26-omap1 within next few days so we can move on again. Cheers, Tony Boot tested on 3430SDP with the defconfig. Things work okay so far. - Anand -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: About to tag v2.6.26-omap1, patch queue deleted, please check and repost
Gadiyar, Anand wrote: Hi all, I've pushed all the patches I have in my omap inbox, except for the omap serial driver that I want to look more. I've tried to comment on the ones that did not get pushed, then erased everything from my omap inbox. Some drivers should get integrated via other mailing lists, and some debug patches can probably stay as debug patches, and some patches I probably have accidentally deleted :) And the PM patches I lost track of, so those should be reposted. So please check your patches, and repost your patches if something is left out. Also please check that things work for your board, let's try to tag v2.6.26-omap1 within next few days so we can move on again. Cheers, Tony Boot tested on 3430SDP with the defconfig. Things work okay so far. Same with BeagleBoard. Dirk -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
