linux-kernel mailing list

FromSubjectsort iconDate
Yinghai Lu
[PATCH] x86_64: restore mask_bits in msi shutdown
I can not kexec RHEL 5.1 from 2.6.25-rc3 later caused by: commit 89d694b9dbe769ca1004e01db0ca43964806a611 Author: Thomas Gleixner <tglx@linutronix.de> Date: Mon Feb 18 18:25:17 2008 +0100 genirq: do not leave interupts enabled on free_irq The default_disable() function was changed in commit: 76d2160147f43f982dfe881404cfde9fd0a9da21 genirq: do not mask interrupts by default It removed the mask function in favour of the default delayed interrupt disabling....
Apr 11, 7:26 pm 2008
mark gross
[RFC] Patch to add private notification data to block notifi...
We where trying to get pm-qos to work with a wireless driver and found that the idiom of passing the *dev in the callback (notification) parameters was not supported. This makes having drivers as clients of PM-QOS sort of a challenge. The driver writer would have to mimic code in md.c where it keeps a list of all its instances and iterates over each upon notifier callback. Not that difficult but as the driver writers are so accustomed to having there instance data passed to them by the callers it...
Apr 11, 7:05 pm 2008
Yinghai Lu
[PATCH] x86_64: don't need set default res if only have one ...
only one root bus, don't need to split that root resources. Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com> diff --git a/arch/x86/pci/k8-bus_64.c b/arch/x86/pci/k8-bus_64.c index 7ed7f51..c433982 100644 --- a/arch/x86/pci/k8-bus_64.c +++ b/arch/x86/pci/k8-bus_64.c @@ -69,7 +69,8 @@ void set_pci_bus_resources_arch_default(struct pci_bus *b) int j; struct pci_root_info *info; - if (!pci_root_num) + /* if only one root bus, don't need to anything */ + if (pci_root_num < 2) ...
Apr 11, 6:14 pm 2008
Rafael J. Wysocki
Re: [PATCH] x86_64: don't need set default res if only have ...
This patch fixes the issue described at Thanks, Rafael --
Apr 11, 6:54 pm 2008
Miguel Ojeda
2.6.25-rc9: hda: task_no_data_intr: error=0x04
Hi! I'm getting the following messages at the very end of dmesg after booting in a new laptop (Dell Vostro 1500, bought about four months ago) in (all?) -rc releases: hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error } hda: task_no_data_intr: error=0x04 { AbortedCommand } ide: failed opcode was: 0xef The laptops works perfectly, so I'm not sure if there is a problem with the hard disk / controller, with the kernel or with nothing at all. Just in case, I'm reporting it. dm...
Apr 11, 5:45 pm 2008
Gary Shi
get a still sysrq-t call trace, not a moving one
Hi friends, when I read sysrq-t call trace, I find the collected call trace for some cases is not a still snapshot, but a moving one. After checking show_state src, I realize other cpus are not frozen when one cpu is doing show_state; thus some task switching can occur among those cpus, even the cpu doing sysrq for some kind of kernels. This moving call traces make debugging much more difficult, or even impossible for some cases, since some tasks have been switched in/out which make us lose the ...
Apr 11, 5:43 pm 2008
Matthew Wilcox
[PATCH] Replace completions with semaphores
A long long time ago when dinosaurs roamed the earth and tech company stock valuations were high (2001), the primitive of the completion was introduced to save us from a problem with semaphores. Those interested in the details can examine http://www.ussg.iu.edu/hypermail/linux/kernel/0107.3/0674.html and related messages, but everyone else can take my word for it that, with the generic semaphores I hope will be merged in 2.6.26, semaphores no longer have the problem that caused us to switch to com...
Apr 11, 5:00 pm 2008
Linus Torvalds
Linux 2.6.25-rc9
I really don't want to do this, and I was actually hoping to release 2.6.25 last weekend (which is why -rc9 is a few days late - just me hoping to not do another -rc at all), but I've done an -rc9. The changes in -rc9 are pretty small (shortlog appended), and 60% of them are m68k updates - mostly defconfigs. And some doc updates. But there's some network driver updates (tg3 and wireless hostap stand out), some late XFS patches and a mvsas driver update (the mvsas driver is new in 2.6.25, s...
Apr 11, 4:51 pm 2008
Bongani Hlope
Shutdown and Reboot Regression 2.6.25-rc[78]
Hi I found a regression in version 2.6.25-rc7, which causes my computer not to shutdown or reboot. I get a complete lock up (no keyboard and Sys-Rq) just before it normally shuts down the alsa service. I did a git bisect and it points to this reversion: [266c2e0abeca649fa6667a1a427ad1da507c6375] Make printk() console semaphore accesses sensible 00:00.0 Host bridge: VIA Technologies, Inc. VT8385 [K8T800 AGP] Host Bridge (rev 01) 00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI bridge...
Apr 11, 4:41 pm 2008
Alexey Dobriyan
Re: Shutdown and Reboot Regression 2.6.25-rc[78]
Is it 100% reproducable? I mean sometimes I also have complete lockup right after one of eth interfaces shutdown during shutdown sequence. And it's also recent. But it triggers ~1 time in 10 subjectively.. --
Apr 11, 5:42 pm 2008
Linus Torvalds
Re: Shutdown and Reboot Regression 2.6.25-rc[78]
Interesting. That commit _should_ have just moved code around with no actual semantic changes. Can you verify that undoing just that one commit makes current git (-rc9) work for you? Ie just try a git revert 266c2e0abeca649fa6667a1a427ad1da507c6375 on top of the current tree. I just want to check, because even after looking at that diff again, I'm not seeing what it could actually change. Linus --
Apr 11, 4:58 pm 2008
Bongani Hlope
Re: Shutdown and Reboot Regression 2.6.25-rc[78]
After about 4 restarts and 4 reboots, 2.6.25-rc9 seems to work fine with and without the revert. I'll do some more testing. The assembly output files for kernel/printk.c don't seem that different between rc9 and rc7. I'll see what else I can test. Thanx --
Apr 11, 5:42 pm 2008
Linus Torvalds
Re: Shutdown and Reboot Regression 2.6.25-rc[78]
Ok, I suspect it may be timing-dependent and slightly random. Sadly, that is absolutely the case where "git bisect" works the worst. The end result of bisection will basically be _totally_ random if even one of the "git bisect bad/good" choises were wrong - doing a binary search is a very efficient way to find the buggy commit, but it also means that a single wrong turn will efficiently find a commit that is somewhere totally different. So if your shutdown/reboot regression is even sli...
Apr 11, 7:12 pm 2008
Henrique de Moraes H...
[GIT PATCH] rfkill support for r/w and r/o rfkill switches
This patch series (based on v2.6.25-rc8-mm2) has several improvements to the rfkill class that I need for thinkpad-acpi, plus two fluff and documentation fixes. I'd appreciate comments, and if the patches are acceptable, that they are sent to mainline early during the 2.6.26 merge window. That way, I could try for a thinkpad-acpi rfkill submission for 2.6.26 as well. The thinkpad-acpi work that needs these patches is ready, and can be looked at on the thinkpad-acpi git tree (devel branch): ht...
Apr 11, 4:37 pm 2008
Henrique de Moraes H...
[PATCH 6/8] rfkill: add the WWAN radio type
Unfortunately, instead of adding a generic Wireless WAN type, a technology- specific type (WiMAX) was added. That's useless for other WWAN devices, such as EDGE, UMTS, X-RTT and other such radios. Add a WWAN rfkill type for generic wireless WAN devices. No keys are added as most devices use KEY_RADIO for WWAN control and need no specific keycode added. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com> Cc: Iñaky Pérez-González <inaky.perez-gonzalez@intel.com> Cc: Ivo va...
Apr 11, 4:37 pm 2008
Inaky Perez-Gonzalez
Re: [PATCH 6/8] rfkill: add the WWAN radio type
I know it is easier to complain than to submit code, but at this point, shouldn't we make this dynamic? [so that the interested technology that provides an rfkill switch registers it?]. Something that given a technology name registers a dynamic key and type number that can be use throughout? -- Inaky --
Apr 11, 4:44 pm 2008
Henrique de Moraes H...
Re: [PATCH 6/8] rfkill: add the WWAN radio type
I wouldn't have anything against that, but we do need to coalesce the types when possible, otherwise the "type" notion becomes useless for rfkill-input. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh --
Apr 11, 4:53 pm 2008
Henrique de Moraes H...
[PATCH 8/8] rfkill: add parameter to disable radios by default
Currently, radios are always enabled when their rfkill interface is registered. This is not optimal, the safest state for a radio is to be offline unless the user turns it on. Add a module parameter that causes all radios to be disabled when their rfkill interface is registered. Add override parameters for each rfkill switch type as well, just in case the user wants the defaults to be different for a given radio type. We don't change the module default, but I'd really recommed doing so in a fu...
Apr 11, 4:37 pm 2008
Henrique de Moraes H...
[PATCH 5/8] rfkill: add read-only rfkill switch support
Some devices (notably laptops) have read-only rfkill switches. Those devices are slider or rocker switches that are *physically* manipulated by the user, most of the time tied to hardware or firmware functions that automatically rf-kill and/or hot-unplug radio devices when in the "radios off" position. Software must not (and in fact, cannot) attempt to change the state of any such switch. These switches exist because of international regulations regarding radio emission devices on airplanes and o...
Apr 11, 4:37 pm 2008
Henrique de Moraes H...
[PATCH 7/8] rfkill: add an "any radio" switch type and funct...
Add a RFKILL_TYPE_ANY switch. This switch can control more than one type of radio, and it is always subject to toggling by any type of rfkill-input event. It is suitable to implement kill-all-radios functionality when coupled with input event EV_SW SW_RADIO. Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Cc: Ivo van Doorn <IvDoorn@gmail.com> Cc: John W. Linville <linville@tuxdriver.com> Cc: Dmitry Torokhov <dtor@mail.ru> --- include/linux/rfkill.h | 2...
Apr 11, 4:37 pm 2008
Henrique de Moraes H...
[PATCH 3/8] rfkill: handle KEY_RADIO and SW_RADIO events
The *_RADIO input events are related to all radios in a system. There are two: KEY_RADIO and SW_RADIO. Teach rfkill-input how to handle them. In particular, SW_RADIO is not a toggle, but an absolute enable-or-disable command. Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Cc: Ivo van Doorn <IvDoorn@gmail.com> Cc: John W. Linville <linville@tuxdriver.com> Cc: Dmitry Torokhov <dtor@mail.ru> --- net/rfkill/rfkill-input.c | 57 ++++++++++++++++++++++++++++++...
Apr 11, 4:37 pm 2008
Henrique de Moraes H...
[PATCH 2/8] rfkill: fix minor typo in kernel doc
Fix a minor typo in an exported function documentation Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Cc: Ivo van Doorn <IvDoorn@gmail.com> Cc: John W. Linville <linville@tuxdriver.com> Cc: Dmitry Torokhov <dtor@mail.ru> --- net/rfkill/rfkill.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/net/rfkill/rfkill.c b/net/rfkill/rfkill.c index 140a0a8..1601e50 100644 --- a/net/rfkill/rfkill.c +++ b/net/rfkill/rfkill.c @@ -412,7 +412,7...
Apr 11, 4:37 pm 2008
Henrique de Moraes H...
[PATCH 4/8] rfkill: add read-write rfkill switch support
Currently, rfkill supports only write-only rfkill switches. There is no provision for querying the current switch state from the hardware/firmware. This is bad on hardware where the switch state can change behind the kernel's back (which is rather common). There is no reason to keep kernel state incorrect, when we have the possibility to match reality. There is also the issue of read-only rfkill switches (support to be added in a later patch), which absolutely requires support to read the curren...
Apr 11, 4:37 pm 2008
Henrique de Moraes H...
[PATCH 1/8] rfkill: clarify meaning of rfkill states
rfkill really should have been named rfswitch. As it is, one can get confused whether RFKILL_STATE_ON means the KILL switch is on (and therefore, the radio is being *blocked* from operating), or whether it means the RADIO rf output is on. Clearly state that RFKILL_STATE_ON means the radio is *unblocked* from operating (i.e. there is no rf killing going on). Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Cc: Ivo van Doorn <IvDoorn@gmail.com> Cc: John W. Linville <linv...
Apr 11, 4:37 pm 2008
Jonathan Corbet
[PULL] Current documentation tree
I have a current version of the documentation tree at: git://git.lwn.net/linux-2.6.git docs There are a couple of code comment changes, but no changes to any code itself. It's safe to pull now (and it would be nice to get a couple of these changes in), but can also easily wait for the merge window to open. What's there: J. Bruce Fields (4): Spell out behavior of atomic_dec_and_lock() in kerneldoc Documentation: move nfsroot.txt to filesystems/ Documentation: move rpc-c...
Apr 11, 3:45 pm 2008
Miles Lane
2.6.25-rc8-mm2 -- initcall acpi_init+0x0/0x216() returned wi...
Is this indicative of a kernel or hardware problem? [ 0.279606] ACPI: Using IOAPIC for interrupt routing [ 0.279789] initcall acpi_init+0x0/0x216() returned with preemption imbalance [ 0.330789] ACPI: PCI Root Bridge [PCI0] (0000:00) Thanks, Miles --
Apr 11, 3:41 pm 2008
Jochen Friedrich
[PATCHv2 7/7] [POWERPC] Add i2c pins to dts and board setup
Initialize I2C pins on boards with CPM1/CPM2 controllers. Signed-off-by: Jochen Friedrich <jochen@scram.de> --- arch/powerpc/boot/dts/mpc8272ads.dts | 10 ++++++++++ arch/powerpc/boot/dts/mpc866ads.dts | 10 ++++++++++ arch/powerpc/boot/dts/mpc885ads.dts | 10 ++++++++++ arch/powerpc/platforms/82xx/mpc8272_ads.c | 4 ++++ arch/powerpc/platforms/8xx/mpc86xads_setup.c | 4 ++++ arch/powerpc/platforms/8xx/mpc885ads_setup.c | 3 +++ 6 files changed, ...
Apr 11, 3:26 pm 2008
Matthew Wilcox
[DOC PATCH] semaphore documentation
I've never programmed in C++ ... I just expect to find API documentation I see that as being "move the complexity around" and "get the interfaces Fine, I've done it the other way round. Please review this doc-patch. Without comments, I'll commit it to the semaphore git tree tomorrow. diff --git a/include/linux/semaphore.h b/include/linux/semaphore.h index a7125da..9cae64b 100644 --- a/include/linux/semaphore.h +++ b/include/linux/semaphore.h @@ -4,8 +4,7 @@ * * Distributed under th...
Apr 11, 3:21 pm 2008
Randy Dunlap
Re: [DOC PATCH] semaphore documentation
Looks good to me. Thanks. --- ~Randy --
Apr 11, 4:27 pm 2008
Jochen Friedrich
[PATCHv2 3/7] i2c: OF helpers for the i2c API
This patch implements various helpers to support OF bindings for the i2c API. Signed-off-by: Jochen Friedrich <jochen@scram.de> --- drivers/of/Kconfig | 6 +++ drivers/of/Makefile | 1 + drivers/of/i2c.c | 115 ++++++++++++++++++++++++++++++++++++++++++++++++ include/linux/of_i2c.h | 24 ++++++++++ 4 files changed, 146 insertions(+), 0 deletions(-) create mode 100644 drivers/of/i2c.c create mode 100644 include/linux/of_i2c.h diff --git a/drivers/of/Kconfig b/dri...
Apr 11, 3:22 pm 2008
David Miller
Re: [PATCHv2 3/7] i2c: OF helpers for the i2c API
From: Jochen Friedrich <jochen@scram.de> Acked-by: David S. Miller <davem@davemloft.net> --
Apr 11, 3:27 pm 2008
Phil Oester
PCI probe order changes after 2.6.22
In commit 08f1c192c3c32797068bfe97738babb3295bbf42 (x86-64: introduce struct pci_sysdata to facilitate sharing of ->sysdata), a change was made from using pcibios_scan_root to pci_scan_bus_parented. pcibios_scan_root applies some quirks to various systems via pciprobe_dmi_table, including a number of Dell PowerEdge servers. The similarly named acpi_pciprobe_dmi_table, however, does not apply the same set_bf_sort quirk, so between .22 and .23, the onboard Broadcom nics reversed their probe order. ...
Apr 11, 2:55 pm 2008
Marc Perkel
AMD Quad Core clock problem?
I was just wondering if there were any known issues with AMD quad core phenom clock drift problems? I';m running a 2.6.24 kernel and it's losing time. I remember the first dual core AMD chips had a lot of clock issues. If this is something new let me know what information to check and post to this list. Marc Perkel Junk Email Filter dot com http://www.junkemailfilter.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protec...
Apr 11, 2:27 pm 2008
Chris Snook
Re: AMD Quad Core clock problem?
When reporting clock problems, please post dmesg. This has all the interesting timekeeping-related log messages from the kernel. Please also describe the drift quantitatively. -- Chris --
Apr 11, 2:38 pm 2008
Marc Perkel
Re: AMD Quad Core clock problem?
OK - thanks Chris. The drift is small. It loses a few seconds every hour. And it might not be kernel related. I just remembered the early dual core days when this took months to get right. I'm running several dual core computers and the only one drifting is the quad. All are running the same OS and kernel. Initializing cgroup subsys cpuset Linux version 2.6.24-ovz004.1 (root@centos4-build.vzlin.sw.ru) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Tue Mar 25 16:23:06 MSK 2008 Comm...
Apr 11, 4:28 pm 2008
Chris Snook
Re: AMD Quad Core clock problem?
With the older chips, each core had its own TSC, which caused synchronization problems. The Barcelona generation chips (including your Phenom) have a constant frequency TSC on the northbridge, so they should be immune to these problems. If it's steadily losing a few seconds every hour, it's probably just slightly mis-calibrated hardware. ntp should fix this right up. If the drift is more extreme than ntp can correct for, or the drift keeps changing, or time is jumping around, that is def...
Apr 11, 5:11 pm 2008
Marc Perkel
Re: AMD Quad Core clock problem?
Is it possible due to calibration that ntpd isn't able to correct the problem? Is there a setting to make ntp more agressive? Marc Perkel Junk Email Filter dot com http://www.junkemailfilter.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --
Apr 11, 6:09 pm 2008
Marc Perkel
Re: AMD Quad Core clock problem?
No - it's not wild like it was back in the early X2 days and I think you're right about the drift being normal. Interesting thing though I am running ntpd and it's not working. I am fairly sure the ntp.conf file is exactly as it was installed by fedora. I'm now looking into that. Thanks for your help. Sorry for the false alarm. But if thee was an issue I thought you would want to know it. Marc Perkel Junk Email Filter dot com http://www.junkemailfilter.com _________________________...
Apr 11, 5:36 pm 2008
Krzysztof Halasa
Re: AMD Quad Core clock problem?
Few seconds an hour is hardly normal, thats 0.1%. The prime suspect is probably the motherboard and it's faulty clock generator (one of - HPET's?). What motherboard is it? -- Krzysztof Halasa --
Apr 11, 5:46 pm 2008
Lennart Sorensen
Re: AMD Quad Core clock problem?
I have found that ntp tends to fail to work on any machine with spread spectrum clocking enabled. On those machines disabling spread specturm in the BIOS seems to fix it. I had to update the BIOS on one machine to even get the option to disable it though. -- Len Sorensen --
Apr 11, 5:38 pm 2008
H. Willstrand Apr 11, 2:35 pm 2008
Davide Pesavento
linux-2.6.25-rc8-git7 - section mismatches on x86
While compiling linux-2.6.25-rc8-git7 with CONFIG_DEBUG_SECTION_MISMATCH=y, I noticed the following "section mismatch" warnings. Please CC me as I'm not subscribed to this list. WARNING: vmlinux.o(.text+0x10d58): Section mismatch in reference from the function cpu_exit_clear() to the function .cpuinit.text:cpu_uninit() The function cpu_exit_clear() references the function __cpuinit cpu_uninit(). This is often because cpu_exit_clear lacks a __cpuinit annotation or the annotation of cpu_uninit is ...
Apr 11, 2:02 pm 2008
Sam Ravnborg
Re: linux-2.6.25-rc8-git7 - section mismatches on x86
Thanks for your report Davide. We have several "Section mismatch warning" fixes queued up in -mm and in x86.git so I expect most of the ones below to be already fixed. Merging is postponed until next merge window. A similar report at -rc1 time would be good. Sam --
Apr 11, 2:25 pm 2008
David Brownell
[patch 2.6.25-rc8] leds: fix platform driver hotplug/coldplug
From: Kay Sievers <kay.sievers@vrfy.org> Since 43cc71eed1250755986da4c0f9898f9a635cb3bf, the platform modalias is prefixed with "platform:". Add MODULE_ALIAS() to the hotpluggable platform LED drivers, to re-enable auto loading. [ dbrownell@users.sourceforge.net: more drivers, registration fixes ] Signed-off-by: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> --- drivers/leds/leds-ams-delta.c | 2 ++ drivers/leds/leds-at...
Apr 11, 1:38 pm 2008
Adrian Bunk
[2.6 patch] make ali_atapi_dma static
This patch makes the needlessly global ali_atapi_dma static. Signed-off-by: Adrian Bunk <bunk@kernel.org> --- de012fdf57e025cf243181cb3fce87f890ccc955 diff --git a/drivers/ata/pata_ali.c b/drivers/ata/pata_ali.c index ce830fe..511a830 100644 --- a/drivers/ata/pata_ali.c +++ b/drivers/ata/pata_ali.c @@ -36,7 +36,7 @@ #define DRV_NAME "pata_ali" #define DRV_VERSION "0.7.5" -int ali_atapi_dma = 0; +static int ali_atapi_dma = 0; module_param_named(atapi_dma, ali_atapi_dma, int, 0644)...
Apr 11, 1:28 pm 2008
Alan Cox
Re: [2.6 patch] make ali_atapi_dma static
On Fri, 11 Apr 2008 20:28:27 +0300 Acked-by: Alan Cox <alan@redhat.com> --
Apr 11, 2:36 pm 2008
Dan Upton
CFS rq lock question
I'm poking around with some scheduler stuff, and there's something I'm not clear on for the CFS runqueue locks. The comments before __load_balance_iterator(...) in sched_fair.c suggests things can be dequeued even though the runqueue lock is held. Can things also be added to the queue while the lock is held? (Also, either way, what's the rationale that dequeueing is a safe procedure when somebody else holds a lock?) -dan --
Apr 11, 1:21 pm 2008
Peter Zijlstra
Re: CFS rq lock question
/* * Load-balancing iterator. Note: while the runqueue stays locked * during the whole iteration, the current task might be * dequeued so the iterator has to be dequeue-safe. Here we * achieve that by always pre-iterating before returning * the current task: */ I don't think this comment is correct, but if it were, it would only apply to rq->curr, not for any enqueue/dequeue. --
Apr 11, 1:37 pm 2008
Peter Zijlstra
Re: CFS rq lock question
D'oh, I'm silly.. the task can be dequeued because we move it to another cpu. --
Apr 11, 1:41 pm 2008
Erik Bosman
[PATCH 3/3] Add tests for prctl PR_GET_TSC and PR_SET_TSC
This patch adds three tests that test whether the PR_GET_TSC and PR_SET_TSC commands have the desirable effect. The tests check whether the control register is updated correctly at context switches and try to discover bugs while enabling/disabling the timestamp counter. Signed-off-by: Erik Bosman <ejbosman@cs.vu.nl> --- .../prctl/disable-tsc-ctxt-sw-stress-test.c | 96 ++++++++++++++++++++ .../prctl/disable-tsc-on-off-stress-test.c | 95 ++++++++++...
Apr 11, 12:57 pm 2008
previous daytodaynext day
April 10, 2008April 11, 2008April 12, 2008