Results 1 to 14 of 14
  1. #1
    Join Date
    Oct 2004
    Posts
    268

    Unanswered: DB2 TSA Takeover not working

    I do apologize for posting this here as I already post it to another group with no answer. Hoping some one here can help.

    DB2 V9.5 FP8 Linux 6.

    I have setup HADR with TSA and started to test the failover. Cluster failover is working as expected when I shutdown one of the servers but the automatic takeover is not working. I was expecting that when I shut down the primary server, the standby server would be issued a takeover command and I should be able to run "db2 connect to MYDB" command without the mesage of

    SQL1776N The command cannot be issued on an HADR standby database. Reason
    code = "1".

    I did not run the Automatic client reroute (ACR) or have an virtual IP for the application but I used a clustered fileserver virtual IP for tiebreak.

    I can not unplug the server to test it, I can only reboot which I have been doing. Do I need some kind of script tied to cluster to get the standby server takeover the cluster or it is automatically supposed to happen when the primary server goes down ?

    Appreciate any help.

    Thank you.

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by mdx34 View Post
    Cluster failover is working as expected when I shutdown one of the servers but the automatic takeover is not working.
    Not sure what that means - they look like contradictory statements to me. I suspect that if you do an orderly shutdown of an instance (db2stop) it's not considered a failure, so no failover is initiated. Try db2_kill instead.

    Have you seen this: http://public.dhe.ibm.com/software/d...dr_tsa_win.pdf ?

  3. #3
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Quote Originally Posted by mdx34 View Post
    I did not run the Automatic client reroute (ACR) or have an virtual IP for the application but I used a clustered fileserver virtual IP for tiebreak.
    You need either ACR, or a VIP used by the application to connect to the database (which TSA moves to the other server when takeover is executed). It sounds like TSA did effect HADR takeover when the primary server went down.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  4. #4
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    "I did not run the Automatic client reroute (ACR)"
    this is a setup only - no command to execute
    can you explain with more detail the scenario
    srv1=prim srv2-stdby
    shutdown srv1 and tsa should execute takeover on srv2 (use lssam or other to monitor)
    after shutdown where is prim/stdby ? use db2pd to check ..
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  5. #5
    Join Date
    Oct 2004
    Posts
    268
    Thank you for all your responses. db2_kill does not work on DB2 9 Workgroup edition (which I have) as stated here.

    IBM db2_kill is not available in DB2 Version 9 Workgroup Server Edition (WSE) - United States

    I have used the db2nkill but did not made any difference.

    Here is what I see after running "db2nkill 0).
    --------------------------------------------------------------------------
    root 2801 1 0 Apr18 ? 00:00:10 /opt/ibm/db2/V9.5/bin/db2fmcd
    db2inst1 7902 1 0 Apr18 ? 00:00:02 /opt/ibm/db2/V9.5/itma/lx8266/ud/bin/kuddb2 proddb01_db2inst1
    dasusr1 8470 1 0 Apr18 ? 00:00:10 /home/dasusr1/das/adm/db2dasrrm
    dasusr1 8828 1 0 Apr18 ? 00:00:00 /opt/ibm/db2/V9.5/das/bin/db2fmd -i dasusr1 -m /opt/ibm/db2/V9.5/das/lib/libdb2dasgcf.so.1
    root 22860 19639 0 08:58 pts/0 00:00:00 su - db2inst1
    db2inst1 22861 22860 0 08:58 pts/0 00:00:00 -bash
    db2inst1 24897 1 6 08:59 ? 00:00:19 [db2sysc] <defunct>
    db2inst1 24925 1 0 08:59 ? 00:00:00 /opt/ibm/db2/V9.5/bin/db2fmd -i db2inst1 -m /opt/ibm/db2/V9.5/lib64/libdb2gcf.so.1
    db2inst1 25814 1 0 08:59 ? 00:00:00 /home/db2inst1/sqllib/bin/db2dasstm 422
    db2inst1 26280 22861 0 09:04 pts/0 00:00:00 ps -ef
    db2inst1 26281 22861 0 09:04 pts/0 00:00:00 grep db2
    -------------------------------------------------------------------------
    What I am trying to accomplish is to be able to connect to standby database and continue working when the primary goes down.

    What I meant with cluster working as expected is the below output when I run lssam command on the standby server after rebooting the primary server which lssam command takes a while to return result.

    [08:39:58] db2inst1@proddb02 ~ $lssam
    Online IBM.ResourceGroup:db2_db2inst1_proddb01_0-rg Nominal=Online
    '- Online IBM.Application:db2_db2inst1_proddb01_0-rs
    '- Failed offline IBM.Application:db2_db2inst1_proddb01_0-rs:proddb01
    Online IBM.ResourceGroup:db2_db2inst1_proddb02_0-rg Nominal=Online
    '- Online IBM.Application:db2_db2inst1_proddb02_0-rs
    '- Online IBM.Application:db2_db2inst1_proddb02_0-rs:proddb02
    Online IBM.Equivalency:db2_db2inst1_proddb01_0-rg_group-equ
    '- Offline IBM.PeerNode:proddb01:proddb01
    Online IBM.Equivalency:db2_db2inst1_proddb02_0-rg_group-equ
    '- Online IBM.PeerNode:proddb02:proddb02
    Online IBM.Equivalency:db2_public_network_0
    |- Offline IBM.NetworkInterface:eth0:proddb01
    '- Online IBM.NetworkInterface:eth0:proddb02
    [08:39:58] db2inst1@proddb02 ~ $


    Thank you.
    Last edited by sathyaram_s; 04-19-12 at 11:36. Reason: disabled smilies.

  6. #6
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Sorry, It is not clear to me what you are trying to do ..

    Based on my understanding of your question -

    a) if you shut down the primary lpar/server, then TSA will initiate TAKEOVER

    b) if you kill the primary instance ,TSA is defined to start the instance. kill of instance is not considered a non-recoverable error for hadr. TSA starts the instance and when started, activates the db

    HTH
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  7. #7
    Join Date
    Oct 2004
    Posts
    268
    " a) if you shut down the primary lpar/server, then TSA will initiate TAKEOVER"

    It does not take over.

  8. #8
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    I saw your lssam output again..

    There is no HADR resource group. You only have the two instances defined in resource groups.

    db2haicu -delete

    and then reconfigure your HADR

    To 'hide' equivalences in the lssam output, you can use
    Code:
     lssam -noequ
    HTH
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  9. #9
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    BTW, you can use the sample file sqllib/samples/ha/xml/db2ha_sample_HADR.xml to create a config file of your own.

    db2haicu -f <xml filename>

    Makes your config easier and repeatable
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  10. #10
    Join Date
    Oct 2004
    Posts
    268
    Quote Originally Posted by sathyaram_s View Post
    I saw your lssam output again..

    There is no HADR resource group. You only have the two instances defined in resource groups.

    db2haicu -delete

    and then reconfigure your HADR

    To 'hide' equivalences in the lssam output, you can use
    Code:
     lssam -noequ
    HTH

    Thank you.

    I have deleted and tried to recreate it but I am getting error at the last step.

    Adding HADR database TMSPROD1 to the domain ...
    Creating resource failed. Refer to db2diag.log and the DB2 Information Center for details.

    and the db2diag.log has

    proddb02
    DATA #2 : String, 10 bytes
    proddb01
    DATA #3 : String, 10 bytes
    proddb02

    2012-04-19-12.46.40.215164-240 E6827E545 LEVEL: Error
    PID : 14260 TID : 140367737964288PROC : db2haicu
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, sqlhaUICreateHADR, probe:210
    RETCODE : ECF=0x90000531=-1879046863=ECF_SQLHA_INVALID_PARAM
    Invalid parameter to SQLHA call
    DATA #1 : String, 8 bytes
    db2inst1
    DATA #2 : String, 8 bytes
    db2inst1
    DATA #3 : String, 10 bytes
    proddb02
    DATA #4 : String, 10 bytes
    proddb01
    DATA #5 : String, 5 bytes
    CIBP1

    2012-04-19-12.46.40.216270-240 E7373E370 LEVEL: Error
    PID : 14260 TID : 140367737964288PROC : db2haicu
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, sqlhaUIConfigureHADR, probe:600
    RETCODE : ECF=0x90000531=-1879046863=ECF_SQLHA_INVALID_PARAM
    Invalid parameter to SQLHA call

    2012-04-19-12.46.40.216343-240 E7744E373 LEVEL: Error
    PID : 14260 TID : 140367737964288PROC : db2haicu
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, sqlhaUINewInstanceSetup, probe:700
    RETCODE : ECF=0x90000531=-1879046863=ECF_SQLHA_INVALID_PARAM
    Invalid parameter to SQLHA call

    2012-04-19-12.46.40.216382-240 E8118E362 LEVEL: Error
    PID : 14260 TID : 140367737964288PROC : db2haicu
    INSTANCE: db2inst1 NODE : 000
    FUNCTION: DB2 Common, SQLHA APIs for DB2 HA Infrastructure, sqlhaUIMain, probe:1800
    RETCODE : ECF=0x90000531=-1879046863=ECF_SQLHA_INVALID_PARAM
    Invalid parameter to SQLHA call

    ------------------------------------------

    Any ideas...........Thank you.

  11. #11
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Did you run the db2haicu command on the primary or standby?

    You must first do it on the standby and then on the primary.

    Dont know if the above error is related, but just wanted to check
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  12. #12
    Join Date
    Oct 2004
    Posts
    268
    Quote Originally Posted by sathyaram_s View Post
    Did you run the db2haicu command on the primary or standby?

    You must first do it on the standby and then on the primary.

    Dont know if the above error is related, but just wanted to check

    Thank you.............I have recreated and found out that the problem was
    a case sensitivity issue but I am not still getting what I want which is to be able connect to the standby server after the primary goes down. I shutdown the primary server and keep it shut. I go back to standby server and issue a command of "db2 connect to my database" and get

    HADR error SQL1768N Unable to start HADR Reason code = "7"

    or

    SQL1776N The command cannot be issued on an HADR standby database. Reason
    code = "1".

    Currently primary server is down and "lssam -noequ" gives me below output (I have 2 HADR databases. Is it not allowed ?)

    [16:43:52] db2inst1@proddb02 ~ $lssam -noequ
    Offline IBM.ResourceGroup:db2_db2inst1_db2inst1_PRODASP2-rg Request=Lock Control=StartInhibitedBecauseSuspended Nominal=Online
    '- Offline IBM.Application:db2_db2inst1_db2inst1_PRODASP2-rs Control=StartInhibitedBecauseSuspended
    |- Failed offline IBM.Application:db2_db2inst1_db2inst1_PRODASP2-rs:proddb01 Node=Offline
    '- Offline IBM.Application:db2_db2inst1_db2inst1_PRODASP2-rs:proddb02
    Offline IBM.ResourceGroup:db2_db2inst1_db2inst1_PRODASP1-rg Request=Lock Control=StartInhibitedBecauseSuspended Nominal=Online
    '- Offline IBM.Application:db2_db2inst1_db2inst1_PRODASP1-rs Control=StartInhibitedBecauseSuspended
    |- Failed offline IBM.Application:db2_db2inst1_db2inst1_PRODASP1-rs:proddb01 Node=Offline
    '- Offline IBM.Application:db2_db2inst1_db2inst1_PRODASP1-rs:proddb02
    Failed offline IBM.ResourceGroup:db2_db2inst1_proddb01_0-rg Nominal=Online
    '- Failed offline IBM.Application:db2_db2inst1_proddb01_0-rs
    '- Failed offline IBM.Application:db2_db2inst1_proddb01_0-rs:proddb01 Node=Offline
    Online IBM.ResourceGroup:db2_db2inst1_proddb02_0-rg Nominal=Online
    '- Online IBM.Application:db2_db2inst1_proddb02_0-rs
    '- Online IBM.Application:db2_db2inst1_proddb02_0-rs:proddb02
    [16:43:52] db2inst1@proddb02 ~ $
    Last edited by sathyaram_s; 04-20-12 at 06:30. Reason: disable smilies

  13. #13
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Have you checked db2diag.log for db2 related error messages on why the takeover did not occur ?

    Have you checked /var/log/messages - this will show the TSA related messages


    ===
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  14. #14
    Join Date
    Oct 2004
    Posts
    268
    Quote Originally Posted by sathyaram_s View Post
    Have you checked db2diag.log for db2 related error messages on why the takeover did not occur ?

    Have you checked /var/log/messages - this will show the TSA related messages


    ===
    At this point I am giving up on it. It looks like it has cluster issues. I have been using a VIP that belong to a cluster with 2 file server in it. Thank for all your help anyway. Below some errors from messages file.

    Apr 19 15:05:33 proddb02 snmpd[4540]: Connection from UDP: [198.23.23.71]:1049->[198.40.11.24]
    Apr 19 15:05:43 proddb02 db2V95_stop.ksh[60123]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh, db2inst1, 0
    Apr 19 15:05:51 proddb02 db2V95_stop.ksh[60805]: Returning 0 from /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh ( db2inst1, 0 )
    Apr 19 15:05:52 proddb02 db2V95_start.ksh[60822]: /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0: Partition started but cannot verify. Failing start: 0
    Apr 19 15:05:52 proddb02 db2V95_start.ksh[60823]: Returning 1 from /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh ( db2inst1, 0)
    Apr 19 15:05:52 proddb02 db2V95_start.ksh[60841]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0
    Apr 19 15:06:02 proddb02 db2V95_stop.ksh[61583]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh, db2inst1, 0
    Apr 19 15:06:10 proddb02 db2V95_stop.ksh[62263]: Returning 0 from /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh ( db2inst1, 0 )
    Apr 19 15:06:11 proddb02 db2V95_start.ksh[62280]: /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0: Partition started but cannot verify. Failing start: 0
    Apr 19 15:06:11 proddb02 db2V95_start.ksh[62281]: Returning 1 from /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh ( db2inst1, 0)
    Apr 19 15:06:11 proddb02 db2V95_start.ksh[62299]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0
    Apr 19 15:06:21 proddb02 db2V95_stop.ksh[63034]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh, db2inst1, 0
    Apr 19 15:06:29 proddb02 db2V95_stop.ksh[63718]: Returning 0 from /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh ( db2inst1, 0 )
    Apr 19 15:06:30 proddb02 db2V95_start.ksh[63739]: /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0: Partition started but cannot verify. Failing start: 0
    Apr 19 15:06:30 proddb02 db2V95_start.ksh[63740]: Returning 1 from /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh ( db2inst1, 0)
    Apr 19 15:06:30 proddb02 db2V95_start.ksh[63758]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0
    Apr 19 15:06:38 proddb02 snmpd[4540]: Connection from UDP: [198.23.23.71]:1099->[198.40.11.24]
    Apr 19 15:06:41 proddb02 db2V95_stop.ksh[64493]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh, db2inst1, 0
    Apr 19 15:06:49 proddb02 db2V95_stop.ksh[65177]: Returning 0 from /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh ( db2inst1, 0 )
    Apr 19 15:06:51 proddb02 db2V95_start.ksh[65207]: /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0: Partition started but cannot verify. Failing start: 0
    Apr 19 15:06:51 proddb02 db2V95_start.ksh[65208]: Returning 1 from /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh ( db2inst1, 0)
    Apr 19 15:06:51 proddb02 db2V95_start.ksh[65226]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_start.ksh, db2inst1, 0
    Apr 19 15:07:01 proddb02 snmpd[4540]: Connection from UDP: [198.23.23.71]:1099->[198.40.11.24]
    Apr 19 15:07:01 proddb02 db2V95_stop.ksh[65964]: Entered /usr/sbin/rsct/sapolicies/db2/db2V95_stop.ksh, db2inst1, 0

    Apr 19 15:25:44 proddb02 /usr/sbin/rsct/sapolicies/db2/hadrV95_monitor.ksh[24325]: Returning 2 : db2inst1 db2inst1 UPD
    Apr 19 15:26:02 proddb02 cthags[10796]: (Recorded using libct_ffdc.a cv 2):::Error ID: 825....8P4YD/ZcV1gGV8K....................:::Reference ID: :::Template ID: 0::etails File: :::Location: RSCT,SRCSocket.C,1.78,482 :::GS_STOP_ST#012Group Services daemon stopped#012DIAGNOSTIC EXPLANATION#012Received signal[SIGTERM]. Converted to normal stop
    Apr 19 15:26:02 proddb02 RMCdaemon[10851]: (Recorded using libct_ffdc.a cv 2):::Error ID: 824....8P4YD/4fV1gGV8K....................:::Reference ID: :::Template ID: 0::etails File: :::Location: RSCT,rmcd.c,1.75.1.2,874 :::RMCD_INFO_1_ST#012The daemon is stopped.#012Number of command that stopped the daemon#0123
    Apr 19 15:26:02 proddb02 ConfigRM[7296]: (Recorded using libct_ffdc.a cv 2):::Error ID: :::Reference ID: :::Template ID: 0::etails File: :::Location: RSCT,ConfigRMDaemon.C,1.16,204 :::CONFIGRM_STOPPED_ST#012IBM.ConfigRM daemon has been stopped.
    Apr 19 15:26:02 proddb02 ctcasd[7916]: (Recorded using libct_ffdc.a cv 2):::Error ID: 824....8P4YD/4gV1gGV8K....................:::Reference ID: :::Template ID: cffb2385::etails File: :::Location: rsct.core.sec,ctcas_main.c,1.30,399 :::ctcasd Daemon Stopped
    Apr 19 1Apr 19 15:28:04 proddb02 kernel: imklog 4.6.2, log source = /proc/kmsg started.
    Apr 19 15:28:04 proddb02 rsyslogd: [origin software="rsyslogd" swVersion="4.6.2" x-pid="2920" x-info="http://www.rsyslog.com"] (re)start
    Apr 19 15:28:04 proddb02 rsyslogd-3000: unknown priority name "" [try http://www.rsyslog.com/e/3000 ]
    Apr 19 15:28:04 proddb02 rsyslogd: the last error occured in /etc/rsyslog.conf, line 9:"logger command)"
    Apr 19 15:28:04 proddb02 rsyslogd: warning: selector line without actions will be discarded
    Apr 19 15:28:04 proddb02 rsyslogd-3000: unknown priority name "" [try http://www.rsyslog.com/e/3000 ]
    Apr 19 15:28:04 proddb02 rsyslogd: the last error occured in /etc/rsyslog.conf, line 11:"rklogd)"
    Apr 19 15:28:04 proddb02 rsyslogd: warning: selector line without actions will be discarded
    Apr 19 15:28:04 proddb02 rsyslogd-2124: CONFIG ERROR: could not interpret master config file '/etc/rsyslog.conf'. [try http://www.rsyslog.com/e/2124 ]
    Apr 19 15:28:04 proddb02 kernel: Initializing cgroup subsys cpuset
    Apr 19 15:28:04 proddb02 kernel: Initializing cgroup subsys cpu
    Apr 19 15:28:04 proddb02 kernel: Linux version 2.6.32-220.el6.x86_64 (mockbuild@x86-004.build.bos.redhat.com) (gcc version 4.4.5 20110214 (Red Hat 4.4.5-6) (GCC) ) #1 SMP Wed Nov 9 08:03:13 EST 2011
    Apr 19 15:28:04 proddb02 kernel: Command line: ro root=/dev/mapper/VolGroup00-LV_ROOT rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 rd_NO_MD quiet rd_LVM_LV=VolGroup00/LV_ROOT SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto rhgb crashkernel=auto quiet rd_LVM_LV=VolGroup00/LV_SWAP rd_NO_DM
    Apr 19 15:28:04 proddb02 kernel: KERNEL supported cpus:
    Apr 19 15:28:04 proddb02 kernel: Intel GenuineIntel
    Apr 19 15:28:04 proddb02 kernel: AMD AuthenticAMD
    Apr 19 15:28:04 proddb02 kernel: Centaur CentaurHauls
    Apr 19 15:28:04 proddb02 kernel: BIOS-provided physical RAM map:
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 0000000000000000 - 000000000009b000 (usable)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000000009b000 - 00000000000a0000 (reserved)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 0000000000100000 - 000000007b447000 (usable)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007b447000 - 000000007b44a000 (reserved)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007b44a000 - 000000007b699000 (ACPI NVS)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007b699000 - 000000007b7bd000 (reserved)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007b7bd000 - 000000007ba3d000 (ACPI NVS)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007ba3d000 - 000000007baa8000 (reserved)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007baa8000 - 000000007bd00000 (ACPI data)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007bd00000 - 000000007bd18000 (reserved)
    Apr 19 15:28:04 proddb02 kernel: BIOS-e820: 000000007bd18000 - 000000007bd1b000 (ACPI data)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •